From Mark.Olesen at esi-group.com  Fri Dec  1 02:34:58 2017
From: Mark.Olesen at esi-group.com (Mark Olesen)
Date: Fri, 1 Dec 2017 08:34:58 +0100
Subject: [Paraview] Writing XML VTK Binary files from C++
In-Reply-To: <MWHPR06MB327729D24C03776C438AEA1680380@MWHPR06MB3277.namprd06.prod.outlook.com>
References: <MWHPR06MB32771608E8AE41C08A01CB9B80380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <MWHPR06MB327729D24C03776C438AEA1680380@MWHPR06MB3277.namprd06.prod.outlook.com>
Message-ID: <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>

When you say "writing binary", you need to distinguish between three 
possibilities.
1) writing binary "inline" (actually base64 encoded)
2) writing binary "append" (actually base64 encoded)
3) writing raw binary "append" (really raw binary)

Since you already have ASCII writing working and its content is 
"inline", it won't take much more to get binary inline working.
By "inline", I mean when the output is placed between the <xxx> </xxx> 
markers. Eg,
     <DataArray ...>
         content
     </DataArray>

For the binary case, the content is written as base64-encoded data, 
which means that your output writer for these sections needs to pass the 
content through a base64 layer to do the encoding for you.

If it helps as reference, we have the same thing in OpenFOAM, except 
that we only write vtu and vtp files (we don't have rectilinear meshes).

In the repo https://develop.openfoam.com/Development/OpenFOAM-plus
we have a foamVtkBase64Formatter and a foamVtkBase64Layer (both under 
src/fileFormats/vtk/format/) that add a base64Layer to encode and output 
as base64 (src/OpenFOAM/db/IOstreams/hashes/base64Layer.[CH]).

You'll see that the foamVtkBase64Layer and base64Layer are quite low 
level means of adding an tiny encoding buffer (3 chars size) to 
intercept output prior to sending through to a std::ostream. It take 
very little effort to adopt for your output and thus quite easy to drop 
in instead of your current ASCII outputter.  For it too work easily, 
however, you should make sure that you need to generate your output 
content with a write() method instead of using '<<'. This allows 
somewhat easy switching between something like a foamVtkAsciiFormatter 
and the binary version, but more importantly it makes it easier to track 
the output state.

When browsing through the code, you may also notice that we have support 
for writing in appended format (raw and base64). However, I would not 
advise you to tackle that immediately. There are a few more things to 
watch out for here, but more importantly it will change many more things 
on the calling side.

I hope this information helps you.
/mark

-- 
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com


On 11/30/17 18:00, Stegmeier, Nicholas wrote:
> Hello,
>
> I am new to Paraview and C++ coming from a mostly mathematics 
> background. I am emailing to get resources or help on writing binary XML 
> VTK files from C++.
>
> I have finally succeeded in using the ASCII XML VTK format for a 2D 
> rectilinear CFD application. My ".pvtr" file is shown below.
>
> How can I write this file and my other XML VTK files in binary from C++? 
> Do I need a special C++ library?

From wilhelm at ycoorsystems.com  Fri Dec  1 04:08:08 2017
From: wilhelm at ycoorsystems.com (Lionel Wilhelm)
Date: Fri, 01 Dec 2017 10:08:08 +0100
Subject: [Paraview] Integrate variable filter
Message-ID: <WC20171201090808.540018@ycoorsystems.com>

Dear Paraviewers,

I'm trying to compute a closed volume in paraview. For that purpose, I define a constant field with value 1 on the domain and use the integrate filter. Unfortunately the result does not seem to be correct.

Attached a screenshot of the GUI where I try to compute the volume of a cube which volume is  0.075^3.

I guess that floating point operations error might result in this error but I'm unsure. Furthermore could you tell me if there is a mean for computing such small volumes enclosed in complex surfaces?

Kindly,

Lionel Wilhelm



From antech777 at gmail.com  Fri Dec  1 05:02:43 2017
From: antech777 at gmail.com (Andrew)
Date: Fri, 1 Dec 2017 13:02:43 +0300
Subject: [Paraview] Integrate variable filter
In-Reply-To: <WC20171201090808.540018@ycoorsystems.com>
References: <WC20171201090808.540018@ycoorsystems.com>
Message-ID: <CANMVBVzw_D7YYUnLgS2trmF+OTMr77Z+2fAmhpycRQVBuu3g+Q@mail.gmail.com>

Hello.
For calculationg volumes and areas, the "Cell Data" attribute type of
Integrate variables filter is usable. You don't need to define additional
constant field for this. I checked it now and it seems to give the correct
domain volume (554 m3 in SolidWorks, 557 m3 in ParaView). The error may be
due to unequality of mesh and "ideal" geometry. You can also use the
Threshold filter before the Intergate variables to define the custom volume
(with particular scalar values).

2017-12-01 12:08 GMT+03:00 Lionel Wilhelm <wilhelm at ycoorsystems.com>:

> Dear Paraviewers,
>
> I'm trying to compute a closed volume in paraview. For that purpose, I
> define a constant field with value 1 on the domain and use the integrate
> filter. Unfortunately the result does not seem to be correct.
>
> Attached a screenshot of the GUI where I try to compute the volume of a
> cube which volume is  0.075^3.
>
> I guess that floating point operations error might result in this error
> but I'm unsure. Furthermore could you tell me if there is a mean for
> computing such small volumes enclosed in complex surfaces?
>
> Kindly,
>
> Lionel Wilhelm
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/5433ac85/attachment.html>

From andy.bauer at kitware.com  Fri Dec  1 07:39:13 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 1 Dec 2017 07:39:13 -0500
Subject: [Paraview] Integrate variable filter
In-Reply-To: <CANMVBVzw_D7YYUnLgS2trmF+OTMr77Z+2fAmhpycRQVBuu3g+Q@mail.gmail.com>
References: <WC20171201090808.540018@ycoorsystems.com>
 <CANMVBVzw_D7YYUnLgS2trmF+OTMr77Z+2fAmhpycRQVBuu3g+Q@mail.gmail.com>
Message-ID: <CAMaOp+Ho9ONvmUesnL-MTFFAdQAoE5UKCPosHo+eOPkuzSHUNw@mail.gmail.com>

You may also want to look at the Cell Size filter which has the advanced
option to globally sum the values.

The Integrate Variable filter can give unexpected results with mixed
dimension elements since it will integrate all 0D, 1D, 2D and 3D cells.

On Fri, Dec 1, 2017 at 5:02 AM, Andrew <antech777 at gmail.com> wrote:

> Hello.
> For calculationg volumes and areas, the "Cell Data" attribute type of
> Integrate variables filter is usable. You don't need to define additional
> constant field for this. I checked it now and it seems to give the correct
> domain volume (554 m3 in SolidWorks, 557 m3 in ParaView). The error may be
> due to unequality of mesh and "ideal" geometry. You can also use the
> Threshold filter before the Intergate variables to define the custom volume
> (with particular scalar values).
>
> 2017-12-01 12:08 GMT+03:00 Lionel Wilhelm <wilhelm at ycoorsystems.com>:
>
>> Dear Paraviewers,
>>
>> I'm trying to compute a closed volume in paraview. For that purpose, I
>> define a constant field with value 1 on the domain and use the integrate
>> filter. Unfortunately the result does not seem to be correct.
>>
>> Attached a screenshot of the GUI where I try to compute the volume of a
>> cube which volume is  0.075^3.
>>
>> I guess that floating point operations error might result in this error
>> but I'm unsure. Furthermore could you tell me if there is a mean for
>> computing such small volumes enclosed in complex surfaces?
>>
>> Kindly,
>>
>> Lionel Wilhelm
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/89bc18fd/attachment.html>

From dave.demarle at kitware.com  Fri Dec  1 09:35:45 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 1 Dec 2017 09:35:45 -0500
Subject: [Paraview] Writing XML VTK Binary files from C++
In-Reply-To: <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>
References: <MWHPR06MB32771608E8AE41C08A01CB9B80380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <MWHPR06MB327729D24C03776C438AEA1680380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>
Message-ID: <CANjZAi9UxVtksW19mJFVD4Y=G8pJH3Z05o5NFuhdupKbdu_qkA@mail.gmail.com>

Another approach is to use VTK itself to write the files.

Since VTK 6 it is straightforward to configure a VTK build consisting
of only the IO/ParallelXML module and its required dependencies. To do
so, in cmake, turn of testing, all groups and turn on
Module_vtkIOParallelXML, and you should be set.

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


On Fri, Dec 1, 2017 at 2:34 AM, Mark Olesen <Mark.Olesen at esi-group.com> wrote:
> When you say "writing binary", you need to distinguish between three
> possibilities.
> 1) writing binary "inline" (actually base64 encoded)
> 2) writing binary "append" (actually base64 encoded)
> 3) writing raw binary "append" (really raw binary)
>
> Since you already have ASCII writing working and its content is "inline", it
> won't take much more to get binary inline working.
> By "inline", I mean when the output is placed between the <xxx> </xxx>
> markers. Eg,
>     <DataArray ...>
>         content
>     </DataArray>
>
> For the binary case, the content is written as base64-encoded data, which
> means that your output writer for these sections needs to pass the content
> through a base64 layer to do the encoding for you.
>
> If it helps as reference, we have the same thing in OpenFOAM, except that we
> only write vtu and vtp files (we don't have rectilinear meshes).
>
> In the repo https://develop.openfoam.com/Development/OpenFOAM-plus
> we have a foamVtkBase64Formatter and a foamVtkBase64Layer (both under
> src/fileFormats/vtk/format/) that add a base64Layer to encode and output as
> base64 (src/OpenFOAM/db/IOstreams/hashes/base64Layer.[CH]).
>
> You'll see that the foamVtkBase64Layer and base64Layer are quite low level
> means of adding an tiny encoding buffer (3 chars size) to intercept output
> prior to sending through to a std::ostream. It take very little effort to
> adopt for your output and thus quite easy to drop in instead of your current
> ASCII outputter.  For it too work easily, however, you should make sure that
> you need to generate your output content with a write() method instead of
> using '<<'. This allows somewhat easy switching between something like a
> foamVtkAsciiFormatter and the binary version, but more importantly it makes
> it easier to track the output state.
>
> When browsing through the code, you may also notice that we have support for
> writing in appended format (raw and base64). However, I would not advise you
> to tackle that immediately. There are a few more things to watch out for
> here, but more importantly it will change many more things on the calling
> side.
>
> I hope this information helps you.
> /mark
>
> --
> Dr Mark OLESEN
> Principal Engineer, ESI-OpenCFD
> ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
> www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com
>
>
> On 11/30/17 18:00, Stegmeier, Nicholas wrote:
>>
>> Hello,
>>
>> I am new to Paraview and C++ coming from a mostly mathematics background.
>> I am emailing to get resources or help on writing binary XML VTK files from
>> C++.
>>
>> I have finally succeeded in using the ASCII XML VTK format for a 2D
>> rectilinear CFD application. My ".pvtr" file is shown below.
>>
>> How can I write this file and my other XML VTK files in binary from C++?
>> Do I need a special C++ library?
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

From paolini at engineering.sdsu.edu  Fri Dec  1 11:27:39 2017
From: paolini at engineering.sdsu.edu (Christopher Paolini)
Date: Fri, 01 Dec 2017 08:27:39 -0800
Subject: [Paraview] undefined references to EGL library functions when using
	NVIDIA's libEGL_nvidia.so.384.90
Message-ID: <6701.1512145659@engineering.sdsu.edu>

Greetings,

I'm trying to build pvserver with GPU headless rendering capability and
am getting undefined references to EGL library functions when using
NVIDIA's libEGL_nvidia.so.384.90 library.  My cmake build specification
is:

cmake ../paraview \
-DVTK_USE_EGL=ON \
-DVTK_OPENGL_HAS_EGL=ON \
-DEGL_INCLUDE_DIR=/usr/include/nvidia-384 \
-DEGL_opengl_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libOpenGL.so.0 \
-DEGL_gldispatch_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libGLdispatch.so.0 \
-DEGL_LIBRARY:FILEPATH=/usr/local/nvidia/lib64/libEGL_nvidia.so.384.90 \
-DOPENGL_INCLUDE_DIR=:FILEPATH=/usr/include/nvidia-384 \
-DVTK_USE_X=OFF \
-DVTK_OPENGL_HAS_OSMESA=OFF \
-DPARAVIEW_BUILD_QT_GUI=OFF \
-DBUILD_SHARED_LIBS=ON -DPARAVIEW_USE_MPI=ON

libvtkRenderingOpenGL2-pv5.4.so.1 is reporting undefined references to
the egl* functions:

[100%] Building CXX object CommandLineExecutables/CMakeFiles/pvserver.dir/pvserver.cxx.o
[100%] Linking CXX executable ../bin/pvserver
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglTerminate'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateWindowSurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQueryString'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetProcAddress'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetError'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreatePbufferSurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroySurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglBindAPI'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglInitialize'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQuerySurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglChooseConfig'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglSwapBuffers'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateContext'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentDisplay'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetDisplay'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglMakeCurrent'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroyContext'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentSurface'
collect2: error: ld returned 1 exit status
CommandLineExecutables/CMakeFiles/pvserver.dir/build.make:124: recipe for target 'bin/pvserver' failed

Manually linking while specifying libEGL_nvidia.so.384.90 and
libEGL.so.1 does not resolve these references either:

/usr/bin/c++   -I/usr/include/nvidia-384  -g    CMakeFiles/pvserver.dir/pvserver.cxx.o  -o ../bin/pvserver -rd
ynamic /usr/lib/nvidia-384/libEGL.so.1  ../lib/libvtkPVServerManagerApplication-pv5.4.so.1 ../lib/libvtkPVServ
erManagerCore-pv5.4.so.1 ../lib/libvtkPVServerImplementationCore-pv5.4.so.1 ../lib/libvtkPVClientServerCoreCor
e-pv5.4.so.1 ../lib/libvtkFiltersParallel-pv5.4.so.1 ../lib/libvtkFiltersExtraction-pv5.4.so.1 ../lib/libvtkFi
ltersModeling-pv5.4.so.1 ../lib/libvtkFiltersGeometry-pv5.4.so.1 ../lib/libvtkPVVTKExtensionsCore-pv5.4.so.1 .
./lib/libvtkPVCommon-pv5.4.so.1 ../lib/libvtkClientServer-pv5.4.so.1 ../lib/libvtkIOXMLParser-pv5.4.so.1 ../li
b/libvtkFiltersSources-pv5.4.so.1 ../lib/libvtkFiltersGeneral-pv5.4.so.1 ../lib/libvtkFiltersCore-pv5.4.so.1 .
./lib/libvtkIOImage-pv5.4.so.1 ../lib/libvtkPVVTKExtensionsSIL-pv5.4.so.1 ../lib/libvtkParallelMPI-pv5.4.so.1
../lib/libvtkParallelCore-pv5.4.so.1 ../lib/libvtkIOLegacy-pv5.4.so.1 ../lib/libvtkIOCore-pv5.4.so.1 ../lib/li
bvtkCommonExecutionModel-pv5.4.so.1 ../lib/libvtkCommonDataModel-pv5.4.so.1 ../lib/libvtkCommonSystem-pv5.4.so
.1 ../lib/libvtkCommonTransforms-pv5.4.so.1 ../lib/libvtkCommonMisc-pv5.4.so.1 ../lib/libvtkCommonMath-pv5.4.s
o.1 ../lib/libvtkCommonCore-pv5.4.so.1 ../lib/libprotobuf.so -lpthread ../lib/libvtkjsoncpp-pv5.4.so.1 -Wl,-rp
ath,/opt/subflow/paraview/paraview_build/lib: -Wl,-rpath-link,/opt/subflow/paraview/paraview_build/lib^Cusr/li
b/nvidia-384/libEGL_nvidia.so.384.90 /usr/lib/nvidia-384/libEGL.so.384.90 /usr/lib/nvidia-384/libEGL.so.1 -Wl,
-rpath-link,/usr/lib/nvidia-384 /usr/lib/nvidia-384/libEGL.so /usr/lib/nvidia-384/libGL.so /usr/lib/nvidia-384
/libGLESv1_CM.so /usr/lib/nvidia-384/libGLESv2.so /usr/lib/nvidia-384/libGLX.so /usr/lib/nvidia-384/libOpenGL.
so /usr/lib/nvidia-384/libnvcuvid.so /usr/lib/nvidia-384/libnvidia-cfg.so /usr/lib/nvidia-384/libnvidia-compil
er.so /usr/lib/nvidia-384/libnvidia-encode.so /usr/lib/nvidia-384/libnvidia-fbc.so /usr/lib/nvidia-384/libnvid
ia-ifr.so /usr/lib/nvidia-384/libnvidia-ml.so 

root at paraview-6dcc64f758-9nkbc:/opt/subflow/paraview/paraview_build/CommandLineExecutables# ../../link.sh     /opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglTerminate'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateWindowSurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQueryString'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetProcAddress'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetError'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreatePbufferSurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroySurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglBindAPI'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglInitialize'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglQuerySurface'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglChooseConfig'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglSwapBuffers'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglCreateContext'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentDisplay'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetDisplay'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglMakeCurrent'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglDestroyContext'
/opt/subflow/paraview/paraview_build/lib/libvtkRenderingOpenGL2-pv5.4.so.1: undefined reference to `eglGetCurrentSurface'
collect2: error: ld returned 1 exit status

Does anyone know what is going wrong here?

Thanks,

Chris

From abarrie at gmail.com  Fri Dec  1 13:11:05 2017
From: abarrie at gmail.com (Alex Barrie)
Date: Fri, 1 Dec 2017 13:11:05 -0500
Subject: [Paraview] particle traces from point data
In-Reply-To: <CAM-GEcTjeffAy-R+Bs9QV2dp_Z_FOemc3aAA+Z03uk+qxcQ87Q@mail.gmail.com>
References: <CAM-GEcQU1+grhCZPzpYsZR23ZKRikU2odVyV=EFOZx8vDWLruw@mail.gmail.com>
 <CACJ=gTjemSFru=77cMSEmPJF+KzJNfWcWgC+peOXFSbHx0t0NQ@mail.gmail.com>
 <CAM-GEcTjxzQ83RaoJJYAMtSqmYn8C6sTSsQC_EFpoVb96CEORQ@mail.gmail.com>
 <CACJ=gTgoEMkc8m6=QsAZzRkjoO9A_9C7NKid0srWZjkfPJ8KdA@mail.gmail.com>
 <CAM-GEcTjeffAy-R+Bs9QV2dp_Z_FOemc3aAA+Z03uk+qxcQ87Q@mail.gmail.com>
Message-ID: <CAM-GEcTzQS5jBHfRvbbc8QzjyNjvFy+f7VRNVtvUf4BaQ5ihsQ@mail.gmail.com>

I was able to find this thread that mentions that maybe the input data set
needs to have a DATA_TIME_STEPS key, but I am not sure how to specify this
with the point3d data.
https://public.kitware.com/pipermail/paraview/2016-February/036211.html

Is there a way just to use whatever mechanism the animate functionality
uses?

On Thu, Nov 30, 2017 at 9:26 AM, Alex Barrie <abarrie at gmail.com> wrote:

> Yes, I have one file per timestep and each file is a list of points, X, Y,
> Z, C with one point per line. I am loading it with the 'Point3D' input.
> Thanks!
> Alex
>
>
> On Thu, Nov 30, 2017 at 9:18 AM, Joachim Pouderoux <
> joachim.pouderoux at kitware.com> wrote:
>
>> Alex,
>>
>> Could you specify how is your data split over time? Do you have one file
>> per timestep? How do you load your data with ParaView?
>>
>> Joachim
>>
>> *Joachim Pouderoux*, PhD
>>
>> *Technical Expert - Scientific Computing Team*
>> *Kitware SAS <http://www.kitware.fr>*
>>
>>
>> 2017-11-30 9:55 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>
>>> Thanks, I see it now - I missed it because it wasn't in the "Temporal"
>>> tab.
>>>
>>> When I apply this filter, however, I get an error about a missing
>>> DATA_TIME_STEPS information key. Is this something I can specify or does it
>>> have to be in the raw data somehow?
>>>
>>> Thanks,
>>> Alex
>>>
>>>
>>> On Wed, Nov 29, 2017 at 3:13 PM, Joachim Pouderoux <
>>> joachim.pouderoux at kitware.com> wrote:
>>>
>>>> Alex,
>>>>
>>>> I think here the filter "Temporal Particles to Pathlines" should do the
>>>> trick.
>>>>
>>>> Best,
>>>> Joachim
>>>>
>>>> *Joachim Pouderoux*, PhD
>>>>
>>>> *Technical Expert - Scientific Computing Team*
>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>
>>>>
>>>> 2017-11-29 14:33 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have animated particles which are imported from point data (x,y,z).
>>>>> I want to add a particle trace, but I am not sure what to put for the
>>>>> 'seed'. I am not using a vector field, but rather just a list of particle
>>>>> positions that updates over time. How can I just add a trace to each
>>>>> particle in the list?
>>>>>
>>>>> Thanks,
>>>>> Alex
>>>>>
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>> http://paraview.org/Wiki/ParaView
>>>>>
>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/5d5572ce/attachment.html>

From Nicholas.Stegmeier at sdstate.edu  Fri Dec  1 13:14:07 2017
From: Nicholas.Stegmeier at sdstate.edu (Stegmeier, Nicholas)
Date: Fri, 1 Dec 2017 18:14:07 +0000
Subject: [Paraview] Writing XML VTK Binary files from C++
In-Reply-To: <CANjZAi9UxVtksW19mJFVD4Y=G8pJH3Z05o5NFuhdupKbdu_qkA@mail.gmail.com>
References: <MWHPR06MB32771608E8AE41C08A01CB9B80380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <MWHPR06MB327729D24C03776C438AEA1680380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>,
 <CANjZAi9UxVtksW19mJFVD4Y=G8pJH3Z05o5NFuhdupKbdu_qkA@mail.gmail.com>
Message-ID: <MWHPR06MB32775F4A98E9BFDBFE6EE65E80390@MWHPR06MB3277.namprd06.prod.outlook.com>

Hello,


Thank you both for your advice. I will be sure to pursue both options and see if I can get them working.


Thank you again,

Nicholas Stegmeier

________________________________
From: David E DeMarle <dave.demarle at kitware.com>
Sent: Friday, December 1, 2017 8:35:45 AM
To: Mark Olesen
Cc: Stegmeier, Nicholas; paraview at paraview.org
Subject: Re: [Paraview] Writing XML VTK Binary files from C++

Another approach is to use VTK itself to write the files.

Since VTK 6 it is straightforward to configure a VTK build consisting
of only the IO/ParallelXML module and its required dependencies. To do
so, in cmake, turn of testing, all groups and turn on
Module_vtkIOParallelXML, and you should be set.

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


On Fri, Dec 1, 2017 at 2:34 AM, Mark Olesen <Mark.Olesen at esi-group.com> wrote:
> When you say "writing binary", you need to distinguish between three
> possibilities.
> 1) writing binary "inline" (actually base64 encoded)
> 2) writing binary "append" (actually base64 encoded)
> 3) writing raw binary "append" (really raw binary)
>
> Since you already have ASCII writing working and its content is "inline", it
> won't take much more to get binary inline working.
> By "inline", I mean when the output is placed between the <xxx> </xxx>
> markers. Eg,
>     <DataArray ...>
>         content
>     </DataArray>
>
> For the binary case, the content is written as base64-encoded data, which
> means that your output writer for these sections needs to pass the content
> through a base64 layer to do the encoding for you.
>
> If it helps as reference, we have the same thing in OpenFOAM, except that we
> only write vtu and vtp files (we don't have rectilinear meshes).
>
> In the repo https://develop.openfoam.com/Development/OpenFOAM-plus
> we have a foamVtkBase64Formatter and a foamVtkBase64Layer (both under
> src/fileFormats/vtk/format/) that add a base64Layer to encode and output as
> base64 (src/OpenFOAM/db/IOstreams/hashes/base64Layer.[CH]).
>
> You'll see that the foamVtkBase64Layer and base64Layer are quite low level
> means of adding an tiny encoding buffer (3 chars size) to intercept output
> prior to sending through to a std::ostream. It take very little effort to
> adopt for your output and thus quite easy to drop in instead of your current
> ASCII outputter.  For it too work easily, however, you should make sure that
> you need to generate your output content with a write() method instead of
> using '<<'. This allows somewhat easy switching between something like a
> foamVtkAsciiFormatter and the binary version, but more importantly it makes
> it easier to track the output state.
>
> When browsing through the code, you may also notice that we have support for
> writing in appended format (raw and base64). However, I would not advise you
> to tackle that immediately. There are a few more things to watch out for
> here, but more importantly it will change many more things on the calling
> side.
>
> I hope this information helps you.
> /mark
>
> --
> Dr Mark OLESEN
> Principal Engineer, ESI-OpenCFD
> ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
> www.openfoam.com<http://www.openfoam.com> | www.esi-group.com<http://www.esi-group.com> | mark.olesen at esi-group.com
>
>
> On 11/30/17 18:00, Stegmeier, Nicholas wrote:
>>
>> Hello,
>>
>> I am new to Paraview and C++ coming from a mostly mathematics background.
>> I am emailing to get resources or help on writing binary XML VTK files from
>> C++.
>>
>> I have finally succeeded in using the ASCII XML VTK format for a 2D
>> rectilinear CFD application. My ".pvtr" file is shown below.
>>
>> How can I write this file and my other XML VTK files in binary from C++?
>> Do I need a special C++ library?
>
> _______________________________________________
> Powered by www.kitware.com<http://www.kitware.com>
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/e610a882/attachment.html>

From joachim.pouderoux at kitware.com  Fri Dec  1 13:39:09 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Fri, 1 Dec 2017 14:39:09 -0400
Subject: [Paraview] particle traces from point data
In-Reply-To: <CAM-GEcTzQS5jBHfRvbbc8QzjyNjvFy+f7VRNVtvUf4BaQ5ihsQ@mail.gmail.com>
References: <CAM-GEcQU1+grhCZPzpYsZR23ZKRikU2odVyV=EFOZx8vDWLruw@mail.gmail.com>
 <CACJ=gTjemSFru=77cMSEmPJF+KzJNfWcWgC+peOXFSbHx0t0NQ@mail.gmail.com>
 <CAM-GEcTjxzQ83RaoJJYAMtSqmYn8C6sTSsQC_EFpoVb96CEORQ@mail.gmail.com>
 <CACJ=gTgoEMkc8m6=QsAZzRkjoO9A_9C7NKid0srWZjkfPJ8KdA@mail.gmail.com>
 <CAM-GEcTjeffAy-R+Bs9QV2dp_Z_FOemc3aAA+Z03uk+qxcQ87Q@mail.gmail.com>
 <CAM-GEcTzQS5jBHfRvbbc8QzjyNjvFy+f7VRNVtvUf4BaQ5ihsQ@mail.gmail.com>
Message-ID: <CACJ=gTi1T5Tn+F9Nw=9BGY3AbiJNgdGXfx=Xhu6Pi6s0o542Ww@mail.gmail.com>

Alex,

Again, could you specify how you are loading your files?
If you open them as a file series, then your data should be considered as
temporal and the filter should work.
See https://www.paraview.org/Wiki/Animating_legacy_VTK_file_series

Best,

*Joachim Pouderoux*, PhD

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


2017-12-01 14:11 GMT-04:00 Alex Barrie <abarrie at gmail.com>:

> I was able to find this thread that mentions that maybe the input data set
> needs to have a DATA_TIME_STEPS key, but I am not sure how to specify this
> with the point3d data.
> https://public.kitware.com/pipermail/paraview/2016-February/036211.html
>
> Is there a way just to use whatever mechanism the animate functionality
> uses?
>
> On Thu, Nov 30, 2017 at 9:26 AM, Alex Barrie <abarrie at gmail.com> wrote:
>
>> Yes, I have one file per timestep and each file is a list of points, X,
>> Y, Z, C with one point per line. I am loading it with the 'Point3D' input.
>> Thanks!
>> Alex
>>
>>
>> On Thu, Nov 30, 2017 at 9:18 AM, Joachim Pouderoux <
>> joachim.pouderoux at kitware.com> wrote:
>>
>>> Alex,
>>>
>>> Could you specify how is your data split over time? Do you have one file
>>> per timestep? How do you load your data with ParaView?
>>>
>>> Joachim
>>>
>>> *Joachim Pouderoux*, PhD
>>>
>>> *Technical Expert - Scientific Computing Team*
>>> *Kitware SAS <http://www.kitware.fr>*
>>>
>>>
>>> 2017-11-30 9:55 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>
>>>> Thanks, I see it now - I missed it because it wasn't in the "Temporal"
>>>> tab.
>>>>
>>>> When I apply this filter, however, I get an error about a missing
>>>> DATA_TIME_STEPS information key. Is this something I can specify or does it
>>>> have to be in the raw data somehow?
>>>>
>>>> Thanks,
>>>> Alex
>>>>
>>>>
>>>> On Wed, Nov 29, 2017 at 3:13 PM, Joachim Pouderoux <
>>>> joachim.pouderoux at kitware.com> wrote:
>>>>
>>>>> Alex,
>>>>>
>>>>> I think here the filter "Temporal Particles to Pathlines" should do
>>>>> the trick.
>>>>>
>>>>> Best,
>>>>> Joachim
>>>>>
>>>>> *Joachim Pouderoux*, PhD
>>>>>
>>>>> *Technical Expert - Scientific Computing Team*
>>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>>
>>>>>
>>>>> 2017-11-29 14:33 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have animated particles which are imported from point data (x,y,z).
>>>>>> I want to add a particle trace, but I am not sure what to put for the
>>>>>> 'seed'. I am not using a vector field, but rather just a list of particle
>>>>>> positions that updates over time. How can I just add a trace to each
>>>>>> particle in the list?
>>>>>>
>>>>>> Thanks,
>>>>>> Alex
>>>>>>
>>>>>> _______________________________________________
>>>>>> Powered by www.kitware.com
>>>>>>
>>>>>> Visit other Kitware open-source projects at
>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>
>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>
>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>>
>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/8eb297af/attachment.html>

From abarrie at gmail.com  Fri Dec  1 13:58:25 2017
From: abarrie at gmail.com (Alex Barrie)
Date: Fri, 1 Dec 2017 13:58:25 -0500
Subject: [Paraview] particle traces from point data
In-Reply-To: <CACJ=gTi1T5Tn+F9Nw=9BGY3AbiJNgdGXfx=Xhu6Pi6s0o542Ww@mail.gmail.com>
References: <CAM-GEcQU1+grhCZPzpYsZR23ZKRikU2odVyV=EFOZx8vDWLruw@mail.gmail.com>
 <CACJ=gTjemSFru=77cMSEmPJF+KzJNfWcWgC+peOXFSbHx0t0NQ@mail.gmail.com>
 <CAM-GEcTjxzQ83RaoJJYAMtSqmYn8C6sTSsQC_EFpoVb96CEORQ@mail.gmail.com>
 <CACJ=gTgoEMkc8m6=QsAZzRkjoO9A_9C7NKid0srWZjkfPJ8KdA@mail.gmail.com>
 <CAM-GEcTjeffAy-R+Bs9QV2dp_Z_FOemc3aAA+Z03uk+qxcQ87Q@mail.gmail.com>
 <CAM-GEcTzQS5jBHfRvbbc8QzjyNjvFy+f7VRNVtvUf4BaQ5ihsQ@mail.gmail.com>
 <CACJ=gTi1T5Tn+F9Nw=9BGY3AbiJNgdGXfx=Xhu6Pi6s0o542Ww@mail.gmail.com>
Message-ID: <CAM-GEcQPj+nXQXMK8vpnAM9XdhvsYR5aDHEAzP-c9uMbGFM+3g@mail.gmail.com>

I am attaching the first input file here. Each file has an incremented
number in the filename and then I load them all at once using the Point3D
reader. I just go to open and select the group, I don't do anything special
to load them. Paraview detects them all as part of the same group, and I
can play the animation just fine with the VCR controls. Is there a
different way to load them specifically as a series?

On Fri, Dec 1, 2017 at 1:39 PM, Joachim Pouderoux <
joachim.pouderoux at kitware.com> wrote:

> Alex,
>
> Again, could you specify how you are loading your files?
> If you open them as a file series, then your data should be considered as
> temporal and the filter should work.
> See https://www.paraview.org/Wiki/Animating_legacy_VTK_file_series
>
> Best,
>
> *Joachim Pouderoux*, PhD
>
> *Technical Expert - Scientific Computing Team*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2017-12-01 14:11 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>
>> I was able to find this thread that mentions that maybe the input data
>> set needs to have a DATA_TIME_STEPS key, but I am not sure how to specify
>> this with the point3d data.
>> https://public.kitware.com/pipermail/paraview/2016-February/036211.html
>>
>> Is there a way just to use whatever mechanism the animate functionality
>> uses?
>>
>> On Thu, Nov 30, 2017 at 9:26 AM, Alex Barrie <abarrie at gmail.com> wrote:
>>
>>> Yes, I have one file per timestep and each file is a list of points, X,
>>> Y, Z, C with one point per line. I am loading it with the 'Point3D' input.
>>> Thanks!
>>> Alex
>>>
>>>
>>> On Thu, Nov 30, 2017 at 9:18 AM, Joachim Pouderoux <
>>> joachim.pouderoux at kitware.com> wrote:
>>>
>>>> Alex,
>>>>
>>>> Could you specify how is your data split over time? Do you have one
>>>> file per timestep? How do you load your data with ParaView?
>>>>
>>>> Joachim
>>>>
>>>> *Joachim Pouderoux*, PhD
>>>>
>>>> *Technical Expert - Scientific Computing Team*
>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>
>>>>
>>>> 2017-11-30 9:55 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>
>>>>> Thanks, I see it now - I missed it because it wasn't in the "Temporal"
>>>>> tab.
>>>>>
>>>>> When I apply this filter, however, I get an error about a missing
>>>>> DATA_TIME_STEPS information key. Is this something I can specify or does it
>>>>> have to be in the raw data somehow?
>>>>>
>>>>> Thanks,
>>>>> Alex
>>>>>
>>>>>
>>>>> On Wed, Nov 29, 2017 at 3:13 PM, Joachim Pouderoux <
>>>>> joachim.pouderoux at kitware.com> wrote:
>>>>>
>>>>>> Alex,
>>>>>>
>>>>>> I think here the filter "Temporal Particles to Pathlines" should do
>>>>>> the trick.
>>>>>>
>>>>>> Best,
>>>>>> Joachim
>>>>>>
>>>>>> *Joachim Pouderoux*, PhD
>>>>>>
>>>>>> *Technical Expert - Scientific Computing Team*
>>>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>>>
>>>>>>
>>>>>> 2017-11-29 14:33 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have animated particles which are imported from point data
>>>>>>> (x,y,z). I want to add a particle trace, but I am not sure what to put for
>>>>>>> the 'seed'. I am not using a vector field, but rather just a list of
>>>>>>> particle positions that updates over time. How can I just add a trace to
>>>>>>> each particle in the list?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Alex
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Powered by www.kitware.com
>>>>>>>
>>>>>>> Visit other Kitware open-source projects at
>>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>>
>>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>>
>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>>>
>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/87d6b05a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: particles_000.3D
Type: application/octet-stream
Size: 5665 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/87d6b05a/attachment.obj>

From robertsawko at gmail.com  Fri Dec  1 14:18:40 2017
From: robertsawko at gmail.com (Robert Sawko)
Date: Fri, 1 Dec 2017 19:18:40 +0000
Subject: [Paraview] PV client-server: browsing remote files
Message-ID: <20171201191840.GA24911@avignon>

Dear ParaViewers,


I am trying to use Python shell in Client-Server mode, but I am running into
some difficulties. How can I actually browse the remote directories. I tried
to use the `os` module, but that obviously ends up being all local. Here's a
minimal example of what I am trying to achieve.


        from paraview.simple import Connect, LegacyVTKReader
        from os import listdir

        Connect('my_server', port)
        location = '/my/remote/location/'

        file_names = listdir(location).sort()
        reader = LegacyVTKReader(FileNames=file_names)


Please let me know if it's at all possible to query the directory on the remote
side through an established connection.

Many thanks,
Robert
-- 
Seems like the famous poem of turbulence comes from Jonathan Swift
http://en.wikipedia.org/wiki/The_Siphonaptera

From cory.quammen at kitware.com  Fri Dec  1 15:45:06 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 1 Dec 2017 15:45:06 -0500
Subject: [Paraview] unable to RGB voxel from tiff/jpeg slice to volume
In-Reply-To: <MWHPR17MB112080B654E2CF93B88FD5B1D0390@MWHPR17MB1120.namprd17.prod.outlook.com>
References: <MWHPR17MB1120940F68AE170B8F02F92CD0390@MWHPR17MB1120.namprd17.prod.outlook.com>
 <CAB5Fpx5qkdEN6KC=NWhkWWD7AdPtmiZVY3VsWS-H0EgL1YJVNg@mail.gmail.com>
 <MWHPR17MB112080B654E2CF93B88FD5B1D0390@MWHPR17MB1120.namprd17.prod.outlook.com>
Message-ID: <CAB5Fpx44=kn=CCX=QWHh=zvz1Ty4mNsG=h4Rjp5ZQ+ZzhvOLtw@mail.gmail.com>

On Thu, Nov 30, 2017 at 9:17 PM, joe kozak <lentilwallop at hotmail.com> wrote:
> that worked...    so why cant IsoVolume work on that type of dataset?  Can i
> not carve out a volume base on some range of Reds or Greens ?   What about
> based on some union of each channel?

I'm not sure what you are referring when you say IsoVolume. Is this
the Contour filter in ParaView? If so, the Contour filter does not
operate on RGB data. The Threshold filter does not work with RGB data,
either. You may be able to instead use Find Data to locate all points
that fall in some range, and you can use a Python expression to
perform a union of thresholds on different channels. After you have
created a selection this way, you can extract the selection with the
Extract Selection button on the bottom of the Find Data dialog.

Note that image data is associated with points in images in ParaView,
not cells, so if you want to extract a selection of cells, you might
use the Point Data to Cell Data filter before creating a selection.

HTH,
Cory

> ________________________________
> From: Cory Quammen <cory.quammen at kitware.com>
> Sent: Thursday, November 30, 2017 7:29 PM
> To: joe kozak
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] unable to RGB voxel from tiff/jpeg slice to volume
>
> Joe,
>
> This is more of a question for the ITK discussion forum [1], but I'll
> give you a potential solution here.
>
> The problem is that
>
> typedef itk::Image<unsigned char, 3>      ImageType;
>
> declares a 3-dimensional scalar-valued image, not a 3-component (RGB)
> 2-dimensional image. To declare an RGB ITK image, try this:
>
> typedef itk::RGBPixel< unsigned char > RGBPixelType;
> typedef itk::Image< RGBPixelType, 3 > ImageType;
>
> I hope that helps.
>
> Cory
>
> [1] https://discourse.itk.org/
>
> On Thu, Nov 30, 2017 at 8:14 PM, joe kozak <lentilwallop at hotmail.com> wrote:
>> grabbed frames from a standard youtube color video via ffmpeg
>> used something like $    ./imageSeriesToVolume -sz 1.0 -o test.vtk -i
>> input*.jpeg
>> loaded test.vtk in paraview 5.0.1 and also paraview 5.4.1
>> on information tab i see:   scalars  unsigned char [33,239]
>>
>> "Map Scalars"  on or off I get no RGB colored voxels, of course, because
>> there is only one datum of type unsigned char.
>>
>> Where are the other two scalars?!?
>>
>> The important part you will ask me is here:
>>
>>  91   io->SetFileName (filenames[0].c_str());
>>  92   io->ReadImageInformation();
>>  93
>>  94   if (io->GetNumberOfDimensions()==2) {
>>  95
>>  96     typedef itk::Image<unsigned char, 3>      ImageType;
>>  97     typedef itk::ImageSeriesReader<ImageType> SeriesReaderType;
>>  98
>>  99
>> 100     SeriesReaderType::Pointer reader = SeriesReaderType::New();
>> 101     std::cout << "Adding:\n";
>> 102     for (unsigned int i=0; i<filenames.size(); i++)
>> 103     {
>> 104       std::cout << filenames[i] << std::endl;
>> 105       reader->AddFileName ( filenames[i].c_str() );
>> 106     }
>> 107
>>
>> Looks pretty standard, but no 3 scalar datums for an RGB voxel for
>> non-false-colored volume.
>> It is perported to work, and all other examples i see are none different
>> from the code i used to generate a .vtk file.
>>
>>
>> I cannot use IsoVolume If I load the jpegs directly in paraview,  but I
>> can
>> get RGB color voxels.
>> The GOAL is to use IsoVolume on a volume of RGB points from frames from a
>> video sequence.
>> I have tried on and off for MANY YEARS to figure this out...    (its for
>> an
>> art project, metalcasting &3d Printing)
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.



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

From joachim.pouderoux at kitware.com  Fri Dec  1 15:59:10 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Fri, 1 Dec 2017 16:59:10 -0400
Subject: [Paraview] particle traces from point data
In-Reply-To: <CAM-GEcQPj+nXQXMK8vpnAM9XdhvsYR5aDHEAzP-c9uMbGFM+3g@mail.gmail.com>
References: <CAM-GEcQU1+grhCZPzpYsZR23ZKRikU2odVyV=EFOZx8vDWLruw@mail.gmail.com>
 <CACJ=gTjemSFru=77cMSEmPJF+KzJNfWcWgC+peOXFSbHx0t0NQ@mail.gmail.com>
 <CAM-GEcTjxzQ83RaoJJYAMtSqmYn8C6sTSsQC_EFpoVb96CEORQ@mail.gmail.com>
 <CACJ=gTgoEMkc8m6=QsAZzRkjoO9A_9C7NKid0srWZjkfPJ8KdA@mail.gmail.com>
 <CAM-GEcTjeffAy-R+Bs9QV2dp_Z_FOemc3aAA+Z03uk+qxcQ87Q@mail.gmail.com>
 <CAM-GEcTzQS5jBHfRvbbc8QzjyNjvFy+f7VRNVtvUf4BaQ5ihsQ@mail.gmail.com>
 <CACJ=gTi1T5Tn+F9Nw=9BGY3AbiJNgdGXfx=Xhu6Pi6s0o542Ww@mail.gmail.com>
 <CAM-GEcQPj+nXQXMK8vpnAM9XdhvsYR5aDHEAzP-c9uMbGFM+3g@mail.gmail.com>
Message-ID: <CACJ=gTju5rCmfP0LEyWq2YtSGZ3OZ60-f8dkPYfhz2gOPvDvAQ@mail.gmail.com>

Alex,

The problem appears because the output of this Visit-based reader is a
multiblock.

Here is a workaround: apply a *Merge Block* filter on your input data, then
apply the *Temporal Particles To Pathline* filter.

Best,

*Joachim Pouderoux*, PhD

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


2017-12-01 14:58 GMT-04:00 Alex Barrie <abarrie at gmail.com>:

> I am attaching the first input file here. Each file has an incremented
> number in the filename and then I load them all at once using the Point3D
> reader. I just go to open and select the group, I don't do anything special
> to load them. Paraview detects them all as part of the same group, and I
> can play the animation just fine with the VCR controls. Is there a
> different way to load them specifically as a series?
>
> On Fri, Dec 1, 2017 at 1:39 PM, Joachim Pouderoux <
> joachim.pouderoux at kitware.com> wrote:
>
>> Alex,
>>
>> Again, could you specify how you are loading your files?
>> If you open them as a file series, then your data should be considered as
>> temporal and the filter should work.
>> See https://www.paraview.org/Wiki/Animating_legacy_VTK_file_series
>>
>> Best,
>>
>> *Joachim Pouderoux*, PhD
>>
>> *Technical Expert - Scientific Computing Team*
>> *Kitware SAS <http://www.kitware.fr>*
>>
>>
>> 2017-12-01 14:11 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>
>>> I was able to find this thread that mentions that maybe the input data
>>> set needs to have a DATA_TIME_STEPS key, but I am not sure how to specify
>>> this with the point3d data.
>>> https://public.kitware.com/pipermail/paraview/2016-February/036211.html
>>>
>>> Is there a way just to use whatever mechanism the animate functionality
>>> uses?
>>>
>>> On Thu, Nov 30, 2017 at 9:26 AM, Alex Barrie <abarrie at gmail.com> wrote:
>>>
>>>> Yes, I have one file per timestep and each file is a list of points, X,
>>>> Y, Z, C with one point per line. I am loading it with the 'Point3D' input.
>>>> Thanks!
>>>> Alex
>>>>
>>>>
>>>> On Thu, Nov 30, 2017 at 9:18 AM, Joachim Pouderoux <
>>>> joachim.pouderoux at kitware.com> wrote:
>>>>
>>>>> Alex,
>>>>>
>>>>> Could you specify how is your data split over time? Do you have one
>>>>> file per timestep? How do you load your data with ParaView?
>>>>>
>>>>> Joachim
>>>>>
>>>>> *Joachim Pouderoux*, PhD
>>>>>
>>>>> *Technical Expert - Scientific Computing Team*
>>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>>
>>>>>
>>>>> 2017-11-30 9:55 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>>
>>>>>> Thanks, I see it now - I missed it because it wasn't in the
>>>>>> "Temporal" tab.
>>>>>>
>>>>>> When I apply this filter, however, I get an error about a missing
>>>>>> DATA_TIME_STEPS information key. Is this something I can specify or does it
>>>>>> have to be in the raw data somehow?
>>>>>>
>>>>>> Thanks,
>>>>>> Alex
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 29, 2017 at 3:13 PM, Joachim Pouderoux <
>>>>>> joachim.pouderoux at kitware.com> wrote:
>>>>>>
>>>>>>> Alex,
>>>>>>>
>>>>>>> I think here the filter "Temporal Particles to Pathlines" should do
>>>>>>> the trick.
>>>>>>>
>>>>>>> Best,
>>>>>>> Joachim
>>>>>>>
>>>>>>> *Joachim Pouderoux*, PhD
>>>>>>>
>>>>>>> *Technical Expert - Scientific Computing Team*
>>>>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>>>>
>>>>>>>
>>>>>>> 2017-11-29 14:33 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have animated particles which are imported from point data
>>>>>>>> (x,y,z). I want to add a particle trace, but I am not sure what to put for
>>>>>>>> the 'seed'. I am not using a vector field, but rather just a list of
>>>>>>>> particle positions that updates over time. How can I just add a trace to
>>>>>>>> each particle in the list?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Alex
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Powered by www.kitware.com
>>>>>>>>
>>>>>>>> Visit other Kitware open-source projects at
>>>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>>>
>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>>>
>>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>>>>
>>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/8b2662b8/attachment.html>

From abarrie at gmail.com  Fri Dec  1 16:04:02 2017
From: abarrie at gmail.com (Alex Barrie)
Date: Fri, 1 Dec 2017 16:04:02 -0500
Subject: [Paraview] particle traces from point data
In-Reply-To: <CACJ=gTju5rCmfP0LEyWq2YtSGZ3OZ60-f8dkPYfhz2gOPvDvAQ@mail.gmail.com>
References: <CAM-GEcQU1+grhCZPzpYsZR23ZKRikU2odVyV=EFOZx8vDWLruw@mail.gmail.com>
 <CACJ=gTjemSFru=77cMSEmPJF+KzJNfWcWgC+peOXFSbHx0t0NQ@mail.gmail.com>
 <CAM-GEcTjxzQ83RaoJJYAMtSqmYn8C6sTSsQC_EFpoVb96CEORQ@mail.gmail.com>
 <CACJ=gTgoEMkc8m6=QsAZzRkjoO9A_9C7NKid0srWZjkfPJ8KdA@mail.gmail.com>
 <CAM-GEcTjeffAy-R+Bs9QV2dp_Z_FOemc3aAA+Z03uk+qxcQ87Q@mail.gmail.com>
 <CAM-GEcTzQS5jBHfRvbbc8QzjyNjvFy+f7VRNVtvUf4BaQ5ihsQ@mail.gmail.com>
 <CACJ=gTi1T5Tn+F9Nw=9BGY3AbiJNgdGXfx=Xhu6Pi6s0o542Ww@mail.gmail.com>
 <CAM-GEcQPj+nXQXMK8vpnAM9XdhvsYR5aDHEAzP-c9uMbGFM+3g@mail.gmail.com>
 <CACJ=gTju5rCmfP0LEyWq2YtSGZ3OZ60-f8dkPYfhz2gOPvDvAQ@mail.gmail.com>
Message-ID: <CAM-GEcSRQYpY1sCmzR0_YbVaRQVfu6u51Nkb6Xm+CgGJbw67aQ@mail.gmail.com>

That got it, thanks!
Alex


On Fri, Dec 1, 2017 at 3:59 PM, Joachim Pouderoux <
joachim.pouderoux at kitware.com> wrote:

> Alex,
>
> The problem appears because the output of this Visit-based reader is a
> multiblock.
>
> Here is a workaround: apply a *Merge Block* filter on your input data,
> then apply the *Temporal Particles To Pathline* filter.
>
> Best,
>
> *Joachim Pouderoux*, PhD
>
> *Technical Expert - Scientific Computing Team*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2017-12-01 14:58 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>
>> I am attaching the first input file here. Each file has an incremented
>> number in the filename and then I load them all at once using the Point3D
>> reader. I just go to open and select the group, I don't do anything special
>> to load them. Paraview detects them all as part of the same group, and I
>> can play the animation just fine with the VCR controls. Is there a
>> different way to load them specifically as a series?
>>
>> On Fri, Dec 1, 2017 at 1:39 PM, Joachim Pouderoux <
>> joachim.pouderoux at kitware.com> wrote:
>>
>>> Alex,
>>>
>>> Again, could you specify how you are loading your files?
>>> If you open them as a file series, then your data should be considered
>>> as temporal and the filter should work.
>>> See https://www.paraview.org/Wiki/Animating_legacy_VTK_file_series
>>>
>>> Best,
>>>
>>> *Joachim Pouderoux*, PhD
>>>
>>> *Technical Expert - Scientific Computing Team*
>>> *Kitware SAS <http://www.kitware.fr>*
>>>
>>>
>>> 2017-12-01 14:11 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>
>>>> I was able to find this thread that mentions that maybe the input data
>>>> set needs to have a DATA_TIME_STEPS key, but I am not sure how to specify
>>>> this with the point3d data.
>>>> https://public.kitware.com/pipermail/paraview/2016-February/036211.html
>>>>
>>>> Is there a way just to use whatever mechanism the animate functionality
>>>> uses?
>>>>
>>>> On Thu, Nov 30, 2017 at 9:26 AM, Alex Barrie <abarrie at gmail.com> wrote:
>>>>
>>>>> Yes, I have one file per timestep and each file is a list of points,
>>>>> X, Y, Z, C with one point per line. I am loading it with the 'Point3D'
>>>>> input.
>>>>> Thanks!
>>>>> Alex
>>>>>
>>>>>
>>>>> On Thu, Nov 30, 2017 at 9:18 AM, Joachim Pouderoux <
>>>>> joachim.pouderoux at kitware.com> wrote:
>>>>>
>>>>>> Alex,
>>>>>>
>>>>>> Could you specify how is your data split over time? Do you have one
>>>>>> file per timestep? How do you load your data with ParaView?
>>>>>>
>>>>>> Joachim
>>>>>>
>>>>>> *Joachim Pouderoux*, PhD
>>>>>>
>>>>>> *Technical Expert - Scientific Computing Team*
>>>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>>>
>>>>>>
>>>>>> 2017-11-30 9:55 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>>>
>>>>>>> Thanks, I see it now - I missed it because it wasn't in the
>>>>>>> "Temporal" tab.
>>>>>>>
>>>>>>> When I apply this filter, however, I get an error about a missing
>>>>>>> DATA_TIME_STEPS information key. Is this something I can specify or does it
>>>>>>> have to be in the raw data somehow?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Alex
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Nov 29, 2017 at 3:13 PM, Joachim Pouderoux <
>>>>>>> joachim.pouderoux at kitware.com> wrote:
>>>>>>>
>>>>>>>> Alex,
>>>>>>>>
>>>>>>>> I think here the filter "Temporal Particles to Pathlines" should do
>>>>>>>> the trick.
>>>>>>>>
>>>>>>>> Best,
>>>>>>>> Joachim
>>>>>>>>
>>>>>>>> *Joachim Pouderoux*, PhD
>>>>>>>>
>>>>>>>> *Technical Expert - Scientific Computing Team*
>>>>>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017-11-29 14:33 GMT-04:00 Alex Barrie <abarrie at gmail.com>:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have animated particles which are imported from point data
>>>>>>>>> (x,y,z). I want to add a particle trace, but I am not sure what to put for
>>>>>>>>> the 'seed'. I am not using a vector field, but rather just a list of
>>>>>>>>> particle positions that updates over time. How can I just add a trace to
>>>>>>>>> each particle in the list?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Alex
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Powered by www.kitware.com
>>>>>>>>>
>>>>>>>>> Visit other Kitware open-source projects at
>>>>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>>>>
>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>>>>
>>>>>>>>> Search the list archives at: http://markmail.org/search/?q=
>>>>>>>>> ParaView
>>>>>>>>>
>>>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171201/15ad85b9/attachment.html>

From jaquick at humboldt.edu  Sat Dec  2 13:34:13 2017
From: jaquick at humboldt.edu (Julian A. Quick)
Date: Sat, 2 Dec 2017 11:34:13 -0700
Subject: [Paraview] python exodus parsing segaults
Message-ID: <CAKYsqYko2x3jtfyHwCMQAS5qeienJg9ex0g_2vKxRLXDw0MWqg@mail.gmail.com>

Hello All,

I wrote a python script using the Paraview ExodusIIReader to convert exodus
II files into csv's. The script usually runs successfully, but sometimes I
get a segfault. Am I missing something? How might I be able to better
handle memory in this code? I tried pasting the reset function I found on
the mailing list
<https://public.kitware.com/pipermail/paraview/2015-July/034588.html> to
the top of the code but it did not seem to help. I appreciate your time and
support.


from paraview.simple import *
from paraview.numpy_support import vtk_to_numpy
import vtk.numpy_interface.dataset_adapter as dsa
import sys
s = ExodusIIReader(FileName='./results/%s.e'%sys.argv[-1])
d = CreateWriter('./out.csv', s)
Delete(d)
d.FieldAssociation = "Points"
d.UpdatePipeline(time=s.TimestepValues[-1])
Delete(s)
Delete(d)
del d



$ pvpython mycode.py my_ecodus_file
$ pvpython mycode.py my_ecodus_file
Segmentation fault: 11


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

From banesulli at gmail.com  Sat Dec  2 17:07:10 2017
From: banesulli at gmail.com (Bane Sullivan)
Date: Sat, 2 Dec 2017 17:07:10 -0500
Subject: [Paraview] Python in the VR Build
Message-ID: <CAD=kO4sPm_sYFFvf3jcSn4MOTW6LbqmR9c=wBykivR1Cf_WDkg@mail.gmail.com>

Is it possible to release a Python compatible version of the VR build of
ParaView?

I am working on a project where I am dynamically linking geophysical
processing code to ParaView for near-real time visualizations. Having
Python included in the VR build would be a huge benefit!

This would also help me for the static visualizations I am working with
where I have created tons of file readers and filters in the Python
Programmable Filter/Source format. Checkout my project here:
https://github.com/banesullivan/ParaViewGeophysics

Thanks,

B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171202/22431d12/attachment.html>

From banesulli at gmail.com  Sat Dec  2 17:43:01 2017
From: banesulli at gmail.com (Bane Sullivan)
Date: Sat, 2 Dec 2017 17:43:01 -0500
Subject: [Paraview] Python Programmable Filter Time Series Source
Message-ID: <CAD=kO4uFfANVe0vQQupkevL7DgZNLcK=dDxHUHi_buLO7P5T8w@mail.gmail.com>

Here is an example of a programmable filter vis XML that I want to simply
print off the various file names or give me and ability to read the file
series. I have this python programmable filter set up to work when I click
File->Open in ParaView. I have the ability to then chose file series from
the file prompt. How might I make a programmable filter via XML attributes
so that it can handle file series.

<ServerManagerConfiguration>
  <ProxyGroup name="sources">
    <SourceProxy name="ListSeries" class="vtkPythonProgrammableFilter"
label="List Series">
      <Documentation
        long_help=""
        short_help="">
      </Documentation>
      <Hints>
        <ShowInMenu category=?File Series Readers" />
      </Hints>
      <Hints>
        <ReaderFactory extensions="dat txt"
          file_description="list series" />
      </Hints>

      <!-- Output data type: "vtkImageData" -->
      <IntVectorProperty command="SetOutputDataSetType"
                         default_values="6"
                         name="OutputDataSetType"
                         number_of_elements="1"
                         panel_visibility="never">
        <Documentation>The value of this property determines the dataset
type
        for the output of the programmable filter.</Documentation>
      </IntVectorProperty>



      <StringVectorProperty
        panel_visibility="default"
        name="FileName"
        label="FileName"
        initial_string="FileName"
        command="SetParameter"
        animateable="1"
        default_values="absolute path"
        number_of_elements="1">
        <FileListDomain name="files"/>
        <Documentation></Documentation>
      </StringVectorProperty>

      <StringVectorProperty
        panel_visibility="default"
        name="files"
        label="files"
        initial_string="files"
        command="SetParameter"
        animateable="1"
        default_values="abs path"
        number_of_elements="1">
        <Documentation></Documentation>
      </StringVectorProperty>

      <StringVectorProperty
        name="Script"
        command="SetScript"
        number_of_elements="1"
        default_values="print(FileName)&#xA;print(files)&#xA;"
        panel_visibility="advanced">
        <Hints>
          <Widget type="multi_line" syntax="python"/>
        </Hints>
        <Documentation>This property contains the text of a python program
that
        the programmable source runs.</Documentation>
        </StringVectorProperty>

      <StringVectorProperty
        name="InformationScript"
        label="RequestInformation Script"
        command="SetInformationScript"
        number_of_elements="1"
        default_values="print(FileName)&#xA;print(files)&#xA;"
        panel_visibility="advanced">
        <Hints>
          <Widget type="multi_line" syntax="python"/>
        </Hints>
        <Documentation>This property is a python script that is executed
during
        the RequestInformation pipeline pass. Use this to provide
information
        such as WHOLE_EXTENT to the pipeline downstream.</Documentation>
      </StringVectorProperty>

    </SourceProxy>
 </ProxyGroup>
</ServerManagerConfiguration>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171202/3af5b42e/attachment.html>

From ken.martin at kitware.com  Sat Dec  2 20:16:24 2017
From: ken.martin at kitware.com (Ken Martin)
Date: Sat, 2 Dec 2017 20:16:24 -0500
Subject: [Paraview] Python in the VR Build
In-Reply-To: <CAD=kO4sPm_sYFFvf3jcSn4MOTW6LbqmR9c=wBykivR1Cf_WDkg@mail.gmail.com>
References: <CAD=kO4sPm_sYFFvf3jcSn4MOTW6LbqmR9c=wBykivR1Cf_WDkg@mail.gmail.com>
Message-ID: <CANXz0Sb=MwcL865SLGGsd=xD-E8DioCn1fwvguZCRiCnpAcsQw@mail.gmail.com>

I believe the nightly PV builds now include the OpenVR plugin on windows. I
have not had a chance to try it but it might do the trick.

On Sat, Dec 2, 2017 at 5:07 PM, Bane Sullivan <banesulli at gmail.com> wrote:

> Is it possible to release a Python compatible version of the VR build of
> ParaView?
>
> I am working on a project where I am dynamically linking geophysical
> processing code to ParaView for near-real time visualizations. Having
> Python included in the VR build would be a huge benefit!
>
> This would also help me for the static visualizations I am working with
> where I have created tons of file readers and filters in the Python
> Programmable Filter/Source format. Checkout my project here:
> https://github.com/banesullivan/ParaViewGeophysics
>
> Thanks,
>
> B
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Ken Martin PhD
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/attachments/20171202/d443f2b0/attachment.html>

From stephen.wornom at inria.fr  Sat Dec  2 23:50:36 2017
From: stephen.wornom at inria.fr (Stephen Wornom)
Date: Sun, 3 Dec 2017 05:50:36 +0100 (CET)
Subject: [Paraview] post-process of CFL3D result with surfaces in
 paraview?
In-Reply-To: <CAMkQf0vGBokzpFmUHZNH9=nVjvoat1We=VdVWcrMc73yZyTb_Q@mail.gmail.com>
References: <CAMkQf0vGBokzpFmUHZNH9=nVjvoat1We=VdVWcrMc73yZyTb_Q@mail.gmail.com>
Message-ID: <1404584315.12707592.1512276636451.JavaMail.zimbra@inria.fr>

I have a different code but had the same problem that I resolved by adding an additional variable which sets value 0 at interior points and a different values for each surface, for example, -3 for the wing surface points. Then I use "extract" to visualize the different surfaces. 
Hope this helps, 
Stephen 

----- Original Message -----

> From: "??" <chengdi123000 at gmail.com>
> To: "ParaView" <paraview at paraview.org>
> Sent: Wednesday, November 29, 2017 9:32:45 PM
> Subject: [Paraview] post-process of CFL3D result with surfaces in paraview?

> Hi paraviewers,

> I am using paraview to render results in CFL3D, which is in Plot3D format,
> including ` abc.xyz ` grid file and `abc.q` solution file. Besides, I have a
> boundary condition file `abc.xyz.fvbnd` in FieldView 1.3 format which was
> generated by grid pre-processor.

> My problem is: How to extract the surface of the aircraft?

> Because the Plot3D format is a multi-block curvilinear grid. When I use
> `Extract Surface` filter, it will extract the block interfaces. My current
> solution to combine blocks by `Merge Blocks` filter. Then I can extract the
> surfaces, including the outer boundary and the inner aircraft walls. After
> that, I need to clip the farfield and keep the aircraft walls. Is there a
> better solution?

> However, what I need to do is to evaluate the force on specific parts. So I
> need to use the information from the boundary condition file `abc.xyz.fvbnd`
> which indicates ranges of indexes in curvilinear grid as wall of certain
> parts. My problem is how to use it to generate several surfaces in paraview
> for rendering and integration.

> p.s. I am using paraview 5.4.1. The grid consists of farfield outer boundary
> and several aircraft parts' wall inner boundaries.

> Di Cheng
> Engineer of Research Center
> China Academy of Aerospace Aerodynamics
> Phone: +86-l58Ol5949ll

> Address: No.17, YunGang West Road, Fengtai District, Beijing, China

> Zip Code?100074

> _______________________________________________
> Powered by www.kitware.com

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

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

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

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

From seongmo.yeon at gmail.com  Sun Dec  3 11:24:23 2017
From: seongmo.yeon at gmail.com (SeongMo)
Date: Mon, 4 Dec 2017 01:24:23 +0900
Subject: [Paraview] need a small working source code for testing OpenFOAM
	reader
Message-ID: <755dc84d-e43f-8b7a-cadd-7b54d0ca77d6@gmail.com>

Hi,


I am trying to work on the vtkOpenFOAMReader class to add a support for 
decomposedBlockData introduced in OpenFOAM 5.x.

I need a small testing code which should invoke OpenFOAMReader's 
requestInformation and requestData function so check and trace how the 
reader is working.

But I am new to VTK library so having trouble to make a code.

It would be highly grateful to give me some tutorials and examples for 
the specific case.


Thanks in advance.


-- 
Seong Mo Yeon
E-mail : seongmo.yeon at gmail.com
Tel :
--------------------------------------------------------
Fluctuat nec mergitur


From Nicholas.Stegmeier at sdstate.edu  Sun Dec  3 18:46:26 2017
From: Nicholas.Stegmeier at sdstate.edu (Stegmeier, Nicholas)
Date: Sun, 3 Dec 2017 23:46:26 +0000
Subject: [Paraview] Writing XML VTK Binary files from C++
In-Reply-To: <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>
References: <MWHPR06MB32771608E8AE41C08A01CB9B80380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <MWHPR06MB327729D24C03776C438AEA1680380@MWHPR06MB3277.namprd06.prod.outlook.com>,
 <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>
Message-ID: <MWHPR06MB3277DB2A6C40922826065F14803F0@MWHPR06MB3277.namprd06.prod.outlook.com>

Hello again Mark,

I have been working on implementing the binary "inline" option for my VTK XML files. I looked through the OpenFOAM code that you suggested and am having trouble interpreting it.

Would you be able to give me a hint as to where I should be looking in foamVtkBase64Layer? For example, in my current code I write the array data like this:

  int i,j;
  ofstream lfile;

  lfile << "\t\t\t\t<DataArray type=\"Float32\" Name=\"rho\" format=\"ascii\">\n";
  lfile << "\t\t\t\t\t";
    for (j = firsty-1; j <= lasty+1; j++){
    for (i = firstx-1; i <= lastx+1; i++){
      lfile << rho[j][i][t] << " ";
    }
    }
  lfile << "\n";
  lfile << "\t\t\t\t</DataArray>\n";

 I have not used the write function in C++ before. Is there a quick way to explain how the above code would be modified (with the contents of "rho" being written to the file)? I wonder if I will run into a problem because of how I have set up the array with the 't' index last.

Thank you so much for your help so far.

Nicholas Stegmeier
Graduate Student
Mathematics and Statistics
South Dakota State University


________________________________
From: Mark Olesen <Mark.Olesen at esi-group.com>
Sent: Friday, December 1, 2017 1:34:58 AM
To: Stegmeier, Nicholas; paraview at paraview.org
Subject: Re: [Paraview] Writing XML VTK Binary files from C++

When you say "writing binary", you need to distinguish between three
possibilities.
1) writing binary "inline" (actually base64 encoded)
2) writing binary "append" (actually base64 encoded)
3) writing raw binary "append" (really raw binary)

Since you already have ASCII writing working and its content is
"inline", it won't take much more to get binary inline working.
By "inline", I mean when the output is placed between the <xxx> </xxx>
markers. Eg,
     <DataArray ...>
         content
     </DataArray>

For the binary case, the content is written as base64-encoded data,
which means that your output writer for these sections needs to pass the
content through a base64 layer to do the encoding for you.

If it helps as reference, we have the same thing in OpenFOAM, except
that we only write vtu and vtp files (we don't have rectilinear meshes).

In the repo https://develop.openfoam.com/Development/OpenFOAM-plus
we have a foamVtkBase64Formatter and a foamVtkBase64Layer (both under
src/fileFormats/vtk/format/) that add a base64Layer to encode and output
as base64 (src/OpenFOAM/db/IOstreams/hashes/base64Layer.[CH]).

You'll see that the foamVtkBase64Layer and base64Layer are quite low
level means of adding an tiny encoding buffer (3 chars size) to
intercept output prior to sending through to a std::ostream. It take
very little effort to adopt for your output and thus quite easy to drop
in instead of your current ASCII outputter.  For it too work easily,
however, you should make sure that you need to generate your output
content with a write() method instead of using '<<'. This allows
somewhat easy switching between something like a foamVtkAsciiFormatter
and the binary version, but more importantly it makes it easier to track
the output state.

When browsing through the code, you may also notice that we have support
for writing in appended format (raw and base64). However, I would not
advise you to tackle that immediately. There are a few more things to
watch out for here, but more importantly it will change many more things
on the calling side.

I hope this information helps you.
/mark

--
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
www.openfoam.com<http://www.openfoam.com> | www.esi-group.com<http://www.esi-group.com> | mark.olesen at esi-group.com


On 11/30/17 18:00, Stegmeier, Nicholas wrote:
> Hello,
>
> I am new to Paraview and C++ coming from a mostly mathematics
> background. I am emailing to get resources or help on writing binary XML
> VTK files from C++.
>
> I have finally succeeded in using the ASCII XML VTK format for a 2D
> rectilinear CFD application. My ".pvtr" file is shown below.
>
> How can I write this file and my other XML VTK files in binary from C++?
> Do I need a special C++ library?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171203/184fe2aa/attachment.html>

From fixed-term.Lukas.Eberle2 at de.bosch.com  Mon Dec  4 02:05:32 2017
From: fixed-term.Lukas.Eberle2 at de.bosch.com (FIXED-TERM Eberle Lukas (CC-PS/ECL5))
Date: Mon, 4 Dec 2017 07:05:32 +0000
Subject: [Paraview] Visualize point cloud UDP stream
Message-ID: <c8903e314e6f4a5dbbff61652f673d25@de.bosch.com>

To whom it may concern,

I would like to visualize a real-time point cloud stream in Paraview.
Up to now I have implemented a "Programmable Source" in Paraview which receives a point cloud stream over UDP. The output of the source is selected as vtkTable. I process the source with a Table To Points filter and visualize it on screen. So far so good this is working very well.
Currently the Python script of the "Programmable Source" is executed only once. What I want to do is to update the source on a given frequency.
I tried to put my script into a while-loop but this is not working(Paraview hangs-up).
Is there a possibility to execute the "Programmable Source" within a loop or a different way to visualize a UDP stream?
Thank you in advance
Best regards

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

From quentin at arrivo-loop.com  Mon Dec  4 13:16:56 2017
From: quentin at arrivo-loop.com (Quentin d'Avout)
Date: Mon, 4 Dec 2017 10:16:56 -0800
Subject: [Paraview] [EXT] RE: Python Annotations
In-Reply-To: <CA+=e1otj8FGOxJDd001Q=372dg=R6LdYa8OyfkieRYUEACr5nQ@mail.gmail.com>
References: <BN3PR0701MB16871683283257BB5FF468179F560@BN3PR0701MB1687.namprd07.prod.outlook.com>
 <01bf0c84f6b566ffda3b2502e60d4228@mail.gmail.com>
 <BN3PR0701MB1687539B2763FF683945E9819F540@BN3PR0701MB1687.namprd07.prod.outlook.com>
 <CAPaR3=w2yeZic0wAzkDD--k4t8ZcQBzi665rj7HsBu5vNntSWg@mail.gmail.com>
 <CA+=e1otj8FGOxJDd001Q=372dg=R6LdYa8OyfkieRYUEACr5nQ@mail.gmail.com>
Message-ID: <CAPaR3=z9D=FXsPRgT35UkWut4ECmshLFjifc-0JfT2XQWqK54g@mail.gmail.com>

Precisely.
Thank you Allie!

On Wed, Nov 29, 2017 at 7:09 AM, Allie Vacanti <allison.vacanti at kitware.com>
wrote:

> Is this what you're looking for?
>
> https://blog.kitware.com/writing-equations-in-paraview-4-0-with-mathtext/
>
> On Tue, Nov 28, 2017 at 8:23 PM, Quentin d'Avout <quentin at arrivo-loop.com>
> wrote:
>
>> Thank you Dennis.
>>
>> All, I'm looking for which code (if any) is used for special characters,
>> superscripts, etc. to insert in annotations, graph legends, plots, etc.
>>
>> Any ideas welcome.
>> Thanks
>> Quentin
>>
>> On Fri, Nov 10, 2017 at 6:30 AM, Dennis Conklin <
>> dennis_conklin at goodyear.com> wrote:
>>
>>> Quentin,
>>>
>>>
>>>
>>> Glad that helped.   I think any Cell, Point or Field variable is
>>> available if you select the corresponding Array Association.   I don?t know
>>> what special characters are allowed, maybe someone else can chime in here.
>>>
>>>
>>>
>>> Dennis
>>>
>>>
>>>
>>> *From:* Quentin d'Avout [mailto:quentin at arrivo-loop.com]
>>> *Sent:* Thursday, November 09, 2017 9:25 PM
>>> *To:* Dennis Conklin <dennis_conklin at goodyear.com>
>>> *Cc:* ParaView <paraview at paraview.org>
>>> *Subject:* [EXT] RE: [Paraview] Python Annotations
>>>
>>>
>>>
>>>  *WARNING - External email; exercise caution.*
>>>
>>>
>>>
>>> Thanks Dennis. That works great. Any chance there is a list of the
>>> useable variables?
>>>
>>>
>>>
>>> aAlso, Any good resource for special characters that we can insert in
>>> the string (e.g. infiniti sign)?
>>>
>>>
>>>
>>> Quentin
>>>
>>>
>>>
>>> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Dennis
>>> Conklin
>>> *Sent:* Wednesday, November 8, 2017 10:23 AM
>>> *To:* Paraview (paraview at paraview.org) <paraview at paraview.org>
>>> *Subject:* Re: [Paraview] Python Annotations
>>>
>>>
>>>
>>> Quentin,
>>>
>>>
>>>
>>> Try this:
>>>
>>>
>>>
>>>    - Example:  Plot Total Vertical force (REACTZ_901+REACTZ_902) in
>>>    animation
>>>
>>>
>>>    - Form is ?Label %g? %(expression)
>>>
>>>
>>>    - Label is:    ?Vertical Force: %g?   where %g is format and will be
>>>          replaced by value of expression
>>>          - Expression is:  %(REACTZ_901[t_index]+REACTZ_902[t_index])
>>>          where t_index is for current time only
>>>          - See next slide
>>>
>>>
>>>
>>> [image: cid:image001.png at 01D35985.135BEBB0]
>>>
>>>
>>>
>>> Dennis
>>>
>>
>>
>>
>> --
>>
>> Quentin d?Avout | Aerodynamics
>> [image: Arrivo Loop] <http://www.arrivo-loop.com/>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>


-- 

Quentin d?Avout | Aerodynamics
[image: Arrivo Loop] <http://www.arrivo-loop.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/5ec37499/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 31028 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/5ec37499/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4364 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/5ec37499/attachment-0001.png>

From quentin at arrivo-loop.com  Mon Dec  4 13:19:42 2017
From: quentin at arrivo-loop.com (Quentin d'Avout)
Date: Mon, 4 Dec 2017 10:19:42 -0800
Subject: [Paraview] More fonts?
Message-ID: <CAPaR3=xn3QpSpzPpqzpnpQBobL1W992d2Gmovyiy52P1LonQvA@mail.gmail.com>

Hi all,

I'm using 5.0.1, and would like to use other fonts than the default
Arial/Courrier/Times.
Any way to add other fonts?

Thanks
Quentin
<http://www.arrivo-loop.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/b8b43833/attachment.html>

From joachim.pouderoux at kitware.com  Mon Dec  4 13:24:52 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Mon, 4 Dec 2017 14:24:52 -0400
Subject: [Paraview] More fonts?
In-Reply-To: <CAPaR3=xn3QpSpzPpqzpnpQBobL1W992d2Gmovyiy52P1LonQvA@mail.gmail.com>
References: <CAPaR3=xn3QpSpzPpqzpnpQBobL1W992d2Gmovyiy52P1LonQvA@mail.gmail.com>
Message-ID: <CACJ=gTiLEy=ukV9DMRgAwk7dfYp=2X3NKcB3TL1dREjpryMmgA@mail.gmail.com>

Quentin,

It is not possible until my recent change in ParaView master code that
allows to specify
a font described in a TrueType file.
See https://gitlab.kitware.com/paraview/paraview/merge_requests/2024.
You might want to download the nightly build binaries to give it a try.

Best,
Joachim

*Joachim Pouderoux*, PhD

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


2017-12-04 14:19 GMT-04:00 Quentin d'Avout <quentin at arrivo-loop.com>:

> Hi all,
>
> I'm using 5.0.1, and would like to use other fonts than the default
> Arial/Courrier/Times.
> Any way to add other fonts?
>
> Thanks
> Quentin
> <http://www.arrivo-loop.com/>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/fb78f499/attachment.html>

From quentin at arrivo-loop.com  Mon Dec  4 14:13:28 2017
From: quentin at arrivo-loop.com (Quentin d'Avout)
Date: Mon, 4 Dec 2017 11:13:28 -0800
Subject: [Paraview] More fonts?
In-Reply-To: <CACJ=gTiLEy=ukV9DMRgAwk7dfYp=2X3NKcB3TL1dREjpryMmgA@mail.gmail.com>
References: <CAPaR3=xn3QpSpzPpqzpnpQBobL1W992d2Gmovyiy52P1LonQvA@mail.gmail.com>
 <CACJ=gTiLEy=ukV9DMRgAwk7dfYp=2X3NKcB3TL1dREjpryMmgA@mail.gmail.com>
Message-ID: <CAPaR3=zQvxYYBPQje1pZovRWuPdQDz5SoU94HgpTA8br7hvYhA@mail.gmail.com>

Timely request, then!
Thanks Joachim!

On Mon, Dec 4, 2017 at 10:24 AM, Joachim Pouderoux <
joachim.pouderoux at kitware.com> wrote:

> Quentin,
>
> It is not possible until my recent change in ParaView master code that
> allows to specify
> a font described in a TrueType file.
> See https://gitlab.kitware.com/paraview/paraview/merge_requests/2024.
> You might want to download the nightly build binaries to give it a try.
>
> Best,
> Joachim
>
> *Joachim Pouderoux*, PhD
>
> *Technical Expert - Scientific Computing Team*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2017-12-04 14:19 GMT-04:00 Quentin d'Avout <quentin at arrivo-loop.com>:
>
>> Hi all,
>>
>> I'm using 5.0.1, and would like to use other fonts than the default
>> Arial/Courrier/Times.
>> Any way to add other fonts?
>>
>> Thanks
>> Quentin
>> <http://www.arrivo-loop.com/>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>


-- 

Quentin d?Avout | Aerodynamics
[image: Arrivo Loop] <http://www.arrivo-loop.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/9890e998/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 4364 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/9890e998/attachment.png>

From hectorb at utexas.edu  Mon Dec  4 14:31:43 2017
From: hectorb at utexas.edu (Hector E Barrios Molano)
Date: Mon, 4 Dec 2017 13:31:43 -0600
Subject: [Paraview] Problem loading of properties from .pvtr
Message-ID: <106d6341-26a0-0a15-7cc4-4558892449aa@utexas.edu>

Hi All,

I am loading a .pvtr file into paraview it contains TIME and CYCLE 
within the definition of each .vtr file and a bunch of DataArray 
properties.

When I load the .pvtr file I cannot visualize any property associated 
with Cell/Points. However, when I load the separately the .vtr pieces, 
paraview recognizes the properties.

Additionally, VisIt can load a visualize with no problem such .pvtr file.

What could be the problem with paraview? Is there any way print a log 
while paraview is reading a file?

I am using paraview 5.4.1.


Thank you very much for your help!

Hector
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171204/72d6ed3f/attachment.html>

From salazardetro1 at llnl.gov  Mon Dec  4 14:25:14 2017
From: salazardetro1 at llnl.gov (Salazar De Troya, Miguel)
Date: Mon, 4 Dec 2017 19:25:14 +0000
Subject: [Paraview] ERROR: Cannot read points array from Points in piece 0.
 The data array in the element may be too short.
Message-ID: <E5F2A5C8-881C-4691-943D-668CF0A32073@llnl.gov>

I am trying to open these two files, which are both similar. They are the result of the same simulation, but with different parameters. For some reason, I can open the first, but not the second one. I am attaching them here (could not attach them to the email)

https://quickfileshare.org/3dm/concentration_nsteps_522_p3_000044.vtu

https://quickfileshare.org/3dl/concentration_nsteps_564_p3_000444.vtu

When I open the second file, I get this error:

ERROR: In /Users/kitware/buildbot-slave/8275bd07/source-paraview/VTK/IO/XML/vtkXMLUnstructuredDataReader.cxx, line 523
vtkXMLUnstructuredGridReader (0x7fe66a5b65b0): Cannot read points array from Points in piece 0. The data array in the element may be too short.

Upon inspection, both files are very similar, not sure what can be wrong with the second.

Thanks
Miguel

--

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

From utkarsh.ayachit at kitware.com  Mon Dec  4 15:19:01 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 4 Dec 2017 15:19:01 -0500
Subject: [Paraview] ERROR: Cannot read points array from Points in piece
 0. The data array in the element may be too short.
In-Reply-To: <E5F2A5C8-881C-4691-943D-668CF0A32073@llnl.gov>
References: <E5F2A5C8-881C-4691-943D-668CF0A32073@llnl.gov>
Message-ID: <CADHSJjD1bRJba-ejnzjhWqmRa2KdYmLyBm49hJ0--hPzC4AJsw@mail.gmail.com>

There should be 10137 (3379*3)  values in the "Points" array, looks
like there are only 10117.

Utkarsh

On Mon, Dec 4, 2017 at 2:25 PM, Salazar De Troya, Miguel
<salazardetro1 at llnl.gov> wrote:
> I am trying to open these two files, which are both similar. They are the
> result of the same simulation, but with different parameters. For some
> reason, I can open the first, but not the second one. I am attaching them
> here (could not attach them to the email)
>
>
>
> https://quickfileshare.org/3dm/concentration_nsteps_522_p3_000044.vtu
>
>
>
> https://quickfileshare.org/3dl/concentration_nsteps_564_p3_000444.vtu
>
>
>
> When I open the second file, I get this error:
>
>
>
> ERROR: In
> /Users/kitware/buildbot-slave/8275bd07/source-paraview/VTK/IO/XML/vtkXMLUnstructuredDataReader.cxx,
> line 523
>
> vtkXMLUnstructuredGridReader (0x7fe66a5b65b0): Cannot read points array from
> Points in piece 0. The data array in the element may be too short.
>
>
>
> Upon inspection, both files are very similar, not sure what can be wrong
> with the second.
>
>
>
> Thanks
>
> Miguel
>
>
>
> --
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From zoharl3 at yahoo.com  Mon Dec  4 16:20:50 2017
From: zoharl3 at yahoo.com (Zohar Levi)
Date: Tue, 5 Dec 2017 10:20:50 +1300
Subject: [Paraview] cygwin installation
In-Reply-To: <bb9e840d-abad-8f38-ea87-4e61e4c1bfa2@yahoo.com>
References: <bb9e840d-abad-8f38-ea87-4e61e4c1bfa2@yahoo.com>
Message-ID: <fcd18228-0728-c146-a601-6866bcf8ed49@yahoo.com>


To be more specific, I'm building paraview 5.4.1 (gcc on cygwin), and I 
get the following errors:

$ make
[??? 0%] Built target vtkWrappingTools
[??? 0%] Built target vtkWrapHierarchy
[??? 0%] Building CXX object 
VTK/Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/EncodingCXX.cxx.o
/c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx: In 
constructor 
'vtksys::Encoding::CommandLineArguments::CommandLineArguments(int, const 
char
* const*)':
/c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx:66:34: 
error: 'strdup' was not declared in this scope
 ???????????? this->argv_[i] = strdup(av[i]);
 ??????????????????????????????????????????????????????????????????????????????????????????????????? ^
/c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx: In 
copy constructor 
'vtksys::Encoding::CommandLineArguments::CommandLineArguments(const vtks
ys::Encoding::CommandLineArguments&)':
/c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx:93:60: 
error: 'strdup' was not declared in this scope
 ???????????? this->argv_[i] = other.argv_[i] ? strdup(other.argv_[i]) : 0;
 ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ^
/c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx: In 
member function 'vtksys::Encoding::CommandLineArguments& 
vtksys::Encoding::CommandLineArg
uments::operator=(const vtksys::Encoding::CommandLineArguments&)':
/c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx:108:62: 
error: 'strdup' was not declared in this scope
 ?????????????????? this->argv_[i] = other.argv_[i] ? strdup(other.argv_[i]) : 0;
 ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ^
make[2]: *** 
[VTK/Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/build.make:231: 
VTK/Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/EncodingCXX.cxx.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1105: 
VTK/Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/all] Error 2
make: *** [Makefile:128: all] Error 2

On 25/11/17 18:06, Zohar Levi wrote:
>
> The doc says that cygwin isn't supported:
>
> https://www.paraview.org/Wiki/ParaView:Build_And_Install
>
> Is there a special reason for that?
>
> I thought to give it a try anyway. cmake ran successfully. When I run 
> make, I get a compilation error about not being able to find strdup 
> even though cmake confirmed it. Any ideas?


From paul.melis at surfsara.nl  Tue Dec  5 04:06:47 2017
From: paul.melis at surfsara.nl (Paul Melis)
Date: Tue, 5 Dec 2017 10:06:47 +0100
Subject: [Paraview] Optimus and Windows 10
Message-ID: <c6d38c35-1d6d-ada6-9ae8-390831a9a917@surfsara.nl>

Hi,

In our paraview course two weeks ago we had a student that had trouble 
running Paraview 5.4.1 (official windows 64-bit binaries) under windows 
10. The symptoms were that the main menu bar was invisible and that the 
mouse cursor did not match up with the position of the click event, 
making it very hard to do anything. It seemed the menu bar somehow had 
shifted under the window title bar, causing the misalignment.

As this laptop was an optimus system we figured it might have something 
to do with that. After some fiddling we found that right-clicking on 
paraview.exe and picking Run with graphics processor -> High-performance 
NVIDIA processor solved the problem.

Is this a known issue?

Regards,
Paul

-- 

Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl |

From dani.schmid at gmail.com  Tue Dec  5 04:55:21 2017
From: dani.schmid at gmail.com (Dani Schmid)
Date: Tue, 5 Dec 2017 10:55:21 +0100
Subject: [Paraview] Optimus and Windows 10
In-Reply-To: <c6d38c35-1d6d-ada6-9ae8-390831a9a917@surfsara.nl>
References: <c6d38c35-1d6d-ada6-9ae8-390831a9a917@surfsara.nl>
Message-ID: <CABjhOAjke4nX0QuygrMmsuG_pVZRPXLeLLEtpF0N4S5S1bXJ0g@mail.gmail.com>

Hi,

I have the same problem on my laptop. Same kind of setup, i.e.
integrated Intel and dedicated GeForce graphics card. 'will check if
your solution also solves it here.

Cheers,

Dani


On Tue, Dec 5, 2017 at 10:06 AM, Paul Melis <paul.melis at surfsara.nl> wrote:
> Hi,
>
> In our paraview course two weeks ago we had a student that had trouble
> running Paraview 5.4.1 (official windows 64-bit binaries) under windows 10.
> The symptoms were that the main menu bar was invisible and that the mouse
> cursor did not match up with the position of the click event, making it very
> hard to do anything. It seemed the menu bar somehow had shifted under the
> window title bar, causing the misalignment.
>
> As this laptop was an optimus system we figured it might have something to
> do with that. After some fiddling we found that right-clicking on
> paraview.exe and picking Run with graphics processor -> High-performance
> NVIDIA processor solved the problem.
>
> Is this a known issue?
>
> Regards,
> Paul
>
> --
>
> Paul Melis
> | Visualization group leader & developer | SURFsara |
> | Science Park 140 | 1098 XG Amsterdam |
> | T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl |
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview



-- 
Dani Schmid
Hystadveien 41
3208 Sandefjord
+47 980 00 120

From Mark.Olesen at esi-group.com  Tue Dec  5 05:28:13 2017
From: Mark.Olesen at esi-group.com (Mark Olesen)
Date: Tue, 5 Dec 2017 10:28:13 +0000
Subject: [Paraview] Writing XML VTK Binary files from C++
In-Reply-To: <MWHPR06MB3277DB2A6C40922826065F14803F0@MWHPR06MB3277.namprd06.prod.outlook.com>
References: <MWHPR06MB32771608E8AE41C08A01CB9B80380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <MWHPR06MB327729D24C03776C438AEA1680380@MWHPR06MB3277.namprd06.prod.outlook.com>,
 <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>,
 <MWHPR06MB3277DB2A6C40922826065F14803F0@MWHPR06MB3277.namprd06.prod.outlook.com>
Message-ID: <HE1PR0502MB38685366284A6A24E2094235BD3D0@HE1PR0502MB3868.eurprd05.prod.outlook.com>

Hi Nicholas,

The ostream 'write' method is indeed normally just used for writing a block of binary data, however for your case you can simply wrap things. In fact, you will pretty much have to wrap things to achieve what you want.

For the sake of discussion, we'll call these wrappers NicholasA (ASCII) and NicholasB (BINARY).
The funny names are just to show that there is no special magic involved, just your own logic.

The classes would be contructed with a reference to an ostream, which you'll use inside.
Eg,

class NicholasA
{
    std::ostream& os_;

public:
    NicholasA(std::ostream& os) : os_(os) {}

    void write (double val)
    {
        os_ << val;
    }

....
}

In the binary version

class NicholasB
{
    std::ostream& os_;

public:
    NicholasB(std::ostream& os) : os_(os) {}

    void write (double val)
    {
        os_.write(reinterpret_cast<const char*>(val), sizeof(val));
    }
....
}

You follow the same type of thing for all the data types you want to support.
Finally, you need to fix the binary example to use the base64 layer instead of
a direct write, but now you have the place to intercept the output. To switch between ASCII and BINARY output you choose different classes. This is what is going on behind the scenes in the OpenFOAM code. Of course, by the time you add in additional bells and whistles the purpose gets a bit obfuscated.

I hope this (terse) explanation helps make things a bit clearer.
/mark

________________________________________
From: Stegmeier, Nicholas <Nicholas.Stegmeier at sdstate.edu>
Sent: Monday, December 4, 2017 12:46:26 AM
To: Mark Olesen; paraview at paraview.org
Subject: Re: [Paraview] Writing XML VTK Binary files from C++

Hello again Mark,

I have been working on implementing the binary "inline" option for my VTK XML files. I looked through the OpenFOAM code that you suggested and am having trouble interpreting it.

Would you be able to give me a hint as to where I should be looking in foamVtkBase64Layer? For example, in my current code I write the array data like this:

  int i,j;
  ofstream lfile;

  lfile << "\t\t\t\t<DataArray type=\"Float32\" Name=\"rho\" format=\"ascii\">\n";
  lfile << "\t\t\t\t\t";
    for (j = firsty-1; j <= lasty+1; j++){
    for (i = firstx-1; i <= lastx+1; i++){
      lfile << rho[j][i][t] << " ";
    }
    }
  lfile << "\n";
  lfile << "\t\t\t\t</DataArray>\n";

 I have not used the write function in C++ before. Is there a quick way to explain how the above code would be modified (with the contents of "rho" being written to the file)? I wonder if I will run into a problem because of how I have set up the array with the 't' index last.

Thank you so much for your help so far.

Nicholas Stegmeier
Graduate Student
Mathematics and Statistics
South Dakota State University


________________________________
From: Mark Olesen <Mark.Olesen at esi-group.com>
Sent: Friday, December 1, 2017 1:34:58 AM
To: Stegmeier, Nicholas; paraview at paraview.org
Subject: Re: [Paraview] Writing XML VTK Binary files from C++

When you say "writing binary", you need to distinguish between three
possibilities.
1) writing binary "inline" (actually base64 encoded)
2) writing binary "append" (actually base64 encoded)
3) writing raw binary "append" (really raw binary)

Since you already have ASCII writing working and its content is
"inline", it won't take much more to get binary inline working.
By "inline", I mean when the output is placed between the <xxx> </xxx>
markers. Eg,
     <DataArray ...>
         content
     </DataArray>

For the binary case, the content is written as base64-encoded data,
which means that your output writer for these sections needs to pass the
content through a base64 layer to do the encoding for you.

If it helps as reference, we have the same thing in OpenFOAM, except
that we only write vtu and vtp files (we don't have rectilinear meshes).

In the repo https://develop.openfoam.com/Development/OpenFOAM-plus
we have a foamVtkBase64Formatter and a foamVtkBase64Layer (both under
src/fileFormats/vtk/format/) that add a base64Layer to encode and output
as base64 (src/OpenFOAM/db/IOstreams/hashes/base64Layer.[CH]).

You'll see that the foamVtkBase64Layer and base64Layer are quite low
level means of adding an tiny encoding buffer (3 chars size) to
intercept output prior to sending through to a std::ostream. It take
very little effort to adopt for your output and thus quite easy to drop
in instead of your current ASCII outputter.  For it too work easily,
however, you should make sure that you need to generate your output
content with a write() method instead of using '<<'. This allows
somewhat easy switching between something like a foamVtkAsciiFormatter
and the binary version, but more importantly it makes it easier to track
the output state.

When browsing through the code, you may also notice that we have support
for writing in appended format (raw and base64). However, I would not
advise you to tackle that immediately. There are a few more things to
watch out for here, but more importantly it will change many more things
on the calling side.

I hope this information helps you.
/mark

--
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
www.openfoam.com<http://www.openfoam.com> | www.esi-group.com<http://www.esi-group.com> | mark.olesen at esi-group.com


On 11/30/17 18:00, Stegmeier, Nicholas wrote:
> Hello,
>
> I am new to Paraview and C++ coming from a mostly mathematics
> background. I am emailing to get resources or help on writing binary XML
> VTK files from C++.
>
> I have finally succeeded in using the ASCII XML VTK format for a 2D
> rectilinear CFD application. My ".pvtr" file is shown below.
>
> How can I write this file and my other XML VTK files in binary from C++?
> Do I need a special C++ library?

From jonathan.borduas at caboma.com  Tue Dec  5 06:40:47 2017
From: jonathan.borduas at caboma.com (Jonathan Borduas)
Date: Tue, 5 Dec 2017 11:40:47 +0000
Subject: [Paraview] Optimus and Windows 10
In-Reply-To: <c6d38c35-1d6d-ada6-9ae8-390831a9a917@surfsara.nl>
References: <c6d38c35-1d6d-ada6-9ae8-390831a9a917@surfsara.nl>
Message-ID: <CY4PR15MB128844018ACF5C421141D7F6FD3D0@CY4PR15MB1288.namprd15.prod.outlook.com>

Was the laptop running with the intel gpu ? If so, it might be related to an Intel driver bug that was reported on the QT and Intel websites.

https://bugreports.qt.io/browse/QTBUG-40485

https://software.intel.com/en-us/node/744153

Jonathan Borduas

_________________________
From: Paul Melis <paul.melis at surfsara.nl<mailto:paul.melis at surfsara.nl>>
Sent: Tuesday, December 5, 2017 04:16
Subject: [Paraview] Optimus and Windows 10
To: <paraview at paraview.org<mailto:paraview at paraview.org>>


Hi,

In our paraview course two weeks ago we had a student that had trouble
running Paraview 5.4.1 (official windows 64-bit binaries) under windows
10. The symptoms were that the main menu bar was invisible and that the
mouse cursor did not match up with the position of the click event,
making it very hard to do anything. It seemed the menu bar somehow had
shifted under the window title bar, causing the misalignment.

As this laptop was an optimus system we figured it might have something
to do with that. After some fiddling we found that right-clicking on
paraview.exe and picking Run with graphics processor -> High-performance
NVIDIA processor solved the problem.

Is this a known issue?

Regards,
Paul

--

Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.melis at surfsara.nl<mailto:paul.melis at surfsara.nl> | www.surfsara.nl<http://www.surfsara.nl> |
_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

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

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

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

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


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

From heiland at iu.edu  Tue Dec  5 06:52:31 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Tue, 5 Dec 2017 11:52:31 +0000
Subject: [Paraview] background color not saved in state
Message-ID: <E85B00F1-789C-458E-8FA6-11CB2CC3F39B@iu.edu>

Is this the expected behavior?

Related: https://www.paraview.org/Bug/bug_relationship_graph.php?bug_id=8722&graph=relation

thanks, Randy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/2c400e7b/attachment.html>

From Mark.Olesen at esi-group.com  Tue Dec  5 07:06:13 2017
From: Mark.Olesen at esi-group.com (Mark Olesen)
Date: Tue, 5 Dec 2017 12:06:13 +0000
Subject: [Paraview] Writing XML VTK Binary files from C++
In-Reply-To: <HE1PR0502MB38685366284A6A24E2094235BD3D0@HE1PR0502MB3868.eurprd05.prod.outlook.com>
References: <MWHPR06MB32771608E8AE41C08A01CB9B80380@MWHPR06MB3277.namprd06.prod.outlook.com>
 <MWHPR06MB327729D24C03776C438AEA1680380@MWHPR06MB3277.namprd06.prod.outlook.com>,
 <c01680af-a688-b8a9-f5c4-f017abeb1e2c@esi-group.com>,
 <MWHPR06MB3277DB2A6C40922826065F14803F0@MWHPR06MB3277.namprd06.prod.outlook.com>,
 <HE1PR0502MB38685366284A6A24E2094235BD3D0@HE1PR0502MB3868.eurprd05.prod.outlook.com>
Message-ID: <HE1PR0502MB38683248798307BAD8926FBCBD3D0@HE1PR0502MB3868.eurprd05.prod.outlook.com>

sorry about the email code quality, should of course have been

    reinterpret_cast<const char*>(&val),...


________________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Mark Olesen <Mark.Olesen at esi-group.com>
Sent: Tuesday, December 5, 2017 11:28:13 AM
To: Stegmeier, Nicholas; paraview at paraview.org
Subject: Re: [Paraview] Writing XML VTK Binary files from C++

[This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]

Hi Nicholas,

The ostream 'write' method is indeed normally just used for writing a block of binary data, however for your case you can simply wrap things. In fact, you will pretty much have to wrap things to achieve what you want.

For the sake of discussion, we'll call these wrappers NicholasA (ASCII) and NicholasB (BINARY).
The funny names are just to show that there is no special magic involved, just your own logic.

The classes would be contructed with a reference to an ostream, which you'll use inside.
Eg,

class NicholasA
{
    std::ostream& os_;

public:
    NicholasA(std::ostream& os) : os_(os) {}

    void write (double val)
    {
        os_ << val;
    }

....
}

In the binary version

class NicholasB
{
    std::ostream& os_;

public:
    NicholasB(std::ostream& os) : os_(os) {}

    void write (double val)
    {
        os_.write(reinterpret_cast<const char*>(val), sizeof(val));
    }
....
}

You follow the same type of thing for all the data types you want to support.
Finally, you need to fix the binary example to use the base64 layer instead of
a direct write, but now you have the place to intercept the output. To switch between ASCII and BINARY output you choose different classes. This is what is going on behind the scenes in the OpenFOAM code. Of course, by the time you add in additional bells and whistles the purpose gets a bit obfuscated.

I hope this (terse) explanation helps make things a bit clearer.
/mark

________________________________________
From: Stegmeier, Nicholas <Nicholas.Stegmeier at sdstate.edu>
Sent: Monday, December 4, 2017 12:46:26 AM
To: Mark Olesen; paraview at paraview.org
Subject: Re: [Paraview] Writing XML VTK Binary files from C++

Hello again Mark,

I have been working on implementing the binary "inline" option for my VTK XML files. I looked through the OpenFOAM code that you suggested and am having trouble interpreting it.

Would you be able to give me a hint as to where I should be looking in foamVtkBase64Layer? For example, in my current code I write the array data like this:

  int i,j;
  ofstream lfile;

  lfile << "\t\t\t\t<DataArray type=\"Float32\" Name=\"rho\" format=\"ascii\">\n";
  lfile << "\t\t\t\t\t";
    for (j = firsty-1; j <= lasty+1; j++){
    for (i = firstx-1; i <= lastx+1; i++){
      lfile << rho[j][i][t] << " ";
    }
    }
  lfile << "\n";
  lfile << "\t\t\t\t</DataArray>\n";

 I have not used the write function in C++ before. Is there a quick way to explain how the above code would be modified (with the contents of "rho" being written to the file)? I wonder if I will run into a problem because of how I have set up the array with the 't' index last.

Thank you so much for your help so far.

Nicholas Stegmeier
Graduate Student
Mathematics and Statistics
South Dakota State University


________________________________
From: Mark Olesen <Mark.Olesen at esi-group.com>
Sent: Friday, December 1, 2017 1:34:58 AM
To: Stegmeier, Nicholas; paraview at paraview.org
Subject: Re: [Paraview] Writing XML VTK Binary files from C++

When you say "writing binary", you need to distinguish between three
possibilities.
1) writing binary "inline" (actually base64 encoded)
2) writing binary "append" (actually base64 encoded)
3) writing raw binary "append" (really raw binary)

Since you already have ASCII writing working and its content is
"inline", it won't take much more to get binary inline working.
By "inline", I mean when the output is placed between the <xxx> </xxx>
markers. Eg,
     <DataArray ...>
         content
     </DataArray>

For the binary case, the content is written as base64-encoded data,
which means that your output writer for these sections needs to pass the
content through a base64 layer to do the encoding for you.

If it helps as reference, we have the same thing in OpenFOAM, except
that we only write vtu and vtp files (we don't have rectilinear meshes).

In the repo https://develop.openfoam.com/Development/OpenFOAM-plus
we have a foamVtkBase64Formatter and a foamVtkBase64Layer (both under
src/fileFormats/vtk/format/) that add a base64Layer to encode and output
as base64 (src/OpenFOAM/db/IOstreams/hashes/base64Layer.[CH]).

You'll see that the foamVtkBase64Layer and base64Layer are quite low
level means of adding an tiny encoding buffer (3 chars size) to
intercept output prior to sending through to a std::ostream. It take
very little effort to adopt for your output and thus quite easy to drop
in instead of your current ASCII outputter.  For it too work easily,
however, you should make sure that you need to generate your output
content with a write() method instead of using '<<'. This allows
somewhat easy switching between something like a foamVtkAsciiFormatter
and the binary version, but more importantly it makes it easier to track
the output state.

When browsing through the code, you may also notice that we have support
for writing in appended format (raw and base64). However, I would not
advise you to tackle that immediately. There are a few more things to
watch out for here, but more importantly it will change many more things
on the calling side.

I hope this information helps you.
/mark

--
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
www.openfoam.com<http://www.openfoam.com> | www.esi-group.com<http://www.esi-group.com> | mark.olesen at esi-group.com


On 11/30/17 18:00, Stegmeier, Nicholas wrote:
> Hello,
>
> I am new to Paraview and C++ coming from a mostly mathematics
> background. I am emailing to get resources or help on writing binary XML
> VTK files from C++.
>
> I have finally succeeded in using the ASCII XML VTK format for a 2D
> rectilinear CFD application. My ".pvtr" file is shown below.
>
> How can I write this file and my other XML VTK files in binary from C++?
> Do I need a special C++ library?
_______________________________________________
Powered by www.kitware.com

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

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

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

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

From aron.helser at kitware.com  Tue Dec  5 08:13:19 2017
From: aron.helser at kitware.com (Aron Helser)
Date: Tue, 5 Dec 2017 08:13:19 -0500
Subject: [Paraview] Optimus and Windows 10
In-Reply-To: <CY4PR15MB128844018ACF5C421141D7F6FD3D0@CY4PR15MB1288.namprd15.prod.outlook.com>
References: <c6d38c35-1d6d-ada6-9ae8-390831a9a917@surfsara.nl>
 <CY4PR15MB128844018ACF5C421141D7F6FD3D0@CY4PR15MB1288.namprd15.prod.outlook.com>
Message-ID: <CAF2skS5YdEkfc8s_Lw_0XYjVA3q3HqnydcbFpW0+Z0KVvoVL_w@mail.gmail.com>

Yes, that Intel driver bug is known to affect ParaView:
https://gitlab.kitware.com/paraview/paraview/issues/17499

Regards,
Aron

On Tue, Dec 5, 2017 at 6:40 AM, Jonathan Borduas <
jonathan.borduas at caboma.com> wrote:

> Was the laptop running with the intel gpu ? If so, it might be related to
> an Intel driver bug that was reported on the QT and Intel websites.
>
> https://bugreports.qt.io/browse/QTBUG-40485
>
> https://software.intel.com/en-us/node/744153
>
> Jonathan Borduas
>
> _________________________
> From: Paul Melis <paul.melis at surfsara.nl>
> Sent: Tuesday, December 5, 2017 04:16
> Subject: [Paraview] Optimus and Windows 10
> To: <paraview at paraview.org>
>
>
>
> Hi,
>
> In our paraview course two weeks ago we had a student that had trouble
> running Paraview 5.4.1 (official windows 64-bit binaries) under windows
> 10. The symptoms were that the main menu bar was invisible and that the
> mouse cursor did not match up with the position of the click event,
> making it very hard to do anything. It seemed the menu bar somehow had
> shifted under the window title bar, causing the misalignment.
>
> As this laptop was an optimus system we figured it might have something
> to do with that. After some fiddling we found that right-clicking on
> paraview.exe and picking Run with graphics processor -> High-performance
> NVIDIA processor solved the problem.
>
> Is this a known issue?
>
> Regards,
> Paul
>
> --
>
> Paul Melis
> | Visualization group leader & developer | SURFsara |
> | Science Park 140 | 1098 XG Amsterdam |
> | T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl |
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/f47fcb45/attachment.html>

From cory.quammen at kitware.com  Tue Dec  5 08:58:59 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 5 Dec 2017 08:58:59 -0500
Subject: [Paraview] background color not saved in state
In-Reply-To: <E85B00F1-789C-458E-8FA6-11CB2CC3F39B@iu.edu>
References: <E85B00F1-789C-458E-8FA6-11CB2CC3F39B@iu.edu>
Message-ID: <CAB5Fpx6_rR8e9vpb04kF8gMR4SWtxufH11yyyJUHPPpq6MwUwQ@mail.gmail.com>

Hmm, I can't reproduce with the following:

* Start ParaView
* Add Wavelet
* Change background color.
* Save state, reset the session, and reload the state.

Can you give step-by-step instructions for how to reproduce?

By the way, if you wish to discuss in the issue tracker, the original
Mantis issue has been copied to GitLab:
https://gitlab.kitware.com/paraview/paraview/issues/8722

Thanks,
Cory

On Tue, Dec 5, 2017 at 6:52 AM, Heiland, Randy <heiland at iu.edu> wrote:
> Is this the expected behavior?
>
> Related:
> https://www.paraview.org/Bug/bug_relationship_graph.php?bug_id=8722&graph=relation
>
> thanks, Randy
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



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

From ben.boeckel at kitware.com  Tue Dec  5 10:18:52 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Tue, 5 Dec 2017 10:18:52 -0500
Subject: [Paraview] cygwin installation
In-Reply-To: <fcd18228-0728-c146-a601-6866bcf8ed49@yahoo.com>
References: <bb9e840d-abad-8f38-ea87-4e61e4c1bfa2@yahoo.com>
 <fcd18228-0728-c146-a601-6866bcf8ed49@yahoo.com>
Message-ID: <20171205151852.GA10996@megas.kitware.com>

On Tue, Dec 05, 2017 at 10:20:50 +1300, Zohar Levi via ParaView wrote:
> To be more specific, I'm building paraview 5.4.1 (gcc on cygwin), and I 
> get the following errors:
> 
> $ make
> [? 0%] Built target vtkWrappingTools
> [? 0%] Built target vtkWrapHierarchy
> [? 0%] Building CXX object 
> VTK/Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/EncodingCXX.cxx.o
> /c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx: In 
> constructor 
> 'vtksys::Encoding::CommandLineArguments::CommandLineArguments(int, const 
> char
> * const*)':
> /c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx:66:34: 
> error: 'strdup' was not declared in this scope

kwsys should certainly be supported on cygwin. It has <string.h>
included at the top. Brad?

> On 25/11/17 18:06, Zohar Levi wrote:
> > The doc says that cygwin isn't supported:
> >
> > https://www.paraview.org/Wiki/ParaView:Build_And_Install

It's not a platform we test on nor hold back releases for if it is
broken. It's on a "if it works, great." support basis. But, if there are
patches that fix it, we'll take a look at them.

--Ben

From heiland at iu.edu  Tue Dec  5 11:51:38 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Tue, 5 Dec 2017 16:51:38 +0000
Subject: [Paraview] background color not saved in state
In-Reply-To: <CAB5Fpx6_rR8e9vpb04kF8gMR4SWtxufH11yyyJUHPPpq6MwUwQ@mail.gmail.com>
References: <E85B00F1-789C-458E-8FA6-11CB2CC3F39B@iu.edu>
 <CAB5Fpx6_rR8e9vpb04kF8gMR4SWtxufH11yyyJUHPPpq6MwUwQ@mail.gmail.com>
Message-ID: <328BE18A-61F7-4194-8189-28A7D5818110@iu.edu>

Strange. I just did the same steps and when I reload, it momentarily flashes the background in black (as I?d saved it), but then switches to white.

ParaView-5.4.1-Qt5-OpenGL2-MPI-OSX10.8-64bit.dmg

> On Dec 5, 2017, at 8:58 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> 
> Hmm, I can't reproduce with the following:
> 
> * Start ParaView
> * Add Wavelet
> * Change background color.
> * Save state, reset the session, and reload the state.
> 
> Can you give step-by-step instructions for how to reproduce?
> 
> By the way, if you wish to discuss in the issue tracker, the original
> Mantis issue has been copied to GitLab:
> https://gitlab.kitware.com/paraview/paraview/issues/8722
> 
> Thanks,
> Cory
> 
> On Tue, Dec 5, 2017 at 6:52 AM, Heiland, Randy <heiland at iu.edu> wrote:
>> Is this the expected behavior?
>> 
>> Related:
>> https://www.paraview.org/Bug/bug_relationship_graph.php?bug_id=8722&graph=relation
>> 
>> thanks, Randy
>> 
>> _______________________________________________
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>> 
> 
> 
> 
> -- 
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.


From wascott at sandia.gov  Tue Dec  5 12:58:20 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 5 Dec 2017 17:58:20 +0000
Subject: [Paraview] [EXTERNAL] Re:  background color not saved in state
In-Reply-To: <328BE18A-61F7-4194-8189-28A7D5818110@iu.edu>
References: <E85B00F1-789C-458E-8FA6-11CB2CC3F39B@iu.edu>
 <CAB5Fpx6_rR8e9vpb04kF8gMR4SWtxufH11yyyJUHPPpq6MwUwQ@mail.gmail.com>
 <328BE18A-61F7-4194-8189-28A7D5818110@iu.edu>
Message-ID: <d9248b2ebd9c45ba97e082d26bbfe062@ES01AMSNLNT.srn.sandia.gov>

Cory,
I've replicated this one.  It is still in master.  I wrote it up a while ago here: https://gitlab.kitware.com/paraview/paraview/issues/16879.  I will update the bug with exactly how to replicate.

Alan

> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
> Heiland, Randy
> Sent: Tuesday, December 5, 2017 9:52 AM
> To: Quammen, Cory (External Contacts) <cory.quammen at kitware.com>
> Cc: ParaView <paraview at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview] background color not saved in state
> 
> Strange. I just did the same steps and when I reload, it momentarily flashes
> the background in black (as I?d saved it), but then switches to white.
> 
> ParaView-5.4.1-Qt5-OpenGL2-MPI-OSX10.8-64bit.dmg
> 
> > On Dec 5, 2017, at 8:58 AM, Cory Quammen
> <cory.quammen at kitware.com> wrote:
> >
> > Hmm, I can't reproduce with the following:
> >
> > * Start ParaView
> > * Add Wavelet
> > * Change background color.
> > * Save state, reset the session, and reload the state.
> >
> > Can you give step-by-step instructions for how to reproduce?
> >
> > By the way, if you wish to discuss in the issue tracker, the original
> > Mantis issue has been copied to GitLab:
> > https://gitlab.kitware.com/paraview/paraview/issues/8722
> >
> > Thanks,
> > Cory
> >
> > On Tue, Dec 5, 2017 at 6:52 AM, Heiland, Randy <heiland at iu.edu> wrote:
> >> Is this the expected behavior?
> >>
> >> Related:
> >>
> https://www.paraview.org/Bug/bug_relationship_graph.php?bug_id=8722&
> g
> >> raph=relation
> >>
> >> thanks, Randy
> >>
> >> _______________________________________________
> >> Powered by www.kitware.com
> >>
> >> Visit other Kitware open-source projects at
> >> http://www.kitware.com/opensource/opensource.html
> >>
> >> Please keep messages on-topic and check the ParaView Wiki at:
> >> http://paraview.org/Wiki/ParaView
> >>
> >> Search the list archives at: http://markmail.org/search/?q=ParaView
> >>
> >> Follow this link to subscribe/unsubscribe:
> >> http://public.kitware.com/mailman/listinfo/paraview
> >>
> >
> >
> >
> > --
> > Cory Quammen
> > 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
> 
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

From cory.quammen at kitware.com  Tue Dec  5 13:11:49 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 5 Dec 2017 13:11:49 -0500
Subject: [Paraview] [EXTERNAL] Re:  background color not saved in state
In-Reply-To: <d9248b2ebd9c45ba97e082d26bbfe062@ES01AMSNLNT.srn.sandia.gov>
References: <E85B00F1-789C-458E-8FA6-11CB2CC3F39B@iu.edu>
 <CAB5Fpx6_rR8e9vpb04kF8gMR4SWtxufH11yyyJUHPPpq6MwUwQ@mail.gmail.com>
 <328BE18A-61F7-4194-8189-28A7D5818110@iu.edu>
 <d9248b2ebd9c45ba97e082d26bbfe062@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CAB5Fpx4GaAib6EsoE8hZm8mXF1EHCEUmnYAK9bvbvrO_gxeccg@mail.gmail.com>

Great, thanks Alan.

Cory

On Tue, Dec 5, 2017 at 12:58 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> Cory,
> I've replicated this one.  It is still in master.  I wrote it up a while ago here: https://gitlab.kitware.com/paraview/paraview/issues/16879.  I will update the bug with exactly how to replicate.
>
> Alan
>
>> -----Original Message-----
>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
>> Heiland, Randy
>> Sent: Tuesday, December 5, 2017 9:52 AM
>> To: Quammen, Cory (External Contacts) <cory.quammen at kitware.com>
>> Cc: ParaView <paraview at paraview.org>
>> Subject: [EXTERNAL] Re: [Paraview] background color not saved in state
>>
>> Strange. I just did the same steps and when I reload, it momentarily flashes
>> the background in black (as I?d saved it), but then switches to white.
>>
>> ParaView-5.4.1-Qt5-OpenGL2-MPI-OSX10.8-64bit.dmg
>>
>> > On Dec 5, 2017, at 8:58 AM, Cory Quammen
>> <cory.quammen at kitware.com> wrote:
>> >
>> > Hmm, I can't reproduce with the following:
>> >
>> > * Start ParaView
>> > * Add Wavelet
>> > * Change background color.
>> > * Save state, reset the session, and reload the state.
>> >
>> > Can you give step-by-step instructions for how to reproduce?
>> >
>> > By the way, if you wish to discuss in the issue tracker, the original
>> > Mantis issue has been copied to GitLab:
>> > https://gitlab.kitware.com/paraview/paraview/issues/8722
>> >
>> > Thanks,
>> > Cory
>> >
>> > On Tue, Dec 5, 2017 at 6:52 AM, Heiland, Randy <heiland at iu.edu> wrote:
>> >> Is this the expected behavior?
>> >>
>> >> Related:
>> >>
>> https://www.paraview.org/Bug/bug_relationship_graph.php?bug_id=8722&
>> g
>> >> raph=relation
>> >>
>> >> thanks, Randy
>> >>
>> >> _______________________________________________
>> >> Powered by www.kitware.com
>> >>
>> >> Visit other Kitware open-source projects at
>> >> http://www.kitware.com/opensource/opensource.html
>> >>
>> >> Please keep messages on-topic and check the ParaView Wiki at:
>> >> http://paraview.org/Wiki/ParaView
>> >>
>> >> Search the list archives at: http://markmail.org/search/?q=ParaView
>> >>
>> >> Follow this link to subscribe/unsubscribe:
>> >> http://public.kitware.com/mailman/listinfo/paraview
>> >>
>> >
>> >
>> >
>> > --
>> > Cory Quammen
>> > 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
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview



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

From wspear at cs.uoregon.edu  Tue Dec  5 14:10:14 2017
From: wspear at cs.uoregon.edu (Wyatt Spear)
Date: Tue, 5 Dec 2017 11:10:14 -0800
Subject: [Paraview] Segfault with 'Hover Cells' over 3d glyphs
Message-ID: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>

Greetings,

I'm using the SC17 preview of 5.5 of ParaView. I first noticed this error
with my own dataset but it appears with the simple test.csv I've included.
To reproduce the segfault:

Load the attached (or presumably any) CSV points file.
Run the TableToPoints filter.
Assign the X/Y/Z column dropdowns to the x coord/y coord/z coord values.
Hit Apply
Hit the 'Hover Cells On' button in the 3d display and mouse over a point to
confirm it works.
In the 'Representation' drop down box select "3D Glyphs".
In the 'Glyph Type' drop down box select "Box" (I wasn't able to reproduce
the error with arrows)
Hover over one of the resulting box glyphs for instant segfault.

Command line output from this session was:

Generic Warning: In
/home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
line 511
Failed to locate property: OSPRayMaterialLibrary

Generic Warning: In
/home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
line 831
Call not supported for the current property type.

Segmentation fault (core dumped)

Regards,
Wyatt Spear
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/c0ea252f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.csv
Type: text/csv
Size: 142 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/c0ea252f/attachment.csv>

From dave.demarle at kitware.com  Tue Dec  5 14:29:26 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 5 Dec 2017 14:29:26 -0500
Subject: [Paraview] Segfault with 'Hover Cells' over 3d glyphs
In-Reply-To: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>
References: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>
Message-ID: <CANjZAi-+ZkT1acufSOVUDefNeLdaW0v446-DjiqZZP5orC9TvQ@mail.gmail.com>

The output warnings you are seeing are unrelated and fixed in master.

Can reproduce the bug with 5.4.1 binary on linux.




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

On Tue, Dec 5, 2017 at 2:10 PM, Wyatt Spear <wspear at cs.uoregon.edu> wrote:

> Greetings,
>
> I'm using the SC17 preview of 5.5 of ParaView. I first noticed this error
> with my own dataset but it appears with the simple test.csv I've included.
> To reproduce the segfault:
>
> Load the attached (or presumably any) CSV points file.
> Run the TableToPoints filter.
> Assign the X/Y/Z column dropdowns to the x coord/y coord/z coord values.
> Hit Apply
> Hit the 'Hover Cells On' button in the 3d display and mouse over a point
> to confirm it works.
> In the 'Representation' drop down box select "3D Glyphs".
> In the 'Glyph Type' drop down box select "Box" (I wasn't able to reproduce
> the error with arrows)
> Hover over one of the resulting box glyphs for instant segfault.
>
> Command line output from this session was:
>
> Generic Warning: In /home/buildslave/dashboards/
> buildbot/paraview-pvbinsdash-linux-shared-release_
> superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
> line 511
> Failed to locate property: OSPRayMaterialLibrary
>
> Generic Warning: In /home/buildslave/dashboards/
> buildbot/paraview-pvbinsdash-linux-shared-release_
> superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
> line 831
> Call not supported for the current property type.
>
> Segmentation fault (core dumped)
>
> Regards,
> Wyatt Spear
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/b445a7ca/attachment.html>

From wspear at cs.uoregon.edu  Tue Dec  5 14:59:06 2017
From: wspear at cs.uoregon.edu (Wyatt Spear)
Date: Tue, 5 Dec 2017 11:59:06 -0800
Subject: [Paraview] Segfault with 'Hover Cells' over 3d glyphs
In-Reply-To: <CANjZAi-+ZkT1acufSOVUDefNeLdaW0v446-DjiqZZP5orC9TvQ@mail.gmail.com>
References: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>
 <CANjZAi-+ZkT1acufSOVUDefNeLdaW0v446-DjiqZZP5orC9TvQ@mail.gmail.com>
Message-ID: <CAHQ20oePBaM04fdJwvJ-AyJT+3czTpaK-mVZmVZTt0KUwh+ezQ@mail.gmail.com>

Nope, 5.4.1 seems to work correctly.
=Wyatt

On Tue, Dec 5, 2017 at 11:29 AM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> The output warnings you are seeing are unrelated and fixed in master.
>
> Can reproduce the bug with 5.4.1 binary on linux.
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> Principal Engineer
> 21 Corporate Drive
> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
> Clifton Park, NY 12065
> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
> -8662
> Phone: 518-881-4909 <(518)%20881-4909>
>
> On Tue, Dec 5, 2017 at 2:10 PM, Wyatt Spear <wspear at cs.uoregon.edu> wrote:
>
>> Greetings,
>>
>> I'm using the SC17 preview of 5.5 of ParaView. I first noticed this error
>> with my own dataset but it appears with the simple test.csv I've included.
>> To reproduce the segfault:
>>
>> Load the attached (or presumably any) CSV points file.
>> Run the TableToPoints filter.
>> Assign the X/Y/Z column dropdowns to the x coord/y coord/z coord values.
>> Hit Apply
>> Hit the 'Hover Cells On' button in the 3d display and mouse over a point
>> to confirm it works.
>> In the 'Representation' drop down box select "3D Glyphs".
>> In the 'Glyph Type' drop down box select "Box" (I wasn't able to
>> reproduce the error with arrows)
>> Hover over one of the resulting box glyphs for instant segfault.
>>
>> Command line output from this session was:
>>
>> Generic Warning: In /home/buildslave/dashboards/bu
>> ildbot/paraview-pvbinsdash-linux-shared-release_superbuild/
>> source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
>> line 511
>> Failed to locate property: OSPRayMaterialLibrary
>>
>> Generic Warning: In /home/buildslave/dashboards/bu
>> ildbot/paraview-pvbinsdash-linux-shared-release_superbuild/
>> source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
>> line 831
>> Call not supported for the current property type.
>>
>> Segmentation fault (core dumped)
>>
>> Regards,
>> Wyatt Spear
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/b872c357/attachment.html>

From dave.demarle at kitware.com  Tue Dec  5 15:00:32 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 5 Dec 2017 15:00:32 -0500
Subject: [Paraview] Segfault with 'Hover Cells' over 3d glyphs
In-Reply-To: <CAHQ20oePBaM04fdJwvJ-AyJT+3czTpaK-mVZmVZTt0KUwh+ezQ@mail.gmail.com>
References: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>
 <CANjZAi-+ZkT1acufSOVUDefNeLdaW0v446-DjiqZZP5orC9TvQ@mail.gmail.com>
 <CAHQ20oePBaM04fdJwvJ-AyJT+3czTpaK-mVZmVZTt0KUwh+ezQ@mail.gmail.com>
Message-ID: <CANjZAi_tSYbZDQkBb58Uci9i2F2TJ6AawYUGtn60w2_b5u3Fsw@mail.gmail.com>

Crashes for me.


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

On Tue, Dec 5, 2017 at 2:59 PM, Wyatt Spear <wspear at cs.uoregon.edu> wrote:

> Nope, 5.4.1 seems to work correctly.
> =Wyatt
>
> On Tue, Dec 5, 2017 at 11:29 AM, David E DeMarle <dave.demarle at kitware.com
> > wrote:
>
>> The output warnings you are seeing are unrelated and fixed in master.
>>
>> Can reproduce the bug with 5.4.1 binary on linux.
>>
>>
>>
>>
>> David E DeMarle
>> Kitware, Inc.
>> Principal Engineer
>> 21 Corporate Drive
>> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
>> Clifton Park, NY 12065
>> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
>> -8662
>> Phone: 518-881-4909 <(518)%20881-4909>
>>
>> On Tue, Dec 5, 2017 at 2:10 PM, Wyatt Spear <wspear at cs.uoregon.edu>
>> wrote:
>>
>>> Greetings,
>>>
>>> I'm using the SC17 preview of 5.5 of ParaView. I first noticed this
>>> error with my own dataset but it appears with the simple test.csv I've
>>> included. To reproduce the segfault:
>>>
>>> Load the attached (or presumably any) CSV points file.
>>> Run the TableToPoints filter.
>>> Assign the X/Y/Z column dropdowns to the x coord/y coord/z coord values.
>>> Hit Apply
>>> Hit the 'Hover Cells On' button in the 3d display and mouse over a point
>>> to confirm it works.
>>> In the 'Representation' drop down box select "3D Glyphs".
>>> In the 'Glyph Type' drop down box select "Box" (I wasn't able to
>>> reproduce the error with arrows)
>>> Hover over one of the resulting box glyphs for instant segfault.
>>>
>>> Command line output from this session was:
>>>
>>> Generic Warning: In /home/buildslave/dashboards/bu
>>> ildbot/paraview-pvbinsdash-linux-shared-release_superbuild/s
>>> ource-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
>>> line 511
>>> Failed to locate property: OSPRayMaterialLibrary
>>>
>>> Generic Warning: In /home/buildslave/dashboards/bu
>>> ildbot/paraview-pvbinsdash-linux-shared-release_superbuild/s
>>> ource-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
>>> line 831
>>> Call not supported for the current property type.
>>>
>>> Segmentation fault (core dumped)
>>>
>>> Regards,
>>> Wyatt Spear
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/f60ebeef/attachment.html>

From wspear at cs.uoregon.edu  Tue Dec  5 15:06:29 2017
From: wspear at cs.uoregon.edu (Wyatt Spear)
Date: Tue, 5 Dec 2017 12:06:29 -0800
Subject: [Paraview] Segfault with 'Hover Cells' over 3d glyphs
In-Reply-To: <CANjZAi_tSYbZDQkBb58Uci9i2F2TJ6AawYUGtn60w2_b5u3Fsw@mail.gmail.com>
References: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>
 <CANjZAi-+ZkT1acufSOVUDefNeLdaW0v446-DjiqZZP5orC9TvQ@mail.gmail.com>
 <CAHQ20oePBaM04fdJwvJ-AyJT+3czTpaK-mVZmVZTt0KUwh+ezQ@mail.gmail.com>
 <CANjZAi_tSYbZDQkBb58Uci9i2F2TJ6AawYUGtn60w2_b5u3Fsw@mail.gmail.com>
Message-ID: <CAHQ20od6jYb8k3gzROKB0_EV5c6OnjfiZAL7MffOzbwhr50t_A@mail.gmail.com>

I just tried it with my larger data set (easier to select individual cells)
and it crashed with 5.4.1. I'm not sure what the difference was with the
smaller data set in 5.4.1 that let it work.
=Wyatt

On Tue, Dec 5, 2017 at 12:00 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> Crashes for me.
>
>
> David E DeMarle
> Kitware, Inc.
> Principal Engineer
> 21 Corporate Drive
> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
> Clifton Park, NY 12065
> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
> -8662
> Phone: 518-881-4909 <(518)%20881-4909>
>
> On Tue, Dec 5, 2017 at 2:59 PM, Wyatt Spear <wspear at cs.uoregon.edu> wrote:
>
>> Nope, 5.4.1 seems to work correctly.
>> =Wyatt
>>
>> On Tue, Dec 5, 2017 at 11:29 AM, David E DeMarle <
>> dave.demarle at kitware.com> wrote:
>>
>>> The output warnings you are seeing are unrelated and fixed in master.
>>>
>>> Can reproduce the bug with 5.4.1 binary on linux.
>>>
>>>
>>>
>>>
>>> David E DeMarle
>>> Kitware, Inc.
>>> Principal Engineer
>>> 21 Corporate Drive
>>> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
>>> Clifton Park, NY 12065
>>> <https://maps.google.com/?q=21+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g>
>>> -8662
>>> Phone: 518-881-4909 <(518)%20881-4909>
>>>
>>> On Tue, Dec 5, 2017 at 2:10 PM, Wyatt Spear <wspear at cs.uoregon.edu>
>>> wrote:
>>>
>>>> Greetings,
>>>>
>>>> I'm using the SC17 preview of 5.5 of ParaView. I first noticed this
>>>> error with my own dataset but it appears with the simple test.csv I've
>>>> included. To reproduce the segfault:
>>>>
>>>> Load the attached (or presumably any) CSV points file.
>>>> Run the TableToPoints filter.
>>>> Assign the X/Y/Z column dropdowns to the x coord/y coord/z coord values.
>>>> Hit Apply
>>>> Hit the 'Hover Cells On' button in the 3d display and mouse over a
>>>> point to confirm it works.
>>>> In the 'Representation' drop down box select "3D Glyphs".
>>>> In the 'Glyph Type' drop down box select "Box" (I wasn't able to
>>>> reproduce the error with arrows)
>>>> Hover over one of the resulting box glyphs for instant segfault.
>>>>
>>>> Command line output from this session was:
>>>>
>>>> Generic Warning: In /home/buildslave/dashboards/bu
>>>> ildbot/paraview-pvbinsdash-linux-shared-release_superbuild/s
>>>> ource-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
>>>> line 511
>>>> Failed to locate property: OSPRayMaterialLibrary
>>>>
>>>> Generic Warning: In /home/buildslave/dashboards/bu
>>>> ildbot/paraview-pvbinsdash-linux-shared-release_superbuild/s
>>>> ource-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx,
>>>> line 831
>>>> Call not supported for the current property type.
>>>>
>>>> Segmentation fault (core dumped)
>>>>
>>>> Regards,
>>>> Wyatt Spear
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView
>>>>
>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/e00dbcc1/attachment.html>

From chris.marsh at usask.ca  Tue Dec  5 16:01:53 2017
From: chris.marsh at usask.ca (Chris Marsh)
Date: Tue, 5 Dec 2017 15:01:53 -0600
Subject: [Paraview] Filter suddenly stopped working "did not create output
	for port 0"
Message-ID: <CAFgDerH7uCZ_DEGHFK+EGz9Yri-=t08cnXGrbbbbQLKp++MzaQ@mail.gmail.com>

Hi, I have a filter that decodes a posix string from a pvd file into a
datetime format. This has worked well, however with the newest paraview I
get the error

ERROR: In
ParaView-v5.4.1/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line
672

vtkPVCompositeDataPipeline (0x60c0001ad9e0): Algorithm
vtkDateTimeAnnotation(0x60c00013e1e0) did not create output for port 0 when
asked by REQUEST_DATA_OBJECT and does not specify any DATA_TYPE_NAME.

I've tried fiddling around with various things I've found on the mailing
list, but I'm at a bit of a loss.

Would appreciate any help. Code is here
https://github.com/Chrismarsh/vtk-paraview-datetimefilter

Cheers
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171205/b522c163/attachment.html>

From fixed-term.Lukas.Eberle2 at de.bosch.com  Wed Dec  6 03:02:38 2017
From: fixed-term.Lukas.Eberle2 at de.bosch.com (FIXED-TERM Eberle Lukas (CC-PS/ECL5))
Date: Wed, 6 Dec 2017 08:02:38 +0000
Subject: [Paraview] Update Programmable Source
Message-ID: <c7f3e9bc063549c7b429dc94ed6207f2@de.bosch.com>

Hi,

Is there a possibility to perform a cyclic update of a Programmable Source?


Best,
Lukas




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

From paul.melis at surfsara.nl  Wed Dec  6 03:34:25 2017
From: paul.melis at surfsara.nl (Paul Melis)
Date: Wed, 6 Dec 2017 09:34:25 +0100
Subject: [Paraview] Optimus and Windows 10
In-Reply-To: <CAF2skS5YdEkfc8s_Lw_0XYjVA3q3HqnydcbFpW0+Z0KVvoVL_w@mail.gmail.com>
References: <c6d38c35-1d6d-ada6-9ae8-390831a9a917@surfsara.nl>
 <CY4PR15MB128844018ACF5C421141D7F6FD3D0@CY4PR15MB1288.namprd15.prod.outlook.com>
 <CAF2skS5YdEkfc8s_Lw_0XYjVA3q3HqnydcbFpW0+Z0KVvoVL_w@mail.gmail.com>
Message-ID: <e1822db6-e8a8-99f9-cb71-e57414e05716@surfsara.nl>

Thanks, good to know. We'll try 5.2 (qt4) if the issue surfaces again,

Paul

On 05-12-17 14:13, Aron Helser wrote:
> Yes, that Intel driver bug is known to affect ParaView:
> https://gitlab.kitware.com/paraview/paraview/issues/17499
> 
> Regards,
> Aron
> 
> On Tue, Dec 5, 2017 at 6:40 AM, Jonathan Borduas 
> <jonathan.borduas at caboma.com <mailto:jonathan.borduas at caboma.com>> wrote:
> 
>     Was the laptop running with the intel gpu ??If so, it might be
>     related to an Intel driver bug that was reported on the QT and Intel
>     websites.
> 
>     https://bugreports.qt.io/browse/QTBUG-40485
>     <https://bugreports.qt.io/browse/QTBUG-40485>
> 
>     https://software.intel.com/en-us/node/744153
>     <https://software.intel.com/en-us/node/744153>
> 
>     Jonathan Borduas
> 
>     _________________________
>     From: Paul Melis <paul.melis at surfsara.nl
>     <mailto:paul.melis at surfsara.nl>>
>     Sent: Tuesday, December 5, 2017 04:16
>     Subject: [Paraview] Optimus and Windows 10
>     To: <paraview at paraview.org <mailto:paraview at paraview.org>>
> 
> 
> 
>     Hi,
> 
>     In our paraview course two weeks ago we had a student that had trouble
>     running Paraview 5.4.1 (official windows 64-bit binaries) under windows
>     10. The symptoms were that the main menu bar was invisible and that the
>     mouse cursor did not match up with the position of the click event,
>     making it very hard to do anything. It seemed the menu bar somehow had
>     shifted under the window title bar, causing the misalignment.
> 
>     As this laptop was an optimus system we figured it might have something
>     to do with that. After some fiddling we found that right-clicking on
>     paraview.exe and picking Run with graphics processor ->
>     High-performance
>     NVIDIA processor solved the problem.
> 
>     Is this a known issue?
> 
>     Regards,
>     Paul
> 
>     -- 
> 
>     Paul Melis
>     | Visualization group leader & developer | SURFsara |
>     | Science Park 140 | 1098 XG Amsterdam |
>     | T 020 800 1312 | paul.melis at surfsara.nl
>     <mailto:paul.melis at surfsara.nl> | www.surfsara.nl
>     <http://www.surfsara.nl> |
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
> 
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     <http://www.kitware.com/opensource/opensource.html>
> 
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
> 
>     Search the list archives at: http://markmail.org/search/?q=ParaView
>     <http://markmail.org/search/?q=ParaView>
> 
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/paraview
>     <http://public.kitware.com/mailman/listinfo/paraview>
> 
> 
> 
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
> 
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     <http://www.kitware.com/opensource/opensource.html>
> 
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
> 
>     Search the list archives at: http://markmail.org/search/?q=ParaView
>     <http://markmail.org/search/?q=ParaView>
> 
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/paraview
>     <http://public.kitware.com/mailman/listinfo/paraview>
> 
> 


-- 

Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl |

From 224252 at via.dk  Wed Dec  6 03:48:35 2017
From: 224252 at via.dk (Doina Gumeniuc (224252 MAHS))
Date: Wed, 6 Dec 2017 08:48:35 +0000
Subject: [Paraview] Warp by vector not fully working
Message-ID: <HE1PR0602MB3468A8652423AB0E959F83E1A4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>

Hi all!

I have a structure from points and lines. The POINT_DATA contains some displacement vectors. When I load it in Paraview and use Warp by Vector, it does not give me any displacement or change in color.

Is my code wrong?

Please see my file attached.


Also, I would like to add under POINT_DATA more vector fields (example, VECTORS mode1 float, VECTORS mode2 float and so on..but it reads only the first field of vectors, how can I solve that?)


Thank you all in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/b40d4f1f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Turbine.vtk
Type: application/octet-stream
Size: 8401 bytes
Desc: Turbine.vtk
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/b40d4f1f/attachment.obj>

From 224252 at via.dk  Wed Dec  6 04:10:26 2017
From: 224252 at via.dk (Doina Gumeniuc (224252 MAHS))
Date: Wed, 6 Dec 2017 09:10:26 +0000
Subject: [Paraview] Warp by vector not fully working
In-Reply-To: <HE1PR0602MB3468A8652423AB0E959F83E1A4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>
References: <HE1PR0602MB3468A8652423AB0E959F83E1A4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>
Message-ID: <HE1PR0602MB34686B3FB9BF829445215DFFA4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>

Sorry! Silly me, I needed point instead of comma. Could you please let me know the way to introduce more displacement fields? Thank you!

________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Doina Gumeniuc (224252 MAHS) <224252 at via.dk>
Sent: December 6, 2017 9:48:35 AM
To: paraview at paraview.org
Subject: [Paraview] Warp by vector not fully working


Hi all!

I have a structure from points and lines. The POINT_DATA contains some displacement vectors. When I load it in Paraview and use Warp by Vector, it does not give me any displacement or change in color.

Is my code wrong?

Please see my file attached.


Also, I would like to add under POINT_DATA more vector fields (example, VECTORS mode1 float, VECTORS mode2 float and so on..but it reads only the first field of vectors, how can I solve that?)


Thank you all in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/85c7dab0/attachment.html>

From 224252 at via.dk  Wed Dec  6 04:18:44 2017
From: 224252 at via.dk (Doina Gumeniuc (224252 MAHS))
Date: Wed, 6 Dec 2017 09:18:44 +0000
Subject: [Paraview] Warp by vector not fully working
In-Reply-To: <HE1PR0602MB34686B3FB9BF829445215DFFA4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>
References: <HE1PR0602MB3468A8652423AB0E959F83E1A4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>,
 <HE1PR0602MB34686B3FB9BF829445215DFFA4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>
Message-ID: <HE1PR0602MB3468505978DE7D166139959EA4320@HE1PR0602MB3468.eurprd06.prod.outlook.com>

SOLVED!

________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Doina Gumeniuc (224252 MAHS) <224252 at via.dk>
Sent: December 6, 2017 10:10:26 AM
To: paraview at paraview.org
Subject: Re: [Paraview] Warp by vector not fully working


Sorry! Silly me, I needed point instead of comma. Could you please let me know the way to introduce more displacement fields? Thank you!

________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Doina Gumeniuc (224252 MAHS) <224252 at via.dk>
Sent: December 6, 2017 9:48:35 AM
To: paraview at paraview.org
Subject: [Paraview] Warp by vector not fully working


Hi all!

I have a structure from points and lines. The POINT_DATA contains some displacement vectors. When I load it in Paraview and use Warp by Vector, it does not give me any displacement or change in color.

Is my code wrong?

Please see my file attached.


Also, I would like to add under POINT_DATA more vector fields (example, VECTORS mode1 float, VECTORS mode2 float and so on..but it reads only the first field of vectors, how can I solve that?)


Thank you all in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/a5b6b25a/attachment.html>

From ahmetskyland at gmail.com  Wed Dec  6 09:00:51 2017
From: ahmetskyland at gmail.com (Ahmet Ahmet)
Date: Wed, 6 Dec 2017 17:00:51 +0300
Subject: [Paraview] wallShearStress Calculation in Paraview
Message-ID: <CAGnrKXsF7U=8sp54JDdqOB2DrTM2tJduqgjM5CqDkyTUWcHdFQ@mail.gmail.com>

Hello everyone,

I have results with OpenFOAM including p,T,U outputs. Due to some reasons,
I can't use wallShearStress or wallgradU utility in OF. So, I have to
calculate it on Paraview. I saw many topics related to that on google, but
I could not find a satisfactory answer. My case is 3-D, compressible and
laminar but we can think about incompressible and may be 2-D.

I think the most important part for WSS is to calculate velocity gradient.
My unsolved problem is to calculate that. How can I calculate gradients on
the wall? I have no-slip wall, that is u=0 and with *Gradient of
Unstructured DataSet/Compute Derivatives *filters, I obtained 0 on the
wall. I think the values in the nearest mesh to the wall should be
accounted for. To do that, what should I do?

*Note:*

   1. The walls are not aligned with a coordinate axis. For this part, I
   tried to extract the wall surface and generate normal vectors.
   2. As an alternative to get directly on wall, I tried to get slice a
   little bit over the wall surface and then take surface vector on slice then
   gradient of unstructured dataset on surface vector. That gives me a result
   but I am not sure it's true.


This may be simple for you, sorry for that.
Thank you in advance,
Ahmet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/71b89be5/attachment.html>

From ezhkr601 at student.liu.se  Wed Dec  6 09:05:56 2017
From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy)
Date: Wed, 6 Dec 2017 15:05:56 +0100
Subject: [Paraview] wallShearStress Calculation in Paraview
In-Reply-To: <CAGnrKXsF7U=8sp54JDdqOB2DrTM2tJduqgjM5CqDkyTUWcHdFQ@mail.gmail.com>
References: <CAGnrKXsF7U=8sp54JDdqOB2DrTM2tJduqgjM5CqDkyTUWcHdFQ@mail.gmail.com>
Message-ID: <CACrYMs+dbh_fZsGtDJRSoX7wihUSwkSOhaEDLGwrnPqWUEYkrg@mail.gmail.com>

Hi Ahmet,

What you can do that is, use the filter name called extract surface.
once you get that surface either you can export those values in form of
from elements or from the points.

It might work, or you may get more clear explanation from this forum.

Cheers,
Mathi



On 6 December 2017 at 15:00, Ahmet Ahmet <ahmetskyland at gmail.com> wrote:

> Hello everyone,
>
> I have results with OpenFOAM including p,T,U outputs. Due to some reasons,
> I can't use wallShearStress or wallgradU utility in OF. So, I have to
> calculate it on Paraview. I saw many topics related to that on google, but
> I could not find a satisfactory answer. My case is 3-D, compressible and
> laminar but we can think about incompressible and may be 2-D.
>
> I think the most important part for WSS is to calculate velocity gradient.
> My unsolved problem is to calculate that. How can I calculate gradients on
> the wall? I have no-slip wall, that is u=0 and with *Gradient of
> Unstructured DataSet/Compute Derivatives *filters, I obtained 0 on the
> wall. I think the values in the nearest mesh to the wall should be
> accounted for. To do that, what should I do?
>
> *Note:*
>
>    1. The walls are not aligned with a coordinate axis. For this part, I
>    tried to extract the wall surface and generate normal vectors.
>    2. As an alternative to get directly on wall, I tried to get slice a
>    little bit over the wall surface and then take surface vector on slice then
>    gradient of unstructured dataset on surface vector. That gives me a result
>    but I am not sure it's true.
>
>
> This may be simple for you, sorry for that.
> Thank you in advance,
> Ahmet
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/101e42be/attachment.html>

From cory.quammen at kitware.com  Wed Dec  6 09:08:07 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 6 Dec 2017 09:08:07 -0500
Subject: [Paraview] Update Programmable Source
In-Reply-To: <c7f3e9bc063549c7b429dc94ed6207f2@de.bosch.com>
References: <c7f3e9bc063549c7b429dc94ed6207f2@de.bosch.com>
Message-ID: <CAB5Fpx4kPENRcSUbOzpPk=0e8oio_p--Ga++3fBEEF_b9Rjqjg@mail.gmail.com>

> Is there a possibility to perform a cyclic update of a Programmable Source?

What do you mean? Do you mean update a Programmable Source once every
time period?

>
>
>
>
>
> Best,
>
> Lukas
>
>
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



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

From stephen.wornom at inria.fr  Wed Dec  6 09:19:51 2017
From: stephen.wornom at inria.fr (Stephen Wornom)
Date: Wed, 6 Dec 2017 15:19:51 +0100 (CET)
Subject: [Paraview] wallShearStress Calculation in Paraview
In-Reply-To: <CACrYMs+dbh_fZsGtDJRSoX7wihUSwkSOhaEDLGwrnPqWUEYkrg@mail.gmail.com>
References: <CAGnrKXsF7U=8sp54JDdqOB2DrTM2tJduqgjM5CqDkyTUWcHdFQ@mail.gmail.com>
 <CACrYMs+dbh_fZsGtDJRSoX7wihUSwkSOhaEDLGwrnPqWUEYkrg@mail.gmail.com>
Message-ID: <1407217001.16229462.1512569991347.JavaMail.zimbra@inria.fr>

Thanks, but did you forget to include the name of the forum? 
Stephen 

----- Original Message -----

> From: "Ezhilmathi Krishnasamy" <ezhkr601 at student.liu.se>
> To: "Ahmet Ahmet" <ahmetskyland at gmail.com>
> Cc: "ParaView" <paraview at paraview.org>
> Sent: Wednesday, December 6, 2017 3:05:56 PM
> Subject: Re: [Paraview] wallShearStress Calculation in Paraview

> Hi Ahmet,

> What you can do that is, use the filter name called extract surface.
> once you get that surface either you can export those values in form of from
> elements or from the points.

> It might work, or you may get more clear explanation from this forum.

> Cheers,
> Mathi

> On 6 December 2017 at 15:00, Ahmet Ahmet < ahmetskyland at gmail.com > wrote:

> > Hello everyone,
> 

> > I have results with OpenFOAM including p,T,U outputs. Due to some reasons,
> > I
> > can't use wallShearStress or wallgradU utility in OF. So, I have to
> > calculate it on Paraview. I saw many topics related to that on google, but
> > I
> > could not find a satisfactory answer. My case is 3-D, compressible and
> > laminar but we can think about incompressible and may be 2-D.
> 

> > I think the most important part for WSS is to calculate velocity gradient.
> > My
> > unsolved problem is to calculate that. How can I calculate gradients on the
> > wall? I have no-slip wall, that is u=0 and with Gradient of Unstructured
> > DataSet/Compute Derivatives filters, I obtained 0 on the wall. I think the
> > values in the nearest mesh to the wall should be accounted for. To do that,
> > what should I do?
> 

> > Note:
> 

> > 1. T he walls are not aligned with a coordinate axis. For this part, I
> > tried
> > to extract the wall surface and generate normal vectors.
> 
> > 2. As an alternative to get directly on wall, I tried to get slice a little
> > bit over the wall surface and then take surface vector on slice then
> > gradient of unstructured dataset on surface vector. That gives me a result
> > but I am not sure it's true.
> 

> > This may be simple for you, sorry for that.
> 
> > Thank you in advance,
> 
> > Ahmet
> 

> > _______________________________________________
> 
> > Powered by www.kitware.com
> 

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

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

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

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

> _______________________________________________
> Powered by www.kitware.com

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

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

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

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

From andy.bauer at kitware.com  Wed Dec  6 11:20:53 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 6 Dec 2017 11:20:53 -0500
Subject: [Paraview] wallShearStress Calculation in Paraview
In-Reply-To: <CACrYMs+dbh_fZsGtDJRSoX7wihUSwkSOhaEDLGwrnPqWUEYkrg@mail.gmail.com>
References: <CAGnrKXsF7U=8sp54JDdqOB2DrTM2tJduqgjM5CqDkyTUWcHdFQ@mail.gmail.com>
 <CACrYMs+dbh_fZsGtDJRSoX7wihUSwkSOhaEDLGwrnPqWUEYkrg@mail.gmail.com>
Message-ID: <CAMaOp+E2OVReqqvX6aAXLZ95gTNJFjbC=rVzULZZS=bTU4Jc5Q@mail.gmail.com>

There's no general way to compute gradients normal to the surface so you
need to compute the gradient on the simulation's cells (e.g. volumetric
cells for 3D). You can use the Gradient Of Unstructured Data set to do
that. Then extract the surface as Mathi said, use the Normals filter to
compute the normals, use the Calculator filter to multiply the normals by
the gradient and the viscosity and you'll have the wall shear stress over
the entire boundary surface. You can then select the cells you want to show
the WSS over the exact portion of the desired boundary.

On Wed, Dec 6, 2017 at 9:05 AM, Ezhilmathi Krishnasamy <
ezhkr601 at student.liu.se> wrote:

> Hi Ahmet,
>
> What you can do that is, use the filter name called extract surface.
> once you get that surface either you can export those values in form of
> from elements or from the points.
>
> It might work, or you may get more clear explanation from this forum.
>
> Cheers,
> Mathi
>
>
>
> On 6 December 2017 at 15:00, Ahmet Ahmet <ahmetskyland at gmail.com> wrote:
>
>> Hello everyone,
>>
>> I have results with OpenFOAM including p,T,U outputs. Due to some
>> reasons, I can't use wallShearStress or wallgradU utility in OF. So, I have
>> to calculate it on Paraview. I saw many topics related to that on google,
>> but I could not find a satisfactory answer. My case is 3-D, compressible
>> and laminar but we can think about incompressible and may be 2-D.
>>
>> I think the most important part for WSS is to calculate velocity
>> gradient. My unsolved problem is to calculate that. How can I calculate
>> gradients on the wall? I have no-slip wall, that is u=0 and with *Gradient
>> of Unstructured DataSet/Compute Derivatives *filters, I obtained 0 on
>> the wall. I think the values in the nearest mesh to the wall should be
>> accounted for. To do that, what should I do?
>>
>> *Note:*
>>
>>    1. The walls are not aligned with a coordinate axis. For this part, I
>>    tried to extract the wall surface and generate normal vectors.
>>    2. As an alternative to get directly on wall, I tried to get slice a
>>    little bit over the wall surface and then take surface vector on slice then
>>    gradient of unstructured dataset on surface vector. That gives me a result
>>    but I am not sure it's true.
>>
>>
>> This may be simple for you, sorry for that.
>> Thank you in advance,
>> Ahmet
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/ff4d46cf/attachment.html>

From heiland at iu.edu  Wed Dec  6 11:15:24 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Wed, 6 Dec 2017 16:15:24 +0000
Subject: [Paraview] animation: files, pgmable source
Message-ID: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>

I?m probably missing a basic concept and hoping someone can enlighten me. I have a pipeline with a Programmable Source that reads in a (non-VTK formatted) file, I process it and then I have filters in my pipeline that act on that data. I want to be able to feed multiple files to the pipeline, save images and/or create animations. I naively created a Python function in the Pgmable Source, then save the PV State to a Python script, thinking I could call the function from the end of that script. Doesn?t seem to be possible. And I confess I?ve not given this deep thought - it?s easier to ask the experts :-)  Bottom line, we want to make this as dead simple for our own users.

Fwiw, I?ve zipped up 2 files - a .pvsm and a sample data file here: http://pages.iu.edu/~heiland/physicell/pv_pcell.zip . You?d need to edit the ?dir? path in the Pgmable Source.

Initially, I just want to save images/animation (over multiple files) with a fixed camera view; later, it?d be nice to have simultaneous camera movement.

thanks, Randy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/d927dc5d/attachment.html>

From ken.martin at kitware.com  Wed Dec  6 12:12:42 2017
From: ken.martin at kitware.com (Ken Martin)
Date: Wed, 6 Dec 2017 12:12:42 -0500
Subject: [Paraview] Windows Mixed Reality
Message-ID: <CANXz0SYeK8iP2=U0_O1toRcd9WZR-Dbib9Rc=XMTM-Th36sfkw@mail.gmail.com>

Just a FYI, I just had a chance to test out a new Windows Mixed Reality
headset and it seems to work well with VTK and ParaView through the SteamVR
driver. I was testing the new Dell Visor headset and controller. The
controllers show up properly and the controls map to reasonable settings.
Tracking was surprisingly good.


-- 
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/attachments/20171206/dc540bd8/attachment.html>

From dennis_conklin at goodyear.com  Wed Dec  6 15:26:24 2017
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Wed, 6 Dec 2017 20:26:24 +0000
Subject: [Paraview] Memory issue for remote visualization
Message-ID: <BN3PR0701MB1687D9F5F85353361FE5C2AA9F320@BN3PR0701MB1687.namprd07.prod.outlook.com>

All,

As we start down the road to parallel visualization, our first baby steps are to try remote visualization.

In Redhat, I ssh onto a node with ~30 gigs of memory available (free -m)   I start pvserver.
Back on my machine I launch paraview541 and connect to the server.  The Memory Inspector shows 2.1 GB of total system ram on the server.
If I try to load a model of any size, the server bombs on a segmentation error (memory).

If I log onto the remote node with 30 GB free memory, I can only run standalone paraview if I use the -mesa-llvm command line.   When I do this,  Memory Inspector in standalone Paraview says there is only 2.1 GB of total system memory.

Am I missing something - I don't see  how this is ever going to work if neither a remote paraview or a remote pvserver can see and/or access the available free memory on the remote machine.

Thanks for any hints

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

From cory.quammen at kitware.com  Wed Dec  6 16:27:52 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 6 Dec 2017 16:27:52 -0500
Subject: [Paraview] How to read the file info in *pvd file
In-Reply-To: <CAMd10VaQPR2r6_QxGtTTkVW8SdVwi1k8kL+-0hVe4CcEF9TeQQ@mail.gmail.com>
References: <CAMd10VZwk4q_N=FSEixEnS8hAJYRcLPhi+7evqSUaxtpO_YJ9A@mail.gmail.com>
 <CAB5Fpx4Q+PNxpspEE-u2qq_zhW6JgyT9Yn7Uanu89GBrxiMjWw@mail.gmail.com>
 <CAMd10VaOmk1Nh0UHGmZo_dYFsa-A-VqT2asx3QrqWa1F3NDBsA@mail.gmail.com>
 <CAB5Fpx7av-8sZH49fL0kYTNBmZZ=F2znrYZTAEEbVoNUjzWDXA@mail.gmail.com>
 <CAMd10VaQPR2r6_QxGtTTkVW8SdVwi1k8kL+-0hVe4CcEF9TeQQ@mail.gmail.com>
Message-ID: <CAB5Fpx54EisWaLGJpdk3axy4P=UwNHNvqBaxE=fh8i9Fxn9mng@mail.gmail.com>

Did you make progress on this? You should just be able to use your
favorite Python XML module to locate all the <DataSet/> elements and
find the "file" attributes to get the *pvtu file names. Then you can
parse those *pvtu XML files to get whatever information you want. One
such module is documented here:
https://docs.python.org/2/library/xml.etree.elementtree.html.

HTH,
Cory

On Wed, Nov 15, 2017 at 1:17 PM, Ke Gao <ke.gao.ut at gmail.com> wrote:
> Actually, what I want to do is using python script to read *pvd file first
> to get the name info of *pvtu files. Then use the *pvtu file name to read
> through all of them one by one to extract the info I want. I'm not sure if
> there is a better way to realize this.
>
> Many thanks.
>
> On Wed, Nov 15, 2017 at 11:05 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>>
>> The file names are embedded in the same XML element as the time step:
>>
>> <DataSet timestep="+1.98800000e+03"  part="001" file="Sout_1012.pvtu"/>
>>
>> But I'll be that's not how you want to access them.
>>
>> Next question: From where do you want to access the file names? A Python
>> script? In the UI?
>>
>> On Wed, Nov 15, 2017 at 12:35 PM, Ke Gao <ke.gao.ut at gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> I mean how to get the file name info such as "Sout_1012.pvtu",
>>> "Sout_1013.pvtu". Currently I can only read the timestep info such as
>>> "+1.98800000e+03".
>>>
>>> Many thanks.
>>>
>>>
>>> <?xml version="1.0"?>
>>>   <VTKFile type="Collection" version="0.1" byte_order="LittleEndian">
>>>   <Collection>
>>>     <DataSet timestep="+1.98800000e+03"  part="001"
>>> file="Sout_1012.pvtu"/>
>>>     <DataSet timestep="+1.99000000e+03"  part="001"
>>> file="Sout_1013.pvtu"/>
>>>     <DataSet timestep="+1.99200000e+03"  part="001"
>>> file="Sout_1014.pvtu"/>
>>>
>>> On Wed, Nov 15, 2017 at 10:33 AM, Cory Quammen <cory.quammen at kitware.com>
>>> wrote:
>>>>
>>>> What do you mean by "file info"? File name? Size of the file? Data
>>>> arrays in the file?
>>>>
>>>> - Cory
>>>>
>>>> On Tue, Nov 14, 2017 at 4:45 PM, Ke Gao <ke.gao.ut at gmail.com> wrote:
>>>>>
>>>>> Does anyone know how to read the file info from *pvd file? I know how
>>>>> to get the time step values, just using the keyword of ?TimestepValues?,
>>>>> however, I tried different ways, still haven?t figured out how to read the
>>>>> file info.
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> <?xml version="1.0"?>
>>>>>   <VTKFile type="Collection" version="0.1" byte_order="LittleEndian">
>>>>>   <Collection>
>>>>>     <DataSet timestep="+1.98800000e+03"  part="001"
>>>>> file="Sout_1012.pvtu"/>
>>>>>     <DataSet timestep="+1.99000000e+03"  part="001"
>>>>> file="Sout_1013.pvtu"/>
>>>>>     <DataSet timestep="+1.99200000e+03"  part="001"
>>>>> file="Sout_1014.pvtu"/>
>>>>> --
>>>>>
>>>>> ..............................................................................................................................................
>>>>> Ke Gao
>>>>>
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>> http://paraview.org/Wiki/ParaView
>>>>>
>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cory Quammen
>>>> Staff R&D Engineer
>>>> Kitware, Inc.
>>>
>>>
>>>
>>>
>>> --
>>>
>>> ..............................................................................................................................................
>>> Ke Gao
>>
>>
>>
>>
>> --
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.
>
>
>
>
> --
> ..............................................................................................................................................
> Ke Gao



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

From ke.gao.ut at gmail.com  Wed Dec  6 16:35:36 2017
From: ke.gao.ut at gmail.com (Ke Gao)
Date: Wed, 6 Dec 2017 14:35:36 -0700
Subject: [Paraview] How to read the file info in *pvd file
In-Reply-To: <CAB5Fpx54EisWaLGJpdk3axy4P=UwNHNvqBaxE=fh8i9Fxn9mng@mail.gmail.com>
References: <CAMd10VZwk4q_N=FSEixEnS8hAJYRcLPhi+7evqSUaxtpO_YJ9A@mail.gmail.com>
 <CAB5Fpx4Q+PNxpspEE-u2qq_zhW6JgyT9Yn7Uanu89GBrxiMjWw@mail.gmail.com>
 <CAMd10VaOmk1Nh0UHGmZo_dYFsa-A-VqT2asx3QrqWa1F3NDBsA@mail.gmail.com>
 <CAB5Fpx7av-8sZH49fL0kYTNBmZZ=F2znrYZTAEEbVoNUjzWDXA@mail.gmail.com>
 <CAMd10VaQPR2r6_QxGtTTkVW8SdVwi1k8kL+-0hVe4CcEF9TeQQ@mail.gmail.com>
 <CAB5Fpx54EisWaLGJpdk3axy4P=UwNHNvqBaxE=fh8i9Fxn9mng@mail.gmail.com>
Message-ID: <CAMd10VYZCf+xW+2p03Dt2ip_wuotQ8eaw_Bnpe28ByDhWB9B=Q@mail.gmail.com>

Thanks Cory. That's what I'm planning to do. It's really helpful.

Ke

On Wed, Dec 6, 2017 at 2:27 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Did you make progress on this? You should just be able to use your
> favorite Python XML module to locate all the <DataSet/> elements and
> find the "file" attributes to get the *pvtu file names. Then you can
> parse those *pvtu XML files to get whatever information you want. One
> such module is documented here:
> https://docs.python.org/2/library/xml.etree.elementtree.html.
>
> HTH,
> Cory
>
> On Wed, Nov 15, 2017 at 1:17 PM, Ke Gao <ke.gao.ut at gmail.com> wrote:
> > Actually, what I want to do is using python script to read *pvd file
> first
> > to get the name info of *pvtu files. Then use the *pvtu file name to read
> > through all of them one by one to extract the info I want. I'm not sure
> if
> > there is a better way to realize this.
> >
> > Many thanks.
> >
> > On Wed, Nov 15, 2017 at 11:05 AM, Cory Quammen <cory.quammen at kitware.com
> >
> > wrote:
> >>
> >> The file names are embedded in the same XML element as the time step:
> >>
> >> <DataSet timestep="+1.98800000e+03"  part="001" file="Sout_1012.pvtu"/>
> >>
> >> But I'll be that's not how you want to access them.
> >>
> >> Next question: From where do you want to access the file names? A Python
> >> script? In the UI?
> >>
> >> On Wed, Nov 15, 2017 at 12:35 PM, Ke Gao <ke.gao.ut at gmail.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I mean how to get the file name info such as "Sout_1012.pvtu",
> >>> "Sout_1013.pvtu". Currently I can only read the timestep info such as
> >>> "+1.98800000e+03".
> >>>
> >>> Many thanks.
> >>>
> >>>
> >>> <?xml version="1.0"?>
> >>>   <VTKFile type="Collection" version="0.1" byte_order="LittleEndian">
> >>>   <Collection>
> >>>     <DataSet timestep="+1.98800000e+03"  part="001"
> >>> file="Sout_1012.pvtu"/>
> >>>     <DataSet timestep="+1.99000000e+03"  part="001"
> >>> file="Sout_1013.pvtu"/>
> >>>     <DataSet timestep="+1.99200000e+03"  part="001"
> >>> file="Sout_1014.pvtu"/>
> >>>
> >>> On Wed, Nov 15, 2017 at 10:33 AM, Cory Quammen <
> cory.quammen at kitware.com>
> >>> wrote:
> >>>>
> >>>> What do you mean by "file info"? File name? Size of the file? Data
> >>>> arrays in the file?
> >>>>
> >>>> - Cory
> >>>>
> >>>> On Tue, Nov 14, 2017 at 4:45 PM, Ke Gao <ke.gao.ut at gmail.com> wrote:
> >>>>>
> >>>>> Does anyone know how to read the file info from *pvd file? I know how
> >>>>> to get the time step values, just using the keyword of
> ?TimestepValues?,
> >>>>> however, I tried different ways, still haven?t figured out how to
> read the
> >>>>> file info.
> >>>>>
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> <?xml version="1.0"?>
> >>>>>   <VTKFile type="Collection" version="0.1" byte_order="LittleEndian">
> >>>>>   <Collection>
> >>>>>     <DataSet timestep="+1.98800000e+03"  part="001"
> >>>>> file="Sout_1012.pvtu"/>
> >>>>>     <DataSet timestep="+1.99000000e+03"  part="001"
> >>>>> file="Sout_1013.pvtu"/>
> >>>>>     <DataSet timestep="+1.99200000e+03"  part="001"
> >>>>> file="Sout_1014.pvtu"/>
> >>>>> --
> >>>>>
> >>>>> ............................................................
> ............................................................
> ......................
> >>>>> Ke Gao
> >>>>>
> >>>>> _______________________________________________
> >>>>> Powered by www.kitware.com
> >>>>>
> >>>>> Visit other Kitware open-source projects at
> >>>>> http://www.kitware.com/opensource/opensource.html
> >>>>>
> >>>>> Please keep messages on-topic and check the ParaView Wiki at:
> >>>>> http://paraview.org/Wiki/ParaView
> >>>>>
> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
> >>>>>
> >>>>> Follow this link to subscribe/unsubscribe:
> >>>>> http://public.kitware.com/mailman/listinfo/paraview
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Cory Quammen
> >>>> Staff R&D Engineer
> >>>> Kitware, Inc.
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> ............................................................
> ............................................................
> ......................
> >>> Ke Gao
> >>
> >>
> >>
> >>
> >> --
> >> Cory Quammen
> >> Staff R&D Engineer
> >> Kitware, Inc.
> >
> >
> >
> >
> > --
> > ............................................................
> ............................................................
> ......................
> > Ke Gao
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>



-- 
..............................................................................................................................................
Ke Gao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/c3143e18/attachment.html>

From cory.quammen at kitware.com  Wed Dec  6 17:06:32 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 6 Dec 2017 17:06:32 -0500
Subject: [Paraview] loading multiple state-files without hiding and
 resetting already loaded objects
In-Reply-To: <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de>
References: <fc803504-8b2e-a854-ab34-a23fe09a8e81@mh-hannover.de>
 <CAB5Fpx7W04E6iE5FiU1buFtzKLnGuUz7s-1BV2TJzWx+7WdSTg@mail.gmail.com>
 <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de>
 <CAB5Fpx5Pq4Ym+qakwQHifMeT-PAP2k3T+8DeuPCxOyE3sfsNcg@mail.gmail.com>
 <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de>
 <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de>
Message-ID: <CAB5Fpx4Z8byiUEwteVfkb_DeZgiO6AbS5PaCqOYC9FmyMw8Q-g@mail.gmail.com>

Hi Roman,

Sorry I failed to follow up. Did you find a solution to this problem?

This line in your script looks funny to me:

d[props] = pvs.GetProperty(repr, props[0])

Shouldn't props[0] just be props?

Thanks,
Cory

On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr.
<grothausmann.roman at mh-hannover.de> wrote:
> Dear Cory,
>
> On 15/09/17 15:27, Grothausmann, Roman Dr. wrote:
>>
>> On 15/09/17 15:14, Cory Quammen wrote:
>>>
>>> Put a ** in front of reppro[i], e.g.,
>>>
>>> pvs.SetProperties(repr, **reppro[i])
>>
>> Hm, I now get:
>> TypeError: SetProperties() argument after ** must be a mapping, not list
>> Do I have to store the dict of object properties in another dict instead
>> of a list?
>
>
> With a dict of dicts
> https://github.com/romangrothausmann/ParaView_scripts/commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420278bfff084788b82c715c452e
> I get:
>
>   File "/net/home/grothama/paraview/scripts/pvsm-multi.py", line 64, in main
>     pvs.SetProperties(repr, **reppro[i]);
>   File
> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py",
> line 568, in SetProperties
>     setattr(proxy, param, params[param])
>   File
> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
> line 317, in __setattr__
>     setter(self, value)
>   File
> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
> line 2528, in setProperty
>     return self.SetPropertyWithName(propName, value)
>   File
> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
> line 375, in SetPropertyWithName
>     prop.SetData(arg)
>   File
> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
> line 803, in SetData
>     raise RuntimeError("This property requires %d values." %
> self.GetNumberOfElements())
> RuntimeError: This property requires 3 values.
>
> Any ideas what could still be wrong?
>
>
>>>> On 07/09/17 23:37, Cory Quammen wrote:
>>>>>
>>>>>
>>>>> Hi Roman,
>>>>>
>>>>> It turns out ParaView was not designed for this use case because of
>>>>> certain difficulties discussed here:
>>>>>
>>>>> https://gitlab.kitware.com/paraview/paraview/issues/17442
>>>>>
>>>>> In your Python script, you could manually cash all the properties of
>>>>> the existing representations and restore them after loading the most
>>>>> recent state file.
>>>>>
>>>>> The functions
>>>>>
>>>>> reprs = GetRepresentations()
>>>>> repr = reprs.values()[0]
>>>>> props = repr.ListProperties()
>>>>> GetProperty(repr, props[0])
>>>>>
>>>>> would be helpful for this.
>>>>>
>>>>> Cory
>>>>>
>>>>>
>>>>> On Mon, Sep 4, 2017 at 8:42 AM, Grothausmann, Roman Dr.
>>>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>>>
>>>>>>
>>>>>> Dear mailing list members,
>>>>>>
>>>>>>
>>>>>> It seems that PV (and paraview.simple.LoadState) by default hides
>>>>>> already
>>>>>> loaded objects (and resets e.g. their coloring) when another
>>>>>> state-file
>>>>>> is
>>>>>> loaded.
>>>>>> Is there a way to load multiple state-files after one another without
>>>>>> hiding
>>>>>> and resetting already existent objects? I.e. a way to concatenate
>>>>>> multiple
>>>>>> state-files and leave their objects in the state as they got loaded
>>>>>> (e.g.
>>>>>> colored, hidden/visible)?
>>>>>> I do understand that loading a new state-file will reset the camera,
>>>>>> but
>>>>>> not
>>>>>> the rest.
>>>>>> Here's my initial attempt to achieve this with pvpython:
>>>>>>
>>>>>>
>>>>>> https://github.com/romangrothausmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea82fd6a9e23/pvsm-multi.py
>>>>>>
>>>>>> Any help or hints are very much appreciated
>>>>>> Roman
>>>>>>
>>>>>> --
>>>>>> Dr. Roman Grothausmann
>>>>>>
>>>>>> Tomographie und Digitale Bildverarbeitung
>>>>>> Tomography and Digital Image Analysis
>>>>>>
>>>>>> Medizinische Hochschule Hannover
>>>>>> Institut f?r Funktionelle und Angewandte Anatomie
>>>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland
>>>>>>
>>>>>> Tel. +49 511 532-2900
>>>>>> grothausmann.roman at mh-hannover.de
>>>>>> http://www.mh-hannover.de/anatomie.html
>>>>>> _______________________________________________
>>>>>> Powered by www.kitware.com
>>>>>>
>>>>>> Visit other Kitware open-source projects at
>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>
>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>
>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>>
>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Dr. Roman Grothausmann
>>>>
>>>> Tomographie und Digitale Bildverarbeitung
>>>> Tomography and Digital Image Analysis
>>>>
>>>> Medizinische Hochschule Hannover
>>>> Institut f?r Funktionelle und Angewandte Anatomie
>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland
>>>>
>>>> Tel. +49 511 532-2900
>>>> grothausmann.roman at mh-hannover.de
>>>> http://www.mh-hannover.de/anatomie.html
>>>
>>>
>>>
>>>
>>
>
> --
> Dr. Roman Grothausmann
>
> Tomographie und Digitale Bildverarbeitung
> Tomography and Digital Image Analysis
>
> Medizinische Hochschule Hannover
> Institut f?r Funktionelle und Angewandte Anatomie
> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland
>
> Tel. +49 511 532-2900
> grothausmann.roman at mh-hannover.de
> http://www.mh-hannover.de/anatomie.html



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

From utkarsh.ayachit at kitware.com  Wed Dec  6 22:44:37 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 6 Dec 2017 22:44:37 -0500
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
Message-ID: <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>

Randy,

You attempting to mix the Python scripting for data processing and
Python scripting for batch scripting. The two environments are
separate. Here's how I'd tackle it.

1. Make your "Programmable Source" become a temporal source i.e.
report to ParaView that it can produce timesteps matching the files
your file series. See [i]. If you get this right, you shuold be able
to render through all the files by hitting "Play" in the VCR control
in the UI.
2. Now you can write a batch script that either loads the predefined
pvsm state file or builds up the pipeline in Python itself and the
either uses `SaveScreenshot` or `SaveAnimation` to save out the
animation.

You can then mix in camera animations too. You can always use the
Python tracing in UI to figure out how to save images and/or animation
in the batch scripting environment.

Hope that helps.
Utkarsh

[i] https://blog.kitware.com/defining-time-varying-sources-with-paraviews-programmable-source/

On Wed, Dec 6, 2017 at 11:15 AM, Heiland, Randy <heiland at iu.edu> wrote:
> I?m probably missing a basic concept and hoping someone can enlighten me. I
> have a pipeline with a Programmable Source that reads in a (non-VTK
> formatted) file, I process it and then I have filters in my pipeline that
> act on that data. I want to be able to feed multiple files to the pipeline,
> save images and/or create animations. I naively created a Python function in
> the Pgmable Source, then save the PV State to a Python script, thinking I
> could call the function from the end of that script. Doesn?t seem to be
> possible. And I confess I?ve not given this deep thought - it?s easier to
> ask the experts :-)  Bottom line, we want to make this as dead simple for
> our own users.
>
> Fwiw, I?ve zipped up 2 files - a .pvsm and a sample data file here:
> http://pages.iu.edu/~heiland/physicell/pv_pcell.zip . You?d need to edit the
> ?dir? path in the Pgmable Source.
>
> Initially, I just want to save images/animation (over multiple files) with a
> fixed camera view; later, it?d be nice to have simultaneous camera movement.
>
> thanks, Randy
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From utkarsh.ayachit at kitware.com  Wed Dec  6 22:53:36 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 6 Dec 2017 22:53:36 -0500
Subject: [Paraview] Filter suddenly stopped working "did not create
 output for port 0"
In-Reply-To: <CAFgDerH7uCZ_DEGHFK+EGz9Yri-=t08cnXGrbbbbQLKp++MzaQ@mail.gmail.com>
References: <CAFgDerH7uCZ_DEGHFK+EGz9Yri-=t08cnXGrbbbbQLKp++MzaQ@mail.gmail.com>
Message-ID: <CADHSJjC_tbisQGa7ppayAVizaCoBDmLwMkfoaZcqFJxyCnT4yg@mail.gmail.com>

I tried to build with latest "master" and I didn't get any errors. The
plugin worked fine. I did remove these lines [1] from the
CMakeLists.txt file since that was causing build errors. What are
those for? I'd discourage you from adding your own FindParaView.cmake.
Once I removed those and simply set ParaView_DIR to my build
directory, all built and ran fine.

Utkarsh


[1] https://github.com/Chrismarsh/vtk-paraview-datetimefilter/blob/master/CMakeLists.txt#L5-L10

On Tue, Dec 5, 2017 at 4:01 PM, Chris Marsh <chris.marsh at usask.ca> wrote:
> Hi, I have a filter that decodes a posix string from a pvd file into a
> datetime format. This has worked well, however with the newest paraview I
> get the error
>
> ERROR: In
> ParaView-v5.4.1/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line
> 672
>
> vtkPVCompositeDataPipeline (0x60c0001ad9e0): Algorithm
> vtkDateTimeAnnotation(0x60c00013e1e0) did not create output for port 0 when
> asked by REQUEST_DATA_OBJECT and does not specify any DATA_TYPE_NAME.
>
>
> I've tried fiddling around with various things I've found on the mailing
> list, but I'm at a bit of a loss.
>
> Would appreciate any help. Code is here
> https://github.com/Chrismarsh/vtk-paraview-datetimefilter
>
> Cheers
> Chris
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ParaView 5.4.1-975-gfcb2303 64-bit_431.png
Type: image/png
Size: 111823 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171206/91c13977/attachment.png>

From 224252 at via.dk  Thu Dec  7 10:09:41 2017
From: 224252 at via.dk (Doina Gumeniuc (224252 MAHS))
Date: Thu, 7 Dec 2017 15:09:41 +0000
Subject: [Paraview] from matlab to paraview
Message-ID: <HE1PR0602MB3468150827411BA259AEEC95A4330@HE1PR0602MB3468.eurprd06.prod.outlook.com>

Hi all!


I have created a vtk file in matlab and I would like to export it to paraview. I need a script/function which would load this vtk file from matlab to paraview.

I would really appreciate if any of you could share some hints or some links where such a process is explained.


Thank you!

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

From heiland at iu.edu  Thu Dec  7 10:51:50 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Thu, 7 Dec 2017 15:51:50 +0000
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
 <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
Message-ID: <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>

Utkarsh,

Thanks very much for that!  Yes, after some fiddling, I got it to work, i.e., I can save .png files for an animation! So now that I?m using the Programmable Source(RequestInfo) script to accomplish the animation, how do I, during a PV session, *easily* switch back to render a single file?

For example, I can do:
frames = range(0,801,100)   #  render every 100th frame, including 800
setOutputTimesteps (self, frames)

or, I can explicitly list specific frames:
frames = [100,101]

so, I thought this would do a single file, but it doesn?t (my previous frames are still there):
frames = [600,]

-Randy



> On Dec 6, 2017, at 10:44 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
> 
> Randy,
> 
> You attempting to mix the Python scripting for data processing and
> Python scripting for batch scripting. The two environments are
> separate. Here's how I'd tackle it.
> 
> 1. Make your "Programmable Source" become a temporal source i.e.
> report to ParaView that it can produce timesteps matching the files
> your file series. See [i]. If you get this right, you shuold be able
> to render through all the files by hitting "Play" in the VCR control
> in the UI.
> 2. Now you can write a batch script that either loads the predefined
> pvsm state file or builds up the pipeline in Python itself and the
> either uses `SaveScreenshot` or `SaveAnimation` to save out the
> animation.
> 
> You can then mix in camera animations too. You can always use the
> Python tracing in UI to figure out how to save images and/or animation
> in the batch scripting environment.
> 
> Hope that helps.
> Utkarsh
> 
> [i] https://blog.kitware.com/defining-time-varying-sources-with-paraviews-programmable-source/
> 
> On Wed, Dec 6, 2017 at 11:15 AM, Heiland, Randy <heiland at iu.edu> wrote:
>> I?m probably missing a basic concept and hoping someone can enlighten me. I
>> have a pipeline with a Programmable Source that reads in a (non-VTK
>> formatted) file, I process it and then I have filters in my pipeline that
>> act on that data. I want to be able to feed multiple files to the pipeline,
>> save images and/or create animations. I naively created a Python function in
>> the Pgmable Source, then save the PV State to a Python script, thinking I
>> could call the function from the end of that script. Doesn?t seem to be
>> possible. And I confess I?ve not given this deep thought - it?s easier to
>> ask the experts :-)  Bottom line, we want to make this as dead simple for
>> our own users.
>> 
>> Fwiw, I?ve zipped up 2 files - a .pvsm and a sample data file here:
>> http://pages.iu.edu/~heiland/physicell/pv_pcell.zip . You?d need to edit the
>> ?dir? path in the Pgmable Source.
>> 
>> Initially, I just want to save images/animation (over multiple files) with a
>> fixed camera view; later, it?d be nice to have simultaneous camera movement.
>> 
>> thanks, Randy
>> 
>> _______________________________________________
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>> 


From chris.marsh at usask.ca  Thu Dec  7 14:41:43 2017
From: chris.marsh at usask.ca (Chris Marsh)
Date: Thu, 7 Dec 2017 13:41:43 -0600
Subject: [Paraview] Filter suddenly stopped working "did not create
 output for port 0"
In-Reply-To: <CADHSJjC_tbisQGa7ppayAVizaCoBDmLwMkfoaZcqFJxyCnT4yg@mail.gmail.com>
References: <CAFgDerH7uCZ_DEGHFK+EGz9Yri-=t08cnXGrbbbbQLKp++MzaQ@mail.gmail.com>
 <CADHSJjC_tbisQGa7ppayAVizaCoBDmLwMkfoaZcqFJxyCnT4yg@mail.gmail.com>
Message-ID: <CAFgDerGBAJFnG1Ez8EHAxJwXcJq2GFZ4L=P8m7gS-VcRzGe47Q@mail.gmail.com>

Hi,

Thanks for trying this. Good call on the removal of the extra CMake stuff.
It was there because I started this filter before I knew about things like
setting ParaView_DIR and forgot to update this!

Interesting that works for you. I just rebuilt with the change to use
ParaView_DIR
(on the off chance it changed something...) but still broken on my end. :(

So, this isn't an issue with the filters code, but rather something with
how either I compiled Paraview or ... something?

Are you using the github version of paraview?

Cheers
Chris


On 6 December 2017 at 21:53, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
wrote:

> I tried to build with latest "master" and I didn't get any errors. The
> plugin worked fine. I did remove these lines [1] from the
> CMakeLists.txt file since that was causing build errors. What are
> those for? I'd discourage you from adding your own FindParaView.cmake.
> Once I removed those and simply set ParaView_DIR to my build
> directory, all built and ran fine.
>
> Utkarsh
>
>
> [1] https://github.com/Chrismarsh/vtk-paraview-datetimefilter/
> blob/master/CMakeLists.txt#L5-L10
>
> On Tue, Dec 5, 2017 at 4:01 PM, Chris Marsh <chris.marsh at usask.ca> wrote:
> > Hi, I have a filter that decodes a posix string from a pvd file into a
> > datetime format. This has worked well, however with the newest paraview I
> > get the error
> >
> > ERROR: In
> > ParaView-v5.4.1/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx,
> line
> > 672
> >
> > vtkPVCompositeDataPipeline (0x60c0001ad9e0): Algorithm
> > vtkDateTimeAnnotation(0x60c00013e1e0) did not create output for port 0
> when
> > asked by REQUEST_DATA_OBJECT and does not specify any DATA_TYPE_NAME.
> >
> >
> > I've tried fiddling around with various things I've found on the mailing
> > list, but I'm at a bit of a loss.
> >
> > Would appreciate any help. Code is here
> > https://github.com/Chrismarsh/vtk-paraview-datetimefilter
> >
> > Cheers
> > Chris
> >
> >
> >
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171207/b7bd5dce/attachment.html>

From chris.marsh at usask.ca  Thu Dec  7 16:54:40 2017
From: chris.marsh at usask.ca (Chris Marsh)
Date: Thu, 7 Dec 2017 15:54:40 -0600
Subject: [Paraview] Filter suddenly stopped working "did not create
 output for port 0"
In-Reply-To: <CAFgDerGBAJFnG1Ez8EHAxJwXcJq2GFZ4L=P8m7gS-VcRzGe47Q@mail.gmail.com>
References: <CAFgDerH7uCZ_DEGHFK+EGz9Yri-=t08cnXGrbbbbQLKp++MzaQ@mail.gmail.com>
 <CADHSJjC_tbisQGa7ppayAVizaCoBDmLwMkfoaZcqFJxyCnT4yg@mail.gmail.com>
 <CAFgDerGBAJFnG1Ez8EHAxJwXcJq2GFZ4L=P8m7gS-VcRzGe47Q@mail.gmail.com>
Message-ID: <CAFgDerHuESsd6FZ71VKrGB1Wk0QOUvdQL4agWKnofd46+hozCQ@mail.gmail.com>

OK I have it working on my end.
I had previously configured paraview with ccmake and set build type to
Release and enabled Python.

Any idea how that may impact this?

Chris Marsh
PhD Candidate
chrismarsh.ca

121 Research Drive
University of Saskatchewan

On 7 December 2017 at 13:41, Chris Marsh <chris.marsh at usask.ca> wrote:

> Hi,
>
> Thanks for trying this. Good call on the removal of the extra CMake stuff.
> It was there because I started this filter before I knew about things like
> setting ParaView_DIR and forgot to update this!
>
> Interesting that works for you. I just rebuilt with the change to use ParaView_DIR
> (on the off chance it changed something...) but still broken on my end. :(
>
> So, this isn't an issue with the filters code, but rather something with
> how either I compiled Paraview or ... something?
>
> Are you using the github version of paraview?
>
> Cheers
> Chris
>
>
> On 6 December 2017 at 21:53, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> wrote:
>
>> I tried to build with latest "master" and I didn't get any errors. The
>> plugin worked fine. I did remove these lines [1] from the
>> CMakeLists.txt file since that was causing build errors. What are
>> those for? I'd discourage you from adding your own FindParaView.cmake.
>> Once I removed those and simply set ParaView_DIR to my build
>> directory, all built and ran fine.
>>
>> Utkarsh
>>
>>
>> [1] https://github.com/Chrismarsh/vtk-paraview-datetimefilter/bl
>> ob/master/CMakeLists.txt#L5-L10
>>
>> On Tue, Dec 5, 2017 at 4:01 PM, Chris Marsh <chris.marsh at usask.ca> wrote:
>> > Hi, I have a filter that decodes a posix string from a pvd file into a
>> > datetime format. This has worked well, however with the newest paraview
>> I
>> > get the error
>> >
>> > ERROR: In
>> > ParaView-v5.4.1/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx,
>> line
>> > 672
>> >
>> > vtkPVCompositeDataPipeline (0x60c0001ad9e0): Algorithm
>> > vtkDateTimeAnnotation(0x60c00013e1e0) did not create output for port 0
>> when
>> > asked by REQUEST_DATA_OBJECT and does not specify any DATA_TYPE_NAME.
>> >
>> >
>> > I've tried fiddling around with various things I've found on the mailing
>> > list, but I'm at a bit of a loss.
>> >
>> > Would appreciate any help. Code is here
>> > https://github.com/Chrismarsh/vtk-paraview-datetimefilter
>> >
>> > Cheers
>> > Chris
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at:
>> > http://paraview.org/Wiki/ParaView
>> >
>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://public.kitware.com/mailman/listinfo/paraview
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171207/1ac21cb9/attachment.html>

From longtuteng249 at gmail.com  Thu Dec  7 23:25:32 2017
From: longtuteng249 at gmail.com (Jianbo Long)
Date: Fri, 8 Dec 2017 00:55:32 -0330
Subject: [Paraview] BUG REPORT: Axes grid option grayed out,
 version 5.4.1 64bit, on Ubuntu 16.04
Message-ID: <CANgE3sDBBuKrhp4e3g4cn0zMd89+n7t6Mu0d9f61LB_Os92OJQ@mail.gmail.com>

Hello,

I am trying to add axes information to a clipped 3-D mesh, which was
generated by clipping, slicing, and clipping of a 3-D mesh from a .VTK
file. However, in the latest Paraview version 5.4.1,  the  'Axes grid'
option sometimes doesn't work (grayed out, please see attached picture). I
remember I could use this button a few days ago with the same version.
Even after restarting Paraview,  there's no luck.  This was not a problem
in previous versions 4.4 and 4.0.  I would like to use v5.4 because this
version has more controls over axis properties like fonts.

Could you give any ideas about this issue ?

Thank you very much,

Jianbo Long

[image: Inline image 1]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/2380349a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 79532 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/2380349a/attachment.png>

From cory.quammen at kitware.com  Thu Dec  7 23:46:27 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 7 Dec 2017 23:46:27 -0500
Subject: [Paraview] BUG REPORT: Axes grid option grayed out,
 version 5.4.1 64bit, on Ubuntu 16.04
In-Reply-To: <CANgE3sDBBuKrhp4e3g4cn0zMd89+n7t6Mu0d9f61LB_Os92OJQ@mail.gmail.com>
References: <CANgE3sDBBuKrhp4e3g4cn0zMd89+n7t6Mu0d9f61LB_Os92OJQ@mail.gmail.com>
Message-ID: <CAB5Fpx4f81BS4qDfuSX08-o=Y-mgXnK0VxkAOB6dnob22eNDaA@mail.gmail.com>

Hmm, that's strange. Can you give step-by-step directions on how to make
the buttons grayed out, preferably with a simple starting source such as
the Sphere source or Wavelet source?

Thanks,
Cory

On Thu, Dec 7, 2017 at 11:25 PM, Jianbo Long <longtuteng249 at gmail.com>
wrote:

> Hello,
>
> I am trying to add axes information to a clipped 3-D mesh, which was
> generated by clipping, slicing, and clipping of a 3-D mesh from a .VTK
> file. However, in the latest Paraview version 5.4.1,  the  'Axes grid'
> option sometimes doesn't work (grayed out, please see attached picture). I
> remember I could use this button a few days ago with the same version.
> Even after restarting Paraview,  there's no luck.  This was not a problem
> in previous versions 4.4 and 4.0.  I would like to use v5.4 because this
> version has more controls over axis properties like fonts.
>
> Could you give any ideas about this issue ?
>
> Thank you very much,
>
> Jianbo Long
>
> [image: Inline image 1]
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171207/16351591/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 79532 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171207/16351591/attachment.png>

From longtuteng249 at gmail.com  Fri Dec  8 01:10:46 2017
From: longtuteng249 at gmail.com (Jianbo Long)
Date: Fri, 8 Dec 2017 02:40:46 -0330
Subject: [Paraview] BUG REPORT: Axes grid option grayed out,
 version 5.4.1 64bit, on Ubuntu 16.04
In-Reply-To: <CAB5Fpx4f81BS4qDfuSX08-o=Y-mgXnK0VxkAOB6dnob22eNDaA@mail.gmail.com>
References: <CANgE3sDBBuKrhp4e3g4cn0zMd89+n7t6Mu0d9f61LB_Os92OJQ@mail.gmail.com>
 <CAB5Fpx4f81BS4qDfuSX08-o=Y-mgXnK0VxkAOB6dnob22eNDaA@mail.gmail.com>
Message-ID: <CANgE3sC69us2crvntLqTAaWG0Hkjj7UWq=7CeURTxujMPQsimA@mail.gmail.com>

Hi Cory,

Thanks for your email !

It feels pretty odd, though, that I cannot re-make this problem easily. I
just tested again, as you suggested, using simple Source object, and had no
problem with the  'Data Axes Grid' button.  Everything seems okay. However,
I still cannot make it work for that specific .vtk file.  I was doubting
that it might be the problem of using .pvsm file I generated  for that
particular .vtk file a few days ago ( so that I can use the same view
settings for a number of other .vtk files ). However, it appears not.  I
just did the test of this way for a different .vtk mesh: first use 'Save
State..' from the File menu to get a .pvsm file,  and then load the same
.vtk with the .pvsm by clicking 'Load State...', but this time, all buttons
seem to be  okay. The odd thing is that, when I want to work with the first
specific .pvsm file, even if with different vtk data files,  the data axes
grid buttons shown in 'Miscellaneous' and 'Annotations' won't wok (again,
see picture below)..

The problem seems to be due to my .pvsm file, but I still have no clue what
might cause the difference.

Thanks,

Jianbo


[image: Inline image 1]




On Fri, Dec 8, 2017 at 1:16 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Hmm, that's strange. Can you give step-by-step directions on how to make
> the buttons grayed out, preferably with a simple starting source such as
> the Sphere source or Wavelet source?
>
> Thanks,
> Cory
>
> On Thu, Dec 7, 2017 at 11:25 PM, Jianbo Long <longtuteng249 at gmail.com>
> wrote:
>
>> Hello,
>>
>> I am trying to add axes information to a clipped 3-D mesh, which was
>> generated by clipping, slicing, and clipping of a 3-D mesh from a .VTK
>> file. However, in the latest Paraview version 5.4.1,  the  'Axes grid'
>> option sometimes doesn't work (grayed out, please see attached picture). I
>> remember I could use this button a few days ago with the same version.
>> Even after restarting Paraview,  there's no luck.  This was not a problem
>> in previous versions 4.4 and 4.0.  I would like to use v5.4 because this
>> version has more controls over axis properties like fonts.
>>
>> Could you give any ideas about this issue ?
>>
>> Thank you very much,
>>
>> Jianbo Long
>>
>> [image: Inline image 1]
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/7ebb0eca/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 77263 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/7ebb0eca/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 79532 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/7ebb0eca/attachment-0003.png>

From utkarsh.ayachit at kitware.com  Fri Dec  8 08:38:34 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 8 Dec 2017 08:38:34 -0500
Subject: [Paraview] Filter suddenly stopped working "did not create
 output for port 0"
In-Reply-To: <CAFgDerHuESsd6FZ71VKrGB1Wk0QOUvdQL4agWKnofd46+hozCQ@mail.gmail.com>
References: <CAFgDerH7uCZ_DEGHFK+EGz9Yri-=t08cnXGrbbbbQLKp++MzaQ@mail.gmail.com>
 <CADHSJjC_tbisQGa7ppayAVizaCoBDmLwMkfoaZcqFJxyCnT4yg@mail.gmail.com>
 <CAFgDerGBAJFnG1Ez8EHAxJwXcJq2GFZ4L=P8m7gS-VcRzGe47Q@mail.gmail.com>
 <CAFgDerHuESsd6FZ71VKrGB1Wk0QOUvdQL4agWKnofd46+hozCQ@mail.gmail.com>
Message-ID: <CADHSJjBa7-2vEOBBPeESzHam+wMDVmh1GaDYY5ZTTW2dPWMt+g@mail.gmail.com>

> I had previously configured paraview with ccmake and set build type to
> Release and enabled Python.
> Any idea how that may impact this?

Not entirely sure how, unless some incorrect libraries are getting
loaded. Are you on Windows? Is your PATH sane?

Utkarsh

From cory.quammen at kitware.com  Fri Dec  8 09:20:00 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 8 Dec 2017 09:20:00 -0500
Subject: [Paraview] BUG REPORT: Axes grid option grayed out,
 version 5.4.1 64bit, on Ubuntu 16.04
In-Reply-To: <CANgE3sC69us2crvntLqTAaWG0Hkjj7UWq=7CeURTxujMPQsimA@mail.gmail.com>
References: <CANgE3sDBBuKrhp4e3g4cn0zMd89+n7t6Mu0d9f61LB_Os92OJQ@mail.gmail.com>
 <CAB5Fpx4f81BS4qDfuSX08-o=Y-mgXnK0VxkAOB6dnob22eNDaA@mail.gmail.com>
 <CANgE3sC69us2crvntLqTAaWG0Hkjj7UWq=7CeURTxujMPQsimA@mail.gmail.com>
Message-ID: <CAB5Fpx5QYEScUiOsV=Jf1MS1ZoaKmk-aaoDZj6LH5b=mxa=VHA@mail.gmail.com>

Jianbo,

How strange. If you would like to send me the offending ParaView state file
(off list is fine), I'd be happy to take a look to see if anything stands
out.

Thanks,
Cory

On Fri, Dec 8, 2017 at 1:10 AM, Jianbo Long <longtuteng249 at gmail.com> wrote:

> Hi Cory,
>
> Thanks for your email !
>
> It feels pretty odd, though, that I cannot re-make this problem easily. I
> just tested again, as you suggested, using simple Source object, and had no
> problem with the  'Data Axes Grid' button.  Everything seems okay. However,
> I still cannot make it work for that specific .vtk file.  I was doubting
> that it might be the problem of using .pvsm file I generated  for that
> particular .vtk file a few days ago ( so that I can use the same view
> settings for a number of other .vtk files ). However, it appears not.  I
> just did the test of this way for a different .vtk mesh: first use 'Save
> State..' from the File menu to get a .pvsm file,  and then load the same
> .vtk with the .pvsm by clicking 'Load State...', but this time, all buttons
> seem to be  okay. The odd thing is that, when I want to work with the first
> specific .pvsm file, even if with different vtk data files,  the data axes
> grid buttons shown in 'Miscellaneous' and 'Annotations' won't wok (again,
> see picture below)..
>
> The problem seems to be due to my .pvsm file, but I still have no clue
> what might cause the difference.
>
> Thanks,
>
> Jianbo
>
>
> [image: Inline image 1]
>
>
>
>
> On Fri, Dec 8, 2017 at 1:16 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> Hmm, that's strange. Can you give step-by-step directions on how to make
>> the buttons grayed out, preferably with a simple starting source such as
>> the Sphere source or Wavelet source?
>>
>> Thanks,
>> Cory
>>
>> On Thu, Dec 7, 2017 at 11:25 PM, Jianbo Long <longtuteng249 at gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I am trying to add axes information to a clipped 3-D mesh, which was
>>> generated by clipping, slicing, and clipping of a 3-D mesh from a .VTK
>>> file. However, in the latest Paraview version 5.4.1,  the  'Axes grid'
>>> option sometimes doesn't work (grayed out, please see attached picture). I
>>> remember I could use this button a few days ago with the same version.
>>> Even after restarting Paraview,  there's no luck.  This was not a problem
>>> in previous versions 4.4 and 4.0.  I would like to use v5.4 because this
>>> version has more controls over axis properties like fonts.
>>>
>>> Could you give any ideas about this issue ?
>>>
>>> Thank you very much,
>>>
>>> Jianbo Long
>>>
>>> [image: Inline image 1]
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.
>>
>
>


-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/e41a664a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 77263 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/e41a664a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 79532 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/e41a664a/attachment-0001.png>

From chuck.atkins at kitware.com  Fri Dec  8 09:35:21 2017
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Fri, 8 Dec 2017 09:35:21 -0500
Subject: [Paraview] from matlab to paraview
In-Reply-To: <HE1PR0602MB3468150827411BA259AEEC95A4330@HE1PR0602MB3468.eurprd06.prod.outlook.com>
References: <HE1PR0602MB3468150827411BA259AEEC95A4330@HE1PR0602MB3468.eurprd06.prod.outlook.com>
Message-ID: <CAOXZzG4gmFq7ERbGA23hnVOK07W49f03UHEztX9piYJpB5ihBg@mail.gmail.com>

Hi Doina,

Can you not just open it directly from [File] -> "Open"?  Or are you
wanting to build a script to do automated processing?  If you're trying to
do automated processing, the easiest way to build your script is perform
the actions in the GU and "record" that as a python script with [Tools] ->
"Start trace", doing the things you want, and then [Tools] -> "Stop
trace".  The resulting python file can be run directly with either pvpython
or pvbatch.

----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.


On Thu, Dec 7, 2017 at 10:09 AM, Doina Gumeniuc (224252 MAHS) <224252 at via.dk
> wrote:

> Hi all!
>
>
> I have created a vtk file in matlab and I would like to export it to
> paraview. I need a script/function which would load this vtk file from
> matlab to paraview.
>
> I would really appreciate if any of you could share some hints or some
> links where such a process is explained.
>
>
> Thank you!
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/a2fd5d96/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Dec  8 10:10:13 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 8 Dec 2017 10:10:13 -0500
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
 <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
 <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>
Message-ID: <CADHSJjCzbbxbSzRJqa_tmidiEq-=AtegFq5X8xWnWt9mrpN-mA@mail.gmail.com>

Hmm, little confused here? Why not keep the timesteps in the reader
unchanged and explcitly do the timestep of interest and save
screenshot?

On Thu, Dec 7, 2017 at 10:51 AM, Heiland, Randy <heiland at iu.edu> wrote:
> Utkarsh,
>
> Thanks very much for that!  Yes, after some fiddling, I got it to work, i.e., I can save .png files for an animation! So now that I?m using the Programmable Source(RequestInfo) script to accomplish the animation, how do I, during a PV session, *easily* switch back to render a single file?
>
> For example, I can do:
> frames = range(0,801,100)   #  render every 100th frame, including 800
> setOutputTimesteps (self, frames)
>
> or, I can explicitly list specific frames:
> frames = [100,101]
>
> so, I thought this would do a single file, but it doesn?t (my previous frames are still there):
> frames = [600,]
>
> -Randy
>
>
>
>> On Dec 6, 2017, at 10:44 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>>
>> Randy,
>>
>> You attempting to mix the Python scripting for data processing and
>> Python scripting for batch scripting. The two environments are
>> separate. Here's how I'd tackle it.
>>
>> 1. Make your "Programmable Source" become a temporal source i.e.
>> report to ParaView that it can produce timesteps matching the files
>> your file series. See [i]. If you get this right, you shuold be able
>> to render through all the files by hitting "Play" in the VCR control
>> in the UI.
>> 2. Now you can write a batch script that either loads the predefined
>> pvsm state file or builds up the pipeline in Python itself and the
>> either uses `SaveScreenshot` or `SaveAnimation` to save out the
>> animation.
>>
>> You can then mix in camera animations too. You can always use the
>> Python tracing in UI to figure out how to save images and/or animation
>> in the batch scripting environment.
>>
>> Hope that helps.
>> Utkarsh
>>
>> [i] https://blog.kitware.com/defining-time-varying-sources-with-paraviews-programmable-source/
>>
>> On Wed, Dec 6, 2017 at 11:15 AM, Heiland, Randy <heiland at iu.edu> wrote:
>>> I?m probably missing a basic concept and hoping someone can enlighten me. I
>>> have a pipeline with a Programmable Source that reads in a (non-VTK
>>> formatted) file, I process it and then I have filters in my pipeline that
>>> act on that data. I want to be able to feed multiple files to the pipeline,
>>> save images and/or create animations. I naively created a Python function in
>>> the Pgmable Source, then save the PV State to a Python script, thinking I
>>> could call the function from the end of that script. Doesn?t seem to be
>>> possible. And I confess I?ve not given this deep thought - it?s easier to
>>> ask the experts :-)  Bottom line, we want to make this as dead simple for
>>> our own users.
>>>
>>> Fwiw, I?ve zipped up 2 files - a .pvsm and a sample data file here:
>>> http://pages.iu.edu/~heiland/physicell/pv_pcell.zip . You?d need to edit the
>>> ?dir? path in the Pgmable Source.
>>>
>>> Initially, I just want to save images/animation (over multiple files) with a
>>> fixed camera view; later, it?d be nice to have simultaneous camera movement.
>>>
>>> thanks, Randy
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>

From utkarsh.ayachit at kitware.com  Fri Dec  8 10:10:58 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 8 Dec 2017 10:10:58 -0500
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <CADHSJjCzbbxbSzRJqa_tmidiEq-=AtegFq5X8xWnWt9mrpN-mA@mail.gmail.com>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
 <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
 <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>
 <CADHSJjCzbbxbSzRJqa_tmidiEq-=AtegFq5X8xWnWt9mrpN-mA@mail.gmail.com>
Message-ID: <CADHSJjArq8spR5Hds5x=ihW2T32rnaaRWER5-78tzgqqamQ==Q@mail.gmail.com>

Oops. I meant to say -- "I am a little confused here" :).

On Fri, Dec 8, 2017 at 10:10 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Hmm, little confused here? Why not keep the timesteps in the reader
> unchanged and explcitly do the timestep of interest and save
> screenshot?
>
> On Thu, Dec 7, 2017 at 10:51 AM, Heiland, Randy <heiland at iu.edu> wrote:
>> Utkarsh,
>>
>> Thanks very much for that!  Yes, after some fiddling, I got it to work, i.e., I can save .png files for an animation! So now that I?m using the Programmable Source(RequestInfo) script to accomplish the animation, how do I, during a PV session, *easily* switch back to render a single file?
>>
>> For example, I can do:
>> frames = range(0,801,100)   #  render every 100th frame, including 800
>> setOutputTimesteps (self, frames)
>>
>> or, I can explicitly list specific frames:
>> frames = [100,101]
>>
>> so, I thought this would do a single file, but it doesn?t (my previous frames are still there):
>> frames = [600,]
>>
>> -Randy
>>
>>
>>
>>> On Dec 6, 2017, at 10:44 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>>>
>>> Randy,
>>>
>>> You attempting to mix the Python scripting for data processing and
>>> Python scripting for batch scripting. The two environments are
>>> separate. Here's how I'd tackle it.
>>>
>>> 1. Make your "Programmable Source" become a temporal source i.e.
>>> report to ParaView that it can produce timesteps matching the files
>>> your file series. See [i]. If you get this right, you shuold be able
>>> to render through all the files by hitting "Play" in the VCR control
>>> in the UI.
>>> 2. Now you can write a batch script that either loads the predefined
>>> pvsm state file or builds up the pipeline in Python itself and the
>>> either uses `SaveScreenshot` or `SaveAnimation` to save out the
>>> animation.
>>>
>>> You can then mix in camera animations too. You can always use the
>>> Python tracing in UI to figure out how to save images and/or animation
>>> in the batch scripting environment.
>>>
>>> Hope that helps.
>>> Utkarsh
>>>
>>> [i] https://blog.kitware.com/defining-time-varying-sources-with-paraviews-programmable-source/
>>>
>>> On Wed, Dec 6, 2017 at 11:15 AM, Heiland, Randy <heiland at iu.edu> wrote:
>>>> I?m probably missing a basic concept and hoping someone can enlighten me. I
>>>> have a pipeline with a Programmable Source that reads in a (non-VTK
>>>> formatted) file, I process it and then I have filters in my pipeline that
>>>> act on that data. I want to be able to feed multiple files to the pipeline,
>>>> save images and/or create animations. I naively created a Python function in
>>>> the Pgmable Source, then save the PV State to a Python script, thinking I
>>>> could call the function from the end of that script. Doesn?t seem to be
>>>> possible. And I confess I?ve not given this deep thought - it?s easier to
>>>> ask the experts :-)  Bottom line, we want to make this as dead simple for
>>>> our own users.
>>>>
>>>> Fwiw, I?ve zipped up 2 files - a .pvsm and a sample data file here:
>>>> http://pages.iu.edu/~heiland/physicell/pv_pcell.zip . You?d need to edit the
>>>> ?dir? path in the Pgmable Source.
>>>>
>>>> Initially, I just want to save images/animation (over multiple files) with a
>>>> fixed camera view; later, it?d be nice to have simultaneous camera movement.
>>>>
>>>> thanks, Randy
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView
>>>>
>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>
>>

From heiland at iu.edu  Fri Dec  8 11:22:18 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Fri, 8 Dec 2017 16:22:18 +0000
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <CADHSJjArq8spR5Hds5x=ihW2T32rnaaRWER5-78tzgqqamQ==Q@mail.gmail.com>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
 <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
 <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>
 <CADHSJjCzbbxbSzRJqa_tmidiEq-=AtegFq5X8xWnWt9mrpN-mA@mail.gmail.com>
 <CADHSJjArq8spR5Hds5x=ihW2T32rnaaRWER5-78tzgqqamQ==Q@mail.gmail.com>
Message-ID: <CF6D3CE4-3224-466A-946B-F1C4AACD4414@iu.edu>

No, no, I?m sure it?s *me* who?s confused.  I?m not sure I understand what you?re saying. Are you suggesting keeping the (full) range of timesteps in my script and then, somehow, only render the one of interest? If so, that would be great, except the way things are currently working for me, after loading the .pvsm initially, it renders the first requested tilmestep, but I cannot just enter a desired timestep value into the ?Time? widget field. I can only single step through them via the up/down arrow widget.

Not sure if it?s related, but after loading the state file, in the Output Messages, I get the following error/warning, even though it does render the first one properly:

Traceback (most recent call last):
  File "<string>", line 20, in <module>
  File "<string>", line 34, in RequestInformation
TypeError: arguments do not match any overloaded methods
------- time=  100.0
fname= /Users/heiland/git/PhysiCell/run2_cancer_immune/output00000100_cells_physicell
num_cells_possible = 38080
num_cells = 38080

I?ve attached my Programmable Source Script and Script(RequestInfo), fwiw. Line 34 of RequestInfo is the very last line in that script.
output.GetInformation().Set(output.DATA_TIME_STEP(), req_time)


thanks!
Randy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Script.py
Type: text/x-python-script
Size: 3736 bytes
Desc: Script.py
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/36895ce7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Script_Reqinfo.py
Type: text/x-python-script
Size: 1248 bytes
Desc: Script_Reqinfo.py
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/36895ce7/attachment-0001.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/36895ce7/attachment.txt>

From wascott at sandia.gov  Fri Dec  8 12:42:49 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 8 Dec 2017 17:42:49 +0000
Subject: [Paraview] [EXTERNAL] Re: BUG REPORT: Axes grid option grayed
 out, version 5.4.1 64bit, on Ubuntu 16.04
In-Reply-To: <CAB5Fpx4f81BS4qDfuSX08-o=Y-mgXnK0VxkAOB6dnob22eNDaA@mail.gmail.com>
References: <CANgE3sDBBuKrhp4e3g4cn0zMd89+n7t6Mu0d9f61LB_Os92OJQ@mail.gmail.com>
 <CAB5Fpx4f81BS4qDfuSX08-o=Y-mgXnK0VxkAOB6dnob22eNDaA@mail.gmail.com>
Message-ID: <B57926C6-DD7D-4B02-B714-1419AA76F19A@sandia.gov>

Also, I have seen times when the configuration files get messed up.  Try moving them to the side, and try again.  If this does clear up the problem, please e-mail the configuration files to Cory, so we can figure out what happened.

Configuration file documentation can be found here: https://www.paraview.org/Wiki/ParaView_Settings_Files

Alan

From: ParaView <paraview-bounces at paraview.org> on behalf of Cory Quammen <cory.quammen at kitware.com>
Date: Thursday, December 7, 2017 at 9:46 PM
To: Jianbo Long <longtuteng249 at gmail.com>
Cc: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] BUG REPORT: Axes grid option grayed out, version 5.4.1 64bit, on Ubuntu 16.04

Hmm, that's strange. Can you give step-by-step directions on how to make the buttons grayed out, preferably with a simple starting source such as the Sphere source or Wavelet source?

Thanks,
Cory

On Thu, Dec 7, 2017 at 11:25 PM, Jianbo Long <longtuteng249 at gmail.com<mailto:longtuteng249 at gmail.com>> wrote:
Hello,

I am trying to add axes information to a clipped 3-D mesh, which was generated by clipping, slicing, and clipping of a 3-D mesh from a .VTK file. However, in the latest Paraview version 5.4.1,  the  'Axes grid' option sometimes doesn't work (grayed out, please see attached picture). I remember I could use this button a few days ago with the same version.  Even after restarting Paraview,  there's no luck.  This was not a problem in previous versions 4.4 and 4.0.  I would like to use v5.4 because this version has more controls over axis properties like fonts.

Could you give any ideas about this issue ?

Thank you very much,

Jianbo Long

[nline image 1]

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

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

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

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

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



--
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/d23bd448/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 104238 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/d23bd448/attachment.png>

From wascott at sandia.gov  Fri Dec  8 14:48:06 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 8 Dec 2017 19:48:06 +0000
Subject: [Paraview] [EXTERNAL] Segfault with 'Hover Cells' over 3d glyphs
In-Reply-To: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>
References: <CAHQ20oe-uzQ7h8D6u67c1sMnEaW9Zhu-ztt4r9gPdmxt=z3GBg@mail.gmail.com>
Message-ID: <E2E038F0-5FDA-4A91-B0FC-70E7FBBC9B83@sandia.gov>

I believe that the warnings you are seeing is new in the developers tree (i.e., the Alpha that was released for SC), and is being looked at here:  https://gitlab.kitware.com/paraview/paraview/issues/17633#note_352250.  If they don?t go away, we will have to fix them.

The main crash is real.  I replicated it here: https://gitlab.kitware.com/paraview/paraview/issues/17882.

Thanks for reporting.

Alan

From: ParaView <paraview-bounces at paraview.org> on behalf of Wyatt Spear <wspear at cs.uoregon.edu>
Date: Tuesday, December 5, 2017 at 12:10 PM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Segfault with 'Hover Cells' over 3d glyphs

Greetings,

I'm using the SC17 preview of 5.5 of ParaView. I first noticed this error with my own dataset but it appears with the simple test.csv I've included. To reproduce the segfault:

Load the attached (or presumably any) CSV points file.
Run the TableToPoints filter.
Assign the X/Y/Z column dropdowns to the x coord/y coord/z coord values.
Hit Apply
Hit the 'Hover Cells On' button in the 3d display and mouse over a point to confirm it works.
In the 'Representation' drop down box select "3D Glyphs".
In the 'Glyph Type' drop down box select "Box" (I wasn't able to reproduce the error with arrows)
Hover over one of the resulting box glyphs for instant segfault.

Command line output from this session was:
Generic Warning: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 511
Failed to locate property: OSPRayMaterialLibrary

Generic Warning: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 831
Call not supported for the current property type.

Segmentation fault (core dumped)

Regards,
Wyatt Spear


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

From utkarsh.ayachit at kitware.com  Fri Dec  8 15:07:07 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 8 Dec 2017 15:07:07 -0500
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <CF6D3CE4-3224-466A-946B-F1C4AACD4414@iu.edu>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
 <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
 <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>
 <CADHSJjCzbbxbSzRJqa_tmidiEq-=AtegFq5X8xWnWt9mrpN-mA@mail.gmail.com>
 <CADHSJjArq8spR5Hds5x=ihW2T32rnaaRWER5-78tzgqqamQ==Q@mail.gmail.com>
 <CF6D3CE4-3224-466A-946B-F1C4AACD4414@iu.edu>
Message-ID: <CADHSJjB57iwzuuVbBdJ4ns0OLQtJHioPMu9WtBP8gokzbfWdxQ@mail.gmail.com>

Randy,

Mind explaining to me what;s your ultimate goal? The way I see it,
there are two options:

1. Provide your users with a state file that they load in ParaView UI
and then use the UI to save animation or images. Use the UI to move
back and forth through the timesteps, etc.
2. Provide your users with a Python script that they run using
pvpython to save out screenshots or animations based on command line
arguments.

Which one are you aiming for? Or is it something else?

Utkarsh



On Fri, Dec 8, 2017 at 11:22 AM, Heiland, Randy <heiland at iu.edu> wrote:
> No, no, I?m sure it?s *me* who?s confused.  I?m not sure I understand what you?re saying. Are you suggesting keeping the (full) range of timesteps in my script and then, somehow, only render the one of interest? If so, that would be great, except the way things are currently working for me, after loading the .pvsm initially, it renders the first requested tilmestep, but I cannot just enter a desired timestep value into the ?Time? widget field. I can only single step through them via the up/down arrow widget.
>
> Not sure if it?s related, but after loading the state file, in the Output Messages, I get the following error/warning, even though it does render the first one properly:
>
> Traceback (most recent call last):
>   File "<string>", line 20, in <module>
>   File "<string>", line 34, in RequestInformation
> TypeError: arguments do not match any overloaded methods
> ------- time=  100.0
> fname= /Users/heiland/git/PhysiCell/run2_cancer_immune/output00000100_cells_physicell
> num_cells_possible = 38080
> num_cells = 38080
>
> I?ve attached my Programmable Source Script and Script(RequestInfo), fwiw. Line 34 of RequestInfo is the very last line in that script.
> output.GetInformation().Set(output.DATA_TIME_STEP(), req_time)
>
>
> thanks!
> Randy

From heiland at iu.edu  Fri Dec  8 15:29:58 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Fri, 8 Dec 2017 20:29:58 +0000
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <CADHSJjB57iwzuuVbBdJ4ns0OLQtJHioPMu9WtBP8gokzbfWdxQ@mail.gmail.com>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
 <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
 <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>
 <CADHSJjCzbbxbSzRJqa_tmidiEq-=AtegFq5X8xWnWt9mrpN-mA@mail.gmail.com>
 <CADHSJjArq8spR5Hds5x=ihW2T32rnaaRWER5-78tzgqqamQ==Q@mail.gmail.com>
 <CF6D3CE4-3224-466A-946B-F1C4AACD4414@iu.edu>
 <CADHSJjB57iwzuuVbBdJ4ns0OLQtJHioPMu9WtBP8gokzbfWdxQ@mail.gmail.com>
Message-ID: <ECFA0EF4-A4F7-4B8C-B3C3-65AD3721E062@iu.edu>

Have a user read in a state file to experiment with a pipeline/filters on a single data file, e.g. they may have 1000 files and they want to initially  look at the last one. When they?re content with the vis on a single file, they?d like to view an animation in PV on all (or mod N) files. When they?re happy with that, they?d like to save .png?s - preferably batch/offscreen, but whatever.

Randy


> On Dec 8, 2017, at 3:07 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
> 
> Randy,
> 
> Mind explaining to me what;s your ultimate goal? The way I see it,
> there are two options:
> 
> 1. Provide your users with a state file that they load in ParaView UI
> and then use the UI to save animation or images. Use the UI to move
> back and forth through the timesteps, etc.
> 2. Provide your users with a Python script that they run using
> pvpython to save out screenshots or animations based on command line
> arguments.
> 
> Which one are you aiming for? Or is it something else?
> 
> Utkarsh
> 
> 
> 
> On Fri, Dec 8, 2017 at 11:22 AM, Heiland, Randy <heiland at iu.edu> wrote:
>> No, no, I?m sure it?s *me* who?s confused.  I?m not sure I understand what you?re saying. Are you suggesting keeping the (full) range of timesteps in my script and then, somehow, only render the one of interest? If so, that would be great, except the way things are currently working for me, after loading the .pvsm initially, it renders the first requested tilmestep, but I cannot just enter a desired timestep value into the ?Time? widget field. I can only single step through them via the up/down arrow widget.
>> 
>> Not sure if it?s related, but after loading the state file, in the Output Messages, I get the following error/warning, even though it does render the first one properly:
>> 
>> Traceback (most recent call last):
>>  File "<string>", line 20, in <module>
>>  File "<string>", line 34, in RequestInformation
>> TypeError: arguments do not match any overloaded methods
>> ------- time=  100.0
>> fname= /Users/heiland/git/PhysiCell/run2_cancer_immune/output00000100_cells_physicell
>> num_cells_possible = 38080
>> num_cells = 38080
>> 
>> I?ve attached my Programmable Source Script and Script(RequestInfo), fwiw. Line 34 of RequestInfo is the very last line in that script.
>> output.GetInformation().Set(output.DATA_TIME_STEP(), req_time)
>> 
>> 
>> thanks!
>> Randy


From chris.marsh at usask.ca  Fri Dec  8 23:43:20 2017
From: chris.marsh at usask.ca (Chris Marsh)
Date: Fri, 8 Dec 2017 22:43:20 -0600
Subject: [Paraview] Filter suddenly stopped working "did not create
 output for port 0"
In-Reply-To: <CADHSJjBa7-2vEOBBPeESzHam+wMDVmh1GaDYY5ZTTW2dPWMt+g@mail.gmail.com>
References: <CAFgDerH7uCZ_DEGHFK+EGz9Yri-=t08cnXGrbbbbQLKp++MzaQ@mail.gmail.com>
 <CADHSJjC_tbisQGa7ppayAVizaCoBDmLwMkfoaZcqFJxyCnT4yg@mail.gmail.com>
 <CAFgDerGBAJFnG1Ez8EHAxJwXcJq2GFZ4L=P8m7gS-VcRzGe47Q@mail.gmail.com>
 <CAFgDerHuESsd6FZ71VKrGB1Wk0QOUvdQL4agWKnofd46+hozCQ@mail.gmail.com>
 <CADHSJjBa7-2vEOBBPeESzHam+wMDVmh1GaDYY5ZTTW2dPWMt+g@mail.gmail.com>
Message-ID: <CAFgDerEsBgZynFAS0tOxj0hQ=N-voSDrGcYMMd2BFBBA4BTk1g@mail.gmail.com>

On MacOS. I had an old paraview in my path that I removed prior to this.
Perhaps that was it...changed too much now....


On 8 December 2017 at 07:38, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
wrote:

> > I had previously configured paraview with ccmake and set build type to
> > Release and enabled Python.
> > Any idea how that may impact this?
>
> Not entirely sure how, unless some incorrect libraries are getting
> loaded. Are you on Windows? Is your PATH sane?
>
> Utkarsh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171208/82ef531d/attachment.html>

From joachim.pouderoux at kitware.com  Sat Dec  9 10:39:32 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Sat, 9 Dec 2017 11:39:32 -0400
Subject: [Paraview] Memory issue for remote visualization
In-Reply-To: <BN3PR0701MB1687D9F5F85353361FE5C2AA9F320@BN3PR0701MB1687.namprd07.prod.outlook.com>
References: <BN3PR0701MB1687D9F5F85353361FE5C2AA9F320@BN3PR0701MB1687.namprd07.prod.outlook.com>
Message-ID: <CACJ=gTijLvwvuzjf10XL9v3-heO6kwYaogP0MDG-nKVq3Gzx3Q@mail.gmail.com>

Dennis,

I guess in this case, the memory inspector shows the process memory limit
(RLIMIT_AS) and not the system memory size.
Did you consider the use of `ulimit`?
You can calling something like: ulimit -u unlimited

Best,
Joachim

*Joachim Pouderoux*, PhD

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


2017-12-06 16:26 GMT-04:00 Dennis Conklin <dennis_conklin at goodyear.com>:

> All,
>
>
>
> As we start down the road to parallel visualization, our first baby steps
> are to try remote visualization.
>
>
>
> In Redhat, I ssh onto a node with ~30 gigs of memory available (free -m)
> I start pvserver.
>
> Back on my machine I launch paraview541 and connect to the server.  The
> Memory Inspector shows 2.1 GB of total system ram on the server.
>
> If I try to load a model of any size, the server bombs on a segmentation
> error (memory).
>
>
>
> If I log onto the remote node with 30 GB free memory, I can only run
> standalone paraview if I use the ?mesa-llvm command line.   When I do
> this,  Memory Inspector in standalone Paraview says there is only 2.1 GB of
> total system memory.
>
>
>
> Am I missing something ? I don?t see  how this is ever going to work if
> neither a remote paraview or a remote pvserver can see and/or access the
> available free memory on the remote machine.
>
>
>
> Thanks for any hints
>
>
>
> Dennis
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171209/acf46041/attachment.html>

From ddeepwell at uwaterloo.ca  Sat Dec  9 11:12:06 2017
From: ddeepwell at uwaterloo.ca (David Deepwell)
Date: Sat, 9 Dec 2017 16:12:06 +0000
Subject: [Paraview] curvilinear CF conventions
Message-ID: <1203465e94504e18b45842b79e153cbf@uwaterloo.ca>

Hi all,

I have a netcdf file that follows the CF conventions in curvilinear (structured) coordinates. Paraview however doesn?t recognize the auxiliary variable as the grid variable on which the rest of the fields should be plotted on. I?m not sure if this a bug with paraview misinterpreting the CF convention or if I just happen to have an attribute missing that Paraview is looking for.

Cheers,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171209/f70deca3/attachment.html>

From kmorel at sandia.gov  Sat Dec  9 11:34:07 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Sat, 9 Dec 2017 16:34:07 +0000
Subject: [Paraview] curvilinear CF conventions
In-Reply-To: <1203465e94504e18b45842b79e153cbf@uwaterloo.ca>
References: <1203465e94504e18b45842b79e153cbf@uwaterloo.ca>
Message-ID: <77E8AE5F-E380-4ACB-9DBB-F1A83FE2B13D@sandia.gov>

David,

The netCDF/CF reader should be able to read curvilinear coordinates. There is not enough information in your email to determine whether the issue is with the ParaView reader or an issue with the data file. It would be helpful if you could send us an example file so we can replicate your problem.

-Ken

Sent from my iPad

On Dec 9, 2017, at 9:12 AM, David Deepwell <ddeepwell at uwaterloo.ca<mailto:ddeepwell at uwaterloo.ca>> wrote:


Hi all,

I have a netcdf file that follows the CF conventions in curvilinear (structured) coordinates. Paraview however doesn't recognize the auxiliary variable as the grid variable on which the rest of the fields should be plotted on. I'm not sure if this a bug with paraview misinterpreting the CF convention or if I just happen to have an attribute missing that Paraview is looking for.

Cheers,
David

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

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

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

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

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

From utkarsh.ayachit at kitware.com  Sat Dec  9 13:40:24 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 9 Dec 2017 13:40:24 -0500
Subject: [Paraview] animation: files, pgmable source
In-Reply-To: <ECFA0EF4-A4F7-4B8C-B3C3-65AD3721E062@iu.edu>
References: <6346CC7B-7ACB-4DDC-8BAE-2A8476A6A3D4@iu.edu>
 <CADHSJjB3L3cXFrazGt+Oty2885gyiyXHvwQ7CgBFG0k-GK4x_Q@mail.gmail.com>
 <A2266B56-474A-414B-9E3A-FD1D69E442A4@iu.edu>
 <CADHSJjCzbbxbSzRJqa_tmidiEq-=AtegFq5X8xWnWt9mrpN-mA@mail.gmail.com>
 <CADHSJjArq8spR5Hds5x=ihW2T32rnaaRWER5-78tzgqqamQ==Q@mail.gmail.com>
 <CF6D3CE4-3224-466A-946B-F1C4AACD4414@iu.edu>
 <CADHSJjB57iwzuuVbBdJ4ns0OLQtJHioPMu9WtBP8gokzbfWdxQ@mail.gmail.com>
 <ECFA0EF4-A4F7-4B8C-B3C3-65AD3721E062@iu.edu>
Message-ID: <CADHSJjB-Dmco6J+y+Z4qSax1ZCQjc93ZMxaWJ4riyxFUQrUmBg@mail.gmail.com>

Randy,

Here's how I'd proceed.

1. Create a programmable source to read a file series as a temporal
dataset. (you have this already).
2. Let the users use ParaView to save animation or screenshots once
they are satisfied.
3. You can put the "Extract TimeSteps" filter after your reader
(before any of the other pipeline) and make it filter timesteps. It
allows filtering over a range of timesteps with an arbitrary interval.
So your users can change this to choose which subset they are
interested in. I'd also point to the "Time INspector" so user can see
what timesteps ParaView is taking into consideration.

Utkarsh



On Fri, Dec 8, 2017 at 3:29 PM, Heiland, Randy <heiland at iu.edu> wrote:
> Have a user read in a state file to experiment with a pipeline/filters on a single data file, e.g. they may have 1000 files and they want to initially  look at the last one. When they?re content with the vis on a single file, they?d like to view an animation in PV on all (or mod N) files. When they?re happy with that, they?d like to save .png?s - preferably batch/offscreen, but whatever.
>
> Randy
>
>
>> On Dec 8, 2017, at 3:07 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>>
>> Randy,
>>
>> Mind explaining to me what;s your ultimate goal? The way I see it,
>> there are two options:
>>
>> 1. Provide your users with a state file that they load in ParaView UI
>> and then use the UI to save animation or images. Use the UI to move
>> back and forth through the timesteps, etc.
>> 2. Provide your users with a Python script that they run using
>> pvpython to save out screenshots or animations based on command line
>> arguments.
>>
>> Which one are you aiming for? Or is it something else?
>>
>> Utkarsh
>>
>>
>>
>> On Fri, Dec 8, 2017 at 11:22 AM, Heiland, Randy <heiland at iu.edu> wrote:
>>> No, no, I?m sure it?s *me* who?s confused.  I?m not sure I understand what you?re saying. Are you suggesting keeping the (full) range of timesteps in my script and then, somehow, only render the one of interest? If so, that would be great, except the way things are currently working for me, after loading the .pvsm initially, it renders the first requested tilmestep, but I cannot just enter a desired timestep value into the ?Time? widget field. I can only single step through them via the up/down arrow widget.
>>>
>>> Not sure if it?s related, but after loading the state file, in the Output Messages, I get the following error/warning, even though it does render the first one properly:
>>>
>>> Traceback (most recent call last):
>>>  File "<string>", line 20, in <module>
>>>  File "<string>", line 34, in RequestInformation
>>> TypeError: arguments do not match any overloaded methods
>>> ------- time=  100.0
>>> fname= /Users/heiland/git/PhysiCell/run2_cancer_immune/output00000100_cells_physicell
>>> num_cells_possible = 38080
>>> num_cells = 38080
>>>
>>> I?ve attached my Programmable Source Script and Script(RequestInfo), fwiw. Line 34 of RequestInfo is the very last line in that script.
>>> output.GetInformation().Set(output.DATA_TIME_STEP(), req_time)
>>>
>>>
>>> thanks!
>>> Randy
>

From ezhkr601 at student.liu.se  Mon Dec 11 18:29:38 2017
From: ezhkr601 at student.liu.se (Ezhilmathi Krishnasamy)
Date: Tue, 12 Dec 2017 00:29:38 +0100
Subject: [Paraview] [paraview] visualize higher order element.
In-Reply-To: <CAMaOp+ERkhhTGu937_Q+VDdBACPvioSbxqHj73qNTSWzDD8dDA@mail.gmail.com>
References: <F2B7862F-3EFA-4A00-8DA4-B7D0C6BA2B9A@student.liu.se>
 <CAMaOp+HCZe2OBPQ_7-b_CrsxaSfrUMnju97kpGHicB9Cop69-g@mail.gmail.com>
 <CACrYMsJ2Ka_tujdX87Nm2Vav+b9QgdEHdPXO-nDN22kdTvb-gQ@mail.gmail.com>
 <CACrYMsJw=dwiXHy2Gi7RUR=bu93dMdT+hRBiPpe8a0D850-nXA@mail.gmail.com>
 <CAMaOp+ERkhhTGu937_Q+VDdBACPvioSbxqHj73qNTSWzDD8dDA@mail.gmail.com>
Message-ID: <CACrYMsKid3DDL8=ykSPNxFwYMHv5FJ+4uU3TqTH+B3j8Ld+mcA@mail.gmail.com>

Hi Andy,

Thanks a lot :) this is working!  this is what I want.

Kind regards,
Mathi

On 11 October 2017 at 17:47, Andy Bauer <andy.bauer at kitware.com> wrote:

> Hi Mathi,
>
> When I looked at the file in ParaView it seems like the connectivity is
> wrong with your cells. If you try the Clean to Grid filter that should fix
> your problem. I would suggest fixing the connectivity though as the best
> way to manage the data since the Clean to Grid filter will merge coincident
> points and may inadvertently mess up your point data fields for the
> coincident points. Note that the Clean to Grid filter reduced the number of
> points in your grid from 2,006,480 to 451,792.
>
> Cheers,
> Andy
>
> On Wed, Oct 11, 2017 at 10:17 AM, Ezhilmathi Krishnasamy <
> ezhkr601 at student.liu.se> wrote:
>
>> Hi Andy,
>>
>> Any idea or info about this extracting the surface of the geometry
>> in higher order element mesh (or solution).
>>
>> Kind regards,
>> Mathi
>>
>> On 20 September 2017 at 21:32, Ezhilmathi Krishnasamy <
>> ezhkr601 at student.liu.se> wrote:
>>
>>> Hi Andy,
>>>
>>> Thanks!
>>>
>>> I am attaching you the image here, I would like to see the sphere
>>> surface inside the
>>> cube. Instead I am still seeing the elements.
>>>
>>> Kind regards,
>>> Mathi?
>>>  sol.vtu
>>> <https://drive.google.com/a/student.liu.se/file/d/0B2nFsji7UDKueGZmU0g0dHZSb2s/view?usp=drive_web>
>>> ?
>>>
>>> On 20 September 2017 at 21:15, Andy Bauer <andy.bauer at kitware.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> What do you mean by the extract operator? ParaView has a variety of
>>>> filters (similar to VisIt's operators) for performing extracts of different
>>>> types. Could you also share your dataset? That may make it easier to
>>>> diagnose the issue.
>>>>
>>>> Best,
>>>> Andy
>>>>
>>>> On Wed, Sep 20, 2017 at 2:33 PM, Ezhilmathi Krishnasamy <
>>>> ezhkr601 at student.liu.se> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have fluid domain as a cube and inside this cube I have sphere. In
>>>>> the linear element mesh if I use extract operator and apply the clip as
>>>>> well I can see the sphere surface.
>>>>>
>>>>> But where as in higher order element mesh.
>>>>> If i follow the same procedure, I don't see the sphere surface instead
>>>>> I see only the elements in the cube.
>>>>>
>>>>> Could anyone please tell me how to solve this problem.
>>>>>
>>>>> Kind regards,
>>>>> Mathi
>>>>>
>>>>>
>>>>> Sent from my iPhone
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>> http://paraview.org/Wiki/ParaView
>>>>>
>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171212/853bac74/attachment.html>

From kmorel at sandia.gov  Mon Dec 11 19:09:57 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 12 Dec 2017 00:09:57 +0000
Subject: [Paraview] curvilinear CF conventions
Message-ID: <8099790f37ab473897140fdf6a992452@ES08AMSNLNT.srn.sandia.gov>

David,

The way you are attempting to specify coordinates does not follow the CF convention. Your variables have a ?coordinates? property that simply says ?zc.? That is not sufficient in the CF convention to use that as a Z coordinate to add to the other independent coordinates. In fact, I cannot find any part of the CF convention (http://cfconventions.org/latest.html) that allows you to arbitrarily assign a Z coordinate to a 2D grid.

That said, accomplishing what you want is easy with ParaView. Just load your data like you are now (so it comes in as a flat rectilinear grid). Then run the ?Warp By Scalar? filter and set the ?Scalars? property to ?zc?. That will apply the elevation to your data like you want.

-Ken

From: David Deepwell [mailto:ddeepwell at uwaterloo.ca]
Sent: Saturday, December 9, 2017 12:54 PM
To: Moreland, Kenneth <kmorel at sandia.gov>
Cc: David Deepwell <ddeepwell at uwaterloo.ca>; paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] curvilinear CF conventions

Hi Ken,

I?ve attached a file which I think satisfies the curvilinear CF conventions. The grid is 2 dimensional where the z coordinate (called zc) depends on the horizontal and vertical dimensions (x and z).

Cheers,
David



On Dec 9, 2017, at 11:34 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:

David,

The netCDF/CF reader should be able to read curvilinear coordinates. There is not enough information in your email to determine whether the issue is with the ParaView reader or an issue with the data file. It would be helpful if you could send us an example file so we can replicate your problem.

-Ken

Sent from my iPad

On Dec 9, 2017, at 9:12 AM, David Deepwell <ddeepwell at uwaterloo.ca<mailto:ddeepwell at uwaterloo.ca>> wrote:
Hi all,

I have a netcdf file that follows the CF conventions in curvilinear (structured) coordinates. Paraview however doesn?t recognize the auxiliary variable as the grid variable on which the rest of the fields should be plotted on. I?m not sure if this a bug with paraview misinterpreting the CF convention or if I just happen to have an attribute missing that Paraview is looking for.

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

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

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

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

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

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

From ddeepwell at uwaterloo.ca  Mon Dec 11 21:16:18 2017
From: ddeepwell at uwaterloo.ca (David Deepwell)
Date: Tue, 12 Dec 2017 02:16:18 +0000
Subject: [Paraview] curvilinear CF conventions
In-Reply-To: <8099790f37ab473897140fdf6a992452@ES08AMSNLNT.srn.sandia.gov>
References: <8099790f37ab473897140fdf6a992452@ES08AMSNLNT.srn.sandia.gov>
Message-ID: <38878F71-FA53-40B2-9DAF-617640C5D062@uwaterloo.ca>

Hi Ken,

So section 5.2 (http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#_two_dimensional_latitude_longitude_coordinate_variables) doesn?t apply for arbitrary coordinate variables? I would have thought that it would be general and not just for latitude and longitude.

I have used the warp by scalar before, but I would prefer it if Paraview simply understood the geometry immediately. I have also found another method to adjust the grid which is quite good. The calculator has a Coordinate Results option which creates the vector field of the grid.

Thanks,
David


On Dec 11, 2017, at 7:09 PM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:

David,

The way you are attempting to specify coordinates does not follow the CF convention. Your variables have a ?coordinates? property that simply says ?zc.? That is not sufficient in the CF convention to use that as a Z coordinate to add to the other independent coordinates. In fact, I cannot find any part of the CF convention (http://cfconventions.org/latest.html) that allows you to arbitrarily assign a Z coordinate to a 2D grid.

That said, accomplishing what you want is easy with ParaView. Just load your data like you are now (so it comes in as a flat rectilinear grid). Then run the ?Warp By Scalar? filter and set the ?Scalars? property to ?zc?. That will apply the elevation to your data like you want.

-Ken

From: David Deepwell [mailto:ddeepwell at uwaterloo.ca]
Sent: Saturday, December 9, 2017 12:54 PM
To: Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: David Deepwell <ddeepwell at uwaterloo.ca<mailto:ddeepwell at uwaterloo.ca>>; paraview at paraview.org<mailto:paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] curvilinear CF conventions

Hi Ken,

I?ve attached a file which I think satisfies the curvilinear CF conventions. The grid is 2 dimensional where the z coordinate (called zc) depends on the horizontal and vertical dimensions (x and z).

Cheers,
David



On Dec 9, 2017, at 11:34 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:

David,

The netCDF/CF reader should be able to read curvilinear coordinates. There is not enough information in your email to determine whether the issue is with the ParaView reader or an issue with the data file. It would be helpful if you could send us an example file so we can replicate your problem.

-Ken

Sent from my iPad

On Dec 9, 2017, at 9:12 AM, David Deepwell <ddeepwell at uwaterloo.ca<mailto:ddeepwell at uwaterloo.ca>> wrote:
Hi all,

I have a netcdf file that follows the CF conventions in curvilinear (structured) coordinates. Paraview however doesn?t recognize the auxiliary variable as the grid variable on which the rest of the fields should be plotted on. I?m not sure if this a bug with paraview misinterpreting the CF convention or if I just happen to have an attribute missing that Paraview is looking for.

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

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

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

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

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

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

From valenpe7 at email.cz  Tue Dec 12 10:12:42 2017
From: valenpe7 at email.cz (Petr Valenta)
Date: Tue, 12 Dec 2017 16:12:42 +0100 (CET)
Subject: [Paraview] Set cells in unstructured grid
Message-ID: <BtC.33O7w.7hqP3flv9xf.1QB}7g@seznam.cz>

Hello,

I have a particle code that is integrated with Catalyst. It exports 
particles using?a vtkUnstructuredGrid containing only points and VTK_VERTEX 
cells that index them. Initially, the cells were created the following way:





grid->Allocate(num_cells);

vtkIdType cell_id[1];

for(vtkIdType i = 0; i < num_cells; i++) {

cell_id[0] = i;

grid->InsertNextCell(VTK_VERTEX, 1, cell_id);

}







Then I wanted to speed up the process by replacing the Insert method:







vtkSmartPointer<vtkIdTypeArray> cell_ids = vtkSmartPointer<vtkIdTypeArray>::
New();

cell_ids->SetNumberOfComponents(2);

cell_ids->SetNumberOfTuples(num_cells);

for(vtkIdType i = 0; i < num_cells; i++) {

cell_ids->SetTuple2(i, 1, i);

}

vtkSmartPointer<vtkCellArray> cells = vtkSmartPointer<vtkCellArray>::New();

cells->SetCells(num_cells, cell_ids);

grid->SetCells(VTK_VERTEX, cells);






Both approaches work, but when I want to dump the grid by putting the 
following lines in co-processing script,




particles_writer = servermanager.writers.XMLPUnstructuredGridWriter(Input=
particles)

coprocessor.RegisterWriter(particles_writer, filename='particles_%t.pvtu', 
freq=output_freq)




the first approach works and the latter causes error:?

Program received signal SIGSEGV: Segmentation fault - invalid memory 
reference.






What is wrong with the second approach? Thank you.




Best regards,

Petr Valenta




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

From kmorel at sandia.gov  Tue Dec 12 11:51:11 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 12 Dec 2017 16:51:11 +0000
Subject: [Paraview] curvilinear CF conventions
Message-ID: <315a24d30b394445965e1274b5359098@ES08AMSNLNT.srn.sandia.gov>

David,

The ParaView netCDF/CF reader does support the coordinates specified in Section 5.2. As the name of that section implies, this specification of coordinates applies explicitly to latitude and longitude coordinates. The rational, as far as I can tell, is that the direction of each coordinate is determined by the ?units? parameter being either latitude or longitude. (At least, this is how the ParaView reader identifies each coordinate.) Even if we were to generalize to non-lat/lon coordinates, this specification provides no mechanism for applying the height field that you want to apply.

This limitation might seem weird, but you have to remember that the CF convention is designed for climate and forecast data and is therefore really geared toward geospatial coordinates. It is a testament to how well thought out the CF convention is that we are able to leverage it for so many different use cases, but sometimes you run into limitations of this nature.

-Ken

From: David Deepwell [mailto:ddeepwell at uwaterloo.ca]
Sent: Monday, December 11, 2017 7:16 PM
To: Moreland, Kenneth <kmorel at sandia.gov>
Cc: David Deepwell <ddeepwell at uwaterloo.ca>; paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] curvilinear CF conventions

Hi Ken,

So section 5.2 (http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#_two_dimensional_latitude_longitude_coordinate_variables) doesn?t apply for arbitrary coordinate variables? I would have thought that it would be general and not just for latitude and longitude.

I have used the warp by scalar before, but I would prefer it if Paraview simply understood the geometry immediately. I have also found another method to adjust the grid which is quite good. The calculator has a Coordinate Results option which creates the vector field of the grid.

Thanks,
David



On Dec 11, 2017, at 7:09 PM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:

David,

The way you are attempting to specify coordinates does not follow the CF convention. Your variables have a ?coordinates? property that simply says ?zc.? That is not sufficient in the CF convention to use that as a Z coordinate to add to the other independent coordinates. In fact, I cannot find any part of the CF convention (http://cfconventions.org/latest.html) that allows you to arbitrarily assign a Z coordinate to a 2D grid.

That said, accomplishing what you want is easy with ParaView. Just load your data like you are now (so it comes in as a flat rectilinear grid). Then run the ?Warp By Scalar? filter and set the ?Scalars? property to ?zc?. That will apply the elevation to your data like you want.

-Ken

From: David Deepwell [mailto:ddeepwell at uwaterloo.ca]
Sent: Saturday, December 9, 2017 12:54 PM
To: Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: David Deepwell <ddeepwell at uwaterloo.ca<mailto:ddeepwell at uwaterloo.ca>>; paraview at paraview.org<mailto:paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] curvilinear CF conventions

Hi Ken,

I?ve attached a file which I think satisfies the curvilinear CF conventions. The grid is 2 dimensional where the z coordinate (called zc) depends on the horizontal and vertical dimensions (x and z).

Cheers,
David




On Dec 9, 2017, at 11:34 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:

David,

The netCDF/CF reader should be able to read curvilinear coordinates. There is not enough information in your email to determine whether the issue is with the ParaView reader or an issue with the data file. It would be helpful if you could send us an example file so we can replicate your problem.

-Ken

Sent from my iPad

On Dec 9, 2017, at 9:12 AM, David Deepwell <ddeepwell at uwaterloo.ca<mailto:ddeepwell at uwaterloo.ca>> wrote:
Hi all,

I have a netcdf file that follows the CF conventions in curvilinear (structured) coordinates. Paraview however doesn?t recognize the auxiliary variable as the grid variable on which the rest of the fields should be plotted on. I?m not sure if this a bug with paraview misinterpreting the CF convention or if I just happen to have an attribute missing that Paraview is looking for.

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

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

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

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

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

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

From heiland at iu.edu  Tue Dec 12 22:37:43 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Wed, 13 Dec 2017 03:37:43 +0000
Subject: [Paraview] installing additional Python modules
Message-ID: <BABDD8EB-B4D6-43C8-982B-D2D607C287C5@iu.edu>

Any good advice for installing additional 3rd party modules for pvpython?  In a Programmable Source I?d written to read in MATLAB (.mat) data files, I was using the scipy module (scipy.io.loadmat). When I wrote that, I naively thought to myself - WOW, it sure was convenient that they included scipy as a 3rd party pkg in pvpython! Turns out, I was of course picking it up from another Python 2.7 distro. I only discovered this while testing on another OS (without any Python).

So, have others found themselves in a similar situation? I realize the hurdle depends on the module itself and, in this case, scipy is not trivial. Right now, I?m thinking maybe requesting that users install Miniconda 2.7 and grow from there, which presumably pvpython could use. Thoughts?

-Randy

From bak at lanl.gov  Wed Dec 13 09:49:57 2017
From: bak at lanl.gov (Kashiwa, Bucky)
Date: Wed, 13 Dec 2017 14:49:57 +0000
Subject: [Paraview] v5.4.0 and v5.4.1 client-server disconnect while
	splitting views
Message-ID: <D6568C23.3AEEA%bak@lanl.gov>

We are getting a very weird kind of client-server disconnect that seems to
be associated with crash that is triggered while splitting the view into
two or more parts.  (This happens on either client-server OS pairs of
mac-linux or linux-linux, in case that may matter.)  A backtrace from the
server window is given below.  Any suggestions are greatly appreciated.  b.



---------------------------------------------------------------------------
---------------------------------------------------------------------------
---
Client connected.


pvserver:14230 terminated with signal 11 at PC=2ab0fe68cf91
SP=7ffe6d91fc90.  Backtrace:
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
nGL2-pv5.4.so.1(_ZN16vtkShaderProgram11SetUniformiEPKci+0x21)[0x2ab0fe68cf9
1]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVVTKExtensi
onsRendering-pv5.4.so.1(_ZN20vtkIceTCompositePass27PushIceTDepthBufferToScr
eenEPK14vtkRenderState+0x288)[0x2ab0f5068038]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
erCoreRendering-pv5.4.so.1(+0x164b28)[0x2ab0f2236b28]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
nGL2-pv5.4.so.1(_ZN27vtkDepthImageProcessingPass14RenderDelegateEPK14vtkRen
derStateiiiiP26vtkOpenGLFramebufferObjectP16vtkTextureObjectS6_+0x209)[0x2a
b0fe5be569]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
nGL2-pv5.4.so.1(_ZN13vtkEDLShading6RenderEPK14vtkRenderState+0x2e3)[0x2ab0f
e5d06c3]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
nGL2-pv5.4.so.1(_ZN17vtkOpenGLRenderer12DeviceRenderEv+0x5f)[0x2ab0fe63f3af
]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
e-pv5.4.so.1(_ZN11vtkRenderer6RenderEv+0x823)[0x2ab0fea654d3]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
e-pv5.4.so.1(_ZN21vtkRendererCollection6RenderEv+0xc5)[0x2ab0fea61fe5]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
e-pv5.4.so.1(_ZN15vtkRenderWindow14DoStereoRenderEv+0xce)[0x2ab0fea6f2ce]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
e-pv5.4.so.1(_ZN15vtkRenderWindow6RenderEv+0xf05)[0x2ab0fea715b5]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
erCoreRendering-pv5.4.so.1(_ZN15vtkPVRenderView6RenderEbb+0x4e8)[0x2ab0f21f
9198]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
erCoreRendering-pv5.4.so.1(_ZN15vtkPVRenderView11StillRenderEv+0x3c)[0x2ab0
f21f1b7c]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerMana
gerApplication-pv5.4.so.1(_Z22vtkPVRenderViewCommandP26vtkClientServerInter
preterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x19f8)[0x2ab0e7b3
06a8]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
-pv5.4.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkO
bjectBaseS1_RK21vtkClientServerStreamRS4_+0x1a4)[0x2ab0e9a30234]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libEyeDomeLighting
View.so(_Z29vtkPVRenderViewWithEDLCommandP26vtkClientServerInterpreterP13vt
kObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x35b)[0x2ab11f01d43b]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
-pv5.4.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkO
bjectBaseS1_RK21vtkClientServerStreamRS4_+0x1a4)[0x2ab0e9a30234]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
-pv5.4.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkCl
ientServerStreami+0x14a)[0x2ab0e9a3059a]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
-pv5.4.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClien
tServerStreami+0x53e)[0x2ab0e9a3110e]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
-pv5.4.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientSer
verStream+0x1d)[0x2ab0e9a3137d]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
ementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore21ExecuteStreamInternalERK21
vtkClientServerStreamb+0xf5)[0x2ab0e85c0d75]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
ementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore13ExecuteStreamEjRK21vtkClie
ntServerStreamb+0x3b)[0x2ab0e85c0bab]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
ementationCore-pv5.4.so.1(_ZN16vtkPVSessionBase13ExecuteStreamEjRK21vtkClie
ntServerStreamb+0x35)[0x2ab0e85bf895]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
ementationCore-pv5.4.so.1(_ZN18vtkPVSessionServer24OnClientServerMessageRMI
EPvi+0x10f)[0x2ab0e85cc2af]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkParallelCore
-pv5.4.so.1(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x143)[0x2ab0e
b24c0e3]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkParallelCore
-pv5.4.so.1(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x14c)[0x2ab0eb2
4c84c]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
erCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager21ProcessEventsInterna
lEmb+0x287)[0x2ab0e88ebd07]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/pvserver(main+0x1e
b)[0x4018db]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x2ab0edffad1d]
/yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/pvserver[0x401599]
srun: error: ls003: task 0: Exited with exit code 1
srun: First task exited 30s ago
srun: tasks 1-47: running
srun: task 0: exited abnormally
srun: Terminating job step 708333.0
srun: Job step aborted: Waiting up to 32 seconds for job step to finish.
slurmstepd: error: *** STEP 708333.0 ON ls003 CANCELLED AT
2017-12-13T07:32:42 ***
srun: error: ls003: tasks 1-11: Killed
srun: error: ls005: tasks 24-35: Killed
srun: error: ls006: tasks 36-47: Killed
srun: error: ls004: tasks 12-23: Killed
salloc: Relinquishing job allocation 708333



=======================================================================73
<>Bucky Kashiwa PhD, PE  <> Post: MS B216, Los Alamos, NM  87545       <>
<>  Ofc: TA3-SM123-RM276 <>Email: bak at lanl.gov, kashiwa at qwest.net      <>
<>Voice: 505-667-8812    <>  Fax: 505-665-5926  <>
                         <> Home: 505-988-7332  <> Cell: 505-795-5581  <>
=======================================================================73



From utkarsh.ayachit at kitware.com  Wed Dec 13 11:43:13 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 13 Dec 2017 11:43:13 -0500
Subject: [Paraview] v5.4.0 and v5.4.1 client-server disconnect while
 splitting views
In-Reply-To: <D6568C23.3AEEA%bak@lanl.gov>
References: <D6568C23.3AEEA%bak@lanl.gov>
Message-ID: <CADHSJjALsAV8p_xuWNtKOLWowpVwCzRR+LhuV-JRAWnbNs-xyQ@mail.gmail.com>

Bucky,

What happens if you don't split, instead close the current view and
create a new render view in its stead? Do you get the same segfault?

Utkarsh



On Wed, Dec 13, 2017 at 9:49 AM, Kashiwa, Bucky <bak at lanl.gov> wrote:
> We are getting a very weird kind of client-server disconnect that seems to
> be associated with crash that is triggered while splitting the view into
> two or more parts.  (This happens on either client-server OS pairs of
> mac-linux or linux-linux, in case that may matter.)  A backtrace from the
> server window is given below.  Any suggestions are greatly appreciated.  b.
>
>
>
> ---------------------------------------------------------------------------
> ---------------------------------------------------------------------------
> ---
> Client connected.
>
>
> pvserver:14230 terminated with signal 11 at PC=2ab0fe68cf91
> SP=7ffe6d91fc90.  Backtrace:
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
> nGL2-pv5.4.so.1(_ZN16vtkShaderProgram11SetUniformiEPKci+0x21)[0x2ab0fe68cf9
> 1]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVVTKExtensi
> onsRendering-pv5.4.so.1(_ZN20vtkIceTCompositePass27PushIceTDepthBufferToScr
> eenEPK14vtkRenderState+0x288)[0x2ab0f5068038]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
> erCoreRendering-pv5.4.so.1(+0x164b28)[0x2ab0f2236b28]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
> nGL2-pv5.4.so.1(_ZN27vtkDepthImageProcessingPass14RenderDelegateEPK14vtkRen
> derStateiiiiP26vtkOpenGLFramebufferObjectP16vtkTextureObjectS6_+0x209)[0x2a
> b0fe5be569]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
> nGL2-pv5.4.so.1(_ZN13vtkEDLShading6RenderEPK14vtkRenderState+0x2e3)[0x2ab0f
> e5d06c3]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingOpe
> nGL2-pv5.4.so.1(_ZN17vtkOpenGLRenderer12DeviceRenderEv+0x5f)[0x2ab0fe63f3af
> ]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
> e-pv5.4.so.1(_ZN11vtkRenderer6RenderEv+0x823)[0x2ab0fea654d3]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
> e-pv5.4.so.1(_ZN21vtkRendererCollection6RenderEv+0xc5)[0x2ab0fea61fe5]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
> e-pv5.4.so.1(_ZN15vtkRenderWindow14DoStereoRenderEv+0xce)[0x2ab0fea6f2ce]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkRenderingCor
> e-pv5.4.so.1(_ZN15vtkRenderWindow6RenderEv+0xf05)[0x2ab0fea715b5]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
> erCoreRendering-pv5.4.so.1(_ZN15vtkPVRenderView6RenderEbb+0x4e8)[0x2ab0f21f
> 9198]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
> erCoreRendering-pv5.4.so.1(_ZN15vtkPVRenderView11StillRenderEv+0x3c)[0x2ab0
> f21f1b7c]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerMana
> gerApplication-pv5.4.so.1(_Z22vtkPVRenderViewCommandP26vtkClientServerInter
> preterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x19f8)[0x2ab0e7b3
> 06a8]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
> -pv5.4.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkO
> bjectBaseS1_RK21vtkClientServerStreamRS4_+0x1a4)[0x2ab0e9a30234]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libEyeDomeLighting
> View.so(_Z29vtkPVRenderViewWithEDLCommandP26vtkClientServerInterpreterP13vt
> kObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x35b)[0x2ab11f01d43b]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
> -pv5.4.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkO
> bjectBaseS1_RK21vtkClientServerStreamRS4_+0x1a4)[0x2ab0e9a30234]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
> -pv5.4.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkCl
> ientServerStreami+0x14a)[0x2ab0e9a3059a]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
> -pv5.4.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClien
> tServerStreami+0x53e)[0x2ab0e9a3110e]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkClientServer
> -pv5.4.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientSer
> verStream+0x1d)[0x2ab0e9a3137d]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
> ementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore21ExecuteStreamInternalERK21
> vtkClientServerStreamb+0xf5)[0x2ab0e85c0d75]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
> ementationCore-pv5.4.so.1(_ZN16vtkPVSessionCore13ExecuteStreamEjRK21vtkClie
> ntServerStreamb+0x3b)[0x2ab0e85c0bab]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
> ementationCore-pv5.4.so.1(_ZN16vtkPVSessionBase13ExecuteStreamEjRK21vtkClie
> ntServerStreamb+0x35)[0x2ab0e85bf895]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVServerImpl
> ementationCore-pv5.4.so.1(_ZN18vtkPVSessionServer24OnClientServerMessageRMI
> EPvi+0x10f)[0x2ab0e85cc2af]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkParallelCore
> -pv5.4.so.1(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x143)[0x2ab0e
> b24c0e3]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkParallelCore
> -pv5.4.so.1(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x14c)[0x2ab0eb2
> 4c84c]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/libvtkPVClientServ
> erCoreCore-pv5.4.so.1(_ZN26vtkTCPNetworkAccessManager21ProcessEventsInterna
> lEmb+0x287)[0x2ab0e88ebd07]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/pvserver(main+0x1e
> b)[0x4018db]
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x2ab0edffad1d]
> /yellow/usr/projects/pv_dev/PV-5.4.0-FX/lib/paraview-5.4/pvserver[0x401599]
> srun: error: ls003: task 0: Exited with exit code 1
> srun: First task exited 30s ago
> srun: tasks 1-47: running
> srun: task 0: exited abnormally
> srun: Terminating job step 708333.0
> srun: Job step aborted: Waiting up to 32 seconds for job step to finish.
> slurmstepd: error: *** STEP 708333.0 ON ls003 CANCELLED AT
> 2017-12-13T07:32:42 ***
> srun: error: ls003: tasks 1-11: Killed
> srun: error: ls005: tasks 24-35: Killed
> srun: error: ls006: tasks 36-47: Killed
> srun: error: ls004: tasks 12-23: Killed
> salloc: Relinquishing job allocation 708333
>
>
>
> =======================================================================73
> <>Bucky Kashiwa PhD, PE  <> Post: MS B216, Los Alamos, NM  87545       <>
> <>  Ofc: TA3-SM123-RM276 <>Email: bak at lanl.gov, kashiwa at qwest.net      <>
> <>Voice: 505-667-8812    <>  Fax: 505-665-5926  <>
>                          <> Home: 505-988-7332  <> Cell: 505-795-5581  <>
> =======================================================================73
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

From luochong at gmail.com  Wed Dec 13 12:28:03 2017
From: luochong at gmail.com (Chong Luo)
Date: Wed, 13 Dec 2017 09:28:03 -0800
Subject: [Paraview] Missing paraview binary in Conda package
Message-ID: <CALZyjCXXqCcY6+-D8g0HQFkfM+E3SM1CeO1SO9gp7=9b1Kv6Qw@mail.gmail.com>

I installed paraview in Miniconda on my linux desktop:
https://anaconda.org/conda-forge/paraview

However, there is only paraview-config under ~/miniconda3/bin/, and no
binary "paraview".

Is this a bug?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171213/ea0d8dab/attachment.html>

From cory.quammen at kitware.com  Wed Dec 13 13:04:41 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 13 Dec 2017 13:04:41 -0500
Subject: [Paraview] Missing paraview binary in Conda package
In-Reply-To: <CALZyjCXXqCcY6+-D8g0HQFkfM+E3SM1CeO1SO9gp7=9b1Kv6Qw@mail.gmail.com>
References: <CALZyjCXXqCcY6+-D8g0HQFkfM+E3SM1CeO1SO9gp7=9b1Kv6Qw@mail.gmail.com>
Message-ID: <CAB5Fpx6ob-c=7jATLbEufPP8ip+WhBy59RKEF+9tT_rdp=1oAg@mail.gmail.com>

If you don't get a response here, you might have better luck checking with
the Conda folks who provide the ParaView Conda package.

On Wed, Dec 13, 2017 at 12:28 PM, Chong Luo <luochong at gmail.com> wrote:

> I installed paraview in Miniconda on my linux desktop:
> https://anaconda.org/conda-forge/paraview
>
> However, there is only paraview-config under ~/miniconda3/bin/, and no
> binary "paraview".
>
> Is this a bug?
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


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

From luochong at gmail.com  Wed Dec 13 16:37:42 2017
From: luochong at gmail.com (Chong Luo)
Date: Wed, 13 Dec 2017 13:37:42 -0800
Subject: [Paraview] Missing paraview binary in Conda package
In-Reply-To: <CAB5Fpx6ob-c=7jATLbEufPP8ip+WhBy59RKEF+9tT_rdp=1oAg@mail.gmail.com>
References: <CALZyjCXXqCcY6+-D8g0HQFkfM+E3SM1CeO1SO9gp7=9b1Kv6Qw@mail.gmail.com>
 <CAB5Fpx6ob-c=7jATLbEufPP8ip+WhBy59RKEF+9tT_rdp=1oAg@mail.gmail.com>
Message-ID: <CALZyjCVCEvu0iTAuj-E2m6o4mn+ZzxLS13BpNM8j4N9HwZ7Rbw@mail.gmail.com>

Thanks for the suggestion. Done. https://github.com/conda/conda/issues/6452

On 13 December 2017 at 10:04, Cory Quammen <cory.quammen at kitware.com> wrote:

> If you don't get a response here, you might have better luck checking with
> the Conda folks who provide the ParaView Conda package.
>
> On Wed, Dec 13, 2017 at 12:28 PM, Chong Luo <luochong at gmail.com> wrote:
>
>> I installed paraview in Miniconda on my linux desktop:
>> https://anaconda.org/conda-forge/paraview
>>
>> However, there is only paraview-config under ~/miniconda3/bin/, and no
>> binary "paraview".
>>
>> Is this a bug?
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171213/f10252d2/attachment.html>

From nico.schloemer at gmail.com  Thu Dec 14 09:15:10 2017
From: nico.schloemer at gmail.com (=?UTF-8?Q?Nico_Schl=C3=B6mer?=)
Date: Thu, 14 Dec 2017 14:15:10 +0000
Subject: [Paraview] plot colors: function value -> RGB tuple
Message-ID: <CAK6Z60exqLt4r7=zteMuQa3+DKsbNB=xmWBGVEDs0+bFwDHL3Q@mail.gmail.com>

Hi everyone,

I need to plot complex-valued functions over various domains, and instead
of splitting the values into real and imaginary part (or absolute value and
angle), I would like to use a "2D colormap" approach as sometimes suggested
for complex-valued functions (see, e.g., [1]).
As a lowkey approach of getting this into ParaView, I was wondering if it's
possible to create a filter that takes a point value (or two), runs it
through some specified (Python) code, and uses the returned RGB tuple for
rendering the plot.

Any hints?

Cheers,
Nico

[1] https://github.com/BIDS/colormap/issues/6#issuecomment-220839685
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171214/6323abfd/attachment.html>

From kmorel at sandia.gov  Thu Dec 14 10:29:12 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 14 Dec 2017 15:29:12 +0000
Subject: [Paraview] plot colors: function value -> RGB tuple
Message-ID: <8e9a0dc42801483482aa1cec38aefdfc@ES08AMSNLNT.srn.sandia.gov>

You can achieve this by writing making a filter that creates a 3D vector field where each vector represents an RGB color. If writing out floating point values, the color channel values should be between 0 and 1. You can then render this 3D vector field directly as colors by turning off the ?Map Scalars? display parameter. ?Map Scalars? is an advanced option, so the easiest way to find it is to type ?map? into the search bar at the top of the properties panel.

-Ken

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Nico Schl?mer
Sent: Thursday, December 14, 2017 7:15 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] plot colors: function value -> RGB tuple

Hi everyone,

I need to plot complex-valued functions over various domains, and instead of splitting the values into real and imaginary part (or absolute value and angle), I would like to use a "2D colormap" approach as sometimes suggested for complex-valued functions (see, e.g., [1]).
As a lowkey approach of getting this into ParaView, I was wondering if it's possible to create a filter that takes a point value (or two), runs it through some specified (Python) code, and uses the returned RGB tuple for rendering the plot.

Any hints?

Cheers,
Nico

[1] https://github.com/BIDS/colormap/issues/6#issuecomment-220839685
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171214/5d99dd91/attachment.html>

From quentin at arrivo-loop.com  Fri Dec 15 17:17:39 2017
From: quentin at arrivo-loop.com (Quentin d'Avout)
Date: Fri, 15 Dec 2017 14:17:39 -0800
Subject: [Paraview] Color bar labels
Message-ID: <CAPaR3=zKxFWf4sp3_ETFRc_ch0rR+YX3R4RK9JiW0x8n1KtbMA@mail.gmail.com>

Hi all,

there used to be (in 5.0.1) a field for setting the number of labels for
color bars in the color bar settings window (summoned by clicking the icon
with the color bar with the little "e" in bold font on it).
Not anymore in 5.4.1 (or at least in the nightly build I got last week).
Could that be just a setting that I'm missing?

As always, thanks for your help.
Quentin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171215/9f5d6c2c/attachment.html>

From klara.schevenels at kuleuven.be  Mon Dec 18 05:04:50 2017
From: klara.schevenels at kuleuven.be (Klara Schevenels)
Date: Mon, 18 Dec 2017 10:04:50 +0000
Subject: [Paraview] open .pvsm file
Message-ID: <6de18002a0fd41ab88c4b3db05d51cda@ICTS-S-EXMBX17.luna.kuleuven.be>



From: Klara Schevenels
Sent: zondag 17 december 2017 18:11
To: 'paraview at paraview.org' <paraview at paraview.org>
Subject: open .pvsm file

Hi all,

How to open a .pvsm state file? When I try this, the program says that a reader to open this kind of files could not be found and that I should choose one from the list. If I try one, the program blocks... Maybe a very stupid question, but I am very new to Paraview :)

Thanks
Klara
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171218/c64f8ddf/attachment.html>

From mathieu.westphal at kitware.com  Mon Dec 18 05:07:36 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Mon, 18 Dec 2017 11:07:36 +0100
Subject: [Paraview] open .pvsm file
In-Reply-To: <6de18002a0fd41ab88c4b3db05d51cda@ICTS-S-EXMBX17.luna.kuleuven.be>
References: <6de18002a0fd41ab88c4b3db05d51cda@ICTS-S-EXMBX17.luna.kuleuven.be>
Message-ID: <CAC2t4USgg57S21V3faNv-cv623+cUTZLDCT17xVewph7GbYs_g@mail.gmail.com>

Hello

A .pvsm is not a "Data" file but a "State" file, you need to use
"File->Load Stat"

Best,

Mathieu Westphal

On Mon, Dec 18, 2017 at 11:04 AM, Klara Schevenels <
klara.schevenels at kuleuven.be> wrote:

>
>
>
>
> *From:* Klara Schevenels
> *Sent:* zondag 17 december 2017 18:11
> *To:* 'paraview at paraview.org' <paraview at paraview.org>
> *Subject:* open .pvsm file
>
>
>
> Hi all,
>
>
>
> How to open a .pvsm state file? When I try this, the program says that a
> reader to open this kind of files could not be found and that I should
> choose one from the list. If I try one, the program blocks? Maybe a very
> stupid question, but I am very new to Paraview J
>
>
>
> Thanks
>
> Klara
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171218/904ecb57/attachment.html>

From mathieu.westphal at kitware.com  Mon Dec 18 05:17:16 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Mon, 18 Dec 2017 11:17:16 +0100
Subject: [Paraview] open .pvsm file
In-Reply-To: <111087a590ef4c878f6f20919ed088a1@ICTS-S-EXMBX17.luna.kuleuven.be>
References: <6de18002a0fd41ab88c4b3db05d51cda@ICTS-S-EXMBX17.luna.kuleuven.be>
 <CAC2t4USgg57S21V3faNv-cv623+cUTZLDCT17xVewph7GbYs_g@mail.gmail.com>
 <CAC2t4UT+F-1as54W5OXVfhEmtqJE7BJTP8rkeP7aOLW-FMxxFA@mail.gmail.com>
 <111087a590ef4c878f6f20919ed088a1@ICTS-S-EXMBX17.luna.kuleuven.be>
Message-ID: <CAC2t4UTw_8KZoffnj+L9=7jwxhJ_JJo6wMrO7Zq7Jdn33nWRNg@mail.gmail.com>

Hello

Indeed, there is no way yet to be able to open a state file with a double
click in the file explorer.

Best,

Mathieu Westphal

On Mon, Dec 18, 2017 at 11:11 AM, Klara Schevenels <
klara.schevenels at kuleuven.be> wrote:

> Okay, when I do this starting from Paraview, it works! But when I double
> click on the file in my folder it won?t open.
>
> Thanks!
>
> *From:* Mathieu Westphal [mailto:mathieu.westphal at kitware.com]
> *Sent:* maandag 18 december 2017 11:08
> *To:* Klara Schevenels <klara.schevenels at kuleuven.be>
> *Subject:* Re: [Paraview] open .pvsm file
>
>
>
> "File->LoadState"
>
>
> Mathieu Westphal
>
>
>
> On Mon, Dec 18, 2017 at 11:07 AM, Mathieu Westphal <
> mathieu.westphal at kitware.com> wrote:
>
> Hello
>
> A .pvsm is not a "Data" file but a "State" file, you need to use
> "File->Load Stat"
>
> Best,
>
>
> Mathieu Westphal
>
>
>
> On Mon, Dec 18, 2017 at 11:04 AM, Klara Schevenels <
> klara.schevenels at kuleuven.be> wrote:
>
>
>
>
>
> *From:* Klara Schevenels
> *Sent:* zondag 17 december 2017 18:11
> *To:* 'paraview at paraview.org' <paraview at paraview.org>
> *Subject:* open .pvsm file
>
>
>
> Hi all,
>
>
>
> How to open a .pvsm state file? When I try this, the program says that a
> reader to open this kind of files could not be found and that I should
> choose one from the list. If I try one, the program blocks? Maybe a very
> stupid question, but I am very new to Paraview J
>
>
>
> Thanks
>
> Klara
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171218/11db02ec/attachment.html>

From heiland at iu.edu  Mon Dec 18 06:19:16 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Mon, 18 Dec 2017 11:19:16 +0000
Subject: [Paraview] installing additional Python modules
In-Reply-To: <BABDD8EB-B4D6-43C8-982B-D2D607C287C5@iu.edu>
References: <BABDD8EB-B4D6-43C8-982B-D2D607C287C5@iu.edu>
Message-ID: <AC17486F-B653-4727-8361-D6644C929D83@iu.edu>

Only heard crickets on this one :-)

I?ve spent some time looking into this and here?s some of what I've discovered so far (I was jumping between OSX and Win10):

1) Stay away from trying to mix Anaconda/conda Python distribution with any other Python distro (including PV?s) [1]

2) Use/install a Python from python.org<http://python.org> that has ?pip? installed (e.g. 2.7.14) and then run:
$ python -m pip install scipy

Note, attempting this with pvpython doesn?t work:
$ pvpython -m pip install scipy
Got unknown argument: -m

3) Ensure pvpython?s sys.path points to *all* relevant dirs containing all necessary scipy-related dependencies in the above installation. Hopefully it gets picked up automatically if it?s a default system install. Alternatively, I *think* I was able to manually copy the scipy and numpy folders from the system install into the appropriate PV Python folder (on Windows anyway).

4) This all feels very fragile.

5) I briefly tinkered with conda-forge and building PV from source, then backed out.

6) About the time I figure out a reasonably good solution, a new version of PV supporting Python3 and pip will come out making life wonderfully simple?

Comments very much welcome.

-Randy


[1] https://groups.google.com/a/continuum.io/forum/#!topic/conda/ozG_nTuQQYk


On Dec 12, 2017, at 10:37 PM, Heiland, Randy <heiland at iu.edu<mailto:heiland at iu.edu>> wrote:

Any good advice for installing additional 3rd party modules for pvpython?  In a Programmable Source I?d written to read in MATLAB (.mat) data files, I was using the scipy module (scipy.io.loadmat). When I wrote that, I naively thought to myself - WOW, it sure was convenient that they included scipy as a 3rd party pkg in pvpython! Turns out, I was of course picking it up from another Python 2.7 distro. I only discovered this while testing on another OS (without any Python).

So, have others found themselves in a similar situation? I realize the hurdle depends on the module itself and, in this case, scipy is not trivial. Right now, I?m thinking maybe requesting that users install Miniconda 2.7 and grow from there, which presumably pvpython could use. Thoughts?

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

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

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

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

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171218/2f21d01a/attachment.html>

From cory.quammen at kitware.com  Mon Dec 18 09:58:59 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 18 Dec 2017 09:58:59 -0500
Subject: [Paraview] Color bar labels
In-Reply-To: <CAPaR3=zKxFWf4sp3_ETFRc_ch0rR+YX3R4RK9JiW0x8n1KtbMA@mail.gmail.com>
References: <CAPaR3=zKxFWf4sp3_ETFRc_ch0rR+YX3R4RK9JiW0x8n1KtbMA@mail.gmail.com>
Message-ID: <CAB5Fpx4=f4Ruw=zZc_f-_2NXXXxoJ_DhTUKkkZcmAGboE1M_tg@mail.gmail.com>

Hi Quentin,

In the refactor of the color bar, we decided to replace the unreliable
"number of labels" option with a list of explicit labels you can set. The
number of labels option was only a maximum number of labels and often
didn't give you the requested number. To use the new list option, turn on
the "Use Custom Labels" checkbox in the "Edit Color Legend Properties"
dialog. The list lets you control exactly how many labels to provide, with
the caveat that you need to specify the label values manually. In addition,
there is no prevention of overlapping labels when this option is enabled.

I hope that helps,
Cory

On Fri, Dec 15, 2017 at 5:17 PM, Quentin d'Avout <quentin at arrivo-loop.com>
wrote:

> Hi all,
>
> there used to be (in 5.0.1) a field for setting the number of labels for
> color bars in the color bar settings window (summoned by clicking the icon
> with the color bar with the little "e" in bold font on it).
> Not anymore in 5.4.1 (or at least in the nightly build I got last week).
> Could that be just a setting that I'm missing?
>
> As always, thanks for your help.
> Quentin
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171218/9ed60585/attachment.html>

From mheuegger at gmail.com  Mon Dec 18 10:22:02 2017
From: mheuegger at gmail.com (mirko heuegger)
Date: Mon, 18 Dec 2017 16:22:02 +0100
Subject: [Paraview] open .pvsm file
In-Reply-To: <CAC2t4UTw_8KZoffnj+L9=7jwxhJ_JJo6wMrO7Zq7Jdn33nWRNg@mail.gmail.com>
References: <6de18002a0fd41ab88c4b3db05d51cda@ICTS-S-EXMBX17.luna.kuleuven.be>
 <CAC2t4USgg57S21V3faNv-cv623+cUTZLDCT17xVewph7GbYs_g@mail.gmail.com>
 <CAC2t4UT+F-1as54W5OXVfhEmtqJE7BJTP8rkeP7aOLW-FMxxFA@mail.gmail.com>
 <111087a590ef4c878f6f20919ed088a1@ICTS-S-EXMBX17.luna.kuleuven.be>
 <CAC2t4UTw_8KZoffnj+L9=7jwxhJ_JJo6wMrO7Zq7Jdn33nWRNg@mail.gmail.com>
Message-ID: <CACR=3K7OnKZYgx=0gue06PH5zftLrZgxNmrGuELL2fVGK2Tz9g@mail.gmail.com>

Hello!

Paraview.exe has an command-line option for loading state-files:
paraview.exe --state=<stateFileName.pvsm>

so maybe this might be helpful.

best regards

mirko


On Mon, Dec 18, 2017 at 11:17 AM, Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> Hello
>
> Indeed, there is no way yet to be able to open a state file with a double
> click in the file explorer.
>
> Best,
>
> Mathieu Westphal
>
> On Mon, Dec 18, 2017 at 11:11 AM, Klara Schevenels <
> klara.schevenels at kuleuven.be> wrote:
>
>> Okay, when I do this starting from Paraview, it works! But when I double
>> click on the file in my folder it won?t open.
>>
>> Thanks!
>>
>> *From:* Mathieu Westphal [mailto:mathieu.westphal at kitware.com]
>> *Sent:* maandag 18 december 2017 11:08
>> *To:* Klara Schevenels <klara.schevenels at kuleuven.be>
>> *Subject:* Re: [Paraview] open .pvsm file
>>
>>
>>
>> "File->LoadState"
>>
>>
>> Mathieu Westphal
>>
>>
>>
>> On Mon, Dec 18, 2017 at 11:07 AM, Mathieu Westphal <
>> mathieu.westphal at kitware.com> wrote:
>>
>> Hello
>>
>> A .pvsm is not a "Data" file but a "State" file, you need to use
>> "File->Load Stat"
>>
>> Best,
>>
>>
>> Mathieu Westphal
>>
>>
>>
>> On Mon, Dec 18, 2017 at 11:04 AM, Klara Schevenels <
>> klara.schevenels at kuleuven.be> wrote:
>>
>>
>>
>>
>>
>> *From:* Klara Schevenels
>> *Sent:* zondag 17 december 2017 18:11
>> *To:* 'paraview at paraview.org' <paraview at paraview.org>
>> *Subject:* open .pvsm file
>>
>>
>>
>> Hi all,
>>
>>
>>
>> How to open a .pvsm state file? When I try this, the program says that a
>> reader to open this kind of files could not be found and that I should
>> choose one from the list. If I try one, the program blocks? Maybe a very
>> stupid question, but I am very new to Paraview J
>>
>>
>>
>> Thanks
>>
>> Klara
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview
>>
>>
>>
>>
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>


-- 
Real programmers don't document; if it was
hard to write, it should be hard to understand.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171218/dd21f6bf/attachment.html>

From joachim.pouderoux at kitware.com  Mon Dec 18 13:53:39 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Mon, 18 Dec 2017 14:53:39 -0400
Subject: [Paraview] open .pvsm file
In-Reply-To: <CACR=3K7OnKZYgx=0gue06PH5zftLrZgxNmrGuELL2fVGK2Tz9g@mail.gmail.com>
References: <6de18002a0fd41ab88c4b3db05d51cda@ICTS-S-EXMBX17.luna.kuleuven.be>
 <CAC2t4USgg57S21V3faNv-cv623+cUTZLDCT17xVewph7GbYs_g@mail.gmail.com>
 <CAC2t4UT+F-1as54W5OXVfhEmtqJE7BJTP8rkeP7aOLW-FMxxFA@mail.gmail.com>
 <111087a590ef4c878f6f20919ed088a1@ICTS-S-EXMBX17.luna.kuleuven.be>
 <CAC2t4UTw_8KZoffnj+L9=7jwxhJ_JJo6wMrO7Zq7Jdn33nWRNg@mail.gmail.com>
 <CACR=3K7OnKZYgx=0gue06PH5zftLrZgxNmrGuELL2fVGK2Tz9g@mail.gmail.com>
Message-ID: <CACJ=gTiRF5wkxmnbAJ4r=6TsEOqAjk4q67mTY=jvw5KDD9PjMw@mail.gmail.com>

Hi,

For your information, since this change:
https://gitlab.kitware.com/paraview/paraview/merge_requests/1704
and ParaView 5.4.1, you should be able to open a pvsm by specifying its
name on the command line, without using the option --state=
... and consequently open state files easily from a file explorer.

Best,

*Joachim Pouderoux*, PhD

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


2017-12-18 11:22 GMT-04:00 mirko heuegger <mheuegger at gmail.com>:

> Hello!
>
> Paraview.exe has an command-line option for loading state-files:
> paraview.exe --state=<stateFileName.pvsm>
>
> so maybe this might be helpful.
>
> best regards
>
> mirko
>
>
> On Mon, Dec 18, 2017 at 11:17 AM, Mathieu Westphal <
> mathieu.westphal at kitware.com> wrote:
>
>> Hello
>>
>> Indeed, there is no way yet to be able to open a state file with a double
>> click in the file explorer.
>>
>> Best,
>>
>> Mathieu Westphal
>>
>> On Mon, Dec 18, 2017 at 11:11 AM, Klara Schevenels <
>> klara.schevenels at kuleuven.be> wrote:
>>
>>> Okay, when I do this starting from Paraview, it works! But when I double
>>> click on the file in my folder it won?t open.
>>>
>>> Thanks!
>>>
>>> *From:* Mathieu Westphal [mailto:mathieu.westphal at kitware.com]
>>> *Sent:* maandag 18 december 2017 11:08
>>> *To:* Klara Schevenels <klara.schevenels at kuleuven.be>
>>> *Subject:* Re: [Paraview] open .pvsm file
>>>
>>>
>>>
>>> "File->LoadState"
>>>
>>>
>>> Mathieu Westphal
>>>
>>>
>>>
>>> On Mon, Dec 18, 2017 at 11:07 AM, Mathieu Westphal <
>>> mathieu.westphal at kitware.com> wrote:
>>>
>>> Hello
>>>
>>> A .pvsm is not a "Data" file but a "State" file, you need to use
>>> "File->Load Stat"
>>>
>>> Best,
>>>
>>>
>>> Mathieu Westphal
>>>
>>>
>>>
>>> On Mon, Dec 18, 2017 at 11:04 AM, Klara Schevenels <
>>> klara.schevenels at kuleuven.be> wrote:
>>>
>>>
>>>
>>>
>>>
>>> *From:* Klara Schevenels
>>> *Sent:* zondag 17 december 2017 18:11
>>> *To:* 'paraview at paraview.org' <paraview at paraview.org>
>>> *Subject:* open .pvsm file
>>>
>>>
>>>
>>> Hi all,
>>>
>>>
>>>
>>> How to open a .pvsm state file? When I try this, the program says that a
>>> reader to open this kind of files could not be found and that I should
>>> choose one from the list. If I try one, the program blocks? Maybe a very
>>> stupid question, but I am very new to Paraview J
>>>
>>>
>>>
>>> Thanks
>>>
>>> Klara
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> https://paraview.org/mailman/listinfo/paraview
>>>
>>>
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview
>>
>>
>
>
> --
> Real programmers don't document; if it was
> hard to write, it should be hard to understand.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171218/809b85c1/attachment.html>

From nguyenvanquang240484 at gmail.com  Mon Dec 18 20:33:04 2017
From: nguyenvanquang240484 at gmail.com (QUANG NGUYEN)
Date: Tue, 19 Dec 2017 10:33:04 +0900
Subject: [Paraview] Using Paraview record stress of soil in Opensees
Message-ID: <CAN1O2iMH_KRSZxOyZVbgWEFRYmk4KcO_sVhXpH97RF_NaSJiyQ@mail.gmail.com>

Hi every one!
I want to use Paraview to record stress time history in OpenSees of soil
domain of soil-structure problem. Do you know how to do that. I try with
displacement of soil domain with this code: "recorder pvd Paraview_Output
basic disp -nodeRange 1 $numTotalNode" and it work, but I do not know how
to do that for stress. Please help me if you know.
Thank in advance!


Best regards,

Quang Van Nguyen

-------------------------------------------------------------------

PhD student, Geo System Research Group.

Dept. of Civil and Environmental Engineering

Hanyang University @ Seoul, South Korea

Cell phone: +8210.2945.8404

-------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171219/982389e3/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Tue Dec 19 05:13:53 2017
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Tue, 19 Dec 2017 13:13:53 +0300
Subject: [Paraview] corrupt k-d tree error.
Message-ID: <72cb0b79-f42d-a3c6-839d-b684fe4285a1@be.itu.edu.tr>

Hi All,

When i try to run my simulation code integrated with ParaView Catalyst, 
i am getting error like following in certain number of processors,

ERROR: In 
/okyanus/users/uturuncoglu/progs/paraview-5.4.1/src/VTK/Common/DataModel/vtkKdTree.cxx, 
line 1945
vtkKdTree (0xeaa0660): vtkKdTree::BuildMapForDuplicatePoints corrupt k-d 
tree

The pipeline uses MergeBlock filter and i tried with both Merge Points 
option and without it but the result is same. I could not find the 
source of the error and maybe you could have some suggestion about it.

Regards,

--ufuk


From mathieu.westphal at kitware.com  Tue Dec 19 08:34:02 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Tue, 19 Dec 2017 14:34:02 +0100
Subject: [Paraview] [vtkusers] How to create vtk/vtp file where is
 possible to enable/disable visibility of some objects
In-Reply-To: <CANMYFJ==7f8atLZ5zAGsABhopRYEDx=7fuRWvks=5edZZX8ikg@mail.gmail.com>
References: <CANMYFJ==7f8atLZ5zAGsABhopRYEDx=7fuRWvks=5edZZX8ikg@mail.gmail.com>
Message-ID: <CAC2t4UT_uY+SVRbMpD8Z0zc1z5DaZ22bOWjxE0cvNTXdA4oWFA@mail.gmail.com>

Hello

Redirecting your mail to ParaView ML.
This simplest way to do that is to use MultiBlockDatasets (.vtm) files.
You can experiment in ParaView using the SphereSource, GroupDataset filter
and Multiblock Inspector Dock widget.

Best,

Mathieu Westphal

On Tue, Dec 19, 2017 at 8:25 AM, Alexey Pechnikov <pechnikov at mobigroup.ru>
wrote:

> As sample could I create vtk/vtp file with 2 spheres where I can plot any
> combination of 0, 1, 2 spheres? In Voxler I can enable/disable some objects
> in layer but I'm not sure if it's possible in ParaView.
>
> --
> Best regards, Alexey Pechnikov.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Search the list archives at: http://markmail.org/search/?q=vtkusers
>
> Follow this link to subscribe/unsubscribe:
> https://vtk.org/mailman/listinfo/vtkusers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171219/3e645b17/attachment.html>

From chengdi123000 at gmail.com  Tue Dec 19 19:01:59 2017
From: chengdi123000 at gmail.com (=?UTF-8?B?56iL6L+q?=)
Date: Tue, 19 Dec 2017 19:01:59 -0500
Subject: [Paraview] paraview GUI entry point not found in win10,
 compiled with qt 5.10 and vs 2017.
Message-ID: <CAMkQf0teAdCrtv2C_0VWwCAGjdMFB3pnDFYS35cSEd3tLYRD8w@mail.gmail.com>

Hi everyone,

I just compiled paraview 5.4.1 using vs 2017 in win 10 using qt 5.10.
The compilation works but only the `pvserver` works while the
`paraview.exe` cannot run.

The error is :Entry Point Not Found:
[image: Inline image 1]
entry point  `?setSelectionModel at QListWidget ... ` could not be located in
the dynamic link library `C:\pv54_diy\bin\vtkpqComponents-pv5.4.dll`


Here is what I did:
- win10 64bit
- vs2017 community version
- MSMPI  8.1.12438.1091 runtime and SDK
- QT 5.10.0 using msvc2017_64/lib
- cmake version 3.10.1
- Python 3.6.3 :: Anaconda, Inc.
- I compiled the boost 1.66.0 myself
- I attached the `CMakeCache.txt` file in the email.


I tried to solve this problem like this:
- locate  `vtkpqComponents` in the vtk source code. I cannot locate where
it is, so I cannot find which file is responsible for this, I also cannot
identify what this `dll` file is used for.
- I searched the maillist archive, cannot find anything useful.
- I tried to read the successful build log on DashBoard:
https://open.cdash.org/buildSummary.php?buildid=5187747, However, I cannot
see essential difference.
- I can run `pvserver` and use the official release of paraview 5.4.1 gui
client to connect to it. I can open the head dataset and render it using
volume mode remotely.

Could anyone help me?

Di Cheng
Engineer of Research and Development Center, visiting scholar at University
of Connecticut
China Academy of Aerospace Aerodynamics
Phone @ China: +86-l58Ol5949ll
Phone @ US: +l-86O-6l7-l886

Address: No.17, YunGang West Road, Fengtai District, Beijing, China

Zip Code?100074
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171219/fabbb5f5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 12306 bytes
Desc: not available
URL: <http://paraview.org/pipermail/paraview/attachments/20171219/fabbb5f5/attachment-0001.png>
-------------- next part --------------
# This is the CMakeCache file.
# For build in directory: c:/workspace/pv/ParaView-v5.4.1/build
# It was generated by CMake: C:/CMake/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//Dependencies for the target
AcceleratedAlgorithms_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Dependencies for the target
AnalyzeNIfTIIO_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkzlib;

//Dependencies for the target
ArrowGlyph_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Build the VTK documentation
BUILD_DOCUMENTATION:BOOL=OFF

BUILD_EXAMPLES:BOOL=OFF

//Build IceT with shared libraries.
BUILD_SHARED_LIBS:BOOL=ON

//Build the testing tree.
BUILD_TESTING:BOOL=OFF

//Build With User Defined Values
BUILD_USER_DEFINED_LIBS:BOOL=OFF

//The directory containing a CMake configuration file for Boost.
Boost_DIR:PATH=c:\workspace\pv\boost_1_66_0

//Path to a file.
Boost_INCLUDE_DIR:PATH=c:\workspace\pv\boost_1_66_0

//For backwards compatibility, what version of CMake commands and
// syntax should this version of CMake try to support.
CMAKE_BACKWARDS_COMPATIBILITY:STRING=2.4

//Semicolon separated list of supported configuration types, only
// supports Debug, Release, MinSizeRel, and RelWithDebInfo, anything
// else will be ignored.
CMAKE_CONFIGURATION_TYPES:STRING=Debug;Release;MinSizeRel;RelWithDebInfo

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3 /GR /EHsc

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=/MDd /Zi /Ob0 /Od /RTC1

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Build with /MP flag enabled
CMAKE_CXX_MP_FLAG:BOOL=ON

//The maximum number of processes for the /MP flag
CMAKE_CXX_MP_NUM_PROCESSORS:STRING=

//Libraries linked by default with all C++ applications.
CMAKE_CXX_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING=/DWIN32 /D_WINDOWS /W3

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=/MDd /Zi /Ob0 /Od /RTC1

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Use HP pthreads.
CMAKE_HP_PTHREADS:BOOL=OFF

//User executables (bin)
CMAKE_INSTALL_BINDIR:PATH=bin

//Read-only architecture-independent data (DATAROOTDIR)
CMAKE_INSTALL_DATADIR:PATH=

//Read-only architecture-independent data root (share)
CMAKE_INSTALL_DATAROOTDIR:PATH=share

//Documentation root (DATAROOTDIR/doc/PROJECT_NAME)
CMAKE_INSTALL_DOCDIR:PATH=

//C header files (include)
CMAKE_INSTALL_INCLUDEDIR:PATH=include

//Info documentation (DATAROOTDIR/info)
CMAKE_INSTALL_INFODIR:PATH=

//Object code libraries (lib)
CMAKE_INSTALL_LIBDIR:PATH=lib

//Program executables (libexec)
CMAKE_INSTALL_LIBEXECDIR:PATH=libexec

//Locale-dependent data (DATAROOTDIR/locale)
CMAKE_INSTALL_LOCALEDIR:PATH=

//Modifiable single-machine data (var)
CMAKE_INSTALL_LOCALSTATEDIR:PATH=var

//Man documentation (DATAROOTDIR/man)
CMAKE_INSTALL_MANDIR:PATH=

//C header files for non-gcc (/usr/include)
CMAKE_INSTALL_OLDINCLUDEDIR:PATH=/usr/include

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=C:/pv54_diy

//Run-time variable data (LOCALSTATEDIR/run)
CMAKE_INSTALL_RUNSTATEDIR:PATH=

//System admin executables (sbin)
CMAKE_INSTALL_SBINDIR:PATH=sbin

//Modifiable architecture-independent data (com)
CMAKE_INSTALL_SHAREDSTATEDIR:PATH=com

//Read-only single-machine data (etc)
CMAKE_INSTALL_SYSCONFDIR:PATH=etc

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/MVS/2017/VC/Tools/MSVC/14.12.25827/bin/Hostx86/x64/link.exe

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=ParaView

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc

//Flags for Windows Resource Compiler.
CMAKE_RC_FLAGS:STRING=/DWIN32

//Flags for Windows Resource Compiler during debug builds.
CMAKE_RC_FLAGS_DEBUG:STRING=/D_DEBUG

//Flags for Windows Resource Compiler during release builds for
// minimum size.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during release builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during release builds with
// debug info.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=OFF

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=OFF

//Flags used by the linker during the creation of static libraries.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during debug builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Thread library used.
CMAKE_THREAD_LIBS:STRING=

//Use the pthreads library.
CMAKE_USE_PTHREADS:BOOL=OFF

//Use sproc libs.
CMAKE_USE_SPROC:BOOL=OFF

//Use the win32 thread library.
CMAKE_USE_WIN32_THREADS:BOOL=ON

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=OFF

//X11 extra flags.
CMAKE_X_CFLAGS:STRING=-I

//Libraries and options used in X11 programs.
CMAKE_X_LIBS:STRING=

//Enable to build 7-Zip packages
CPACK_BINARY_7Z:BOOL=OFF

//Enable to build IFW packages
CPACK_BINARY_IFW:BOOL=OFF

//Enable to build NSIS packages
CPACK_BINARY_NSIS:BOOL=ON

//Enable to build WiX packages
CPACK_BINARY_WIX:BOOL=OFF

//Enable to build ZIP packages
CPACK_BINARY_ZIP:BOOL=OFF

//Enable to build 7-Zip source packages
CPACK_SOURCE_7Z:BOOL=ON

//Enable to build ZIP source packages
CPACK_SOURCE_ZIP:BOOL=ON

//Value Computed by CMake
CatalystScriptGeneratorPlugin_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/Plugins/CatalystScriptGenerator

//Dependencies for the target
CatalystScriptGeneratorPlugin_LIB_DEPENDS:STATIC=general;pqComponents;general;Qt5::Widgets;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;vtkPVServerManagerRendering;

//Value Computed by CMake
CatalystScriptGeneratorPlugin_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/Plugins/CatalystScriptGenerator

//Value Computed by CMake
DICOMParser_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/Utilities/DICOMParser

//Value Computed by CMake
DICOMParser_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/Utilities/DICOMParser

//Disable compiler warnings
EXODUSII_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Additional URL templates for the ExternalData CMake script to
// look for testing data. E.g.
//\nfile:///var/bigharddrive/%(algo)/%(hash)
ExternalData_URL_TEMPLATES:STRING=

//Dependencies for the target
EyeDomeLightingView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Value Computed by CMake
EyeDomeLighting_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/Plugins/EyeDomeLighting

//Value Computed by CMake
EyeDomeLighting_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/Plugins/EyeDomeLighting

//Value Computed by CMake
FmmMesh_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/Plugins/GeodesicMeasurementPlugin/FmmMesh

//Dependencies for target
FmmMesh_LIB_DEPENDS:STATIC=

//Value Computed by CMake
FmmMesh_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/Plugins/GeodesicMeasurementPlugin/FmmMesh

//Git command line client
GIT_EXECUTABLE:FILEPATH=C:/Git/cmd/git.exe

//Dependencies for the target
GMVReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtksys;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Calculate minimum and maximum of data arrays in RequestInformation
// calls.
//\n   A feature inherited from AVSucdReader, but it seems this
// information is
//\n   never queried by ParaView.
GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS:BOOL=OFF

//Value Computed by CMake
GeodesicMeasurementPlugin_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/Plugins/GeodesicMeasurementPlugin

//Value Computed by CMake
GeodesicMeasurementPlugin_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/Plugins/GeodesicMeasurementPlugin

//Dependencies for the target
GeodesicMeasurement_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;FmmMesh;

//IEEE floating point is available
HAVE_IEEEFP:STRING=1

//Value Computed by CMake
HDF5_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/hdf5/vtkhdf5

//Build Static Executabless
HDF5_BUILD_STATIC_EXECS:BOOL=OFF

//Enable all warnings
HDF5_ENABLE_ALL_WARNINGS:BOOL=OFF

//Turn on debugging in all packages
HDF5_ENABLE_DEBUG_APIS:BOOL=OFF

//embed library info into executables
HDF5_ENABLE_EMBEDDED_LIBINFO:BOOL=ON

//Enable group five warnings
HDF5_ENABLE_GROUPFIVE_WARNINGS:BOOL=OFF

//Enable group four warnings
HDF5_ENABLE_GROUPFOUR_WARNINGS:BOOL=OFF

//Enable group one warnings
HDF5_ENABLE_GROUPONE_WARNINGS:BOOL=OFF

//Enable group three warnings
HDF5_ENABLE_GROUPTHREE_WARNINGS:BOOL=OFF

//Enable group two warnings
HDF5_ENABLE_GROUPTWO_WARNINGS:BOOL=OFF

//Enable group zero warnings
HDF5_ENABLE_GROUPZERO_WARNINGS:BOOL=OFF

//Value Computed by CMake
HDF5_HL_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/hdf5/vtkhdf5/hl

//Value Computed by CMake
HDF5_HL_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/hdf5/vtkhdf5/hl

//Value Computed by CMake
HDF5_HL_SRC_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/hdf5/vtkhdf5/hl/src

//Value Computed by CMake
HDF5_HL_SRC_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/hdf5/vtkhdf5/hl/src

//CPACK - Disable packaging
HDF5_NO_PACKAGES:BOOL=OFF

//Package the HDF5 Library Examples Compressed File
HDF5_PACK_EXAMPLES:BOOL=OFF

//Value Computed by CMake
HDF5_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/hdf5/vtkhdf5

//Value Computed by CMake
HDF5_SRC_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/hdf5/vtkhdf5/src

//Value Computed by CMake
HDF5_SRC_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/hdf5/vtkhdf5/src

//Enable folder grouping of projects in IDEs.
HDF5_USE_FOLDERS:BOOL=ON

//Native CPU bit order
HOST_BIG_ENDIAN:STRING=OFF

//Native CPU bit order
HOST_FILLORDER:STRING=FILLORDER_MSB2LSB

//Value Computed by CMake
ICET_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/ThirdParty/IceT/vtkicet

//Sets the preferred `k' value for the radix-k algorithm.  This
// is the amount of simultaneous messages each process receives.
//  A value of 8 is generally good on most architectures, but in
// others that have slower computation with respect to network
// (such as BlueGene), a larger value may give better performance.
ICET_MAGIC_K:STRING=8

//Sets the preferred number of times an image may be split.  Some
// image compositing algorithms prefer to partition the images
// such that each process gets a piece.  Too many partitions, though,
// and you end up spending more time collecting them than you save
// balancing the compositing.
ICET_MAX_IMAGE_SPLIT:STRING=512

//Value Computed by CMake
ICET_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/ThirdParty/IceT/vtkicet

//Use MPE to trace MPI communications.  This is helpful for developers
// trying to measure the performance of parallel compositing algorithms.
ICET_USE_MPE:BOOL=OFF

//Build MPI communication layer for IceT.
ICET_USE_MPI:BOOL=ON

//Build OpenGL support layer for IceT.
ICET_USE_OPENGL:BOOL=ON

//Installation directory for executables
INSTALL_BIN_DIR:PATH=C:/Program Files/ParaView/bin

//Installation directory for headers
INSTALL_INC_DIR:PATH=C:/Program Files/ParaView/include

//Installation directory for libraries
INSTALL_LIB_DIR:PATH=C:/Program Files/ParaView/lib

//Installation directory for manual pages
INSTALL_MAN_DIR:PATH=C:/Program Files/ParaView/share/man

//Installation directory for pkgconfig (.pc) files
INSTALL_PKGCONFIG_DIR:PATH=C:/Program Files/ParaView/share/pkgconfig

//Dependencies for target
IceTCore_LIB_DEPENDS:STATIC=

//Dependencies for the target
IceTGL_LIB_DEPENDS:STATIC=general;IceTCore;general;opengl32;general;glu32;

//Dependencies for the target
IceTMPI_LIB_DEPENDS:STATIC=general;IceTCore;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Value Computed by CMake
JsonCpp_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/jsoncpp/vtkjsoncpp

//Value Computed by CMake
JsonCpp_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/jsoncpp/vtkjsoncpp

//Value Computed by CMake
LZ4_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/lz4/vtklz4

//Value Computed by CMake
LZ4_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/lz4/vtklz4

//Dependencies for the target
LagrangianParticleTracker_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkFiltersFlowPaths;

//Executable for running MPI programs.
MPIEXEC:FILEPATH=C:/Program Files/Microsoft MPI/Bin/mpiexec.exe

//Maximum number of processors available to run MPI applications.
MPIEXEC_MAX_NUMPROCS:STRING=2

//Flag used by MPI to specify the number of processes for MPIEXEC;
// the next option will be the number of processes.
MPIEXEC_NUMPROC_FLAG:STRING=-np

//These flags will come after all flags given to MPIEXEC.
MPIEXEC_POSTFLAGS:STRING=

//These flags will be directly before the executable that is being
// run by MPIEXEC.
MPIEXEC_PREFLAGS:STRING=

//Path to a program.
MPI_CXX_COMPILER:FILEPATH=MPI_CXX_COMPILER-NOTFOUND

//MPI CXX compilation flags
MPI_CXX_COMPILE_FLAGS:STRING=

//MPI CXX include path
MPI_CXX_INCLUDE_PATH:STRING=C:/Program Files (x86)/Microsoft SDKs/MPI/include

//MPI CXX libraries to link against
MPI_CXX_LIBRARIES:STRING=C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib

//MPI CXX linking flags
MPI_CXX_LINK_FLAGS:STRING=

//Path to a program.
MPI_C_COMPILER:FILEPATH=MPI_C_COMPILER-NOTFOUND

//MPI C compilation flags
MPI_C_COMPILE_FLAGS:STRING=

//MPI C include path
MPI_C_INCLUDE_PATH:STRING=C:/Program Files (x86)/Microsoft SDKs/MPI/include

//MPI C libraries to link against
MPI_C_LIBRARIES:STRING=C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib

//MPI C linking flags
MPI_C_LINK_FLAGS:STRING=

//Extra MPI libraries to link against
MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND

//MPI library to link against
MPI_LIBRARY:FILEPATH=C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib

//Path to a library.
M_LIBRARY:FILEPATH=M_LIBRARY-NOTFOUND

//Path to a file.
Mili_INCLUDE_DIR:PATH=Mili_INCLUDE_DIR-NOTFOUND

//Path to a library.
Mili_LIBRARY:FILEPATH=Mili_LIBRARY-NOTFOUND

//Request building AutobahnPython
Module_AutobahnPython:BOOL=OFF

//Poisson Surface reconstruction from unorganized points
Module_PoissonReconstruction:BOOL=OFF

//Second rank tensor glyphs that visualize eigenvalue signs.
Module_SignedTensor:BOOL=OFF

//Request building SixPython
Module_SixPython:BOOL=OFF

//Spline Driven Image Slicer - http://www.vtkjournal.org/browse/publication/838
Module_SplineDrivenImageSlicer:BOOL=OFF

//Request building Twisted
Module_Twisted:BOOL=OFF

//Request building VisItLib
Module_VisItLib:BOOL=OFF

//A collection of examples that illustrate how to use VTK.
Module_WikiExamples:BOOL=OFF

//Request building ZopeInterface
Module_ZopeInterface:BOOL=OFF

//Request building constantly
Module_constantly:BOOL=OFF

//Request building incremental
Module_incremental:BOOL=OFF

//Request building pqDeprecated
Module_pqDeprecated:BOOL=OFF

//Request building vtkAcceleratorsVTKm
Module_vtkAcceleratorsVTKm:BOOL=OFF

//Slicer additions to vtk
Module_vtkAddon:BOOL=OFF

//Request building vtkCosmoHaloFinder
Module_vtkCosmoHaloFinder:BOOL=OFF

//Dicom classes and utilities
Module_vtkDICOM:BOOL=OFF

//Request building vtkDomainsMicroscopy
Module_vtkDomainsMicroscopy:BOOL=OFF

//Request building vtkFiltersMatlab
Module_vtkFiltersMatlab:BOOL=OFF

//Request building vtkFiltersReebGraph
Module_vtkFiltersReebGraph:BOOL=OFF

//Request building vtkFiltersSMP
Module_vtkFiltersSMP:BOOL=OFF

//Request building vtkFiltersSelection
Module_vtkFiltersSelection:BOOL=OFF

//Request building vtkFiltersStatisticsGnuR
Module_vtkFiltersStatisticsGnuR:BOOL=OFF

//Request building vtkFiltersTopology
Module_vtkFiltersTopology:BOOL=OFF

//Request building vtkGUISupportMFC
Module_vtkGUISupportMFC:BOOL=OFF

//Request building vtkGUISupportQtOpenGL
Module_vtkGUISupportQtOpenGL:BOOL=OFF

//Request building vtkGUISupportQtSQL
Module_vtkGUISupportQtSQL:BOOL=OFF

//Request building vtkGUISupportQtWebkit
Module_vtkGUISupportQtWebkit:BOOL=OFF

//Request building vtkGeovisCore
Module_vtkGeovisCore:BOOL=OFF

//Request building vtkIOADIOS
Module_vtkIOADIOS:BOOL=OFF

//Request building vtkIOFFMPEG
Module_vtkIOFFMPEG:BOOL=OFF

//Request building vtkIOGDAL
Module_vtkIOGDAL:BOOL=OFF

//Request building vtkIOGeoJSON
Module_vtkIOGeoJSON:BOOL=OFF

//Request building vtkIOMINC
Module_vtkIOMINC:BOOL=OFF

//Request building vtkIOMySQL
Module_vtkIOMySQL:BOOL=OFF

//Request building vtkIOODBC
Module_vtkIOODBC:BOOL=OFF

//Request building vtkIOPostgreSQL
Module_vtkIOPostgreSQL:BOOL=OFF

//Request building vtkIOSQL
Module_vtkIOSQL:BOOL=OFF

//Request building vtkIOVideo
Module_vtkIOVideo:BOOL=OFF

//Request building vtkIOVisItBridge
Module_vtkIOVisItBridge:BOOL=OFF

//Request building vtkIOXdmf3
Module_vtkIOXdmf3:BOOL=OFF

//Request building vtkImagingOpenGL2
Module_vtkImagingOpenGL2:BOOL=OFF

//Request building vtkImagingStatistics
Module_vtkImagingStatistics:BOOL=OFF

//Request building vtkImagingStencil
Module_vtkImagingStencil:BOOL=OFF

//Request building vtkInfovisBoost
Module_vtkInfovisBoost:BOOL=OFF

//Request building vtkInfovisBoostGraphAlgorithms
Module_vtkInfovisBoostGraphAlgorithms:BOOL=OFF

//Request building vtkInfovisLayout
Module_vtkInfovisLayout:BOOL=OFF

//Request building vtkInfovisParallel
Module_vtkInfovisParallel:BOOL=OFF

//Request building vtkPVCatalystTestDriver
Module_vtkPVCatalystTestDriver:BOOL=OFF

//Request building vtkPVVTKExtensionsCosmoTools
Module_vtkPVVTKExtensionsCosmoTools:BOOL=OFF

//Request building vtkParseOGLExt
Module_vtkParseOGLExt:BOOL=OFF

//Request building vtkRenderingExternal
Module_vtkRenderingExternal:BOOL=OFF

//Request building vtkRenderingFreeTypeFontConfig
Module_vtkRenderingFreeTypeFontConfig:BOOL=OFF

//Request building vtkRenderingImage
Module_vtkRenderingImage:BOOL=OFF

//Request building vtkRenderingOSPRay
Module_vtkRenderingOSPRay:BOOL=OFF

//Request building vtkRenderingOculus
Module_vtkRenderingOculus:BOOL=OFF

//Request building vtkRenderingOpenVR
Module_vtkRenderingOpenVR:BOOL=OFF

//Request building vtkRenderingQt
Module_vtkRenderingQt:BOOL=OFF

//Request building vtkRenderingSceneGraph
Module_vtkRenderingSceneGraph:BOOL=OFF

//Request building vtkRenderingTk
Module_vtkRenderingTk:BOOL=OFF

//Request building vtkTclTk
Module_vtkTclTk:BOOL=OFF

//Request building vtkTestingGenericBridge
Module_vtkTestingGenericBridge:BOOL=OFF

//Request building vtkTestingIOSQL
Module_vtkTestingIOSQL:BOOL=OFF

//Request building vtkUtilitiesBenchmarks
Module_vtkUtilitiesBenchmarks:BOOL=OFF

//Request building vtkUtilitiesColorSeriesToXML
Module_vtkUtilitiesColorSeriesToXML:BOOL=OFF

//Request building vtkViewsGeovis
Module_vtkViewsGeovis:BOOL=OFF

//Request building vtkViewsInfovis
Module_vtkViewsInfovis:BOOL=OFF

//Request building vtkViewsQt
Module_vtkViewsQt:BOOL=OFF

//Request building vtkWebCore
Module_vtkWebCore:BOOL=OFF

//Request building vtkWebGLExporter
Module_vtkWebGLExporter:BOOL=OFF

//Request building vtkWebPython
Module_vtkWebPython:BOOL=OFF

//Request building vtkWrappingJava
Module_vtkWrappingJava:BOOL=OFF

//Request building vtkWrappingPythonCore
Module_vtkWrappingPythonCore:BOOL=ON

//Request building vtkWrappingTcl
Module_vtkWrappingTcl:BOOL=OFF

//Request building vtklibproj4
Module_vtklibproj4:BOOL=OFF

//Request building vtksqlite
Module_vtksqlite:BOOL=OFF

//Request building vtkxdmf3
Module_vtkxdmf3:BOOL=OFF

//Request building vtkzfp
Module_vtkzfp:BOOL=OFF

//Dependencies for the target
Moments_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Specify default maximum number of elements in the file chunk
// cache chunk for HDF5 files (should be prime number).
NETCDF4_CHUNK_CACHE_NELEMS:STRING=1009

//Specify default file chunk cache preemption policy for HDF5 files
// (a number between 0 and 1, inclusive).
NETCDF4_CHUNK_CACHE_PREEMPTION:STRING=0.75

//Specify default file cache chunk size for HDF5 files in bytes.
NETCDF4_CHUNK_CACHE_SIZE:STRING=4194304

//Specify the number of chunks to store in default per-variable
// cache.
NETCDF4_DEFAULT_CHUNKS_IN_CACHE:STRING=10

//Specify default size of chunks in bytes.
NETCDF4_DEFAULT_CHUNK_SIZE:STRING=4194304

//Specify maximum size (in bytes) for the default per-var chunk
// cache.
NETCDF4_MAX_DEFAULT_CACHE_SIZE:STRING=67108864

//Disable compiler warnings
NETCDF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Dependencies for the target
NonOrthogonalSource_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;pqApplicationComponents;

//OpenGL library for win32
OPENGL_gl_LIBRARY:STRING=opengl32

//GLU library for win32
OPENGL_glu_LIBRARY:STRING=glu32

//Directory to search for private OpenVR headers
OPENVR_HEADERS_ROOT_DIR:PATH=

//Path to a file.
OPENVR_INCLUDE_DIR:PATH=OPENVR_INCLUDE_DIR-NOTFOUND

//Path to a library.
OPENVR_LIBRARY_TEMP:FILEPATH=OPENVR_LIBRARY_TEMP-NOTFOUND

//Directory to search for OpenVR SDK
OPENVR_ROOT_DIR:PATH=

//build location of ospray
OSPRAY_BUILD_DIR:PATH=

//install location of ospray
OSPRAY_INSTALL_DIR:PATH=

//C++ compiler flags for OpenMP parallization
OpenMP_CXX_FLAGS:STRING=/openmp

//C compiler flags for OpenMP parallization
OpenMP_C_FLAGS:STRING=/openmp

//Load AcceleratedAlgorithms Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms:BOOL=OFF

//Load AnalyzeNIfTIIO Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO:BOOL=OFF

//Load ArrowGlyph Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph:BOOL=OFF

//Load CatalystScriptGeneratorPlugin Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin:BOOL=OFF

//Load EyeDomeLighting Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting:BOOL=OFF

//Load GMVReader Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_GMVReader:BOOL=OFF

//Load GeodesicMeasurement Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement:BOOL=OFF

//Load LagrangianParticleTracker Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_LagrangianParticleTracker:BOOL=OFF

//Load Moments Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_Moments:BOOL=OFF

//Load NonOrthogonalSource Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource:BOOL=OFF

//Load PacMan Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_PacMan:BOOL=OFF

//Load SLACTools Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_SLACTools:BOOL=OFF

//Load SierraPlotTools Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools:BOOL=OFF

//Load StreamLinesRepresentation Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_StreamLinesRepresentation:BOOL=OFF

//Load StreamingParticles Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles:BOOL=OFF

//Load SurfaceLIC Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC:BOOL=OFF

//Load ThickenLayeredCells Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells:BOOL=OFF

//Build Adaptors for various simulation codes
PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=OFF

//Build AcceleratedAlgorithms Plugin
PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms:BOOL=ON

//Build AdiosReader Plugin
PARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=OFF

//Build AnalyzeNIfTIIO Plugin
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=ON

//Build ArrowGlyph Plugin
PARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=ON

//Build CatalystScriptGeneratorPlugin Plugin
PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin:BOOL=ON

//Build EyeDomeLighting Plugin
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=ON

//Build GMVReader Plugin
PARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=ON

//Build GeodesicMeasurement Plugin
PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement:BOOL=ON

//Build InSituExodus Plugin
PARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=OFF

//Build LagrangianParticleTracker Plugin
PARAVIEW_BUILD_PLUGIN_LagrangianParticleTracker:BOOL=ON

//Build Moments Plugin
PARAVIEW_BUILD_PLUGIN_Moments:BOOL=ON

//Build NonOrthogonalSource Plugin
PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=ON

//Build PacMan Plugin
PARAVIEW_BUILD_PLUGIN_PacMan:BOOL=ON

//Build PythonQtPlugin Plugin
PARAVIEW_BUILD_PLUGIN_PythonQtPlugin:BOOL=OFF

//Build SLACTools Plugin
PARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON

//Build SierraPlotTools Plugin
PARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=ON

//Build StreamLinesRepresentation Plugin
PARAVIEW_BUILD_PLUGIN_StreamLinesRepresentation:BOOL=ON

//Build StreamingParticles Plugin
PARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=ON

//Build SurfaceLIC Plugin
PARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=ON

//Build TemporalParallelismScriptGenerator Plugin
PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator:BOOL=OFF

//Build ThickenLayeredCells Plugin
PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells:BOOL=ON

//Build VRPlugin Plugin
PARAVIEW_BUILD_PLUGIN_VRPlugin:BOOL=OFF

//Build VaporPlugin Plugin
PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=OFF

//Enable ParaView Qt-based client
PARAVIEW_BUILD_QT_GUI:BOOL=ON

//Exclude test data download from default 'all' target.
PARAVIEW_DATA_EXCLUDE_FROM_ALL:BOOL=OFF

//Local directory holding ExternalData objects in the layout %(algo)/%(hash).
PARAVIEW_DATA_STORE:PATH=

//Enable Catalyst CoProcessing modules
PARAVIEW_ENABLE_CATALYST:BOOL=ON

//Build the ParaView help menu documentation for ParaView and its
// plugins
PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION:BOOL=ON

//Enable/Disable Python scripting support
PARAVIEW_ENABLE_MATPLOTLIB:BOOL=ON

//Enable/Disable Python scripting support
PARAVIEW_ENABLE_PYTHON:BOOL=ON

//Enables markers in the spyplot reader
PARAVIEW_ENABLE_SPYPLOT_MARKERS:BOOL=ON

//Turn off to avoid ParaView depending on all used VTK modules.
PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=ON

//Enable/Disable web support
PARAVIEW_ENABLE_WEB:BOOL=OFF

//Enable Xdmf3 support (requires Boost).
PARAVIEW_ENABLE_XDMF3:BOOL=OFF

//Semicolon separated absolute paths to external directories containing
// extra VTK/ParaView modules.
PARAVIEW_EXTERNAL_MODULE_ROOTS:STRING=

//Semi-colon seperated paths to extrenal plugin directories.
PARAVIEW_EXTERNAL_PLUGIN_DIRS:STRING=

//A list of plugins to autoload (but not built as part of ParaView
// itself)
PARAVIEW_EXTRA_EXTERNAL_PLUGINS:STRING=

//Initialize MPI on client-processes by default. Can be overridden
// using command line arguments
PARAVIEW_INITIALIZE_MPI_ON_CLIENT:BOOL=OFF

//Extra paths to search for plugins
PARAVIEW_PLUGIN_LOADER_PATHS:STRING=

//Select Qt version to use 4 or 5
PARAVIEW_QT_VERSION:STRING=5

//Link to Cray ATP library to enable debug features on Cray Systems
PARAVIEW_USE_ATP:BOOL=OFF

//Enable IceT (needed for parallel rendering)
PARAVIEW_USE_ICE_T:BOOL=ON

//Enable MPI support for parallel computing
PARAVIEW_USE_MPI:BOOL=ON

//Use MPI synchronous-send commands for communication
PARAVIEW_USE_MPI_SSEND:BOOL=ON

//Build ParaView with OpenVR rendering
PARAVIEW_USE_OPENVR:BOOL=OFF

//Build ParaView with OSPRay Ray Traced rendering
PARAVIEW_USE_OSPRAY:BOOL=OFF

//Use Qt Help infrastructure as needed.
PARAVIEW_USE_QTHELP:BOOL=ON

//Use Qt WebKit components as needed.
PARAVIEW_USE_QTWEBKIT:BOOL=OFF

//If enabled, Python bindings will back the ClientServer wrapping
// implementation
PARAVIEW_USE_UNIFIED_BINDINGS:BOOL=OFF

//Build ParaView with VisIt readers.
PARAVIEW_USE_VISITBRIDGE:BOOL=OFF

//Build ParaView with VTKm many-core filters
PARAVIEW_USE_VTKM:BOOL=OFF

//Disable compiler warnings
PROTOBUF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Command to run after a failed test to cleanup processes.  Example:
// "killall -9 rsh paraview"
PV_TEST_CLEAN_COMMAND:STRING=

//Node which serves as the client node, used to connect from the
// server side in reverse connection mode.
PV_TEST_CLIENT:STRING=localhost

//Command to run before a test begins. Multiple commands are separated
// by ';'.
PV_TEST_INIT_COMMAND:STRING=

//Use random port numbers when testing client-server configurations.
PV_TEST_USE_RANDOM_PORTS:BOOL=ON

//Path to the PythonQt include directory
PYTHONQT_INCLUDE_DIR:PATH=PYTHONQT_INCLUDE_DIR-NOTFOUND

//The PythonQt library
PYTHONQT_LIBRARY:FILEPATH=PYTHONQT_LIBRARY-NOTFOUND

//Path to a library.
PYTHON_DEBUG_LIBRARY:FILEPATH=PYTHON_DEBUG_LIBRARY-NOTFOUND

//Path to a program.
PYTHON_EXECUTABLE:FILEPATH=C:/ProgramData/Miniconda3/python.exe

//Path to a file.
PYTHON_INCLUDE_DIR:PATH=C:/ProgramData/Miniconda3/include

//Path to a library.
PYTHON_LIBRARY:FILEPATH=C:/ProgramData/Miniconda3/libs/python36.lib

//Dependencies for the target
PacMan_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Value Computed by CMake
ParaView_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build

//Value Computed by CMake
ParaView_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1

//qhelpgenerator used to compile Qt help project files
QT_HELP_GENERATOR:FILEPATH=C:/Qt/5.10.0/msvc2017_64/bin/qhelpgenerator.exe

//Delay between invocation of each testing event.
QT_TESTING_EVENT_PLAYBACK_DELAY:STRING=100

//xmlpatterns used to generate html from Proxy documentation.
QT_XMLPATTERNS_EXECUTABLE:FILEPATH=C:/Qt/5.10.0/msvc2017_64/bin/xmlpatterns.exe

//The directory containing a CMake configuration file for Qt5Core.
Qt5Core_DIR:PATH=C:/Qt/5.10.0/msvc2017_64/lib/cmake/Qt5Core

//The directory containing a CMake configuration file for Qt5Gui.
Qt5Gui_DIR:PATH=C:/Qt/5.10.0/msvc2017_64/lib/cmake/Qt5Gui

//The directory containing a CMake configuration file for Qt5Help.
Qt5Help_DIR:PATH=C:/Qt/5.10.0/msvc2017_64/lib/cmake/Qt5Help

//The directory containing a CMake configuration file for Qt5Network.
Qt5Network_DIR:PATH=C:/Qt/5.10.0/msvc2017_64/lib/cmake/Qt5Network

//The directory containing a CMake configuration file for Qt5Sql.
Qt5Sql_DIR:PATH=C:/Qt/5.10.0/msvc2017_64/lib/cmake/Qt5Sql

//The directory containing a CMake configuration file for Qt5Widgets.
Qt5Widgets_DIR:PATH=C:/Qt/5.10.0/msvc2017_64/lib/cmake/Qt5Widgets

//The directory containing a CMake configuration file for Qt5.
Qt5_DIR:PATH=C:/Qt/5.10.0/msvc2017_64/lib/cmake/Qt5

//Value Computed by CMake
QtTesting_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/ThirdParty/QtTesting/vtkqttesting

//Dependencies for the target
QtTesting_LIB_DEPENDS:STATIC=general;Qt5::Core;general;Qt5::Widgets;

//Value Computed by CMake
QtTesting_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/ThirdParty/QtTesting/vtkqttesting

//Path to a file.
SILO_INCLUDE_DIR:PATH=SILO_INCLUDE_DIR-NOTFOUND

//Path to a library.
SILO_LIBRARY:FILEPATH=SILO_LIBRARY-NOTFOUND

//Dependencies for the target
SLACTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Explicitly disable SurfaceLIC plugin ctests
SURFACELIC_PLUGIN_TESTING:BOOL=ON

//Dependencies for the target
SierraPlotTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVVTKExtensionsDefault;general;Qt5::Widgets;

//Dependencies for the target
StreamLinesRepresentation_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;opengl32;general;glu32;general;pqApplicationComponents;

//Dependencies for the target
StreamingParticles_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Dependencies for the target
SurfaceLIC_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkRenderingLICOpenGL2;

//Dependencies for the target
ThickenLayeredCells_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Use HIDDEN visibility support if available.
USE_COMPILER_HIDDEN_VISIBILITY:BOOL=ON

//Disable compiler warnings
VISIT_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Value Computed by CMake
VPIC_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/VPIC

//Dependencies for the target
VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Value Computed by CMake
VPIC_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/VPIC

//Value Computed by CMake
VTKFREETYPE_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/freetype/vtkfreetype

//Value Computed by CMake
VTKFREETYPE_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/freetype/vtkfreetype

//Value Computed by CMake
VTKGL2PS_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/gl2ps/vtkgl2ps

//Value Computed by CMake
VTKGL2PS_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/gl2ps/vtkgl2ps

//Value Computed by CMake
VTKGLEW_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/glew/vtkglew

//Value Computed by CMake
VTKGLEW_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/glew/vtkglew

//Value Computed by CMake
VTKJPEG_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/jpeg/vtkjpeg

//Value Computed by CMake
VTKJPEG_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/jpeg/vtkjpeg

//Value Computed by CMake
VTKNETCDF_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/netcdf/vtknetcdf

//Value Computed by CMake
VTKNETCDF_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/netcdf/vtknetcdf

//Value Computed by CMake
VTKOGGTHEORA_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/oggtheora/vtkoggtheora

//Disable assemby optimizations
VTKOGGTHEORA_DISABLE_ASM:BOOL=OFF

//Disable the use of floating point code in theora
VTKOGGTHEORA_DISABLE_FLOAT:BOOL=OFF

//Additional linker flags for vtkoggtheora when building as a shared
// library
VTKOGGTHEORA_SHARED_LINKER_FLAGS:STRING=

//Value Computed by CMake
VTKOGGTHEORA_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/oggtheora/vtkoggtheora

//Value Computed by CMake
VTKPNG_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/png/vtkpng

//Value Computed by CMake
VTKPNG_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/png/vtkpng

//Build all vtkObject derived classes with object factory new methods.
VTK_ALL_NEW_OBJECT_FACTORY:BOOL=OFF

//Build VTK for Android
VTK_ANDROID_BUILD:BOOL=OFF

//Value Computed by CMake
VTK_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK

//Request to build all modules
VTK_BUILD_ALL_MODULES:BOOL=OFF

//Build the VTK Qt plugin for the Qt Designer.
VTK_BUILD_QT_DESIGNER_PLUGIN:BOOL=OFF

//Local directory holding ExternalData objects in the layout %(algo)/%(hash).
VTK_DATA_STORE:PATH=

//Build leak checking support into VTK.
VTK_DEBUG_LEAKS:BOOL=OFF

//Include array-of-structs vtkDataArray subclasses in dispatcher.
VTK_DISPATCH_AOS_ARRAYS:BOOL=ON

//Include struct-of-arrays vtkDataArray subclasses in dispatcher.
VTK_DISPATCH_SOA_ARRAYS:BOOL=OFF

//Include vtkTypedDataArray subclasses (e.g. old mapped arrays)
// in dispatcher.
VTK_DISPATCH_TYPED_ARRAYS:BOOL=OFF

//Index of the EGL device (graphics card) to use.
VTK_EGL_DEVICE_INDEX:STRING=0

//Build VTK using kits instead of modules.
VTK_ENABLE_KITS:BOOL=OFF

//Enable vtkpython and pvtkpython binaries
VTK_ENABLE_VTKPYTHON:BOOL=ON

//Whether the system libharu in use is a shared library or not
VTK_EXTERNAL_LIBHARU_IS_SHARED:BOOL=ON

//Do not download source code or data from the network
VTK_FORBID_DOWNLOADS:BOOL=OFF

//Location of the OpenGL extensions header file (glext.h).
VTK_GLEXT_FILE:FILEPATH=C:/workspace/pv/ParaView-v5.4.1/VTK/Utilities/ParseOGLExt/headers/glext.h

//Location of the GLX extensions header file (glxext.h).
VTK_GLXEXT_FILE:FILEPATH=C:/workspace/pv/ParaView-v5.4.1/VTK/Utilities/ParseOGLExt/headers/glxext.h

//Request building Imaging modules
VTK_Group_Imaging:BOOL=OFF

//Request building MPI modules
VTK_Group_MPI:BOOL=OFF

//Request building ParaViewCore modules
VTK_Group_ParaViewCore:BOOL=ON

//Request building ParaViewQt modules
VTK_Group_ParaViewQt:BOOL=OFF

//Request building ParaViewRendering modules
VTK_Group_ParaViewRendering:BOOL=ON

//Request building Qt modules
VTK_Group_Qt:BOOL=OFF

//Request building Rendering modules
VTK_Group_Rendering:BOOL=OFF

//Request building of all stand alone modules (no external dependencies
// required)
VTK_Group_StandAlone:BOOL=OFF

//Request building Tk modules
VTK_Group_Tk:BOOL=OFF

//Request building Views modules
VTK_Group_Views:BOOL=OFF

//Request building Web modules
VTK_Group_Web:BOOL=OFF

//Build vtk.framework for iOS
VTK_IOS_BUILD:BOOL=OFF

//Remove all legacy code completely.
VTK_LEGACY_REMOVE:BOOL=OFF

//Silence all legacy code messages.
VTK_LEGACY_SILENT:BOOL=OFF

//Should all modules build instantiators
VTK_MAKE_INSTANTIATORS:BOOL=OFF

//Max number of threads vktMultiThreader will allocate.
VTK_MAX_THREADS:STRING=64

//The full path to mpirun command
VTK_MPIRUN_EXE:FILEPATH=C:/Program Files/Microsoft MPI/Bin/mpiexec.exe

//Maximum number of processors available to run parallel applications.
// (see C:/workspace/pv/ParaView-v5.4.1/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_MAX_NUMPROCS:STRING=2

//Flag used by mpi to specify the number of processes, the next
// option will be the number of processes. (see C:/workspace/pv/ParaView-v5.4.1/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_NUMPROC_FLAG:STRING=-np

//These flags will come after all flags given to MPIRun.(see C:/workspace/pv/ParaView-v5.4.1/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_POSTFLAGS:STRING=

//These flags will be directly before the executable that is being
// run by VTK_MPIRUN_EXE. (see C:/workspace/pv/ParaView-v5.4.1/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_PREFLAGS:STRING=

//These flags will be directly before the number of processess
// flag (see C:/workspace/pv/ParaView-v5.4.1/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_PRENUMPROC_FLAGS:STRING=

//Disable Python Threads support
VTK_NO_PYTHON_THREADS:BOOL=ON

//The OpenGL library being used supports off screen Mesa calls
VTK_OPENGL_HAS_OSMESA:BOOL=OFF

//Python version to use: 2, 2.x, 3, 3.x, or empty
VTK_PYTHON_VERSION:STRING=2

//enable parallel timers for the 2d line integral convolution
VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER:BOOL=OFF

//enable parallel timers for the surface lic painter
VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER:BOOL=OFF

//Choose the rendering backend.
VTK_RENDERING_BACKEND:STRING=OpenGL2

//Enable OpenGL error check and report
VTK_REPORT_OPENGL_ERRORS:BOOL=ON

//Enable OpenGL error check and reporting in non-debug builds.
VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS:BOOL=OFF

//Which multi-threaded parallelism implementation to use. Options
// are Sequential, OpenMP or TBB
VTK_SMP_IMPLEMENTATION_TYPE:STRING=OpenMP

//Value Computed by CMake
VTK_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK

//Build VTK with 64 bit ids
VTK_USE_64BIT_IDS:BOOL=ON

//Enable tests requiring "large" data
VTK_USE_LARGE_DATA:BOOL=OFF

//Use off screen calls by default
VTK_USE_OFFSCREEN:BOOL=OFF

//Use EGL for OpenGL client API for offscreen rendering.
VTK_USE_OFFSCREEN_EGL:BOOL=OFF

//Use system-installed CGNS
VTK_USE_SYSTEM_CGNS:BOOL=OFF

//Use system 'cinema_python' Python package
VTK_USE_SYSTEM_CINEMA_PYTHON:BOOL=OFF

//Use system-installed EXPAT
VTK_USE_SYSTEM_EXPAT:BOOL=OFF

//Use system-installed Freetype
VTK_USE_SYSTEM_FREETYPE:BOOL=OFF

//Use system-installed GL2PS
VTK_USE_SYSTEM_GL2PS:BOOL=OFF

//Use system-installed GLEW
VTK_USE_SYSTEM_GLEW:BOOL=OFF

//Use system-installed HDF5
VTK_USE_SYSTEM_HDF5:BOOL=OFF

//Use system-installed icet
VTK_USE_SYSTEM_ICET:BOOL=OFF

//Use system-installed JPEG
VTK_USE_SYSTEM_JPEG:BOOL=OFF

//Use system-installed JsonCpp
VTK_USE_SYSTEM_JSONCPP:BOOL=OFF

//Use system-installed LibHaru
VTK_USE_SYSTEM_LIBHARU:BOOL=OFF

//Use the system's libraries by default.
VTK_USE_SYSTEM_LIBRARIES:BOOL=OFF

//Use system-installed LibXml2
VTK_USE_SYSTEM_LIBXML2:BOOL=OFF

//Use system-installed LZ4
VTK_USE_SYSTEM_LZ4:BOOL=OFF

//Use system 'mpi4py' Python package
VTK_USE_SYSTEM_MPI4PY:BOOL=OFF

//Use system-installed NetCDF
VTK_USE_SYSTEM_NETCDF:BOOL=OFF

//Use system-installed NetCDFCPP
VTK_USE_SYSTEM_NETCDFCPP:BOOL=OFF

//Use system-installed OGGTHEORA
VTK_USE_SYSTEM_OGGTHEORA:BOOL=OFF

//Use system-installed PNG
VTK_USE_SYSTEM_PNG:BOOL=OFF

//Use system-installed Protobuf
VTK_USE_SYSTEM_PROTOBUF:BOOL=OFF

//Use system-installed pugixml
VTK_USE_SYSTEM_PUGIXML:BOOL=OFF

//Use system 'pygments' Python package
VTK_USE_SYSTEM_PYGMENTS:BOOL=OFF

//Use system-installed qttesting
VTK_USE_SYSTEM_QTTESTING:BOOL=OFF

//Use system-installed TIFF
VTK_USE_SYSTEM_TIFF:BOOL=OFF

//Use system-installed VisItLib
VTK_USE_SYSTEM_VISITLIB:BOOL=OFF

//Use system-installed xdmf2
VTK_USE_SYSTEM_XDMF2:BOOL=OFF

//Use system-installed ZLIB
VTK_USE_SYSTEM_ZLIB:BOOL=OFF

//Build VTK with Tk support
VTK_USE_TK:BOOL=OFF

//Enable using Video for Windows (vfw32) for video input and output.
VTK_USE_VIDEO_FOR_WINDOWS:BOOL=ON

//Use X for VTK render windows
VTK_USE_X:BOOL=OFF

//Build VPIC with MPI
VTK_VPIC_USE_MPI:BOOL=ON

//If enabled, vtkArrayDispatch will print a warning when a dispatch
// fails.
VTK_WARN_ON_DISPATCH_FAILURE:BOOL=OFF

//Location of the WGL extensions header file (wglext.h).
VTK_WGLEXT_FILE:FILEPATH=C:/workspace/pv/ParaView-v5.4.1/VTK/Utilities/ParseOGLExt/headers/wglext.h

//Path to a file.
VTK_WRAP_HINTS:FILEPATH=C:/workspace/pv/ParaView-v5.4.1/VTK/Wrapping/Tools/hints

//Should VTK Java wrapping be built?
VTK_WRAP_JAVA:BOOL=OFF

//Should VTK Tcl wrapping be built?
VTK_WRAP_TCL:BOOL=OFF

//Build Xdmf with MPI
VTK_XDMF_USE_MPI:BOOL=OFF

//Value Computed by CMake
VisItBridgePlugin_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/Utilities/VisItBridge/Library/VisItLib

//Value Computed by CMake
VisItBridgePlugin_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib

//XDMF should use MPI
XDMF_BUILD_MPI:BOOL=OFF

//XDMF has Network Distributed Global Memory (NDGM)
XDMF_HAS_NDGM:BOOL=OFF

//Path to a file.
XDMF_HAVE_FCNTL:PATH=XDMF_HAVE_FCNTL-NOTFOUND

//Path to a file.
XDMF_HAVE_MMAN:PATH=XDMF_HAVE_MMAN-NOTFOUND

//Path to a file.
XDMF_HAVE_NETINET:PATH=XDMF_HAVE_NETINET-NOTFOUND

//Use bzip2
XDMF_USE_BZIP2:BOOL=OFF

//Build GZip Compression
XDMF_USE_GZIP:BOOL=OFF

//Build Support for MySQL DataItems
XDMF_USE_MYSQL:BOOL=OFF

//Value Computed by CMake
alglib_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/alglib

//Value Computed by CMake
alglib_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/alglib

//Dependencies for the target
avtdatabase_par_LIB_DEPENDS:STATIC=general;visitcommon;general;avtdbatts;general;avtpipeline_par;general;visit_vtk;

//Dependencies for the target
avtdbatts_LIB_DEPENDS:STATIC=general;visitcommon;

//Dependencies for the target
avtmath_LIB_DEPENDS:STATIC=general;visitcommon;general;vtkCommonCore;

//Dependencies for the target
avtpipeline_par_LIB_DEPENDS:STATIC=general;visitcommon;general;avtmath;general;avtdbatts;general;lightweight_visit_vtk;general;visit_vtk;general;vtkFiltersCore;general;vtkInteractionStyle;general;vtkIOLegacy;general;vtkIOXML;general;vtkRenderingOpenGL2;general;vtkFiltersGeometry;general;vtkzlib;

//Value Computed by CMake
cgns_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/ThirdParty/cgns/vtkcgns

//Value Computed by CMake
cgns_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/ThirdParty/cgns/vtkcgns

//Value Computed by CMake
expat_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/expat/vtkexpat

//Value Computed by CMake
expat_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/expat/vtkexpat

//Dependencies for the target
lightweight_visit_vtk_LIB_DEPENDS:STATIC=general;visitcommon;general;vtkCommonCore;general;vtkFiltersGeneral;general;vtkIOXML;general;vtkIOLegacy;

//Value Computed by CMake
netcdf_libdispatch_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch

//Value Computed by CMake
netcdf_libdispatch_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch

//Value Computed by CMake
netcdf_liblib_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/netcdf/vtknetcdf/liblib

//Value Computed by CMake
netcdf_liblib_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/netcdf/vtknetcdf/liblib

//Value Computed by CMake
netcdf_libsrc4_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4

//Value Computed by CMake
netcdf_libsrc4_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4

//Value Computed by CMake
netcdf_libsrc_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc

//Value Computed by CMake
netcdf_libsrc_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/netcdf/vtknetcdf/libsrc

//Dependencies for the target
pqApplicationComponents_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkGUISupportQt;general;vtkjsoncpp;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;vtkPVCinemaReader;general;Qt5::Widgets;general;Qt5::Help;

//Dependencies for the target
pqComponents_LIB_DEPENDS:STATIC=general;pqCore;general;pqPython;general;vtkjsoncpp;general;vtkChartsCore;general;vtkIOImage;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;Qt5::Widgets;general;Qt5::Network;

//Dependencies for the target
pqCore_LIB_DEPENDS:STATIC=general;pqWidgets;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVClientServerCoreDefault;general;vtkPVServerManagerApplication;general;vtkPVServerManagerDefault;general;vtksys;general;vtkTestingRendering;general;Qt5::Help;

//Dependencies for the target
pqPython_LIB_DEPENDS:STATIC=general;pqCore;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;Qt5::Widgets;

//Dependencies for the target
pqWidgets_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkPVServerManagerCore;general;QtTesting;general;Qt5::Network;general;Qt5::Help;general;Qt5::Core;general;Qt5::Gui;general;Qt5::Widgets;

//Dependencies for target
protobuf-lite_LIB_DEPENDS:STATIC=

//Value Computed by CMake
protobuf_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/ThirdParty/protobuf/vtkprotobuf

//Dependencies for target
protobuf_LIB_DEPENDS:STATIC=

//Value Computed by CMake
protobuf_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/ThirdParty/protobuf/vtkprotobuf

//Value Computed by CMake
tiff_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/tiff/vtktiff

//Value Computed by CMake
tiff_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/tiff/vtktiff

//Value Computed by CMake
verdict_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/verdict/vtkverdict

//Dependencies for target
verdict_LIB_DEPENDS:STATIC=

//Value Computed by CMake
verdict_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/verdict/vtkverdict

//Value Computed by CMake
visit_vtk_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/Utilities/VisItBridge/Library/VisItLib/visit_vtk

//Dependencies for the target
visit_vtk_LIB_DEPENDS:STATIC=general;visitcommon;general;lightweight_visit_vtk;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOImage;general;vtkFiltersExtraction;general;vtkFiltersFlowPaths;general;vtkFiltersSources;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkIOLegacy;general;vtkRenderingOpenGL2;

//Value Computed by CMake
visit_vtk_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/visit_vtk

//Dependencies for the target
visitcommon_LIB_DEPENDS:STATIC=general;ws2_32;general;shlwapi;general;userenv;general;vtkzlib;

//Dependencies for the target
vtkChartsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkChartsCore;

//Dependencies for the target
vtkChartsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkCommonColorPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkInfovisCorePythonD;general;vtkChartsCore;

//Dependencies for the target
vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD;

//Dependencies for the target
vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtksys;general;vtkCommonColor;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkInfovisCore;

//Dependencies for the target
vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;vtksys;

//Dependencies for the target
vtkCommonColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonColor;

//Dependencies for the target
vtkCommonColorPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonColor;

//Dependencies for the target
vtkCommonColorPython_LIB_DEPENDS:STATIC=general;vtkCommonColorPythonD;

//Dependencies for the target
vtkCommonColor_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonComputationalGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonComputationalGeometry;

//Dependencies for the target
vtkCommonComputationalGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonComputationalGeometry;

//Dependencies for the target
vtkCommonComputationalGeometryPython_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometryPythonD;

//Dependencies for the target
vtkCommonComputationalGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;

//Dependencies for the target
vtkCommonCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCore;

//Dependencies for the target
vtkCommonCorePython_LIB_DEPENDS:STATIC=general;vtkCommonCorePythonD;

//Dependencies for the target
vtkCommonCore_LIB_DEPENDS:STATIC=general;vtksys;

//Dependencies for the target
vtkCommonDataModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonDataModelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonDataModelPython_LIB_DEPENDS:STATIC=general;vtkCommonDataModelPythonD;

//Dependencies for the target
vtkCommonDataModel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkCommonMisc;general;vtkCommonSystem;general;vtksys;

//Dependencies for the target
vtkCommonExecutionModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonExecutionModel;

//Dependencies for the target
vtkCommonExecutionModelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonExecutionModel;

//Dependencies for the target
vtkCommonExecutionModelPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkCommonExecutionModel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;

//Dependencies for the target
vtkCommonMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMath;

//Dependencies for the target
vtkCommonMathPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMath;

//Dependencies for the target
vtkCommonMathPython_LIB_DEPENDS:STATIC=general;vtkCommonMathPythonD;

//Dependencies for the target
vtkCommonMath_LIB_DEPENDS:STATIC=general;vtkCommonCore;

//Dependencies for the target
vtkCommonMiscCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMisc;

//Dependencies for the target
vtkCommonMiscPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonMisc;

//Dependencies for the target
vtkCommonMiscPython_LIB_DEPENDS:STATIC=general;vtkCommonMiscPythonD;

//Dependencies for the target
vtkCommonMisc_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath;

//Dependencies for the target
vtkCommonSystemCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonSystem;

//Dependencies for the target
vtkCommonSystemPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonSystem;

//Dependencies for the target
vtkCommonSystemPython_LIB_DEPENDS:STATIC=general;vtkCommonSystemPythonD;

//Dependencies for the target
vtkCommonSystem_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys;

//Dependencies for the target
vtkCommonTransformsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonTransforms;

//Dependencies for the target
vtkCommonTransformsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransforms;

//Dependencies for the target
vtkCommonTransformsPython_LIB_DEPENDS:STATIC=general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkCommonTransforms_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath;

//Dependencies for target
vtkDICOMParser_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkDomainsChemistryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistry;

//Dependencies for the target
vtkDomainsChemistryOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistryOpenGL2;

//Dependencies for the target
vtkDomainsChemistryOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkDomainsChemistryPythonD;general;vtkDomainsChemistryPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkRenderingCorePythonD;general;vtkDomainsChemistryOpenGL2;

//Dependencies for the target
vtkDomainsChemistryOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryOpenGL2PythonD;

//Dependencies for the target
vtkDomainsChemistryOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkDomainsChemistry;general;vtkDomainsChemistry;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkglew;general;opengl32;general;glu32;

//Dependencies for the target
vtkDomainsChemistryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLParserPythonD;general;vtkRenderingCorePythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkDomainsChemistry;

//Dependencies for the target
vtkDomainsChemistryPython_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryPythonD;

//Dependencies for the target
vtkDomainsChemistry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXMLParser;general;vtkRenderingCore;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys;

//Value Computed by CMake
vtkExodus2_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/exodusII/vtkexodusII

//Value Computed by CMake
vtkExodus2_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/exodusII/vtkexodusII

//Dependencies for the target
vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR;

//Dependencies for the target
vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;general;vtkFiltersAMR;

//Dependencies for the target
vtkFiltersAMRPython_LIB_DEPENDS:STATIC=general;vtkFiltersAMRPythonD;

//Dependencies for the target
vtkFiltersAMR_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkIOXML;general;vtkParallelCore;

//Dependencies for the target
vtkFiltersCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersCorePython_LIB_DEPENDS:STATIC=general;vtkFiltersCorePythonD;

//Dependencies for the target
vtkFiltersCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;

//Dependencies for the target
vtkFiltersExtractionCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersExtraction;

//Dependencies for the target
vtkFiltersExtractionPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersStatisticsPythonD;general;vtkFiltersExtraction;

//Dependencies for the target
vtkFiltersExtractionPython_LIB_DEPENDS:STATIC=general;vtkFiltersExtractionPythonD;

//Dependencies for the target
vtkFiltersExtraction_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersCore;general;vtkFiltersStatistics;

//Dependencies for the target
vtkFiltersFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersFlowPaths;

//Dependencies for the target
vtkFiltersFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOCorePythonD;general;vtkFiltersFlowPaths;

//Dependencies for the target
vtkFiltersFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPathsPythonD;

//Dependencies for the target
vtkFiltersFlowPaths_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkFiltersGeometry;general;vtkFiltersSources;general;vtkIOCore;

//Dependencies for the target
vtkFiltersGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersCorePythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersGeneralPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersGeneral_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonComputationalGeometry;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;

//Dependencies for the target
vtkFiltersGenericCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneric;

//Dependencies for the target
vtkFiltersGenericPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersGeneric;

//Dependencies for the target
vtkFiltersGenericPython_LIB_DEPENDS:STATIC=general;vtkFiltersGenericPythonD;

//Dependencies for the target
vtkFiltersGeneric_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeometry;

//Dependencies for the target
vtkFiltersGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometry;

//Dependencies for the target
vtkFiltersGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeometryPythonD;

//Dependencies for the target
vtkFiltersGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHybrid;

//Dependencies for the target
vtkFiltersHybridPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkFiltersHybrid;

//Dependencies for the target
vtkFiltersHybridPython_LIB_DEPENDS:STATIC=general;vtkFiltersHybridPythonD;

//Dependencies for the target
vtkFiltersHybrid_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkCommonMath;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkImagingCore;general;vtkImagingSources;general;vtkRenderingCore;general;vtksys;

//Dependencies for the target
vtkFiltersHyperTreeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHyperTree;

//Dependencies for the target
vtkFiltersHyperTreePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonSystemPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersHyperTree;

//Dependencies for the target
vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD;

//Dependencies for the target
vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonCore;general;vtkCommonSystem;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersImaging;

//Dependencies for the target
vtkFiltersImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersStatisticsPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkImagingGeneralPythonD;general;vtkFiltersImaging;

//Dependencies for the target
vtkFiltersImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersImagingPythonD;

//Dependencies for the target
vtkFiltersImaging_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersStatistics;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkImagingGeneral;

//Dependencies for the target
vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling;

//Dependencies for the target
vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersGeneralPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersModeling;

//Dependencies for the target
vtkFiltersModelingPython_LIB_DEPENDS:STATIC=general;vtkFiltersModelingPythonD;

//Dependencies for the target
vtkFiltersModeling_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallel;

//Dependencies for the target
vtkFiltersParallelFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelFlowPaths;

//Dependencies for the target
vtkFiltersParallelFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersFlowPathsPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkIOCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelFlowPaths;

//Dependencies for the target
vtkFiltersParallelFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelFlowPathsPythonD;

//Dependencies for the target
vtkFiltersParallelFlowPaths_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkFiltersFlowPaths;general;vtkFiltersFlowPaths;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkIOCore;general;vtkParallelCore;general;vtkParallelMPI;

//Dependencies for the target
vtkFiltersParallelGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelGeometry;

//Dependencies for the target
vtkFiltersParallelGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeometryPythonD;general;vtkParallelMPIPythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelGeometry;

//Dependencies for the target
vtkFiltersParallelGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelGeometryPythonD;

//Dependencies for the target
vtkFiltersParallelGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeometry;general;vtkParallelMPI;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkIOLegacy;general;vtkParallelCore;

//Dependencies for the target
vtkFiltersParallelImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelImaging;

//Dependencies for the target
vtkFiltersParallelImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersImagingPythonD;general;vtkFiltersParallelPythonD;general;vtkImagingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersStatisticsPythonD;general;vtkImagingGeneralPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelImaging;

//Dependencies for the target
vtkFiltersParallelImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImagingPythonD;

//Dependencies for the target
vtkFiltersParallelImaging_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersImaging;general;vtkFiltersParallel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersStatistics;general;vtkImagingGeneral;general;vtkParallelCore;

//Dependencies for the target
vtkFiltersParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelMPI;

//Dependencies for the target
vtkFiltersParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkImagingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelMPI;

//Dependencies for the target
vtkFiltersParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelMPIPythonD;

//Dependencies for the target
vtkFiltersParallelMPI_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkImagingCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkFiltersParallel;general;vtkIOLegacy;general;vtkParallelCore;general;vtkParallelMPI;

//Dependencies for the target
vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersSourcesPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkFiltersParallel;

//Dependencies for the target
vtkFiltersParallelPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelPythonD;

//Dependencies for the target
vtkFiltersParallelStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelStatistics;

//Dependencies for the target
vtkFiltersParallelStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersStatisticsPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelStatistics;

//Dependencies for the target
vtkFiltersParallelStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelStatisticsPythonD;

//Dependencies for the target
vtkFiltersParallelStatistics_LIB_DEPENDS:STATIC=general;vtkFiltersStatistics;general;vtkalglib;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkParallelCore;

//Dependencies for the target
vtkFiltersParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersModeling;general;vtkFiltersSources;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOLegacy;general;vtkParallelCore;general;vtkRenderingCore;

//Dependencies for the target
vtkFiltersPointsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPoints;

//Dependencies for the target
vtkFiltersPointsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersPoints;

//Dependencies for the target
vtkFiltersPointsPython_LIB_DEPENDS:STATIC=general;vtkFiltersPointsPythonD;

//Dependencies for the target
vtkFiltersPoints_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;

//Dependencies for the target
vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable;

//Dependencies for the target
vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersProgrammable;

//Dependencies for the target
vtkFiltersProgrammablePython_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammablePythonD;

//Dependencies for the target
vtkFiltersProgrammable_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;

//Dependencies for the target
vtkFiltersPythonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPython;

//Dependencies for the target
vtkFiltersPythonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkFiltersPython;

//Dependencies for the target
vtkFiltersPythonPython_LIB_DEPENDS:STATIC=general;vtkFiltersPythonPythonD;

//Dependencies for the target
vtkFiltersPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;vtkCommonCore;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkFiltersSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonCorePythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersSourcesPython_LIB_DEPENDS:STATIC=general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkFiltersSources_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonComputationalGeometry;general;vtkCommonCore;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersStatistics;

//Dependencies for the target
vtkFiltersStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkImagingFourierPythonD;general;vtkFiltersStatistics;

//Dependencies for the target
vtkFiltersStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersStatisticsPythonD;

//Dependencies for the target
vtkFiltersStatistics_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkalglib;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkImagingFourier;

//Dependencies for the target
vtkFiltersTextureCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersTexture;

//Dependencies for the target
vtkFiltersTexturePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersTexture;

//Dependencies for the target
vtkFiltersTexturePython_LIB_DEPENDS:STATIC=general;vtkFiltersTexturePythonD;

//Dependencies for the target
vtkFiltersTexture_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersVerdictCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersVerdict;

//Dependencies for the target
vtkFiltersVerdictPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersVerdict;

//Dependencies for the target
vtkFiltersVerdictPython_LIB_DEPENDS:STATIC=general;vtkFiltersVerdictPythonD;

//Dependencies for the target
vtkFiltersVerdict_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;verdict;general;vtkCommonCore;general;vtkCommonDataModel;

//Dependencies for the target
vtkGUISupportQt_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkInteractionStyle;general;Qt5::Widgets;

//Dependencies for the target
vtkIOAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOAMR;

//Dependencies for the target
vtkIOAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;general;vtkIOAMR;

//Dependencies for the target
vtkIOAMRPython_LIB_DEPENDS:STATIC=general;vtkIOAMRPythonD;

//Dependencies for the target
vtkIOAMR_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkParallelCore;general;vtkhdf5_hl;general;vtkhdf5;general;vtksys;

//Dependencies for the target
vtkIOCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOCore;

//Dependencies for the target
vtkIOCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCore;

//Dependencies for the target
vtkIOCorePython_LIB_DEPENDS:STATIC=general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtklz4;general;vtksys;general;vtkzlib;

//Dependencies for the target
vtkIOEnSightCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOEnSight;

//Dependencies for the target
vtkIOEnSightPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOEnSight;

//Dependencies for the target
vtkIOEnSightPython_LIB_DEPENDS:STATIC=general;vtkIOEnSightPythonD;

//Dependencies for the target
vtkIOEnSight_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;

//Dependencies for the target
vtkIOExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExodus;

//Dependencies for the target
vtkIOExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkFiltersCorePythonD;general;vtkIOExodus;

//Dependencies for the target
vtkIOExodusPython_LIB_DEPENDS:STATIC=general;vtkIOExodusPythonD;

//Dependencies for the target
vtkIOExodus_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOXMLParser;general;vtkexoIIc;general;vtkFiltersCore;general;vtksys;

//Dependencies for the target
vtkIOExportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExport;

//Dependencies for the target
vtkIOExportOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExportOpenGL2;

//Dependencies for the target
vtkIOExportOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOExportPythonD;general;vtkIOExportPythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkIOExportOpenGL2;

//Dependencies for the target
vtkIOExportOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkIOExportOpenGL2PythonD;

//Dependencies for the target
vtkIOExportOpenGL2_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtkIOExport;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkRenderingCore;general;vtkgl2ps;general;opengl32;general;glu32;

//Dependencies for the target
vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeometryPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkIOExport;

//Dependencies for the target
vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD;

//Dependencies for the target
vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeometry;general;vtkIOImage;general;vtkImagingCore;general;vtklibharu;general;opengl32;general;glu32;

//Dependencies for the target
vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry;

//Dependencies for the target
vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkCommonCorePythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOGeometry;

//Dependencies for the target
vtkIOGeometryPython_LIB_DEPENDS:STATIC=general;vtkIOGeometryPythonD;

//Dependencies for the target
vtkIOGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOLegacy;general;vtkCommonCore;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtksys;general;vtkzlib;

//Dependencies for the target
vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage;

//Dependencies for the target
vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImage;

//Dependencies for the target
vtkIOImagePython_LIB_DEPENDS:STATIC=general;vtkIOImagePythonD;

//Dependencies for the target
vtkIOImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkDICOMParser;general;vtkmetaio;general;vtkjpeg;general;vtkpng;general;vtksys;general;vtktiff;general;vtkzlib;

//Dependencies for the target
vtkIOImportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImport;

//Dependencies for the target
vtkIOImportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkIOImagePythonD;general;vtkIOImport;

//Dependencies for the target
vtkIOImportPython_LIB_DEPENDS:STATIC=general;vtkIOImportPythonD;

//Dependencies for the target
vtkIOImport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkRenderingCore;general;vtksys;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersSources;general;vtkIOImage;

//Dependencies for the target
vtkIOInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOInfovis;

//Dependencies for the target
vtkIOInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkInfovisCorePythonD;general;vtkIOInfovis;

//Dependencies for the target
vtkIOInfovisPython_LIB_DEPENDS:STATIC=general;vtkIOInfovisPythonD;

//Dependencies for the target
vtkIOInfovis_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXML;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkIOCore;general;vtkIOXMLParser;general;vtkInfovisCore;general;vtklibxml2;general;vtksys;

//Dependencies for the target
vtkIOLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLSDyna;

//Dependencies for the target
vtkIOLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLParserPythonD;general;vtkCommonDataModelPythonD;general;vtkIOLSDyna;

//Dependencies for the target
vtkIOLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOLSDynaPythonD;

//Dependencies for the target
vtkIOLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;general;vtksys;

//Dependencies for the target
vtkIOLegacyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLegacy;

//Dependencies for the target
vtkIOLegacyPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkCommonMiscPythonD;general;vtkIOLegacy;

//Dependencies for the target
vtkIOLegacyPython_LIB_DEPENDS:STATIC=general;vtkIOLegacyPythonD;

//Dependencies for the target
vtkIOLegacy_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkCommonMisc;general;vtksys;

//Dependencies for the target
vtkIOMPIImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIImage;

//Dependencies for the target
vtkIOMPIImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkIOMPIImage;

//Dependencies for the target
vtkIOMPIImagePython_LIB_DEPENDS:STATIC=general;vtkIOMPIImagePythonD;

//Dependencies for the target
vtkIOMPIImage_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkIOImage;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkParallelCore;general;vtkParallelMPI;general;vtksys;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkIOMPIParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIParallel;

//Dependencies for the target
vtkIOMPIParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOGeometryPythonD;general;vtkIOGeometryPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkParallelMPIPythonD;general;vtkIOMPIParallel;

//Dependencies for the target
vtkIOMPIParallelPython_LIB_DEPENDS:STATIC=general;vtkIOMPIParallelPythonD;

//Dependencies for the target
vtkIOMPIParallel_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkIOGeometry;general;vtkIOParallel;general;vtkIOParallel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelMPI;general;vtksys;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie;

//Dependencies for the target
vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOMovie;

//Dependencies for the target
vtkIOMoviePython_LIB_DEPENDS:STATIC=general;vtkIOMoviePythonD;

//Dependencies for the target
vtkIOMovie_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkoggtheora;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vfw32;

//Dependencies for the target
vtkIONetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIONetCDF;

//Dependencies for the target
vtkIONetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkIONetCDF;

//Dependencies for the target
vtkIONetCDFPython_LIB_DEPENDS:STATIC=general;vtkIONetCDFPythonD;

//Dependencies for the target
vtkIONetCDF_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkNetCDF;general;vtknetcdfcpp;general;vtksys;

//Dependencies for the target
vtkIOPLYCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOPLY;

//Dependencies for the target
vtkIOPLYPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOPLY;

//Dependencies for the target
vtkIOPLYPython_LIB_DEPENDS:STATIC=general;vtkIOPLYPythonD;

//Dependencies for the target
vtkIOPLY_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkCommonDataModel;general;vtkCommonMisc;

//Dependencies for the target
vtkIOParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallel;

//Dependencies for the target
vtkIOParallelExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelExodus;

//Dependencies for the target
vtkIOParallelExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOExodusPythonD;general;vtkIOExodusPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkParallelCorePythonD;general;vtkIOParallelExodus;

//Dependencies for the target
vtkIOParallelExodusPython_LIB_DEPENDS:STATIC=general;vtkIOParallelExodusPythonD;

//Dependencies for the target
vtkIOParallelExodus_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOExodus;general;vtkIOExodus;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkParallelCore;general;vtkexoIIc;general;vtksys;

//Dependencies for the target
vtkIOParallelLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelLSDyna;

//Dependencies for the target
vtkIOParallelLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOLSDynaPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkParallelCorePythonD;general;vtkIOParallelLSDyna;

//Dependencies for the target
vtkIOParallelLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOParallelLSDynaPythonD;

//Dependencies for the target
vtkIOParallelLSDyna_LIB_DEPENDS:STATIC=general;vtkIOLSDyna;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkParallelCore;

//Dependencies for the target
vtkIOParallelNetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelNetCDF;

//Dependencies for the target
vtkIOParallelNetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelMPIPythonD;general;vtkIOParallelNetCDF;

//Dependencies for the target
vtkIOParallelNetCDFPython_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDFPythonD;

//Dependencies for the target
vtkIOParallelNetCDF_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkNetCDF;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOGeometryPythonD;general;vtkIOImagePythonD;general;vtkIOLegacyPythonD;general;vtkIONetCDFPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkParallelCorePythonD;general;vtkIOParallel;

//Dependencies for the target
vtkIOParallelPython_LIB_DEPENDS:STATIC=general;vtkIOParallelPythonD;

//Dependencies for the target
vtkIOParallelXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelXML;

//Dependencies for the target
vtkIOParallelXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOXMLPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkParallelCorePythonD;general;vtkIOParallelXML;

//Dependencies for the target
vtkIOParallelXMLPython_LIB_DEPENDS:STATIC=general;vtkIOParallelXMLPythonD;

//Dependencies for the target
vtkIOParallelXML_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelCore;general;vtksys;

//Dependencies for the target
vtkIOParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOGeometry;general;vtkIOImage;general;vtkIOLegacy;general;vtkIONetCDF;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkParallelCore;general;vtkexoIIc;general;vtkjsoncpp;general;vtkNetCDF;general;vtksys;

//Dependencies for the target
vtkIOTRUCHASCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOTRUCHAS;

//Dependencies for the target
vtkIOTRUCHASPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkIOTRUCHAS;

//Dependencies for the target
vtkIOTRUCHASPython_LIB_DEPENDS:STATIC=general;vtkIOTRUCHASPythonD;

//Dependencies for the target
vtkIOTRUCHAS_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkhdf5_hl;general;vtkhdf5;

//Dependencies for the target
vtkIOTecplotTableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOTecplotTable;

//Dependencies for the target
vtkIOTecplotTablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkIOCorePythonD;general;vtkIOTecplotTable;

//Dependencies for the target
vtkIOTecplotTablePython_LIB_DEPENDS:STATIC=general;vtkIOTecplotTablePythonD;

//Dependencies for the target
vtkIOTecplotTable_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOCore;general;vtksys;

//Dependencies for the target
vtkIOVPICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOVPIC;

//Dependencies for the target
vtkIOVPICPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkParallelCorePythonD;general;vtkIOVPIC;

//Dependencies for the target
vtkIOVPICPython_LIB_DEPENDS:STATIC=general;vtkIOVPICPythonD;

//Dependencies for the target
vtkIOVPIC_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;VPIC;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkParallelCore;

//Dependencies for the target
vtkIOXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXML;

//Dependencies for the target
vtkIOXMLParserCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXMLParser;

//Dependencies for the target
vtkIOXMLParserPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParser;

//Dependencies for the target
vtkIOXMLParserPython_LIB_DEPENDS:STATIC=general;vtkIOXMLParserPythonD;

//Dependencies for the target
vtkIOXMLParser_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkIOCore;general;vtkexpat;general;vtksys;

//Dependencies for the target
vtkIOXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLParserPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOXML;

//Dependencies for the target
vtkIOXMLPython_LIB_DEPENDS:STATIC=general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOXML_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtksys;

//Dependencies for the target
vtkIOXdmf2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXdmf2;

//Dependencies for the target
vtkIOXdmf2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOLegacyPythonD;general;vtkFiltersExtractionPythonD;general;vtkIOXMLParserPythonD;general;vtkIOXdmf2;

//Dependencies for the target
vtkIOXdmf2Python_LIB_DEPENDS:STATIC=general;vtkIOXdmf2PythonD;

//Dependencies for the target
vtkIOXdmf2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkFiltersExtraction;general;vtkIOXMLParser;general;vtksys;general;vtkxdmf2;

//Dependencies for the target
vtkImagingColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingColor;

//Dependencies for the target
vtkImagingColorPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkImagingColor;

//Dependencies for the target
vtkImagingColorPython_LIB_DEPENDS:STATIC=general;vtkImagingColorPythonD;

//Dependencies for the target
vtkImagingColor_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;

//Dependencies for the target
vtkImagingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingCore;

//Dependencies for the target
vtkImagingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCore;

//Dependencies for the target
vtkImagingCorePython_LIB_DEPENDS:STATIC=general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonTransforms;

//Dependencies for the target
vtkImagingFourierCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingFourier;

//Dependencies for the target
vtkImagingFourierPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingFourier;

//Dependencies for the target
vtkImagingFourierPython_LIB_DEPENDS:STATIC=general;vtkImagingFourierPythonD;

//Dependencies for the target
vtkImagingFourier_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonDataModel;general;vtksys;

//Dependencies for the target
vtkImagingGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingGeneral;

//Dependencies for the target
vtkImagingGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingSourcesPythonD;general;vtkImagingGeneral;

//Dependencies for the target
vtkImagingGeneralPython_LIB_DEPENDS:STATIC=general;vtkImagingGeneralPythonD;

//Dependencies for the target
vtkImagingGeneral_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingSources;

//Dependencies for the target
vtkImagingHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingHybrid;

//Dependencies for the target
vtkImagingHybridPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkImagingHybrid;

//Dependencies for the target
vtkImagingHybridPython_LIB_DEPENDS:STATIC=general;vtkImagingHybridPythonD;

//Dependencies for the target
vtkImagingHybrid_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOImage;general;vtkImagingCore;

//Dependencies for the target
vtkImagingMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMath;

//Dependencies for the target
vtkImagingMathPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingMath;

//Dependencies for the target
vtkImagingMathPython_LIB_DEPENDS:STATIC=general;vtkImagingMathPythonD;

//Dependencies for the target
vtkImagingMath_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;

//Dependencies for the target
vtkImagingMorphologicalCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMorphological;

//Dependencies for the target
vtkImagingMorphologicalPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkImagingMorphological;

//Dependencies for the target
vtkImagingMorphologicalPython_LIB_DEPENDS:STATIC=general;vtkImagingMorphologicalPythonD;

//Dependencies for the target
vtkImagingMorphological_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkImagingGeneral;general;vtkImagingSources;

//Dependencies for the target
vtkImagingSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingSources;

//Dependencies for the target
vtkImagingSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingSources;

//Dependencies for the target
vtkImagingSourcesPython_LIB_DEPENDS:STATIC=general;vtkImagingSourcesPythonD;

//Dependencies for the target
vtkImagingSources_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;

//Dependencies for the target
vtkInfovisCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInfovisCore;

//Dependencies for the target
vtkInfovisCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkInfovisCore;

//Dependencies for the target
vtkInfovisCorePython_LIB_DEPENDS:STATIC=general;vtkInfovisCorePythonD;

//Dependencies for the target
vtkInfovisCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkFiltersGeneral;

//Dependencies for the target
vtkInteractionImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionImage;

//Dependencies for the target
vtkInteractionImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkInteractionImage;

//Dependencies for the target
vtkInteractionImagePython_LIB_DEPENDS:STATIC=general;vtkInteractionImagePythonD;

//Dependencies for the target
vtkInteractionImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingColor;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkInteractionWidgets;

//Dependencies for the target
vtkInteractionStyleCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionStyle;

//Dependencies for the target
vtkInteractionStylePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkInteractionStyle;

//Dependencies for the target
vtkInteractionStylePython_LIB_DEPENDS:STATIC=general;vtkInteractionStylePythonD;

//Dependencies for the target
vtkInteractionStyle_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersExtraction;general;vtkFiltersSources;

//Dependencies for the target
vtkInteractionWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionWidgets;

//Dependencies for the target
vtkInteractionWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingVolumePythonD;general;vtkInteractionWidgets;

//Dependencies for the target
vtkInteractionWidgetsPython_LIB_DEPENDS:STATIC=general;vtkInteractionWidgetsPythonD;

//Dependencies for the target
vtkInteractionWidgets_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkRenderingCore;general;vtkCommonComputationalGeometry;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersHybrid;general;vtkFiltersModeling;general;vtkImagingColor;general;vtkImagingCore;general;vtkImagingGeneral;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingVolume;

//Dependencies for the target
vtkNetCDF_LIB_DEPENDS:STATIC=general;vtkhdf5_hl;general;vtkhdf5;

//Dependencies for the target
vtkPVAnimationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVAnimation;

//Dependencies for the target
vtkPVAnimationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkIOMoviePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkPVAnimation;

//Dependencies for the target
vtkPVAnimationPython_LIB_DEPENDS:STATIC=general;vtkPVAnimationPythonD;

//Dependencies for the target
vtkPVAnimation_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtkPVVTKExtensionsDefault;general;vtksys;general;vtkIOMovie;general;vtkPVServerManagerDefault;

//Dependencies for the target
vtkPVCatalystCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalyst;

//Dependencies for the target
vtkPVCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerApplicationPythonD;general;vtkPVCatalyst;

//Dependencies for the target
vtkPVCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystPythonD;

//Dependencies for the target
vtkPVCatalyst_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtksys;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkPVCinemaReaderCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCinemaReader;

//Dependencies for the target
vtkPVCinemaReaderPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkPVServerManagerCorePythonD;general;vtkRenderingCorePythonD;general;vtkPVAnimationPythonD;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerManagerRenderingPythonD;general;vtkPythonInterpreterPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkPVCinemaReader;

//Dependencies for the target
vtkPVCinemaReaderPython_LIB_DEPENDS:STATIC=general;vtkPVCinemaReaderPythonD;

//Dependencies for the target
vtkPVCinemaReader_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkPVServerManagerCore;general;vtkRenderingCore;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;vtkPVAnimation;general;vtkPVClientServerCoreRendering;general;vtkPVServerManagerRendering;general;vtkPythonInterpreter;general;vtkRenderingOpenGL2;general;opengl32;general;glu32;

//Dependencies for the target
vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore;

//Dependencies for the target
vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkIOLegacyPythonD;general;vtkPVCommonPythonD;general;vtkPVCommonPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkPythonInterpreterPythonD;general;vtkPVClientServerCoreCore;

//Dependencies for the target
vtkPVClientServerCoreCorePython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCorePythonD;

//Dependencies for the target
vtkPVClientServerCoreCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkFiltersProgrammable;general;vtkIOLegacy;general;vtkPVCommon;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkPythonInterpreter;general;vtksys;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkPVClientServerCoreDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreDefault;

//Dependencies for the target
vtkPVClientServerCoreDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkIOInfovisPythonD;general;vtkPVClientServerCoreDefault;

//Dependencies for the target
vtkPVClientServerCoreDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefaultPythonD;

//Dependencies for the target
vtkPVClientServerCoreDefault_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVVTKExtensionsDefault;general;vtksys;general;vtkIOInfovis;general;mpr;

//Dependencies for the target
vtkPVClientServerCoreRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreRendering;

//Dependencies for the target
vtkPVClientServerCoreRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkPVClientServerCoreCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;general;vtkPVClientServerCoreRendering;

//Dependencies for the target
vtkPVClientServerCoreRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRenderingPythonD;

//Dependencies for the target
vtkPVClientServerCoreRendering_LIB_DEPENDS:STATIC=general;vtkDomainsChemistry;general;vtkFiltersAMR;general;vtkPVClientServerCoreCore;general;vtkPVVTKExtensionsDefault;general;vtkPVVTKExtensionsRendering;general;vtkRenderingLabel;general;vtkRenderingVolumeOpenGL2;general;vtkViewsContext2D;general;vtkViewsCore;general;vtksys;general;vtkzlib;general;opengl32;general;glu32;

//Dependencies for the target
vtkPVCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCommon;

//Dependencies for the target
vtkPVCommonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOXMLParserPythonD;general;vtkPVCommon;

//Dependencies for the target
vtkPVCommonPython_LIB_DEPENDS:STATIC=general;vtkPVCommonPythonD;

//Dependencies for the target
vtkPVCommon_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;general;vtkIOXMLParser;general;vtksys;

//Dependencies for the target
vtkPVPythonCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;general;vtkPythonInterpreterPythonD;general;vtkPVPythonCatalyst;

//Dependencies for the target
vtkPVPythonCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVPythonCatalystPythonD;

//Dependencies for the target
vtkPVPythonCatalyst_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;general;vtkPythonInterpreter;general;vtkUtilitiesPythonInitializer;

//Dependencies for the target
vtkPVServerImplementationCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationCore;

//Dependencies for the target
vtkPVServerImplementationCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreCorePythonD;general;vtkPVServerImplementationCore;

//Dependencies for the target
vtkPVServerImplementationCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCorePythonD;

//Dependencies for the target
vtkPVServerImplementationCore_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;protobuf;general;vtksys;

//Dependencies for the target
vtkPVServerImplementationRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationRendering;

//Dependencies for the target
vtkPVServerImplementationRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPVServerImplementationRendering;

//Dependencies for the target
vtkPVServerImplementationRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRenderingPythonD;

//Dependencies for the target
vtkPVServerImplementationRendering_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVServerImplementationCore;

//Dependencies for the target
vtkPVServerManagerApplicationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerApplication;

//Dependencies for the target
vtkPVServerManagerApplicationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerApplication;

//Dependencies for the target
vtkPVServerManagerApplicationPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplicationPythonD;

//Dependencies for the target
vtkPVServerManagerApplication_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtksys;general;vtkCommonCoreCS;general;vtkCommonMathCS;general;vtkCommonMiscCS;general;vtkCommonSystemCS;general;vtkCommonTransformsCS;general;vtkCommonDataModelCS;general;vtkCommonExecutionModelCS;general;vtkFiltersCoreCS;general;vtkCommonComputationalGeometryCS;general;vtkFiltersGeneralCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkFiltersSourcesCS;general;vtkCommonColorCS;general;vtkFiltersGeometryCS;general;vtkRenderingCoreCS;general;vtkInteractionStyleCS;general;vtkRenderingOpenGL2CS;general;vtkFiltersModelingCS;general;vtkIOCoreCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersParallelCS;general;vtkFiltersProgrammableCS;general;vtkPythonInterpreterCS;general;vtkIOXMLParserCS;general;vtkPVCommonCS;general;vtkIOImageCS;general;vtkPVVTKExtensionsCoreCS;general;vtkParallelMPICS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkIOMovieCS;general;vtkIOXMLCS;general;vtkInfovisCoreCS;general;vtkIOInfovisCS;general;vtkDomainsChemistryCS;general;vtkFiltersAMRCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersParallelFlowPathsCS;general;vtkFiltersParallelStatisticsCS;general;vtkIOEnSightCS;general;vtkIOImportCS;general;vtkIOMPIImageCS;general;vtkIOPLYCS;general;vtkIOGeometryCS;general;vtkIONetCDFCS;general;vtkIOParallelCS;general;vtkIOExodusCS;general;vtkIOParallelExodusCS;general;vtkIOParallelXMLCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkImagingColorCS;general;vtkImagingGeneralCS;general;vtkImagingHybridCS;general;vtkRenderingAnnotationCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkFiltersGenericCS;general;vtkFiltersHyperTreeCS;general;vtkFiltersParallelMPICS;general;vtkRenderingGL2PSOpenGL2CS;general;vtkIOExportCS;general;vtkIOExportOpenGL2CS;general;vtkRenderingContextOpenGL2CS;general;vtkRenderingMatplotlibCS;general;vtkRenderingParallelCS;general;vtkImagingMathCS;general;vtkRenderingVolumeOpenGL2CS;general;vtkRenderingVolumeAMRCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingLabelCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkDomainsChemistryOpenGL2CS;general;vtkFiltersParallelGeometryCS;general;vtkFiltersImagingCS;general;vtkFiltersParallelImagingCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOMPIParallelCS;general;vtkIOLSDynaCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelNetCDFCS;general;vtkIOTRUCHASCS;general;vtkIOTecplotTableCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionImageCS;general;vtkPVCinemaReaderCS;general;vtkPVVTKExtensionsCGNSReaderCS;general;vtkPVVTKExtensionsH5PartReaderCS;general;vtkFiltersPointsCS;general;vtkPVVTKExtensionsPointsCS;general;vtkParallelMPI4PyCS;general;vtkRenderingLICOpenGL2CS;general;vtkRenderingLODCS;general;vtkRenderingParallelLICCS;general;vtkPVServerManagerCore;

//Dependencies for the target
vtkPVServerManagerCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerCore;

//Dependencies for the target
vtkPVServerManagerCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkPVServerManagerCore;

//Dependencies for the target
vtkPVServerManagerCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCorePythonD;

//Dependencies for the target
vtkPVServerManagerCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkPVServerImplementationCore;general;vtkjsoncpp;general;vtksys;general;vtkpugixml;general;vtkPythonInterpreter;

//Dependencies for the target
vtkPVServerManagerDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerDefault;

//Dependencies for the target
vtkPVServerManagerDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerRenderingPythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkTestingRenderingPythonD;general;vtkPVClientServerCoreDefaultPythonD;general;vtkPVServerManagerDefault;

//Dependencies for the target
vtkPVServerManagerDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefaultPythonD;

//Dependencies for the target
vtkPVServerManagerDefault_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRendering;general;vtksys;general;vtkpugixml;general;vtkRenderingVolumeOpenGL2;general;vtkTestingRendering;general;vtkPVClientServerCoreDefault;

//Dependencies for the target
vtkPVServerManagerRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerRendering;

//Dependencies for the target
vtkPVServerManagerRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerImplementationRenderingPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerCorePythonD;general;vtkCommonColorPythonD;general;vtkPVServerManagerRendering;

//Dependencies for the target
vtkPVServerManagerRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRenderingPythonD;

//Dependencies for the target
vtkPVServerManagerRendering_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRendering;general;vtkPVServerManagerCore;general;vtkPVServerManagerCore;general;vtkjsoncpp;general;vtkCommonColor;general;vtksys;

//Dependencies for the target
vtkPVVTKExtensionsCGNSReaderCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCGNSReader;

//Dependencies for the target
vtkPVVTKExtensionsCGNSReaderPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkPVVTKExtensionsCGNSReader;

//Dependencies for the target
vtkPVVTKExtensionsCGNSReaderPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCGNSReaderPythonD;

//Dependencies for the target
vtkPVVTKExtensionsCGNSReader_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkPVVTKExtensionsCore;general;vtkParallelCore;general;vtkcgns;general;vtksys;general;vtkParallelCore;general;vtkFiltersExtraction;

//Dependencies for the target
vtkPVVTKExtensionsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCore;

//Dependencies for the target
vtkPVVTKExtensionsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkIOImagePythonD;general;vtkPVCommonPythonD;general;vtkParallelCorePythonD;general;vtkPVVTKExtensionsCore;

//Dependencies for the target
vtkPVVTKExtensionsCorePython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCorePythonD;

//Dependencies for the target
vtkPVVTKExtensionsCore_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkFiltersSources;general;vtkIOImage;general;vtkPVCommon;general;vtkParallelCore;general;vtksys;

//Dependencies for the target
vtkPVVTKExtensionsDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsDefault;

//Dependencies for the target
vtkPVVTKExtensionsDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelFlowPathsPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkIOEnSightPythonD;general;vtkIOImportPythonD;general;vtkIOMPIImagePythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelXMLPythonD;general;vtkImagingFourierPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkIOInfovisPythonD;general;vtkChartsCorePythonD;general;vtkIOPLYPythonD;general;vtkPVVTKExtensionsDefault;

//Dependencies for the target
vtkPVVTKExtensionsDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefaultPythonD;

//Dependencies for the target
vtkPVVTKExtensionsDefault_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersParallelFlowPaths;general;vtkFiltersParallelStatistics;general;vtkIOEnSight;general;vtkIOImport;general;vtkIOMPIImage;general;vtkIOParallel;general;vtkIOParallelExodus;general;vtkIOParallelXML;general;vtkImagingFourier;general;vtkImagingSources;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkPVVTKExtensionsRendering;general;vtkIOInfovis;general;vtknetcdfcpp;general;vtksys;general;vtkChartsCore;general;vtkIOPLY;general;opengl32;general;glu32;

//Dependencies for the target
vtkPVVTKExtensionsH5PartReaderCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsH5PartReader;

//Dependencies for the target
vtkPVVTKExtensionsH5PartReaderPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelCorePythonD;general;vtkPVVTKExtensionsH5PartReader;

//Dependencies for the target
vtkPVVTKExtensionsH5PartReaderPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsH5PartReaderPythonD;

//Dependencies for the target
vtkPVVTKExtensionsH5PartReader_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkPVVTKExtensionsCore;general;vtkParallelCore;general;vtkcgns;general;vtkhdf5_hl;general;vtkhdf5;general;vtksys;general;vtkParallelCore;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkPVVTKExtensionsPointsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsPoints;

//Dependencies for the target
vtkPVVTKExtensionsPointsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersPointsPythonD;general;vtkFiltersCorePythonD;general;vtkPVVTKExtensionsPoints;

//Dependencies for the target
vtkPVVTKExtensionsPointsPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsPointsPythonD;

//Dependencies for the target
vtkPVVTKExtensionsPoints_LIB_DEPENDS:STATIC=general;vtkFiltersPoints;general;vtkFiltersCore;

//Dependencies for the target
vtkPVVTKExtensionsRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsRendering;

//Dependencies for the target
vtkPVVTKExtensionsRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkIOExportPythonD;general;vtkIOExportOpenGL2PythonD;general;vtkIOImagePythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContextOpenGL2PythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingVolumeAMRPythonD;general;vtkCommonColorPythonD;general;vtkPVVTKExtensionsRendering;

//Dependencies for the target
vtkPVVTKExtensionsRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRenderingPythonD;

//Dependencies for the target
vtkPVVTKExtensionsRendering_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersGeneric;general;vtkFiltersHyperTree;general;vtkFiltersParallel;general;vtkFiltersParallelMPI;general;vtkGUISupportQt;general;vtkIOExport;general;vtkIOExportOpenGL2;general;vtkIOImage;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkRenderingAnnotation;general;vtkRenderingContextOpenGL2;general;vtkRenderingFreeType;general;vtkRenderingMatplotlib;general;vtkRenderingOpenGL2;general;vtkRenderingParallel;general;vtkRenderingVolumeAMR;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkCommonColor;general;vtkglew;general;vtkzlib;general;vtklz4;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;opengl32;general;glu32;

//Dependencies for the target
vtkParaViewDocumentation_LIB_DEPENDS:STATIC=general;Qt5::Widgets;

//Dependencies for the target
vtkParallelCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelCore;

//Dependencies for the target
vtkParallelCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCore;

//Dependencies for the target
vtkParallelCorePython_LIB_DEPENDS:STATIC=general;vtkParallelCorePythonD;

//Dependencies for the target
vtkParallelCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkIOLegacy;general;vtksys;

//Dependencies for the target
vtkParallelMPI4PyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI4Py;

//Dependencies for the target
vtkParallelMPI4PyPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkParallelMPIPythonD;general;vtkParallelMPIPythonD;general;vtkParallelMPI4Py;

//Dependencies for the target
vtkParallelMPI4PyPython_LIB_DEPENDS:STATIC=general;vtkParallelMPI4PyPythonD;

//Dependencies for the target
vtkParallelMPI4Py_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelMPI;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;vtkParallelMPI;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI;

//Dependencies for the target
vtkParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkParallelCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelMPI;

//Dependencies for the target
vtkParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkParallelMPI_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelCore;general;vtkCommonDataModel;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkPythonInterpreterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPythonInterpreter;

//Dependencies for the target
vtkPythonInterpreterPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPythonInterpreter;

//Dependencies for the target
vtkPythonInterpreterPython_LIB_DEPENDS:STATIC=general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPythonInterpreter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;vtksys;general;C:/ProgramData/Miniconda3/libs/python36.lib;

//Dependencies for the target
vtkRenderingAnnotationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingAnnotation;

//Dependencies for the target
vtkRenderingAnnotationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingAnnotation;

//Dependencies for the target
vtkRenderingAnnotationPython_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotationPythonD;

//Dependencies for the target
vtkRenderingAnnotation_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkImagingColor;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContext2D;

//Dependencies for the target
vtkRenderingContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingContext2D;

//Dependencies for the target
vtkRenderingContext2DPython_LIB_DEPENDS:STATIC=general;vtkRenderingContext2DPythonD;

//Dependencies for the target
vtkRenderingContext2D_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingContextOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContextOpenGL2;

//Dependencies for the target
vtkRenderingContextOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkRenderingContextOpenGL2;

//Dependencies for the target
vtkRenderingContextOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL2PythonD;

//Dependencies for the target
vtkRenderingContextOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingContext2D;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkImagingCore;general;vtkglew;general;opengl32;general;glu32;

//Dependencies for the target
vtkRenderingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;general;vtkCommonColorPythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingCorePython_LIB_DEPENDS:STATIC=general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkCommonColor;general;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersSources;general;vtksys;

//Dependencies for the target
vtkRenderingFreeTypeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingFreeTypePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingFreeTypePython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingFreeType_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkfreetype;general;vtkCommonDataModel;general;vtkFiltersGeneral;

//Dependencies for the target
vtkRenderingGL2PSOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PSOpenGL2;

//Dependencies for the target
vtkRenderingGL2PSOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingGL2PSOpenGL2;

//Dependencies for the target
vtkRenderingGL2PSOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PSOpenGL2PythonD;

//Dependencies for the target
vtkRenderingGL2PSOpenGL2_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2;general;vtkRenderingOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkgl2ps;general;opengl32;general;glu32;

//Dependencies for the target
vtkRenderingLICOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLICOpenGL2;

//Dependencies for the target
vtkRenderingLICOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingLICOpenGL2;

//Dependencies for the target
vtkRenderingLICOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingLICOpenGL2PythonD;

//Dependencies for the target
vtkRenderingLICOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonSystem;general;vtkIOCore;general;vtkIOLegacy;general;vtkIOXML;general;vtkImagingCore;general;vtkImagingSources;general;vtkRenderingCore;general;vtkglew;general;vtksys;general;opengl32;general;glu32;

//Dependencies for the target
vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD;

//Dependencies for the target
vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersModelingPythonD;general;vtkRenderingLOD;

//Dependencies for the target
vtkRenderingLODPython_LIB_DEPENDS:STATIC=general;vtkRenderingLODPythonD;

//Dependencies for the target
vtkRenderingLOD_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersModeling;

//Dependencies for the target
vtkRenderingLabelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLabel;

//Dependencies for the target
vtkRenderingLabelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingLabel;

//Dependencies for the target
vtkRenderingLabelPython_LIB_DEPENDS:STATIC=general;vtkRenderingLabelPythonD;

//Dependencies for the target
vtkRenderingLabel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral;

//Dependencies for the target
vtkRenderingMatplotlibCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingMatplotlib;

//Dependencies for the target
vtkRenderingMatplotlibPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPythonInterpreterPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingMatplotlib;

//Dependencies for the target
vtkRenderingMatplotlibPython_LIB_DEPENDS:STATIC=general;vtkRenderingMatplotlibPythonD;

//Dependencies for the target
vtkRenderingMatplotlib_LIB_DEPENDS:STATIC=general;vtkPythonInterpreter;general;vtkRenderingFreeType;general;vtkRenderingFreeType;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkImagingCore;general;C:/ProgramData/Miniconda3/libs/python36.lib;general;vtkRenderingCore;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkRenderingOSPRay_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkRenderingSceneGraph;general;vtkRenderingVolume;general;vtkCommonCore;general;vtkIOImage;general;vtkIOLegacy;general;Winmm;general;opengl32;general;glu32;

//Dependencies for the target
vtkRenderingOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOpenGL2;

//Dependencies for the target
vtkRenderingOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkRenderingOpenGL2;

//Dependencies for the target
vtkRenderingOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2PythonD;

//Dependencies for the target
vtkRenderingOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkglew;general;vtksys;general;opengl32;general;glu32;

//Dependencies for the target
vtkRenderingParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallel;

//Dependencies for the target
vtkRenderingParallelLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallelLIC;

//Dependencies for the target
vtkRenderingParallelLICPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelMPIPythonD;general;vtkRenderingLICOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingParallelLIC;

//Dependencies for the target
vtkRenderingParallelLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLICPythonD;

//Dependencies for the target
vtkRenderingParallelLIC_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkRenderingLICOpenGL2;general;vtkRenderingOpenGL2;general;vtkIOLegacy;general;vtkParallelCore;general;vtkRenderingCore;general;opengl32;general;glu32;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;general;C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib;

//Dependencies for the target
vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkRenderingParallel;

//Dependencies for the target
vtkRenderingParallelPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelPythonD;

//Dependencies for the target
vtkRenderingParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkglew;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersParallel;general;vtkIOImage;general;vtkImagingCore;general;vtkParallelCore;general;opengl32;general;glu32;

//Dependencies for the target
vtkRenderingSceneGraph_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR;

//Dependencies for the target
vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingVolumeAMR;

//Dependencies for the target
vtkRenderingVolumeAMRPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMRPythonD;

//Dependencies for the target
vtkRenderingVolumeAMR_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingVolume;general;vtkRenderingVolumeOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingVolumeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolume;

//Dependencies for the target
vtkRenderingVolumeOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeOpenGL2;

//Dependencies for the target
vtkRenderingVolumeOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumePythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingVolumeOpenGL2;

//Dependencies for the target
vtkRenderingVolumeOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGL2PythonD;

//Dependencies for the target
vtkRenderingVolumeOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkImagingMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkRenderingVolume;general;vtkRenderingVolume;general;vtkglew;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys;general;opengl32;general;glu32;

//Dependencies for the target
vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOXMLPythonD;general;vtkImagingCorePythonD;general;vtkRenderingVolume;

//Dependencies for the target
vtkRenderingVolumePython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkRenderingVolume_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOXML;general;vtkImagingCore;

//Dependencies for the target
vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering;

//Dependencies for the target
vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkTestingRendering;

//Dependencies for the target
vtkTestingRenderingPython_LIB_DEPENDS:STATIC=general;vtkTestingRenderingPythonD;

//Dependencies for the target
vtkTestingRendering_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkIOImage;general;vtkImagingCore;general;vtksys;

//Dependencies for the target
vtkUtilitiesPythonInitializer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkWrappingPythonCore;general;vtkWrappingPythonCore;general;vtkCommonCore;

//Dependencies for the target
vtkViewsContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsContext2D;

//Dependencies for the target
vtkViewsContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkViewsCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkViewsContext2D;

//Dependencies for the target
vtkViewsContext2DPython_LIB_DEPENDS:STATIC=general;vtkViewsContext2DPythonD;

//Dependencies for the target
vtkViewsContext2D_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkViewsCore;general;vtkRenderingContext2D;

//Dependencies for the target
vtkViewsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsCore;

//Dependencies for the target
vtkViewsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkInteractionWidgetsPythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingCorePythonD;general;vtkViewsCore;

//Dependencies for the target
vtkViewsCorePython_LIB_DEPENDS:STATIC=general;vtkViewsCorePythonD;

//Dependencies for the target
vtkViewsCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkInteractionWidgets;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkRenderingCore;

//Dependencies for the target
vtkWrappingPythonCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys;general;C:/ProgramData/Miniconda3/libs/python36.lib;

//Dependencies for target
vtkWrappingTools_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkalglib_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkcgns_LIB_DEPENDS:STATIC=general;vtkhdf5_hl;general;vtkhdf5;

//Dependencies for the target
vtkexoIIc_LIB_DEPENDS:STATIC=general;vtkNetCDF;

//Dependencies for target
vtkexpat_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkfreetype_LIB_DEPENDS:STATIC=general;vtkzlib;

//Dependencies for the target
vtkgl2ps_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkpng;general;opengl32;general;glu32;

//Dependencies for the target
vtkglew_LIB_DEPENDS:STATIC=general;opengl32;general;glu32;

//Dependencies for the target
vtkhdf5_LIB_DEPENDS:STATIC=general;vtkzlib;

//Dependencies for the target
vtkhdf5_hl_LIB_DEPENDS:STATIC=general;vtkhdf5;

//Dependencies for target
vtkjpeg_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkjsoncpp_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtklibharu_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/libharu/vtklibharu

//Dependencies for the target
vtklibharu_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkpng;

//Value Computed by CMake
vtklibharu_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/libharu/vtklibharu

//Value Computed by CMake
vtklibxml2_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/libxml2/vtklibxml2

//Dependencies for the target
vtklibxml2_LIB_DEPENDS:STATIC=general;vtkzlib;

//Value Computed by CMake
vtklibxml2_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/libxml2/vtklibxml2

//Dependencies for target
vtklz4_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtkmetaio_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/Utilities/MetaIO/vtkmetaio

//Dependencies for the target
vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib;general;comctl32;general;wsock32;

//Value Computed by CMake
vtkmetaio_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/Utilities/MetaIO/vtkmetaio

//Value Computed by CMake
vtknetcdfcpp_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/netcdfcpp/vtknetcdfcpp

//Dependencies for the target
vtknetcdfcpp_LIB_DEPENDS:STATIC=general;vtkNetCDF;

//Value Computed by CMake
vtknetcdfcpp_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/netcdfcpp/vtknetcdfcpp

//Dependencies for target
vtkoggtheora_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkpng_LIB_DEPENDS:STATIC=general;vtkzlib;

//Dependencies for target
vtkpugixml_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtksys_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/Utilities/KWSys/vtksys

//Dependencies for the target
vtksys_LIB_DEPENDS:STATIC=general;ws2_32;general;Psapi;

//Value Computed by CMake
vtksys_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/Utilities/KWSys/vtksys

//Dependencies for the target
vtktiff_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkjpeg;

//Dependencies for the target
vtkxdmf2_LIB_DEPENDS:STATIC=general;vtklibxml2;general;vtkhdf5_hl;general;vtkhdf5;

//Dependencies for target
vtkzlib_LIB_DEPENDS:STATIC=

//Value Computed by CMake
xdmf2_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/xdmf2/vtkxdmf2

//Value Computed by CMake
xdmf2_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/xdmf2/vtkxdmf2

//Value Computed by CMake
zlib_BINARY_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/build/VTK/ThirdParty/zlib/vtkzlib

//Value Computed by CMake
zlib_SOURCE_DIR:STATIC=C:/workspace/pv/ParaView-v5.4.1/VTK/ThirdParty/zlib/vtkzlib


########################
# INTERNAL cache entries
########################

ALGLIB_SHARED_LIB:INTERNAL=ON
//Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN
ARCH_TO_BUILD:INTERNAL=Windows
//CXX test 
BOOL_NOTDEFINED:INTERNAL=
//ADVANCED property for variable: BUILD_USER_DEFINED_LIBS
BUILD_USER_DEFINED_LIBS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Boost_DIR
Boost_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Boost_INCLUDE_DIR
Boost_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_ANSI_FOR_SCOPE:INTERNAL=TRUE
//Have include iostream
CMAKE_ANSI_STREAM_HEADERS:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=c:/workspace/pv/ParaView-v5.4.1/build
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=10
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=C:/CMake/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=C:/CMake/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=C:/CMake/bin/ctest.exe
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_STANDARD_LIBRARIES
CMAKE_CXX_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Visual Studio 15 2017 Win64
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Result of TRY_COMPILE
CMAKE_HAS_ANSI_STRING_STREAM:INTERNAL=TRUE
//Is X11 around.
CMAKE_HAS_X:INTERNAL=
//Have include limits.h
CMAKE_HAVE_LIMITS_H:INTERNAL=1
//Have include pthread.h
CMAKE_HAVE_PTHREAD_H:INTERNAL=
//Have includes sys/types.h;sys/prctl.h
CMAKE_HAVE_SYS_PRCTL_H:INTERNAL=
//Have include unistd.h
CMAKE_HAVE_UNISTD_H:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=C:/workspace/pv/ParaView-v5.4.1
//ADVANCED property for variable: CMAKE_HP_PTHREADS
CMAKE_HP_PTHREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_BINDIR
CMAKE_INSTALL_BINDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_DATADIR
CMAKE_INSTALL_DATADIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_DATAROOTDIR
CMAKE_INSTALL_DATAROOTDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_DOCDIR
CMAKE_INSTALL_DOCDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_INCLUDEDIR
CMAKE_INSTALL_INCLUDEDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_INFODIR
CMAKE_INSTALL_INFODIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LIBDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_LIBEXECDIR
CMAKE_INSTALL_LIBEXECDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_LOCALEDIR
CMAKE_INSTALL_LOCALEDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_LOCALSTATEDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_MANDIR
CMAKE_INSTALL_MANDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_OLDINCLUDEDIR
CMAKE_INSTALL_OLDINCLUDEDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_RUNSTATEDIR
CMAKE_INSTALL_RUNSTATEDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_SBINDIR
CMAKE_INSTALL_SBINDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_SHAREDSTATEDIR
CMAKE_INSTALL_SHAREDSTATEDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_INSTALL_SYSCONFDIR
CMAKE_INSTALL_SYSCONFDIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Does the compiler support ansi for scope.
CMAKE_NO_ANSI_FOR_SCOPE:INTERNAL=0
//Does the compiler support headers like iostream.
CMAKE_NO_ANSI_STREAM_HEADERS:INTERNAL=0
//Does the compiler support sstream
CMAKE_NO_ANSI_STRING_STREAM:INTERNAL=0
//Does the compiler support std::.
CMAKE_NO_STD_NAMESPACE:INTERNAL=0
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=247
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_DEBUG
CMAKE_RC_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_MINSIZEREL
CMAKE_RC_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELEASE
CMAKE_RC_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELWITHDEBINFO
CMAKE_RC_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Test Support for 64 bit file systems
CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=C:/CMake/share/cmake-3.10
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(char)
CMAKE_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
CMAKE_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
CMAKE_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
CMAKE_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
CMAKE_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(short)
CMAKE_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(unsigned short)
CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(void*)
CMAKE_SIZEOF_VOID_P:INTERNAL=8
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_STD_NAMESPACE:INTERNAL=TRUE
//ADVANCED property for variable: CMAKE_THREAD_LIBS
CMAKE_THREAD_LIBS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_USE_PTHREADS
CMAKE_USE_PTHREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_USE_SPROC
CMAKE_USE_SPROC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_USE_WIN32_THREADS
CMAKE_USE_WIN32_THREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Result of TEST_BIG_ENDIAN
CMAKE_WORDS_BIGENDIAN:INTERNAL=0
//ADVANCED property for variable: CMAKE_X_CFLAGS
CMAKE_X_CFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_X_LIBS
CMAKE_X_LIBS-ADVANCED:INTERNAL=1
//Test COMPILER_HAS_DEPRECATED
COMPILER_HAS_DEPRECATED:INTERNAL=1
//Test COMPILER_HAS_DEPRECATED_ATTR
COMPILER_HAS_DEPRECATED_ATTR:INTERNAL=
//ADVANCED property for variable: CPACK_BINARY_7Z
CPACK_BINARY_7Z-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_IFW
CPACK_BINARY_IFW-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_NSIS
CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_WIX
CPACK_BINARY_WIX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_ZIP
CPACK_BINARY_ZIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_7Z
CPACK_SOURCE_7Z-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_ZIP
CPACK_SOURCE_ZIP-ADVANCED:INTERNAL=1
//Test C_HAS_inline
C_HAS_inline:INTERNAL=1
//ADVANCED property for variable: EXECUTABLE_OUTPUT_PATH
EXECUTABLE_OUTPUT_PATH-ADVANCED:INTERNAL=1
EXECUTABLE_OUTPUT_PATH:INTERNAL=C:/workspace/pv/ParaView-v5.4.1/build/ThirdParty/protobuf/vtkprotobuf/bin
//ADVANCED property for variable: EXODUSII_DISABLE_COMPILER_WARNINGS
EXODUSII_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//Have include malloc.h
EX_HAVE_MALLOC_H:INTERNAL=1
//ADVANCED property for variable: ExternalData_URL_TEMPLATES
ExternalData_URL_TEMPLATES-ADVANCED:INTERNAL=1
//Details about finding Git
FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[C:/Git/cmd/git.exe][v2.15.1.windows.2()]
//Details about finding MPI_C
FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib][C:/Program Files (x86)/Microsoft SDKs/MPI/include][v()]
//Details about finding MPI_CXX
FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[C:/Program Files (x86)/Microsoft SDKs/MPI/lib/x64/msmpi.lib][C:/Program Files (x86)/Microsoft SDKs/MPI/include][v()]
//Details about finding OpenGL
FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[opengl32][c ][v()]
//Details about finding OpenMP
FIND_PACKAGE_MESSAGE_DETAILS_OpenMP:INTERNAL=[/openmp][/openmp][v()]
//Details about finding PythonInterp
FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[C:/ProgramData/Miniconda3/python.exe][v3.6.3()]
//Details about finding PythonLibs
FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[C:/ProgramData/Miniconda3/libs/python36.lib][C:/ProgramData/Miniconda3/include][v()]
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
//ADVANCED property for variable: GIT_EXECUTABLE
GIT_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS
GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS-ADVANCED:INTERNAL=1
//Define if your system generates wrong code for log2 routine
H5_BAD_LOG2_CODE_GENERATED:INTERNAL=0
//Checking IF overflows normally converting floating-point to integer
// values
H5_FP_TO_INTEGER_OVERFLOW_WORKS:INTERNAL=1
//Result of TRY_COMPILE
H5_FP_TO_INTEGER_OVERFLOW_WORKS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_INTEGER_OVERFLOW_WORKS_RUN:INTERNAL=0
//Checking IF accurately roundup converting floating-point to unsigned
// long long values
H5_FP_TO_ULLONG_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_FP_TO_ULLONG_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_ULLONG_ACCURATE_RUN:INTERNAL=0
//Checking IF right maximum converting floating-point to unsigned
// long long values
H5_FP_TO_ULLONG_RIGHT_MAXIMUM:INTERNAL=1
//Result of TRY_COMPILE
H5_FP_TO_ULLONG_RIGHT_MAXIMUM_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_ULLONG_RIGHT_MAXIMUM_RUN:INTERNAL=0
//Have function alarm
H5_HAVE_ALARM:INTERNAL=
//Have symbol tzname
H5_HAVE_DECL_TZNAME:INTERNAL=
//Have function difftime
H5_HAVE_DIFFTIME:INTERNAL=1
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;dirent.h
H5_HAVE_DIRENT_H:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h;time.h;stdlib.h;memory.h;dlfcn.h
H5_HAVE_DLFCN_H:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;features.h
H5_HAVE_FEATURES_H:INTERNAL=
//Have function fork
H5_HAVE_FORK:INTERNAL=
//Have function frexpf
H5_HAVE_FREXPF:INTERNAL=
//Have function frexpl
H5_HAVE_FREXPL:INTERNAL=
//Have function getpwuid
H5_HAVE_GETPWUID:INTERNAL=
//Have function getrusage
H5_HAVE_GETRUSAGE:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;globus/common.h
H5_HAVE_GLOBUS_COMMON_H:INTERNAL=
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h;time.h;stdlib.h;memory.h;inttypes.h
H5_HAVE_INTTYPES_H:INTERNAL=1
//Test InitOnceExecuteOnce
H5_HAVE_IOEO:INTERNAL=1
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h
H5_HAVE_IO_H:INTERNAL=1
//Have library nsl;
H5_HAVE_LIBNSL:INTERNAL=
//Have library socket;
H5_HAVE_LIBSOCKET:INTERNAL=
//Have library ucb;
H5_HAVE_LIBUCB:INTERNAL=
//Have function lstat
H5_HAVE_LSTAT:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;mach/mach_time.h
H5_HAVE_MACH_MACH_TIME_H:INTERNAL=
//Have symbol sigsetjmp
H5_HAVE_MACRO_SIGSETJMP:INTERNAL=
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h;time.h;stdlib.h;memory.h
H5_HAVE_MEMORY_H:INTERNAL=1
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h;time.h;stdlib.h;memory.h;inttypes.h;netinet/in.h
H5_HAVE_NETINET_IN_H:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;pdb.h
H5_HAVE_PDB_H:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;pthread.h
H5_HAVE_PTHREAD_H:INTERNAL=
//Have function random
H5_HAVE_RANDOM:INTERNAL=
//Have function rand_r
H5_HAVE_RAND_R:INTERNAL=
//Have function setjmp
H5_HAVE_SETJMP:INTERNAL=1
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h
H5_HAVE_SETJMP_H:INTERNAL=1
//Have function setsysinfo
H5_HAVE_SETSYSINFO:INTERNAL=
//Have function sigaction
H5_HAVE_SIGACTION:INTERNAL=
//Have function siglongjmp
H5_HAVE_SIGLONGJMP:INTERNAL=
//Have function signal
H5_HAVE_SIGNAL:INTERNAL=1
//Have function sigprocmask
H5_HAVE_SIGPROCMASK:INTERNAL=
//Have function sigsetjmp
H5_HAVE_SIGSETJMP:INTERNAL=
//Have function snprintf
H5_HAVE_SNPRINTF:INTERNAL=
//Have function srandom
H5_HAVE_SRANDOM:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;srbclient.h
H5_HAVE_SRBCLIENT_H:INTERNAL=
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h
H5_HAVE_STDINT_H:INTERNAL=1
//Have include stdint.h
H5_HAVE_STDINT_H_CXX:INTERNAL=1
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h;time.h;stdlib.h
H5_HAVE_STDLIB_H:INTERNAL=1
//Have includes windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h;strings.h
H5_HAVE_STRINGS_H:INTERNAL=
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h
H5_HAVE_STRING_H:INTERNAL=1
//Have function symlink
H5_HAVE_SYMLINK:INTERNAL=
//Have includes windows.h;sys/ioctl.h
H5_HAVE_SYS_IOCTL_H:INTERNAL=
H5_HAVE_SYS_PROC_H:INTERNAL=
//Have includes windows.h;sys/resource.h
H5_HAVE_SYS_RESOURCE_H:INTERNAL=
//Have includes windows.h;sys/stat.h;sys/socket.h
H5_HAVE_SYS_SOCKET_H:INTERNAL=
H5_HAVE_SYS_SYSINFO_H:INTERNAL=
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h
H5_HAVE_SYS_TIMEB_H:INTERNAL=1
//Have includes windows.h;sys/time.h
H5_HAVE_SYS_TIME_H:INTERNAL=
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h;sys/timeb.h;string.h;time.h
H5_HAVE_TIME_H:INTERNAL=1
//Have includes windows.h;unistd.h
H5_HAVE_UNISTD_H:INTERNAL=
//Have function vasprintf
H5_HAVE_VASPRINTF:INTERNAL=
//Have function vsnprintf
H5_HAVE_VSNPRINTF:INTERNAL=
//Have function waitpid
H5_HAVE_WAITPID:INTERNAL=
//Have include windows.h;sys/stat.h;sys/types.h;stddef.h;setjmp.h;stdint.h;io.h;winsock2.h
H5_HAVE_WINSOCK2_H:INTERNAL=1
//Other test 
H5_INLINE_TEST___inline:INTERNAL=1
//Other test 
H5_INLINE_TEST___inline__:INTERNAL=
//Other test 
H5_INLINE_TEST_inline:INTERNAL=1
//checking IF accurately converting from integers to long double
H5_INTEGER_TO_LDOUBLE_ACCURATE:INTERNAL=1
//checking IF converting from long double to integers is accurate
H5_LDOUBLE_TO_INTEGER_ACCURATE:INTERNAL=1
//Checking IF correctly converting long double to (unsigned) long
// long values
H5_LDOUBLE_TO_LLONG_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_LLONG_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_LLONG_ACCURATE_RUN:INTERNAL=0
//Define if your system converts long double to (unsigned) long
// values with special algorithm
H5_LDOUBLE_TO_LONG_SPECIAL:INTERNAL=0
//Checking IF correctly converting long double to unsigned int
// values
H5_LDOUBLE_TO_UINT_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_UINT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_UINT_ACCURATE_RUN:INTERNAL=0
//Use Legacy Names for Libraries and Programs
H5_LEGACY_NAMING:INTERNAL=ON
//Checking IF compiling long long to floating-point typecasts work
H5_LLONG_TO_FP_CAST_WORKS:INTERNAL=1
//Checking IF correctly converting (unsigned) long long to long
// double values
H5_LLONG_TO_LDOUBLE_CORRECT:INTERNAL=1
//Result of TRY_COMPILE
H5_LLONG_TO_LDOUBLE_CORRECT_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LLONG_TO_LDOUBLE_CORRECT_RUN:INTERNAL=0
//Define if your system can convert (unsigned) long to long double
// values with special algorithm
H5_LONG_TO_LDOUBLE_SPECIAL:INTERNAL=0
//Checking IF alignment restrictions are strictly enforced
H5_NO_ALIGNMENT_RESTRICTIONS:INTERNAL=1
//Result of TRY_COMPILE
H5_NO_ALIGNMENT_RESTRICTIONS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_NO_ALIGNMENT_RESTRICTIONS_RUN:INTERNAL=0
//CXX test 
H5_NO_NAMESPACE:INTERNAL=
//CXX test 
H5_NO_STD:INTERNAL=
//Width for printf for type `long long' or `__int64', us. `ll
H5_PRINTF_LL_WIDTH:INTERNAL="I64"
//CHECK_TYPE_SIZE: sizeof(char)
H5_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
H5_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
H5_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
H5_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int16_t)
H5_SIZEOF_INT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int32_t)
H5_SIZEOF_INT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int64_t)
H5_SIZEOF_INT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int8_t)
H5_SIZEOF_INT8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int_fast16_t)
H5_SIZEOF_INT_FAST16_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int_fast32_t)
H5_SIZEOF_INT_FAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int_fast64_t)
H5_SIZEOF_INT_FAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_fast8_t)
H5_SIZEOF_INT_FAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int_least16_t)
H5_SIZEOF_INT_LEAST16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int_least32_t)
H5_SIZEOF_INT_LEAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int_least64_t)
H5_SIZEOF_INT_LEAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_least8_t)
H5_SIZEOF_INT_LEAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(long)
H5_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long double)
H5_SIZEOF_LONG_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long long)
H5_SIZEOF_LONG_LONG:INTERNAL=8
//SizeOf for off64_t
H5_SIZEOF_OFF64_T:INTERNAL=0
//CHECK_TYPE_SIZE: sizeof(off_t)
H5_SIZEOF_OFF_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(short)
H5_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(size_t)
H5_SIZEOF_SIZE_T:INTERNAL=8
//SizeOf for ssize_t
H5_SIZEOF_SSIZE_T:INTERNAL=0
//CHECK_TYPE_SIZE: sizeof(uint16_t)
H5_SIZEOF_UINT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint32_t)
H5_SIZEOF_UINT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint64_t)
H5_SIZEOF_UINT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint8_t)
H5_SIZEOF_UINT8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(uint_fast16_t)
H5_SIZEOF_UINT_FAST16_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint_fast32_t)
H5_SIZEOF_UINT_FAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint_fast64_t)
H5_SIZEOF_UINT_FAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_fast8_t)
H5_SIZEOF_UINT_FAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(uint_least16_t)
H5_SIZEOF_UINT_LEAST16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint_least32_t)
H5_SIZEOF_UINT_LEAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint_least64_t)
H5_SIZEOF_UINT_LEAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_least8_t)
H5_SIZEOF_UINT_LEAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(unsigned)
H5_SIZEOF_UNSIGNED:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(__int64)
H5_SIZEOF___INT64:INTERNAL=8
//Other test 
H5_STDC_HEADERS:INTERNAL=1
//Checking IF compiling unsigned long long to floating-point typecasts
// work
H5_ULLONG_TO_FP_CAST_WORKS:INTERNAL=1
//Checking IF accurately converting unsigned long to float values
H5_ULONG_TO_FLOAT_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_ULONG_TO_FLOAT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_ULONG_TO_FLOAT_ACCURATE_RUN:INTERNAL=0
//Have symbol alloca
HAVE_ALLOCA:INTERNAL=
//Have includes ;alloca.h
HAVE_ALLOCA_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ansidecl.h
HAVE_ANSIDECL_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;arpa/inet.h
HAVE_ARPA_INET_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;arpa/nameser.h
HAVE_ARPA_NAMESER_H:INTERNAL=
//Have include assert.h
HAVE_ASSERT_H:INTERNAL=1
//Have function bcopy
HAVE_BCOPY:INTERNAL=
//Result of TRY_COMPILE
HAVE_CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_VOID_P:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_WORDS_BIGENDIAN:INTERNAL=TRUE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h
HAVE_CTYPE_H:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;dirent.h
HAVE_DIRENT_H:INTERNAL=
//Have include dlfcn.h
HAVE_DLFCN_H:INTERNAL=
//Have library 
HAVE_DLOPEN:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;dl.h
HAVE_DL_H:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h
HAVE_ERRNO_H:INTERNAL=1
//Have include fcntl.h
HAVE_FCNTL_H:INTERNAL=1
//Have include fenv.h
HAVE_FENV_H:INTERNAL=1
//Have symbol finite
HAVE_FINITE:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h
HAVE_FLOAT_H:INTERNAL=1
//Have function floor
HAVE_FLOOR:INTERNAL=1
//Have symbol fpclass
HAVE_FPCLASS:INTERNAL=
//Have symbol fprintf
HAVE_FPRINTF:INTERNAL=1
//Have symbol fp_class
HAVE_FP_CLASS:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;fp_class.h
HAVE_FP_CLASS_H:INTERNAL=
//Have function fseeko
HAVE_FSEEKO:INTERNAL=
//Have symbol ftime
HAVE_FTIME:INTERNAL=1
//NetCDF test 
HAVE_FTRUNCATE:INTERNAL=
//Result of TRY_COMPILE
HAVE_GETADDRINFO_COMPILED:INTERNAL=FALSE
//Have function getopt
HAVE_GETOPT:INTERNAL=
//Have function getpagesize
HAVE_GETPAGESIZE:INTERNAL=
//Have symbol gettimeofday
HAVE_GETTIMEOFDAY:INTERNAL=
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_OFF64_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_OFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SSIZE_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UNSIGNED:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF___INT64:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_VOID_P:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF___INT64:INTERNAL=TRUE
//ADVANCED property for variable: HAVE_IEEEFP
HAVE_IEEEFP-ADVANCED:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;ieeefp.h
HAVE_IEEEFP_H:INTERNAL=
//Have include inttypes.h
HAVE_INTTYPES_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_IOEO_COMPILED:INTERNAL=TRUE
//Result of TRY_RUN
HAVE_IOEO_EXITCODE:INTERNAL=0
//Have include io.h
HAVE_IO_H:INTERNAL=1
//Have function isascii
HAVE_ISASCII:INTERNAL=
//Have function jbg_newlen
HAVE_JBG_NEWLEN:INTERNAL=
//Test HAVE_LD_VERSION_SCRIPT
HAVE_LD_VERSION_SCRIPT:INTERNAL=
//Have function lfind
HAVE_LFIND:INTERNAL=1
//Have library dl;
HAVE_LIBDL:INTERNAL=
//Have include limits.h
HAVE_LIMITS_H:INTERNAL=1
//Have symbol localtime
HAVE_LOCALTIME:INTERNAL=1
//Have include malloc.h
HAVE_MALLOC_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h
HAVE_MATH_H:INTERNAL=1
//Have symbol memmove
HAVE_MEMMOVE:INTERNAL=1
//Have include memory.h
HAVE_MEMORY_H:INTERNAL=1
//Have function memset
HAVE_MEMSET:INTERNAL=1
//Have function mmap
HAVE_MMAP:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;nan.h
HAVE_NAN_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;ndir.h
HAVE_NDIR_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;netdb.h
HAVE_NETDB_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;netinet/in.h
HAVE_NETINET_IN_H:INTERNAL=
//Result of TRY_COMPILE
HAVE_OFF64_T:INTERNAL=FALSE
//Have function pow
HAVE_POW:INTERNAL=1
//Have symbol printf
HAVE_PRINTF:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;pthread.h
HAVE_PTHREAD_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;resolv.h
HAVE_RESOLV_H:INTERNAL=
//Have include search.h
HAVE_SEARCH_H:INTERNAL=1
//Have function setmode
HAVE_SETMODE:INTERNAL=1
//Have library dld;
HAVE_SHLLOAD:INTERNAL=
//Have symbol signal
HAVE_SIGNAL:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h
HAVE_SIGNAL_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_OFF64_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF_OFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_PTRDIFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIGNED_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIGNED_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIGNED_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIGNED_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SSIZE_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF_UCHAR:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF_UNSIGNED_CHAR_P:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_UNSIGNED_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_UNSIGNED_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_VOID_P:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF__BOOL:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF___INT64:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZE_OF_LONG:INTERNAL=TRUE
//Test HAVE_SNPRINTF
HAVE_SNPRINTF:INTERNAL=1
//support for socklen_t
HAVE_SOCKLEN_T:INTERNAL=0
//Result of TRY_COMPILE
HAVE_SOCKLEN_T_COMPILED:INTERNAL=FALSE
//Have symbol sprintf
HAVE_SPRINTF:INTERNAL=1
//Have function sqrt
HAVE_SQRT:INTERNAL=1
//Have symbol sscanf
HAVE_SSCANF:INTERNAL=1
//Have symbol stat
HAVE_STAT:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;stdarg.h
HAVE_STDARG_H:INTERNAL=1
//Have include stdlib.h;sys/types.h;sys/stat.h;fcntl.h;stdio.h;string.h;stddef.h;stdint.h;inttypes.h;stdbool.h
HAVE_STDBOOL_H:INTERNAL=1
//Have include stddef.h
HAVE_STDDEF_H:INTERNAL=1
//Have include stdint.h
HAVE_STDINT_H:INTERNAL=1
//Have include ;stdio.h
HAVE_STDIO_H:INTERNAL=1
//Have include stdlib.h
HAVE_STDLIB_H:INTERNAL=1
//Have function strcasecmp
HAVE_STRCASECMP:INTERNAL=
//Have function strchr
HAVE_STRCHR:INTERNAL=1
//Have symbol strdup
HAVE_STRDUP:INTERNAL=1
//Have symbol strerror
HAVE_STRERROR:INTERNAL=1
//Have symbol strftime
HAVE_STRFTIME:INTERNAL=1
//Have include strings.h
HAVE_STRINGS_H:INTERNAL=
//Have include string.h
HAVE_STRING_H:INTERNAL=1
//Have symbol strndup
HAVE_STRNDUP:INTERNAL=
//Have function strrchr
HAVE_STRRCHR:INTERNAL=1
//Have function strstr
HAVE_STRSTR:INTERNAL=1
//Have function strtol
HAVE_STRTOL:INTERNAL=1
//Have function strtoll
HAVE_STRTOLL:INTERNAL=1
//Have function strtol
HAVE_STRTOUL:INTERNAL=1
//Have function strtoull
HAVE_STRTOULL:INTERNAL=1
//NetCDF test 
HAVE_ST_BLKSIZE:INTERNAL=
//Result of TRY_COMPILE
HAVE_SYS_DIR_H_COMPILED:INTERNAL=FALSE
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;stdarg.h;sys/mman.h
HAVE_SYS_MMAN_H:INTERNAL=
//Result of TRY_COMPILE
HAVE_SYS_NDIR_H_COMPILED:INTERNAL=FALSE
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;sys/select.h
HAVE_SYS_SELECT_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;sys/socket.h
HAVE_SYS_SOCKET_H:INTERNAL=
//Have include sys/stat.h
HAVE_SYS_STAT_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;stdarg.h;sys/timeb.h
HAVE_SYS_TIMEB_H:INTERNAL=1
//Have include sys/time.h
HAVE_SYS_TIME_H:INTERNAL=
//Have include sys/types.h
HAVE_SYS_TYPES_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h
HAVE_TIME_H:INTERNAL=1
//Have include unistd.h
HAVE_UNISTD_H:INTERNAL=
//Result of TRY_COMPILE
HAVE_VA_COPY_COMPILED:INTERNAL=TRUE
//Have symbol vfprintf
HAVE_VFPRINTF:INTERNAL=1
//Have symbol vsnprintf
HAVE_VSNPRINTF:INTERNAL=1
//Have symbol vsprintf
HAVE_VSPRINTF:INTERNAL=1
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_UINT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_UINT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_U_INT16_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_U_INT32_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_WORDS_BIGENDIAN:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_XDMF_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_XDMF_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_XDMF_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_XDMF_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_XDMF_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_XDMF_SIZEOF_SHORT:INTERNAL=TRUE
//Have symbol _stat
HAVE__STAT:INTERNAL=1
//Result of TRY_COMPILE
HAVE___VA_COPY_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_bigendian:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_int16:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_int32:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_int8:INTERNAL=FALSE
//Allow External Library Building (NO SVN TGZ)
HDF5_ALLOW_EXTERNAL_SUPPORT:INTERNAL=OFF
//Build HDF5 C++ Library
HDF5_BUILD_CPP_LIB:INTERNAL=OFF
//Build HIGH Level HDF5 Library
HDF5_BUILD_HL_LIB:INTERNAL=ON
//ADVANCED property for variable: HDF5_BUILD_STATIC_EXECS
HDF5_BUILD_STATIC_EXECS-ADVANCED:INTERNAL=1
//Disable compiler warnings
HDF5_DISABLE_COMPILER_WARNINGS:INTERNAL=ON
//ADVANCED property for variable: HDF5_ENABLE_ALL_WARNINGS
HDF5_ENABLE_ALL_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_CODESTACK
HDF5_ENABLE_CODESTACK-ADVANCED:INTERNAL=1
//Enable the function stack tracing (for developer debugging).
HDF5_ENABLE_CODESTACK:INTERNAL=OFF
//Enable code coverage for Libraries and Programs
HDF5_ENABLE_COVERAGE:INTERNAL=OFF
//ADVANCED property for variable: HDF5_ENABLE_DEBUG_APIS
HDF5_ENABLE_DEBUG_APIS-ADVANCED:INTERNAL=1
//Enable deprecated public API symbols
HDF5_ENABLE_DEPRECATED_SYMBOLS:INTERNAL=ON
//ADVANCED property for variable: HDF5_ENABLE_EMBEDDED_LIBINFO
HDF5_ENABLE_EMBEDDED_LIBINFO-ADVANCED:INTERNAL=1
//Enable GPFS hints for the MPI/POSIX file driver
HDF5_ENABLE_GPFS:INTERNAL=OFF
//ADVANCED property for variable: HDF5_ENABLE_GROUPFIVE_WARNINGS
HDF5_ENABLE_GROUPFIVE_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_GROUPFOUR_WARNINGS
HDF5_ENABLE_GROUPFOUR_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_GROUPONE_WARNINGS
HDF5_ENABLE_GROUPONE_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_GROUPTHREE_WARNINGS
HDF5_ENABLE_GROUPTHREE_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_GROUPTWO_WARNINGS
HDF5_ENABLE_GROUPTWO_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_GROUPZERO_WARNINGS
HDF5_ENABLE_GROUPZERO_WARNINGS-ADVANCED:INTERNAL=1
//Enable datasets larger than memory
HDF5_ENABLE_HSIZET:INTERNAL=ON
//Enable support for large (64-bit) files on Linux.
HDF5_ENABLE_LARGE_FILE:INTERNAL=ON
//Enable parallel build (requires MPI)
HDF5_ENABLE_PARALLEL:INTERNAL=OFF
//Use SZip Filter
HDF5_ENABLE_SZIP_SUPPORT:INTERNAL=OFF
//Enable thread-safety
HDF5_ENABLE_THREADSAFE:INTERNAL=OFF
//Enable API tracing capability
HDF5_ENABLE_TRACE:INTERNAL=OFF
//Indicate that a memory checker is used
HDF5_ENABLE_USING_MEMCHECKER:INTERNAL=OFF
//Enable Zlib Filters
HDF5_ENABLE_Z_LIB_SUPPORT:INTERNAL=ON
//ADVANCED property for variable: HDF5_Enable_Clear_File_Buffers
HDF5_Enable_Clear_File_Buffers-ADVANCED:INTERNAL=1
//Securely clear file buffers before writing to file
HDF5_Enable_Clear_File_Buffers:INTERNAL=ON
//Instrument The library
HDF5_Enable_Instrument:INTERNAL=OFF
//Used to pass variables between directories
HDF5_LIBRARIES_TO_EXPORT:INTERNAL=vtkhdf5;vtkhdf5_hl
//ADVANCED property for variable: HDF5_METADATA_TRACE_FILE
HDF5_METADATA_TRACE_FILE-ADVANCED:INTERNAL=1
//Enable metadata trace file collection
HDF5_METADATA_TRACE_FILE:INTERNAL=OFF
//ADVANCED property for variable: HDF5_NO_PACKAGES
HDF5_NO_PACKAGES-ADVANCED:INTERNAL=1
//CPACK - include external libraries
HDF5_PACKAGE_EXTLIBS:INTERNAL=OFF
//ADVANCED property for variable: HDF5_PACK_EXAMPLES
HDF5_PACK_EXAMPLES-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
HDF5_PRINTF_LL_TEST_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
HDF5_PRINTF_LL_TEST_RUN:INTERNAL=0
//ADVANCED property for variable: HDF5_STRICT_FORMAT_CHECKS
HDF5_STRICT_FORMAT_CHECKS-ADVANCED:INTERNAL=1
//Whether to perform strict file format checks
HDF5_STRICT_FORMAT_CHECKS:INTERNAL=OFF
//Use the HDF5 1.6.x API by default
HDF5_USE_16_API_DEFAULT:INTERNAL=OFF
//Use the FLETCHER32 Filter
HDF5_USE_FILTER_FLETCHER32:INTERNAL=ON
//Use the NBIT Filter
HDF5_USE_FILTER_NBIT:INTERNAL=ON
//Use the SCALEOFFSET Filter
HDF5_USE_FILTER_SCALEOFFSET:INTERNAL=ON
//Use the SHUFFLE Filter
HDF5_USE_FILTER_SHUFFLE:INTERNAL=ON
//ADVANCED property for variable: HDF5_USE_FOLDERS
HDF5_USE_FOLDERS-ADVANCED:INTERNAL=1
//Use the PACKED BITS feature in h5dump
HDF5_USE_H5DUMP_PACKED_BITS:INTERNAL=ON
//ADVANCED property for variable: HDF5_WANT_DATA_ACCURACY
HDF5_WANT_DATA_ACCURACY-ADVANCED:INTERNAL=1
//IF data accuracy is guaranteed during data conversions
HDF5_WANT_DATA_ACCURACY:INTERNAL=ON
//ADVANCED property for variable: HDF5_WANT_DCONV_EXCEPTION
HDF5_WANT_DCONV_EXCEPTION-ADVANCED:INTERNAL=1
//exception handling functions is checked during data conversions
HDF5_WANT_DCONV_EXCEPTION:INTERNAL=ON
//ADVANCED property for variable: HOST_BIG_ENDIAN
HOST_BIG_ENDIAN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HOST_FILLORDER
HOST_FILLORDER-ADVANCED:INTERNAL=1
ICET_INSTALL_TARGETS:INTERNAL=IceTCore;IceTMPI;IceTGL
//ADVANCED property for variable: ICET_MAGIC_K
ICET_MAGIC_K-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_MAX_IMAGE_SPLIT
ICET_MAX_IMAGE_SPLIT-ADVANCED:INTERNAL=1
//This is set from VTK_MPIRUN_EXE.
ICET_MPIRUN_EXE:INTERNAL=C:/Program Files/Microsoft MPI/Bin/mpiexec.exe
//ADVANCED property for variable: ICET_MPI_MAX_NUMPROCS
ICET_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//This is set from VTK_MPI_MAX_NUMPROCS.
ICET_MPI_MAX_NUMPROCS:INTERNAL=2
//This is set from a combination of VTK_MPI_PRENUMPROC_FLAGS and
// VTK_MPI_NUMPROC_FLAG
ICET_MPI_NUMPROC_FLAG:INTERNAL=;-np
//This is set from VTK_MPI_POSTFLAGS.
ICET_MPI_POSTFLAGS:INTERNAL=
//This is set from VTK_MPI_PREFLAGS.
ICET_MPI_PREFLAGS:INTERNAL=
//CHECK_TYPE_SIZE: sizeof(char)
ICET_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
ICET_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
ICET_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
ICET_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
ICET_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
ICET_SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
ICET_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(void*)
ICET_SIZEOF_VOID_P:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(__int64)
ICET_SIZEOF___INT64:INTERNAL=8
//ADVANCED property for variable: ICET_USE_MPE
ICET_USE_MPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_USE_MPI
ICET_USE_MPI-ADVANCED:INTERNAL=1
//Use OffScreen rendering through EGL
ICET_USE_OFFSCREEN_EGL:INTERNAL=OFF
//ADVANCED property for variable: ICET_USE_OPENGL
ICET_USE_OPENGL-ADVANCED:INTERNAL=1
//Use OffScreen Mesa
ICET_USE_OSMESA:INTERNAL=OFF
//Result of TRY_COMPILE
INLINE_TEST___inline:INTERNAL=TRUE
//Result of TRY_COMPILE
INLINE_TEST___inline__:INTERNAL=FALSE
//Result of TRY_COMPILE
INLINE_TEST_inline:INTERNAL=TRUE
//ADVANCED property for variable: INSTALL_BIN_DIR
INSTALL_BIN_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: INSTALL_INC_DIR
INSTALL_INC_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: INSTALL_LIB_DIR
INSTALL_LIB_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: INSTALL_MAN_DIR
INSTALL_MAN_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: INSTALL_PKGCONFIG_DIR
INSTALL_PKGCONFIG_DIR-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ATOLL_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ATOL_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CSTDIO_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ENVIRON_IN_STDLIB_H_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_EXT_STDIO_FILEBUF_H_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_LONG_LONG_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_RLIMIT64_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_SETENV_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UNSETENV_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UTIMENSAT_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UTIMES_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS__ATOI64_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS___INT64_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_SAME_LONG_AND___INT64_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_SAME_LONG_LONG_AND___INT64_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_STAT_HAS_ST_MTIMESPEC_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_STAT_HAS_ST_MTIM_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_C_HAS_PTRDIFF_T_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_C_HAS_SSIZE_T_COMPILED:INTERNAL=FALSE
//Checking for Large File Support failed to compile.
KWSYS_LFS_WORKS:INTERNAL=-1
//Result of TRY_COMPILE
KWSYS_LFS_WORKS_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_STL_HAS_WSTRING_COMPILED:INTERNAL=TRUE
//Have includes sys/types.h;ifaddrs.h
KWSYS_SYS_HAS_IFADDRS_H:INTERNAL=
//Have symbol GetProcessMemoryInfo
KWSYS_SYS_HAS_PSAPI:INTERNAL=1
//Have includes dlfcn.h
LIBHPDF_HAVE_DLFCN_H:INTERNAL=
//Have include inttypes.h
LIBHPDF_HAVE_INTTYPES_H:INTERNAL=1
//Have include memory.h
LIBHPDF_HAVE_MEMORY_H:INTERNAL=1
//Have include stdint.h
LIBHPDF_HAVE_STDINT_H:INTERNAL=1
//Have include stdlib.h
LIBHPDF_HAVE_STDLIB_H:INTERNAL=1
//Have includes strings.h
LIBHPDF_HAVE_STRINGS_H:INTERNAL=
//Have include string.h
LIBHPDF_HAVE_STRING_H:INTERNAL=1
//Have include sys/stat.h
LIBHPDF_HAVE_SYS_STAT_H:INTERNAL=1
//Have include sys/types.h
LIBHPDF_HAVE_SYS_TYPES_H:INTERNAL=1
//Have includes unistd.h
LIBHPDF_HAVE_UNISTD_H:INTERNAL=
//ADVANCED property for variable: LIBRARY_OUTPUT_PATH
LIBRARY_OUTPUT_PATH-ADVANCED:INTERNAL=1
LIBRARY_OUTPUT_PATH:INTERNAL=C:/workspace/pv/ParaView-v5.4.1/build/ThirdParty/protobuf/vtkprotobuf/bin
//ADVANCED property for variable: MPIEXEC
MPIEXEC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS
MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG
MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_POSTFLAGS
MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_PREFLAGS
MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILER
MPI_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS
MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_INCLUDE_PATH
MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_LIBRARIES
MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_LINK_FLAGS
MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILER
MPI_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILE_FLAGS
MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_INCLUDE_PATH
MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=0
//ADVANCED property for variable: MPI_C_LIBRARIES
MPI_C_LIBRARIES-ADVANCED:INTERNAL=0
//ADVANCED property for variable: MPI_C_LINK_FLAGS
MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_EXTRA_LIBRARY
MPI_EXTRA_LIBRARY-ADVANCED:INTERNAL=1
//Scratch variable for MPI header detection
MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND
//Scratch variable for MPI lib detection
MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND
//ADVANCED property for variable: MPI_LIBRARY
MPI_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: M_LIBRARY
M_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Mili_INCLUDE_DIR
Mili_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Mili_LIBRARY
Mili_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_AutobahnPython
Module_AutobahnPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_CinemaPython
Module_CinemaPython-ADVANCED:INTERNAL=1
//Request building CinemaPython
Module_CinemaPython:INTERNAL=OFF
//ADVANCED property for variable: Module_PoissonReconstruction
Module_PoissonReconstruction-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_Pygments
Module_Pygments-ADVANCED:INTERNAL=1
//Request building Pygments
Module_Pygments:INTERNAL=OFF
//ADVANCED property for variable: Module_SignedTensor
Module_SignedTensor-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_SixPython
Module_SixPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_SplineDrivenImageSlicer
Module_SplineDrivenImageSlicer-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_Twisted
Module_Twisted-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_VisItLib
Module_VisItLib-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_WikiExamples
Module_WikiExamples-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_ZopeInterface
Module_ZopeInterface-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_constantly
Module_constantly-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_incremental
Module_incremental-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqApplicationComponents
Module_pqApplicationComponents-ADVANCED:INTERNAL=1
//Request building pqApplicationComponents
Module_pqApplicationComponents:INTERNAL=OFF
//ADVANCED property for variable: Module_pqComponents
Module_pqComponents-ADVANCED:INTERNAL=1
//Request building pqComponents
Module_pqComponents:INTERNAL=OFF
//ADVANCED property for variable: Module_pqCore
Module_pqCore-ADVANCED:INTERNAL=1
//Request building pqCore
Module_pqCore:INTERNAL=OFF
//ADVANCED property for variable: Module_pqDeprecated
Module_pqDeprecated-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqPython
Module_pqPython-ADVANCED:INTERNAL=1
//Request building pqPython
Module_pqPython:INTERNAL=OFF
//ADVANCED property for variable: Module_pqWidgets
Module_pqWidgets-ADVANCED:INTERNAL=1
//Request building pqWidgets
Module_pqWidgets:INTERNAL=OFF
//ADVANCED property for variable: Module_smTestDriver
Module_smTestDriver-ADVANCED:INTERNAL=1
//Request building smTestDriver
Module_smTestDriver:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkAcceleratorsVTKm
Module_vtkAcceleratorsVTKm-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkAddon
Module_vtkAddon-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkChartsCore
Module_vtkChartsCore-ADVANCED:INTERNAL=1
//Request building vtkChartsCore
Module_vtkChartsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkClientServer
Module_vtkClientServer-ADVANCED:INTERNAL=1
//Request building vtkClientServer
Module_vtkClientServer:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonColor
Module_vtkCommonColor-ADVANCED:INTERNAL=1
//Request building vtkCommonColor
Module_vtkCommonColor:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonComputationalGeometry
Module_vtkCommonComputationalGeometry-ADVANCED:INTERNAL=1
//Request building vtkCommonComputationalGeometry
Module_vtkCommonComputationalGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonCore
Module_vtkCommonCore-ADVANCED:INTERNAL=1
//Request building vtkCommonCore
Module_vtkCommonCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonDataModel
Module_vtkCommonDataModel-ADVANCED:INTERNAL=1
//Request building vtkCommonDataModel
Module_vtkCommonDataModel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonExecutionModel
Module_vtkCommonExecutionModel-ADVANCED:INTERNAL=1
//Request building vtkCommonExecutionModel
Module_vtkCommonExecutionModel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonMath
Module_vtkCommonMath-ADVANCED:INTERNAL=1
//Request building vtkCommonMath
Module_vtkCommonMath:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonMisc
Module_vtkCommonMisc-ADVANCED:INTERNAL=1
//Request building vtkCommonMisc
Module_vtkCommonMisc:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonSystem
Module_vtkCommonSystem-ADVANCED:INTERNAL=1
//Request building vtkCommonSystem
Module_vtkCommonSystem:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonTransforms
Module_vtkCommonTransforms-ADVANCED:INTERNAL=1
//Request building vtkCommonTransforms
Module_vtkCommonTransforms:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCosmoHaloFinder
Module_vtkCosmoHaloFinder-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkDICOM
Module_vtkDICOM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkDICOMParser
Module_vtkDICOMParser-ADVANCED:INTERNAL=1
//Request building vtkDICOMParser
Module_vtkDICOMParser:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDomainsChemistry
Module_vtkDomainsChemistry-ADVANCED:INTERNAL=1
//Request building vtkDomainsChemistry
Module_vtkDomainsChemistry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDomainsChemistryOpenGL2
Module_vtkDomainsChemistryOpenGL2-ADVANCED:INTERNAL=1
//Request building vtkDomainsChemistryOpenGL2
Module_vtkDomainsChemistryOpenGL2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDomainsMicroscopy
Module_vtkDomainsMicroscopy-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersAMR
Module_vtkFiltersAMR-ADVANCED:INTERNAL=1
//Request building vtkFiltersAMR
Module_vtkFiltersAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersCore
Module_vtkFiltersCore-ADVANCED:INTERNAL=1
//Request building vtkFiltersCore
Module_vtkFiltersCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersExtraction
Module_vtkFiltersExtraction-ADVANCED:INTERNAL=1
//Request building vtkFiltersExtraction
Module_vtkFiltersExtraction:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersFlowPaths
Module_vtkFiltersFlowPaths-ADVANCED:INTERNAL=1
//Request building vtkFiltersFlowPaths
Module_vtkFiltersFlowPaths:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeneral
Module_vtkFiltersGeneral-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeneral
Module_vtkFiltersGeneral:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeneric
Module_vtkFiltersGeneric-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeneric
Module_vtkFiltersGeneric:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeometry
Module_vtkFiltersGeometry-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeometry
Module_vtkFiltersGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersHybrid
Module_vtkFiltersHybrid-ADVANCED:INTERNAL=1
//Request building vtkFiltersHybrid
Module_vtkFiltersHybrid:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersHyperTree
Module_vtkFiltersHyperTree-ADVANCED:INTERNAL=1
//Request building vtkFiltersHyperTree
Module_vtkFiltersHyperTree:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersImaging
Module_vtkFiltersImaging-ADVANCED:INTERNAL=1
//Request building vtkFiltersImaging
Module_vtkFiltersImaging:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersMatlab
Module_vtkFiltersMatlab-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersModeling
Module_vtkFiltersModeling-ADVANCED:INTERNAL=1
//Request building vtkFiltersModeling
Module_vtkFiltersModeling:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallel
Module_vtkFiltersParallel-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallel
Module_vtkFiltersParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelFlowPaths
Module_vtkFiltersParallelFlowPaths-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelFlowPaths
Module_vtkFiltersParallelFlowPaths:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelGeometry
Module_vtkFiltersParallelGeometry-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelGeometry
Module_vtkFiltersParallelGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelImaging
Module_vtkFiltersParallelImaging-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelImaging
Module_vtkFiltersParallelImaging:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelMPI
Module_vtkFiltersParallelMPI-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelMPI
Module_vtkFiltersParallelMPI:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelStatistics
Module_vtkFiltersParallelStatistics-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelStatistics
Module_vtkFiltersParallelStatistics:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersPoints
Module_vtkFiltersPoints-ADVANCED:INTERNAL=1
//Request building vtkFiltersPoints
Module_vtkFiltersPoints:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersProgrammable
Module_vtkFiltersProgrammable-ADVANCED:INTERNAL=1
//Request building vtkFiltersProgrammable
Module_vtkFiltersProgrammable:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersPython
Module_vtkFiltersPython-ADVANCED:INTERNAL=1
//Request building vtkFiltersPython
Module_vtkFiltersPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersReebGraph
Module_vtkFiltersReebGraph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSMP
Module_vtkFiltersSMP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSelection
Module_vtkFiltersSelection-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSources
Module_vtkFiltersSources-ADVANCED:INTERNAL=1
//Request building vtkFiltersSources
Module_vtkFiltersSources:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersStatistics
Module_vtkFiltersStatistics-ADVANCED:INTERNAL=1
//Request building vtkFiltersStatistics
Module_vtkFiltersStatistics:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersStatisticsGnuR
Module_vtkFiltersStatisticsGnuR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersTexture
Module_vtkFiltersTexture-ADVANCED:INTERNAL=1
//Request building vtkFiltersTexture
Module_vtkFiltersTexture:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersTopology
Module_vtkFiltersTopology-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersVerdict
Module_vtkFiltersVerdict-ADVANCED:INTERNAL=1
//Request building vtkFiltersVerdict
Module_vtkFiltersVerdict:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkGUISupportMFC
Module_vtkGUISupportMFC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQt
Module_vtkGUISupportQt-ADVANCED:INTERNAL=1
//Request building vtkGUISupportQt
Module_vtkGUISupportQt:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkGUISupportQtOpenGL
Module_vtkGUISupportQtOpenGL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQtSQL
Module_vtkGUISupportQtSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQtWebkit
Module_vtkGUISupportQtWebkit-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGeovisCore
Module_vtkGeovisCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOADIOS
Module_vtkIOADIOS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOAMR
Module_vtkIOAMR-ADVANCED:INTERNAL=1
//Request building vtkIOAMR
Module_vtkIOAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOCore
Module_vtkIOCore-ADVANCED:INTERNAL=1
//Request building vtkIOCore
Module_vtkIOCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOEnSight
Module_vtkIOEnSight-ADVANCED:INTERNAL=1
//Request building vtkIOEnSight
Module_vtkIOEnSight:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExodus
Module_vtkIOExodus-ADVANCED:INTERNAL=1
//Request building vtkIOExodus
Module_vtkIOExodus:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExport
Module_vtkIOExport-ADVANCED:INTERNAL=1
//Request building vtkIOExport
Module_vtkIOExport:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExportOpenGL
Module_vtkIOExportOpenGL-ADVANCED:INTERNAL=1
//Request building vtkIOExportOpenGL
Module_vtkIOExportOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExportOpenGL2
Module_vtkIOExportOpenGL2-ADVANCED:INTERNAL=1
//Request building vtkIOExportOpenGL2
Module_vtkIOExportOpenGL2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOFFMPEG
Module_vtkIOFFMPEG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGDAL
Module_vtkIOGDAL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGeoJSON
Module_vtkIOGeoJSON-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGeometry
Module_vtkIOGeometry-ADVANCED:INTERNAL=1
//Request building vtkIOGeometry
Module_vtkIOGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOImage
Module_vtkIOImage-ADVANCED:INTERNAL=1
//Request building vtkIOImage
Module_vtkIOImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOImport
Module_vtkIOImport-ADVANCED:INTERNAL=1
//Request building vtkIOImport
Module_vtkIOImport:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOInfovis
Module_vtkIOInfovis-ADVANCED:INTERNAL=1
//Request building vtkIOInfovis
Module_vtkIOInfovis:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOLSDyna
Module_vtkIOLSDyna-ADVANCED:INTERNAL=1
//Request building vtkIOLSDyna
Module_vtkIOLSDyna:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOLegacy
Module_vtkIOLegacy-ADVANCED:INTERNAL=1
//Request building vtkIOLegacy
Module_vtkIOLegacy:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMINC
Module_vtkIOMINC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOMPIImage
Module_vtkIOMPIImage-ADVANCED:INTERNAL=1
//Request building vtkIOMPIImage
Module_vtkIOMPIImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMPIParallel
Module_vtkIOMPIParallel-ADVANCED:INTERNAL=1
//Request building vtkIOMPIParallel
Module_vtkIOMPIParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMovie
Module_vtkIOMovie-ADVANCED:INTERNAL=1
//Request building vtkIOMovie
Module_vtkIOMovie:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMySQL
Module_vtkIOMySQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIONetCDF
Module_vtkIONetCDF-ADVANCED:INTERNAL=1
//Request building vtkIONetCDF
Module_vtkIONetCDF:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOODBC
Module_vtkIOODBC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOPLY
Module_vtkIOPLY-ADVANCED:INTERNAL=1
//Request building vtkIOPLY
Module_vtkIOPLY:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallel
Module_vtkIOParallel-ADVANCED:INTERNAL=1
//Request building vtkIOParallel
Module_vtkIOParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelExodus
Module_vtkIOParallelExodus-ADVANCED:INTERNAL=1
//Request building vtkIOParallelExodus
Module_vtkIOParallelExodus:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelLSDyna
Module_vtkIOParallelLSDyna-ADVANCED:INTERNAL=1
//Request building vtkIOParallelLSDyna
Module_vtkIOParallelLSDyna:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelNetCDF
Module_vtkIOParallelNetCDF-ADVANCED:INTERNAL=1
//Request building vtkIOParallelNetCDF
Module_vtkIOParallelNetCDF:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelXML
Module_vtkIOParallelXML-ADVANCED:INTERNAL=1
//Request building vtkIOParallelXML
Module_vtkIOParallelXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOPostgreSQL
Module_vtkIOPostgreSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOSQL
Module_vtkIOSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOTRUCHAS
Module_vtkIOTRUCHAS-ADVANCED:INTERNAL=1
//Request building vtkIOTRUCHAS
Module_vtkIOTRUCHAS:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOTecplotTable
Module_vtkIOTecplotTable-ADVANCED:INTERNAL=1
//Request building vtkIOTecplotTable
Module_vtkIOTecplotTable:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOVPIC
Module_vtkIOVPIC-ADVANCED:INTERNAL=1
//Request building vtkIOVPIC
Module_vtkIOVPIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOVideo
Module_vtkIOVideo-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOVisItBridge
Module_vtkIOVisItBridge-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOXML
Module_vtkIOXML-ADVANCED:INTERNAL=1
//Request building vtkIOXML
Module_vtkIOXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXMLParser
Module_vtkIOXMLParser-ADVANCED:INTERNAL=1
//Request building vtkIOXMLParser
Module_vtkIOXMLParser:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXdmf2
Module_vtkIOXdmf2-ADVANCED:INTERNAL=1
//Request building vtkIOXdmf2
Module_vtkIOXdmf2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXdmf3
Module_vtkIOXdmf3-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingColor
Module_vtkImagingColor-ADVANCED:INTERNAL=1
//Request building vtkImagingColor
Module_vtkImagingColor:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingCore
Module_vtkImagingCore-ADVANCED:INTERNAL=1
//Request building vtkImagingCore
Module_vtkImagingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingFourier
Module_vtkImagingFourier-ADVANCED:INTERNAL=1
//Request building vtkImagingFourier
Module_vtkImagingFourier:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingGeneral
Module_vtkImagingGeneral-ADVANCED:INTERNAL=1
//Request building vtkImagingGeneral
Module_vtkImagingGeneral:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingHybrid
Module_vtkImagingHybrid-ADVANCED:INTERNAL=1
//Request building vtkImagingHybrid
Module_vtkImagingHybrid:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingMath
Module_vtkImagingMath-ADVANCED:INTERNAL=1
//Request building vtkImagingMath
Module_vtkImagingMath:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingMorphological
Module_vtkImagingMorphological-ADVANCED:INTERNAL=1
//Request building vtkImagingMorphological
Module_vtkImagingMorphological:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingOpenGL2
Module_vtkImagingOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingSources
Module_vtkImagingSources-ADVANCED:INTERNAL=1
//Request building vtkImagingSources
Module_vtkImagingSources:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingStatistics
Module_vtkImagingStatistics-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingStencil
Module_vtkImagingStencil-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisBoost
Module_vtkInfovisBoost-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisBoostGraphAlgorithms
Module_vtkInfovisBoostGraphAlgorithms-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisCore
Module_vtkInfovisCore-ADVANCED:INTERNAL=1
//Request building vtkInfovisCore
Module_vtkInfovisCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInfovisLayout
Module_vtkInfovisLayout-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisParallel
Module_vtkInfovisParallel-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInteractionImage
Module_vtkInteractionImage-ADVANCED:INTERNAL=1
//Request building vtkInteractionImage
Module_vtkInteractionImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInteractionStyle
Module_vtkInteractionStyle-ADVANCED:INTERNAL=1
//Request building vtkInteractionStyle
Module_vtkInteractionStyle:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInteractionWidgets
Module_vtkInteractionWidgets-ADVANCED:INTERNAL=1
//Request building vtkInteractionWidgets
Module_vtkInteractionWidgets:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkMetaIO
Module_vtkMetaIO-ADVANCED:INTERNAL=1
//Request building vtkMetaIO
Module_vtkMetaIO:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVAnimation
Module_vtkPVAnimation-ADVANCED:INTERNAL=1
//Request building vtkPVAnimation
Module_vtkPVAnimation:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCatalyst
Module_vtkPVCatalyst-ADVANCED:INTERNAL=1
//Request building vtkPVCatalyst
Module_vtkPVCatalyst:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCatalystTestDriver
Module_vtkPVCatalystTestDriver-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkPVCinemaReader
Module_vtkPVCinemaReader-ADVANCED:INTERNAL=1
//Request building vtkPVCinemaReader
Module_vtkPVCinemaReader:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreCore
Module_vtkPVClientServerCoreCore-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreCore
Module_vtkPVClientServerCoreCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreDefault
Module_vtkPVClientServerCoreDefault-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreDefault
Module_vtkPVClientServerCoreDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreRendering
Module_vtkPVClientServerCoreRendering-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreRendering
Module_vtkPVClientServerCoreRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCommon
Module_vtkPVCommon-ADVANCED:INTERNAL=1
//Request building vtkPVCommon
Module_vtkPVCommon:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerImplementationCore
Module_vtkPVServerImplementationCore-ADVANCED:INTERNAL=1
//Request building vtkPVServerImplementationCore
Module_vtkPVServerImplementationCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerImplementationRendering
Module_vtkPVServerImplementationRendering-ADVANCED:INTERNAL=1
//Request building vtkPVServerImplementationRendering
Module_vtkPVServerImplementationRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerApplication
Module_vtkPVServerManagerApplication-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerApplication
Module_vtkPVServerManagerApplication:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerCore
Module_vtkPVServerManagerCore-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerCore
Module_vtkPVServerManagerCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerDefault
Module_vtkPVServerManagerDefault-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerDefault
Module_vtkPVServerManagerDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerRendering
Module_vtkPVServerManagerRendering-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerRendering
Module_vtkPVServerManagerRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsCGNSReader
Module_vtkPVVTKExtensionsCGNSReader-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsCGNSReader
Module_vtkPVVTKExtensionsCGNSReader:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsCore
Module_vtkPVVTKExtensionsCore-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsCore
Module_vtkPVVTKExtensionsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsCosmoTools
Module_vtkPVVTKExtensionsCosmoTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkPVVTKExtensionsDefault
Module_vtkPVVTKExtensionsDefault-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsDefault
Module_vtkPVVTKExtensionsDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsH5PartReader
Module_vtkPVVTKExtensionsH5PartReader-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsH5PartReader
Module_vtkPVVTKExtensionsH5PartReader:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsPoints
Module_vtkPVVTKExtensionsPoints-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsPoints
Module_vtkPVVTKExtensionsPoints:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsRendering
Module_vtkPVVTKExtensionsRendering-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsRendering
Module_vtkPVVTKExtensionsRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelCore
Module_vtkParallelCore-ADVANCED:INTERNAL=1
//Request building vtkParallelCore
Module_vtkParallelCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelMPI
Module_vtkParallelMPI-ADVANCED:INTERNAL=1
//Request building vtkParallelMPI
Module_vtkParallelMPI:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelMPI4Py
Module_vtkParallelMPI4Py-ADVANCED:INTERNAL=1
//Request building vtkParallelMPI4Py
Module_vtkParallelMPI4Py:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParseOGLExt
Module_vtkParseOGLExt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkPython
Module_vtkPython-ADVANCED:INTERNAL=1
//Request building vtkPython
Module_vtkPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPythonInterpreter
Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1
//Request building vtkPythonInterpreter
Module_vtkPythonInterpreter:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingAnnotation
Module_vtkRenderingAnnotation-ADVANCED:INTERNAL=1
//Request building vtkRenderingAnnotation
Module_vtkRenderingAnnotation:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContext2D
Module_vtkRenderingContext2D-ADVANCED:INTERNAL=1
//Request building vtkRenderingContext2D
Module_vtkRenderingContext2D:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContextOpenGL
Module_vtkRenderingContextOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingContextOpenGL
Module_vtkRenderingContextOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContextOpenGL2
Module_vtkRenderingContextOpenGL2-ADVANCED:INTERNAL=1
//Request building vtkRenderingContextOpenGL2
Module_vtkRenderingContextOpenGL2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingCore
Module_vtkRenderingCore-ADVANCED:INTERNAL=1
//Request building vtkRenderingCore
Module_vtkRenderingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingExternal
Module_vtkRenderingExternal-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingFreeType
Module_vtkRenderingFreeType-ADVANCED:INTERNAL=1
//Request building vtkRenderingFreeType
Module_vtkRenderingFreeType:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingFreeTypeFontConfig
Module_vtkRenderingFreeTypeFontConfig-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingGL2PS
Module_vtkRenderingGL2PS-ADVANCED:INTERNAL=1
//Request building vtkRenderingGL2PS
Module_vtkRenderingGL2PS:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingGL2PSOpenGL2
Module_vtkRenderingGL2PSOpenGL2-ADVANCED:INTERNAL=1
//Request building vtkRenderingGL2PSOpenGL2
Module_vtkRenderingGL2PSOpenGL2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingImage
Module_vtkRenderingImage-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingLIC
Module_vtkRenderingLIC-ADVANCED:INTERNAL=1
//Request building vtkRenderingLIC
Module_vtkRenderingLIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingLICOpenGL2
Module_vtkRenderingLICOpenGL2-ADVANCED:INTERNAL=1
//Request building vtkRenderingLICOpenGL2
Module_vtkRenderingLICOpenGL2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingLOD
Module_vtkRenderingLOD-ADVANCED:INTERNAL=1
//Request building vtkRenderingLOD
Module_vtkRenderingLOD:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingLabel
Module_vtkRenderingLabel-ADVANCED:INTERNAL=1
//Request building vtkRenderingLabel
Module_vtkRenderingLabel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingMatplotlib
Module_vtkRenderingMatplotlib-ADVANCED:INTERNAL=1
//Request building vtkRenderingMatplotlib
Module_vtkRenderingMatplotlib:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingOSPRay
Module_vtkRenderingOSPRay-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingOculus
Module_vtkRenderingOculus-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingOpenGL
Module_vtkRenderingOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingOpenGL
Module_vtkRenderingOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingOpenGL2
Module_vtkRenderingOpenGL2-ADVANCED:INTERNAL=1
//Request building vtkRenderingOpenGL2
Module_vtkRenderingOpenGL2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingOpenVR
Module_vtkRenderingOpenVR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingParallel
Module_vtkRenderingParallel-ADVANCED:INTERNAL=1
//Request building vtkRenderingParallel
Module_vtkRenderingParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingParallelLIC
Module_vtkRenderingParallelLIC-ADVANCED:INTERNAL=1
//Request building vtkRenderingParallelLIC
Module_vtkRenderingParallelLIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingQt
Module_vtkRenderingQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingSceneGraph
Module_vtkRenderingSceneGraph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingTk
Module_vtkRenderingTk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingVolume
Module_vtkRenderingVolume-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolume
Module_vtkRenderingVolume:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeAMR
Module_vtkRenderingVolumeAMR-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolumeAMR
Module_vtkRenderingVolumeAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL
Module_vtkRenderingVolumeOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolumeOpenGL
Module_vtkRenderingVolumeOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL2
Module_vtkRenderingVolumeOpenGL2-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolumeOpenGL2
Module_vtkRenderingVolumeOpenGL2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTclTk
Module_vtkTclTk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkTestingCore
Module_vtkTestingCore-ADVANCED:INTERNAL=1
//Request building vtkTestingCore
Module_vtkTestingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTestingGenericBridge
Module_vtkTestingGenericBridge-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkTestingIOSQL
Module_vtkTestingIOSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkTestingRendering
Module_vtkTestingRendering-ADVANCED:INTERNAL=1
//Request building vtkTestingRendering
Module_vtkTestingRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesBenchmarks
Module_vtkUtilitiesBenchmarks-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkUtilitiesColorSeriesToXML
Module_vtkUtilitiesColorSeriesToXML-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkUtilitiesEncodeString
Module_vtkUtilitiesEncodeString-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesEncodeString
Module_vtkUtilitiesEncodeString:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesHashSource
Module_vtkUtilitiesHashSource-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesHashSource
Module_vtkUtilitiesHashSource:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesLegacyColorMapXMLToJSON
Module_vtkUtilitiesLegacyColorMapXMLToJSON-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesLegacyColorMapXMLToJSON
Module_vtkUtilitiesLegacyColorMapXMLToJSON:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesProcessXML
Module_vtkUtilitiesProcessXML-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesProcessXML
Module_vtkUtilitiesProcessXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesWrapClientServer
Module_vtkUtilitiesWrapClientServer-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesWrapClientServer
Module_vtkUtilitiesWrapClientServer:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkVPIC
Module_vtkVPIC-ADVANCED:INTERNAL=1
//Request building vtkVPIC
Module_vtkVPIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsContext2D
Module_vtkViewsContext2D-ADVANCED:INTERNAL=1
//Request building vtkViewsContext2D
Module_vtkViewsContext2D:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsCore
Module_vtkViewsCore-ADVANCED:INTERNAL=1
//Request building vtkViewsCore
Module_vtkViewsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsGeovis
Module_vtkViewsGeovis-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkViewsInfovis
Module_vtkViewsInfovis-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkViewsQt
Module_vtkViewsQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebCore
Module_vtkWebCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebGLExporter
Module_vtkWebGLExporter-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebPython
Module_vtkWebPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingJava
Module_vtkWrappingJava-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingPythonCore
Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingTcl
Module_vtkWrappingTcl-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingTools
Module_vtkWrappingTools-ADVANCED:INTERNAL=1
//Request building vtkWrappingTools
Module_vtkWrappingTools:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkalglib
Module_vtkalglib-ADVANCED:INTERNAL=1
//Request building vtkalglib
Module_vtkalglib:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkcgns
Module_vtkcgns-ADVANCED:INTERNAL=1
//Request building vtkcgns
Module_vtkcgns:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkexodusII
Module_vtkexodusII-ADVANCED:INTERNAL=1
//Request building vtkexodusII
Module_vtkexodusII:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkexpat
Module_vtkexpat-ADVANCED:INTERNAL=1
//Request building vtkexpat
Module_vtkexpat:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkfreetype
Module_vtkfreetype-ADVANCED:INTERNAL=1
//Request building vtkfreetype
Module_vtkfreetype:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkgl2ps
Module_vtkgl2ps-ADVANCED:INTERNAL=1
//Request building vtkgl2ps
Module_vtkgl2ps:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkglew
Module_vtkglew-ADVANCED:INTERNAL=1
//Request building vtkglew
Module_vtkglew:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkhdf5
Module_vtkhdf5-ADVANCED:INTERNAL=1
//Request building vtkhdf5
Module_vtkhdf5:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkicet
Module_vtkicet-ADVANCED:INTERNAL=1
//Request building vtkicet
Module_vtkicet:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkjpeg
Module_vtkjpeg-ADVANCED:INTERNAL=1
//Request building vtkjpeg
Module_vtkjpeg:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkjsoncpp
Module_vtkjsoncpp-ADVANCED:INTERNAL=1
//Request building vtkjsoncpp
Module_vtkjsoncpp:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkkwiml
Module_vtkkwiml-ADVANCED:INTERNAL=1
//Request building vtkkwiml
Module_vtkkwiml:INTERNAL=OFF
//ADVANCED property for variable: Module_vtklibharu
Module_vtklibharu-ADVANCED:INTERNAL=1
//Request building vtklibharu
Module_vtklibharu:INTERNAL=OFF
//ADVANCED property for variable: Module_vtklibproj4
Module_vtklibproj4-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtklibxml2
Module_vtklibxml2-ADVANCED:INTERNAL=1
//Request building vtklibxml2
Module_vtklibxml2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtklz4
Module_vtklz4-ADVANCED:INTERNAL=1
//Request building vtklz4
Module_vtklz4:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkmpi4py
Module_vtkmpi4py-ADVANCED:INTERNAL=1
//Request building vtkmpi4py
Module_vtkmpi4py:INTERNAL=OFF
//ADVANCED property for variable: Module_vtknetcdf
Module_vtknetcdf-ADVANCED:INTERNAL=1
//Request building vtknetcdf
Module_vtknetcdf:INTERNAL=OFF
//ADVANCED property for variable: Module_vtknetcdfcpp
Module_vtknetcdfcpp-ADVANCED:INTERNAL=1
//Request building vtknetcdfcpp
Module_vtknetcdfcpp:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkoggtheora
Module_vtkoggtheora-ADVANCED:INTERNAL=1
//Request building vtkoggtheora
Module_vtkoggtheora:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkpng
Module_vtkpng-ADVANCED:INTERNAL=1
//Request building vtkpng
Module_vtkpng:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkprotobuf
Module_vtkprotobuf-ADVANCED:INTERNAL=1
//Request building vtkprotobuf
Module_vtkprotobuf:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkpugixml
Module_vtkpugixml-ADVANCED:INTERNAL=1
//Request building vtkpugixml
Module_vtkpugixml:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkqttesting
Module_vtkqttesting-ADVANCED:INTERNAL=1
//Request building vtkqttesting
Module_vtkqttesting:INTERNAL=OFF
//ADVANCED property for variable: Module_vtksqlite
Module_vtksqlite-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtksys
Module_vtksys-ADVANCED:INTERNAL=1
//Request building vtksys
Module_vtksys:INTERNAL=OFF
//ADVANCED property for variable: Module_vtktiff
Module_vtktiff-ADVANCED:INTERNAL=1
//Request building vtktiff
Module_vtktiff:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkverdict
Module_vtkverdict-ADVANCED:INTERNAL=1
//Request building vtkverdict
Module_vtkverdict:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkxdmf2
Module_vtkxdmf2-ADVANCED:INTERNAL=1
//Request building vtkxdmf2
Module_vtkxdmf2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkxdmf3
Module_vtkxdmf3-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkzfp
Module_vtkzfp-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkzlib
Module_vtkzlib-ADVANCED:INTERNAL=1
//Request building vtkzlib
Module_vtkzlib:INTERNAL=OFF
//ADVANCED property for variable: NETCDF4_CHUNK_CACHE_NELEMS
NETCDF4_CHUNK_CACHE_NELEMS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_CHUNK_CACHE_PREEMPTION
NETCDF4_CHUNK_CACHE_PREEMPTION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_CHUNK_CACHE_SIZE
NETCDF4_CHUNK_CACHE_SIZE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_DEFAULT_CHUNKS_IN_CACHE
NETCDF4_DEFAULT_CHUNKS_IN_CACHE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_DEFAULT_CHUNK_SIZE
NETCDF4_DEFAULT_CHUNK_SIZE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_MAX_DEFAULT_CACHE_SIZE
NETCDF4_MAX_DEFAULT_CACHE_SIZE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF_DISABLE_COMPILER_WARNINGS
NETCDF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//Have library c
NOT_NEED_LIBNSL:INTERNAL=
//CXX test 
NO_STATIC_CAST:INTERNAL=
//CHECK_TYPE_SIZE: off64_t unknown
OFF64_T:INTERNAL=
//Have symbol off_t
OFF_T:INTERNAL=
//CXX test 
OLD_HEADER_FILENAME:INTERNAL=
//ADVANCED property for variable: OPENGL_gl_LIBRARY
OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_glu_LIBRARY
OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSPRAY_BUILD_DIR
OSPRAY_BUILD_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSPRAY_INSTALL_DIR
OSPRAY_INSTALL_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OpenMP_CXX_FLAGS
OpenMP_CXX_FLAGS-ADVANCED:INTERNAL=1
//C++ compiler's OpenMP specification date
OpenMP_CXX_SPEC_DATE:INTERNAL=200203
//ADVANCED property for variable: OpenMP_C_FLAGS
OpenMP_C_FLAGS-ADVANCED:INTERNAL=1
//C compiler's OpenMP specification date
OpenMP_C_SPEC_DATE:INTERNAL=200203
//Test OpenMP_FLAG_DETECTED
OpenMP_FLAG_DETECTED:INTERNAL=1
//Result of TRY_COMPILE
OpenMP_TRY_COMPILE_RESULT:INTERNAL=TRUE
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms
PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO
PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph
PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin
PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting
PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_GMVReader
PARAVIEW_AUTOLOAD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement
PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_LagrangianParticleTracker
PARAVIEW_AUTOLOAD_PLUGIN_LagrangianParticleTracker-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_Moments
PARAVIEW_AUTOLOAD_PLUGIN_Moments-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource
PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_PacMan
PARAVIEW_AUTOLOAD_PLUGIN_PacMan-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_PythonQtPlugin
PARAVIEW_AUTOLOAD_PLUGIN_PythonQtPlugin-ADVANCED:INTERNAL=1
//Load PythonQtPlugin Plugin Automatically
PARAVIEW_AUTOLOAD_PLUGIN_PythonQtPlugin:INTERNAL=OFF
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SLACTools
PARAVIEW_AUTOLOAD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools
PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_StreamLinesRepresentation
PARAVIEW_AUTOLOAD_PLUGIN_StreamLinesRepresentation-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles
PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC
PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells
PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_CATALYST_ADAPTORS
PARAVIEW_BUILD_CATALYST_ADAPTORS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms
PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AdiosReader
PARAVIEW_BUILD_PLUGIN_AdiosReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ArrowGlyph
PARAVIEW_BUILD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin
PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_EyeDomeLighting
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GMVReader
PARAVIEW_BUILD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement
PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_InSituExodus
PARAVIEW_BUILD_PLUGIN_InSituExodus-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_LagrangianParticleTracker
PARAVIEW_BUILD_PLUGIN_LagrangianParticleTracker-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Moments
PARAVIEW_BUILD_PLUGIN_Moments-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource
PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PacMan
PARAVIEW_BUILD_PLUGIN_PacMan-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PythonQtPlugin
PARAVIEW_BUILD_PLUGIN_PythonQtPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SLACTools
PARAVIEW_BUILD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SierraPlotTools
PARAVIEW_BUILD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamLinesRepresentation
PARAVIEW_BUILD_PLUGIN_StreamLinesRepresentation-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamingParticles
PARAVIEW_BUILD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SurfaceLIC
PARAVIEW_BUILD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator
PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells
PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VRPlugin
PARAVIEW_BUILD_PLUGIN_VRPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin
PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1
//List of modules to CS wrap
PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonExecutionModel;vtkFiltersCore;vtkCommonComputationalGeometry;vtkFiltersGeneral;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkFiltersSources;vtkCommonColor;vtkFiltersGeometry;vtkRenderingCore;vtkInteractionStyle;vtkRenderingOpenGL2;vtkFiltersModeling;vtkIOCore;vtkIOLegacy;vtkParallelCore;vtkFiltersParallel;vtkFiltersProgrammable;vtkPythonInterpreter;vtkIOXMLParser;vtkPVCommon;vtkIOImage;vtkPVVTKExtensionsCore;vtkParallelMPI;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkIOMovie;vtkIOXML;vtkInfovisCore;vtkIOInfovis;vtkDomainsChemistry;vtkFiltersAMR;vtkRenderingFreeType;vtkRenderingContext2D;vtkChartsCore;vtkFiltersFlowPaths;vtkFiltersParallelFlowPaths;vtkFiltersParallelStatistics;vtkIOEnSight;vtkIOImport;vtkIOMPIImage;vtkIOPLY;vtkIOGeometry;vtkIONetCDF;vtkIOParallel;vtkIOExodus;vtkIOParallelExodus;vtkIOParallelXML;vtkImagingSources;vtkFiltersHybrid;vtkImagingColor;vtkImagingGeneral;vtkImagingHybrid;vtkRenderingAnnotation;vtkRenderingVolume;vtkInteractionWidgets;vtkFiltersGeneric;vtkFiltersHyperTree;vtkFiltersParallelMPI;vtkRenderingGL2PSOpenGL2;vtkIOExport;vtkIOExportOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingMatplotlib;vtkRenderingParallel;vtkImagingMath;vtkRenderingVolumeOpenGL2;vtkRenderingVolumeAMR;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingLabel;vtkViewsCore;vtkViewsContext2D;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkDomainsChemistryOpenGL2;vtkFiltersParallelGeometry;vtkFiltersImaging;vtkFiltersParallelImaging;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOMPIParallel;vtkIOLSDyna;vtkIOParallelLSDyna;vtkIOParallelNetCDF;vtkIOTRUCHAS;vtkIOTecplotTable;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionImage;vtkPVCinemaReader;vtkPVVTKExtensionsCGNSReader;vtkPVVTKExtensionsH5PartReader;vtkFiltersPoints;vtkPVVTKExtensionsPoints;vtkParallelMPI4Py;vtkRenderingLICOpenGL2;vtkRenderingLOD;vtkRenderingParallelLIC;vtkPVServerManagerApplication;vtkPVCatalyst
//ADVANCED property for variable: PARAVIEW_DATA_EXCLUDE_FROM_ALL
PARAVIEW_DATA_EXCLUDE_FROM_ALL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_DATA_STORE
PARAVIEW_DATA_STORE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION
PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_MATPLOTLIB
PARAVIEW_ENABLE_MATPLOTLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_SPYPLOT_MARKERS
PARAVIEW_ENABLE_SPYPLOT_MARKERS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED
PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_WEB
PARAVIEW_ENABLE_WEB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_EXTERNAL_MODULE_ROOTS
PARAVIEW_EXTERNAL_MODULE_ROOTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_EXTERNAL_PLUGIN_DIRS
PARAVIEW_EXTERNAL_PLUGIN_DIRS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_EXTRA_EXTERNAL_PLUGINS
PARAVIEW_EXTRA_EXTERNAL_PLUGINS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_INITIALIZE_MPI_ON_CLIENT
PARAVIEW_INITIALIZE_MPI_ON_CLIENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_PLUGIN_LOADER_PATHS
PARAVIEW_PLUGIN_LOADER_PATHS-ADVANCED:INTERNAL=1
//STRINGS property for variable: PARAVIEW_QT_VERSION
PARAVIEW_QT_VERSION-STRINGS:INTERNAL=4;5
//Server Manager XMLs
PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/Default/settings.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/Animation/animation.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/CinemaReader/cinemareader.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/VTKExtensions/CGNSReader/resources/CGNSReader.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/VTKExtensions/H5PartReader/H5PartServerManager.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/VTKExtensions/Points/points.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/proxies_mpi.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/proxies_opengl2.xml;C:/workspace/pv/ParaView-v5.4.1/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml
//ADVANCED property for variable: PARAVIEW_USE_ATP
PARAVIEW_USE_ATP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_ICE_T
PARAVIEW_USE_ICE_T-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_MPI_SSEND
PARAVIEW_USE_MPI_SSEND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_QTHELP
PARAVIEW_USE_QTHELP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_QTWEBKIT
PARAVIEW_USE_QTWEBKIT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_UNIFIED_BINDINGS
PARAVIEW_USE_UNIFIED_BINDINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PROTOBUF_DISABLE_COMPILER_WARNINGS
PROTOBUF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_CLEAN_COMMAND
PV_TEST_CLEAN_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_CLIENT
PV_TEST_CLIENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_INIT_COMMAND
PV_TEST_INIT_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_USE_RANDOM_PORTS
PV_TEST_USE_RANDOM_PORTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_DEBUG_LIBRARY
PYTHON_DEBUG_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_INCLUDE_DIR
PYTHON_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_LIBRARY
PYTHON_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_HELP_GENERATOR
QT_HELP_GENERATOR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TESTING_EVENT_PLAYBACK_DELAY
QT_TESTING_EVENT_PLAYBACK_DELAY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_XMLPATTERNS_EXECUTABLE
QT_XMLPATTERNS_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SILO_INCLUDE_DIR
SILO_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SILO_LIBRARY
SILO_LIBRARY-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: off64_t unknown
SIZEOF_OFF64_T:INTERNAL=
//CHECK_TYPE_SIZE: sizeof(off_t)
SIZEOF_OFF_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(ptrdiff_t)
SIZEOF_PTRDIFF_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(signed int)
SIZEOF_SIGNED_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(signed long)
SIZEOF_SIGNED_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(signed long long)
SIZEOF_SIGNED_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(signed short)
SIZEOF_SIGNED_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(size_t)
SIZEOF_SIZE_T:INTERNAL=8
//CHECK_TYPE_SIZE: ssize_t unknown
SIZEOF_SSIZE_T:INTERNAL=
//CHECK_TYPE_SIZE: uchar unknown
SIZEOF_UCHAR:INTERNAL=
//CHECK_TYPE_SIZE: sizeof(unsigned char *)
SIZEOF_UNSIGNED_CHAR_P:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(unsigned int)
SIZEOF_UNSIGNED_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(unsigned long)
SIZEOF_UNSIGNED_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(unsigned long long)
SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(unsigned short)
SIZEOF_UNSIGNED_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(void *)
SIZEOF_VOID_P:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(_Bool)
SIZEOF__BOOL:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(__int64)
SIZEOF___INT64:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long)
SIZE_OF_LONG:INTERNAL=4
//Have symbol size_t
SIZE_T:INTERNAL=
//Result of TRY_COMPILE
STDC_HEADERS:INTERNAL=TRUE
//Result of TRY_COMPILE
SUCCEED:INTERNAL=FALSE
//Result of TRY_COMPILE
SUCCEED_MAP:INTERNAL=FALSE
//Result of TRY_COMPILE
SUCCEED_SET:INTERNAL=FALSE
//Result of TRY_COMPILE
SUPPORT_IP6_COMPILED:INTERNAL=FALSE
//ADVANCED property for variable: SURFACELIC_PLUGIN_TESTING
SURFACELIC_PLUGIN_TESTING-ADVANCED:INTERNAL=1
//Test TIME_WITH_SYS_TIME
TIME_WITH_SYS_TIME:INTERNAL=
//Test TM_IN_SYS_TIME
TM_IN_SYS_TIME:INTERNAL=1
//ADVANCED property for variable: USE_COMPILER_HIDDEN_VISIBILITY
USE_COMPILER_HIDDEN_VISIBILITY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_BUILD_DOC
VERDICT_BUILD_DOC-ADVANCED:INTERNAL=1
//Build the 2007 Verdict User Manual
VERDICT_BUILD_DOC:INTERNAL=OFF
//ADVANCED property for variable: VERDICT_ENABLE_TESTING
VERDICT_ENABLE_TESTING-ADVANCED:INTERNAL=1
//Should tests of the VERDICT library be built?
VERDICT_ENABLE_TESTING:INTERNAL=OFF
//ADVANCED property for variable: VERDICT_MANGLE
VERDICT_MANGLE-ADVANCED:INTERNAL=1
//Mangle verdict names for inclusion in a larger library?
VERDICT_MANGLE:INTERNAL=OFF
//A string to prepend to all verdict function names and classes.
VERDICT_MANGLE_PREFIX:INTERNAL=
VISITBRIDGE_INCLUDE_DIRS:INTERNAL=C:/workspace/pv/ParaView-v5.4.1/build/Utilities/VisItBridge/Library/VisItLib;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/Exceptions/Database;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/Exceptions/Pipeline;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/Exceptions/Plotter;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/comm;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/expr;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/misc;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/parser;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/plugin;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/proxybase;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/state;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/common/utility;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/include;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Database/Database;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Database/Ghost;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/DBAtts/MetaData;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/DBAtts/SIL;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Math;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/VisWindow/VisWindow;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/AbstractFilters;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Data;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Pipeline;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Sinks;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/avt/Pipeline/Sources;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/visit_vtk/full;C:/workspace/pv/ParaView-v5.4.1/Utilities/VisItBridge/Library/VisItLib/visit_vtk/lightweight;Boost_INCLUDE_DIR-NOTFOUND
//Result of TRY_COMPILE
VISIT_COMPILER_FSTREAM_WORKAROUND:INTERNAL=FALSE
//ADVANCED property for variable: VISIT_DISABLE_COMPILER_WARNINGS
VISIT_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
VTKFTGL_BINARY_DIR:INTERNAL=C:/workspace/pv/ParaView-v5.4.1/build/VTK/Utilities/ftgl
VTKFTGL_SOURCE_DIR:INTERNAL=C:/workspace/pv/ParaView-v5.4.1/VTK/Utilities/ftgl
//ADVANCED property for variable: VTKOGGTHEORA_DISABLE_ASM
VTKOGGTHEORA_DISABLE_ASM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTKOGGTHEORA_DISABLE_FLOAT
VTKOGGTHEORA_DISABLE_FLOAT-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int)
VTKOGGTHEORA_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int16_t)
VTKOGGTHEORA_INT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int32_t)
VTKOGGTHEORA_INT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int64_t)
VTKOGGTHEORA_INT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long)
VTKOGGTHEORA_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
VTKOGGTHEORA_LONG_LONG:INTERNAL=8
//ADVANCED property for variable: VTKOGGTHEORA_SHARED_LINKER_FLAGS
VTKOGGTHEORA_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(short)
VTKOGGTHEORA_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint16_t)
VTKOGGTHEORA_UINT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint32_t)
VTKOGGTHEORA_UINT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: u_int16_t unknown
VTKOGGTHEORA_U_INT16_T:INTERNAL=
//CHECK_TYPE_SIZE: u_int32_t unknown
VTKOGGTHEORA_U_INT32_T:INTERNAL=
//ADVANCED property for variable: VTK_ALL_NEW_OBJECT_FACTORY
VTK_ALL_NEW_OBJECT_FACTORY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_ANDROID_BUILD
VTK_ANDROID_BUILD-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_BUILD_ALL_MODULES
VTK_BUILD_ALL_MODULES-ADVANCED:INTERNAL=1
//Directory where python modules will be built
VTK_BUILD_PYTHON_MODULE_DIR:INTERNAL=C:/workspace/pv/ParaView-v5.4.1/build/lib/site-packages
//ADVANCED property for variable: VTK_BUILD_QT_DESIGNER_PLUGIN
VTK_BUILD_QT_DESIGNER_PLUGIN-ADVANCED:INTERNAL=1
//Test VTK_CONST_REVERSE_ITERATOR_COMPARISON
VTK_CONST_REVERSE_ITERATOR_COMPARISON:INTERNAL=1
//ADVANCED property for variable: VTK_DATA_STORE
VTK_DATA_STORE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_DEBUG_LEAKS
VTK_DEBUG_LEAKS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_DISPATCH_AOS_ARRAYS
VTK_DISPATCH_AOS_ARRAYS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_DISPATCH_SOA_ARRAYS
VTK_DISPATCH_SOA_ARRAYS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_DISPATCH_TYPED_ARRAYS
VTK_DISPATCH_TYPED_ARRAYS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_EGL_DEVICE_INDEX
VTK_EGL_DEVICE_INDEX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_ENABLE_KITS
VTK_ENABLE_KITS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_ENABLE_VTKPYTHON
VTK_ENABLE_VTKPYTHON-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_EXTERNAL_LIBHARU_IS_SHARED
VTK_EXTERNAL_LIBHARU_IS_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_FORBID_DOWNLOADS
VTK_FORBID_DOWNLOADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Imaging
VTK_Group_Imaging-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_MPI
VTK_Group_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewCore
VTK_Group_ParaViewCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewQt
VTK_Group_ParaViewQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewRendering
VTK_Group_ParaViewRendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Qt
VTK_Group_Qt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Rendering
VTK_Group_Rendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_StandAlone
VTK_Group_StandAlone-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Tk
VTK_Group_Tk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Views
VTK_Group_Views-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Web
VTK_Group_Web-ADVANCED:INTERNAL=1
//Have symbol feenableexcept
VTK_HAS_FEENABLEEXCEPT:INTERNAL=
//Have symbol finite
VTK_HAS_FINITE:INTERNAL=
//Have symbol InterlockedAdd
VTK_HAS_INTERLOCKEDADD:INTERNAL=1
//Have symbol isfinite
VTK_HAS_ISFINITE:INTERNAL=1
//Have symbol isinf
VTK_HAS_ISINF:INTERNAL=1
//Have symbol isnan
VTK_HAS_ISNAN:INTERNAL=1
//Test VTK_HAS_STD_ISFINITE
VTK_HAS_STD_ISFINITE:INTERNAL=1
//Test VTK_HAS_STD_ISINF
VTK_HAS_STD_ISINF:INTERNAL=1
//Test VTK_HAS_STD_ISNAN
VTK_HAS_STD_ISNAN:INTERNAL=1
//Support for getsockname with socklen_t
VTK_HAVE_GETSOCKNAME_WITH_SOCKLEN_T:INTERNAL=0
//Have library socket
VTK_HAVE_LIBSOCKET:INTERNAL=
//Have symbol SO_REUSEADDR
VTK_HAVE_SO_REUSEADDR:INTERNAL=
//Directory where python modules will be installed
VTK_INSTALL_PYTHON_MODULE_DIR:INTERNAL=lib/paraview-5.4/site-packages
//ADVANCED property for variable: VTK_IOS_BUILD
VTK_IOS_BUILD-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_REMOVE
VTK_LEGACY_REMOVE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_SILENT
VTK_LEGACY_SILENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MAKE_INSTANTIATORS
VTK_MAKE_INSTANTIATORS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MAX_THREADS
VTK_MAX_THREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPIRUN_EXE
VTK_MPIRUN_EXE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_MAX_NUMPROCS
VTK_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_NUMPROC_FLAG
VTK_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_POSTFLAGS
VTK_MPI_POSTFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_PREFLAGS
VTK_MPI_PREFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_PRENUMPROC_FLAGS
VTK_MPI_PRENUMPROC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_NO_PYTHON_THREADS
VTK_NO_PYTHON_THREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_OPENGL_HAS_OSMESA
VTK_OPENGL_HAS_OSMESA-ADVANCED:INTERNAL=1
//ParaView requires the OpenVR factory be disabled
VTK_OPENVR_OBJECT_FACTORY:INTERNAL=OFF
//ADVANCED property for variable: VTK_PYTHON_FULL_THREADSAFE
VTK_PYTHON_FULL_THREADSAFE-ADVANCED:INTERNAL=1
//Ensure all calls to Python using GIL
VTK_PYTHON_FULL_THREADSAFE:INTERNAL=OFF
//ADVANCED property for variable: VTK_PYTHON_VERSION
VTK_PYTHON_VERSION-ADVANCED:INTERNAL=1
//STRINGS property for variable: VTK_QT_VERSION
VTK_QT_VERSION-STRINGS:INTERNAL=4;5
VTK_QT_VERSION:INTERNAL=5
//ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER
VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER
VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER-ADVANCED:INTERNAL=1
//STRINGS property for variable: VTK_RENDERING_BACKEND
VTK_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL2;OpenGL;None
//ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS
VTK_REPORT_OPENGL_ERRORS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS
VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS-ADVANCED:INTERNAL=1
//STRINGS property for variable: VTK_SMP_IMPLEMENTATION_TYPE
VTK_SMP_IMPLEMENTATION_TYPE-STRINGS:INTERNAL=Sequential;OpenMP;TBB
//Result of TRY_COMPILE
VTK_UNDEFINED_SYMBOLS_ALLOWED:INTERNAL=FALSE
//hashed try_compile flags
VTK_UNDEFINED_SYMBOLS_ALLOWED_hash:INTERNAL=92cac7e7f3ab5e0d638f3de146fc8686
//ADVANCED property for variable: VTK_USE_64BIT_IDS
VTK_USE_64BIT_IDS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_LARGE_DATA
VTK_USE_LARGE_DATA-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_OFFSCREEN
VTK_USE_OFFSCREEN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_OFFSCREEN_EGL
VTK_USE_OFFSCREEN_EGL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_CGNS
VTK_USE_SYSTEM_CGNS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_CINEMA_PYTHON
VTK_USE_SYSTEM_CINEMA_PYTHON-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_EXPAT
VTK_USE_SYSTEM_EXPAT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_FREETYPE
VTK_USE_SYSTEM_FREETYPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_GL2PS
VTK_USE_SYSTEM_GL2PS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_GLEW
VTK_USE_SYSTEM_GLEW-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_HDF5
VTK_USE_SYSTEM_HDF5-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_ICET
VTK_USE_SYSTEM_ICET-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_JPEG
VTK_USE_SYSTEM_JPEG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_JSONCPP
VTK_USE_SYSTEM_JSONCPP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBHARU
VTK_USE_SYSTEM_LIBHARU-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBRARIES
VTK_USE_SYSTEM_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBXML2
VTK_USE_SYSTEM_LIBXML2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LZ4
VTK_USE_SYSTEM_LZ4-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_MPI4PY
VTK_USE_SYSTEM_MPI4PY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_NETCDF
VTK_USE_SYSTEM_NETCDF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_NETCDFCPP
VTK_USE_SYSTEM_NETCDFCPP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_OGGTHEORA
VTK_USE_SYSTEM_OGGTHEORA-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PNG
VTK_USE_SYSTEM_PNG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PROTOBUF
VTK_USE_SYSTEM_PROTOBUF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PUGIXML
VTK_USE_SYSTEM_PUGIXML-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PYGMENTS
VTK_USE_SYSTEM_PYGMENTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_QTTESTING
VTK_USE_SYSTEM_QTTESTING-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_TIFF
VTK_USE_SYSTEM_TIFF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_VISITLIB
VTK_USE_SYSTEM_VISITLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_XDMF2
VTK_USE_SYSTEM_XDMF2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_ZLIB
VTK_USE_SYSTEM_ZLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TK
VTK_USE_TK-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_VIDEO_FOR_WINDOWS
VTK_USE_VIDEO_FOR_WINDOWS-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
VTK_USE_VIDEO_FOR_WINDOWS_DEFAULT:INTERNAL=TRUE
//ADVANCED property for variable: VTK_USE_X
VTK_USE_X-ADVANCED:INTERNAL=1
//Enable using Video for Windows (vfw32) for video capture.
VTK_VFW_SUPPORTS_CAPTURE:INTERNAL=1
//ADVANCED property for variable: VTK_VPIC_USE_MPI
VTK_VPIC_USE_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WARN_ON_DISPATCH_FAILURE
VTK_WARN_ON_DISPATCH_FAILURE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_HINTS
VTK_WRAP_HINTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_JAVA
VTK_WRAP_JAVA-ADVANCED:INTERNAL=1
//Should VTK Python wrapping be built?
VTK_WRAP_PYTHON:INTERNAL=ON
//ADVANCED property for variable: VTK_WRAP_TCL
VTK_WRAP_TCL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_XDMF_USE_MPI
VTK_XDMF_USE_MPI-ADVANCED:INTERNAL=1
//Result of TEST_BIG_ENDIAN
WORDS_BIGENDIAN:INTERNAL=0
//ADVANCED property for variable: XDMF_BUILD_MPI
XDMF_BUILD_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAS_NDGM
XDMF_HAS_NDGM-ADVANCED:INTERNAL=1
//Whether streams support 64-bit types
XDMF_HAVE_64BIT_STREAMS:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_FCNTL
XDMF_HAVE_FCNTL-ADVANCED:INTERNAL=1
//Have include malloc.h
XDMF_HAVE_MALLOC_H:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_MMAN
XDMF_HAVE_MMAN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_NETINET
XDMF_HAVE_NETINET-ADVANCED:INTERNAL=1
XDMF_REGENERATE_WRAPPERS:INTERNAL=OFF
XDMF_REGENERATE_YACCLEX:INTERNAL=OFF
//CHECK_TYPE_SIZE: sizeof(char)
XDMF_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
XDMF_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
XDMF_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
XDMF_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
XDMF_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(short)
XDMF_SIZEOF_SHORT:INTERNAL=2
//ADVANCED property for variable: XDMF_USE_BZIP2
XDMF_USE_BZIP2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_USE_GZIP
XDMF_USE_GZIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_USE_MYSQL
XDMF_USE_MYSQL-ADVANCED:INTERNAL=1
XDMF_WRAP_CSHARP:INTERNAL=OFF
XDMF_WRAP_PYTHON:INTERNAL=OFF
XDMF_WRAP_TCL:INTERNAL=OFF
//Have include unistd.h
Z_HAVE_UNISTD_H:INTERNAL=
//Components requested for this build tree.
_Boost_COMPONENTS_SEARCHED:INTERNAL=
//Last used Boost_INCLUDE_DIR value.
_Boost_INCLUDE_DIR_LAST:INTERNAL=Boost_INCLUDE_DIR-NOTFOUND
//Last used Boost_NAMESPACE value.
_Boost_NAMESPACE_LAST:INTERNAL=boost
//Last used Boost_USE_MULTITHREADED value.
_Boost_USE_MULTITHREADED_LAST:INTERNAL=TRUE
//CMAKE_INSTALL_PREFIX during last run
_GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX:INTERNAL=C:/pv54_diy
//ParaView has been configured
__paraview_configured:INTERNAL=TRUE
//Result of TEST_BIG_ENDIAN
bigendian:INTERNAL=0
//CHECK_TYPE_SIZE: INT16 unknown
int16:INTERNAL=
//CHECK_TYPE_SIZE: INT32 unknown
int32:INTERNAL=
//CHECK_TYPE_SIZE: INT8 unknown
int8:INTERNAL=
protobut_determine_hash_namespace_done:INTERNAL=TRUE
protobut_pthread_test_done:INTERNAL=TRUE
pthread_test_result:INTERNAL=UNKNOWN


From heiland at iu.edu  Wed Dec 20 08:26:37 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Wed, 20 Dec 2017 13:26:37 +0000
Subject: [Paraview] getting Client Info
Message-ID: <A78F1224-F0DB-4792-9649-A6257217535F@iu.edu>

On the ?About ParaView? popup window, there?s a ?Client Information? tab, but I can?t seem to copy/paste that info. Is there a way to easily get it? I happen to be on OS X, but interested for all OSes.

thanks, Randy

From cory.quammen at kitware.com  Wed Dec 20 09:43:55 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 20 Dec 2017 09:43:55 -0500
Subject: [Paraview] paraview GUI entry point not found in win10,
 compiled with qt 5.10 and vs 2017.
In-Reply-To: <CAMkQf0teAdCrtv2C_0VWwCAGjdMFB3pnDFYS35cSEd3tLYRD8w@mail.gmail.com>
References: <CAMkQf0teAdCrtv2C_0VWwCAGjdMFB3pnDFYS35cSEd3tLYRD8w@mail.gmail.com>
Message-ID: <CAB5Fpx6B+hL7JGV-jHQ_Cv6VwkVn_y79eUxEtLGpEa_QPvx=ZQ@mail.gmail.com>

Check your PATH environment variable to make sure nothing is inserting a
path Qt DLLs different from the Qt with which you built ParaView. Note that
CMake installs Qt DLLs, so if you have that installed, your PATH may be set
to point to those DLLs.

HTH,
Cory

On Tue, Dec 19, 2017 at 7:01 PM, ?? <chengdi123000 at gmail.com> wrote:

> Hi everyone,
>
> I just compiled paraview 5.4.1 using vs 2017 in win 10 using qt 5.10.
> The compilation works but only the `pvserver` works while the
> `paraview.exe` cannot run.
>
> The error is :Entry Point Not Found:
> [image: Inline image 1]
> entry point  `?setSelectionModel at QListWidget ... ` could not be located
> in the dynamic link library `C:\pv54_diy\bin\vtkpqComponents-pv5.4.dll`
>
>
> Here is what I did:
> - win10 64bit
> - vs2017 community version
> - MSMPI  8.1.12438.1091 runtime and SDK
> - QT 5.10.0 using msvc2017_64/lib
> - cmake version 3.10.1
> - Python 3.6.3 :: Anaconda, Inc.
> - I compiled the boost 1.66.0 myself
> - I attached the `CMakeCache.txt` file in the email.
>
>
> I tried to solve this problem like this:
> - locate  `vtkpqComponents` in the vtk source code. I cannot locate where
> it is, so I cannot find which file is responsible for this, I also cannot
> identify what this `dll` file is used for.
> - I searched the maillist archive, cannot find anything useful.
> - I tried to read the successful build log on DashBoard:
> https://open.cdash.org/buildSummary.php?buildid=5187747, However, I
> cannot see essential difference.
> - I can run `pvserver` and use the official release of paraview 5.4.1 gui
> client to connect to it. I can open the head dataset and render it using
> volume mode remotely.
>
> Could anyone help me?
>
> Di Cheng
> Engineer of Research and Development Center, visiting scholar at
> University of Connecticut
> China Academy of Aerospace Aerodynamics
> Phone @ China: +86-l58Ol5949ll
> Phone @ US: +l-86O-6l7-l886
>
> Address: No.17, YunGang West Road, Fengtai District, Beijing, China
>
> Zip Code?100074
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/849e8ae2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 12306 bytes
Desc: not available
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/849e8ae2/attachment.png>

From cory.quammen at kitware.com  Wed Dec 20 10:04:08 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 20 Dec 2017 10:04:08 -0500
Subject: [Paraview] getting Client Info
In-Reply-To: <A78F1224-F0DB-4792-9649-A6257217535F@iu.edu>
References: <A78F1224-F0DB-4792-9649-A6257217535F@iu.edu>
Message-ID: <CAB5Fpx7V83GX5jhZ-xXF76EF5pRsY3nm00Q3U=c_xCxCckP1Cw@mail.gmail.com>

On my Mac, I can copy individual cells, but not the whole table.

It would be a nice feature. Feel free to write up a feature request in the
issue tracker: gitlab.kitware.com/paraview/paraview/issues

Thanks,
Cory

On Wed, Dec 20, 2017 at 8:26 AM, Heiland, Randy <heiland at iu.edu> wrote:

> On the ?About ParaView? popup window, there?s a ?Client Information? tab,
> but I can?t seem to copy/paste that info. Is there a way to easily get it?
> I happen to be on OS X, but interested for all OSes.
>
> thanks, Randy
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/1d25947a/attachment.html>

From mathieu.westphal at kitware.com  Wed Dec 20 10:13:40 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 20 Dec 2017 16:13:40 +0100
Subject: [Paraview] getting Client Info
In-Reply-To: <CAB5Fpx7V83GX5jhZ-xXF76EF5pRsY3nm00Q3U=c_xCxCckP1Cw@mail.gmail.com>
References: <A78F1224-F0DB-4792-9649-A6257217535F@iu.edu>
 <CAB5Fpx7V83GX5jhZ-xXF76EF5pRsY3nm00Q3U=c_xCxCckP1Cw@mail.gmail.com>
Message-ID: <CAC2t4UQc71R7DsPoZk+C6MbBrNN3CUPms2LsOk29d9ay9SErvw@mail.gmail.com>

Hello

At least some of these information can be recovered via the PythonShell :


>>> GetParaViewSourceVersion()

'paraview version 5.4.1-1057-g3ffb4b3e0a'

>>> GetParaViewVersion()

5.4


Best,



Mathieu Westphal

On Wed, Dec 20, 2017 at 4:04 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> On my Mac, I can copy individual cells, but not the whole table.
>
> It would be a nice feature. Feel free to write up a feature request in the
> issue tracker: gitlab.kitware.com/paraview/paraview/issues
>
> Thanks,
> Cory
>
> On Wed, Dec 20, 2017 at 8:26 AM, Heiland, Randy <heiland at iu.edu> wrote:
>
>> On the ?About ParaView? popup window, there?s a ?Client Information? tab,
>> but I can?t seem to copy/paste that info. Is there a way to easily get it?
>> I happen to be on OS X, but interested for all OSes.
>>
>> thanks, Randy
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview
>>
>
>
>
> --
> 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
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/d7ff6eae/attachment.html>

From stephen.wornom at inria.fr  Wed Dec 20 10:15:43 2017
From: stephen.wornom at inria.fr (Stephen Wornom)
Date: Wed, 20 Dec 2017 16:15:43 +0100 (CET)
Subject: [Paraview] PV4.10 extracting a surface
In-Reply-To: <1937833022.27238202.1513782441836.JavaMail.zimbra@inria.fr>
Message-ID: <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>

The geometry is a cylinder. 
Using the calculator I do 
rad =sqrt( x**2+y**2) 
I would like to extract the cylinder surface which is rad = 0.1 
I click on threshold then information to see rad 0.1<rad<7 
I click on extract and enter the values min = 0.1 and max 0.1 for rad 
I get this message 
w arning: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/ServerManager/Rendering/vtkSMPVRepresentationProxy.cxx, line 279 

vtkSMPVRepresentationProxy (0x359fd080): Could not determine array range. 
Any ideas to the solution of my problem? 
Thanks in advance, 
Stephen 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/1b8739fd/attachment.html>

From stephen.wornom at inria.fr  Wed Dec 20 10:31:21 2017
From: stephen.wornom at inria.fr (Stephen Wornom)
Date: Wed, 20 Dec 2017 16:31:21 +0100 (CET)
Subject: [Paraview] PV4.10 extracting a surface
In-Reply-To: <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>
References: <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>
Message-ID: <1810826893.27254871.1513783881277.JavaMail.zimbra@inria.fr>

Forgot to mention that the mesh is 3D x,y,z. 
rad =sqrt( x**2+y**2) thus varies with the z-coordinate. 
Stephen 
----- Original Message -----

> From: "Stephen Wornom" <stephen.wornom at inria.fr>
> To: "ParaView" <paraview at paraview.org>
> Sent: Wednesday, December 20, 2017 4:15:43 PM
> Subject: [Paraview] PV4.10 extracting a surface

> The geometry is a cylinder.
> Using the calculator I do
> rad =sqrt( x**2+y**2)
> I would like to extract the cylinder surface which is rad = 0.1
> I click on threshold then information to see rad 0.1<rad<7
> I click on extract and enter the values min = 0.1 and max 0.1 for rad
> I get this message
> w arning: In
> /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/ServerManager/Rendering/vtkSMPVRepresentationProxy.cxx,
> line 279

> vtkSMPVRepresentationProxy (0x359fd080): Could not determine array range.
> Any ideas to the solution of my problem?
> Thanks in advance,
> Stephen

> _______________________________________________
> Powered by www.kitware.com

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

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

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

> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/2aad8d53/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Dec 20 10:32:18 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 20 Dec 2017 10:32:18 -0500
Subject: [Paraview] PV4.10 extracting a surface
In-Reply-To: <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>
References: <1937833022.27238202.1513782441836.JavaMail.zimbra@inria.fr>
 <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>
Message-ID: <CADHSJjB-G7WE+FscxG=0CYWTdyWjMGPvTnYkrZTBdsfvwR80HQ@mail.gmail.com>

I believe you're getting  the warning because the threshold ended up
not producing any output. If you can attach the state/data file, I may
be able to can give more info.

Utkarsh

On Wed, Dec 20, 2017 at 10:15 AM, Stephen Wornom
<stephen.wornom at inria.fr> wrote:
> The geometry is a cylinder.
> Using the calculator I do
> rad =sqrt( x**2+y**2)
> I would like to extract the cylinder surface which is rad = 0.1
> I click on threshold then information to see rad 0.1<rad<7
> I click on extract and enter the values min = 0.1 and max 0.1 for rad
> I get this message
> warning: In
> /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/ServerManager/Rendering/vtkSMPVRepresentationProxy.cxx,
> line 279
>
> vtkSMPVRepresentationProxy (0x359fd080): Could not determine array range.
>
>
> Any ideas to the solution of my problem?
> Thanks in advance,
> Stephen
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>

From andy.bauer at kitware.com  Wed Dec 20 10:46:54 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 20 Dec 2017 10:46:54 -0500
Subject: [Paraview] PV4.10 extracting a surface
In-Reply-To: <CADHSJjB-G7WE+FscxG=0CYWTdyWjMGPvTnYkrZTBdsfvwR80HQ@mail.gmail.com>
References: <1937833022.27238202.1513782441836.JavaMail.zimbra@inria.fr>
 <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>
 <CADHSJjB-G7WE+FscxG=0CYWTdyWjMGPvTnYkrZTBdsfvwR80HQ@mail.gmail.com>
Message-ID: <CAMaOp+GUP=ajdB8snfpPzrKkNJ6x2mCbZYu90VsGin1m84BRAQ@mail.gmail.com>

The Threshold filter works by selecting cells that have cell data in the
selected range. If you're requesting to do thresholding on a point data
array then it will use the point data to cell data filter to create a cell
data array and threshold on that. With this, it's very unlikely that any
cell data ends up with exactly a value of .1. It sounds like what you want
is to use the Contour filter on your rad array.

On Wed, Dec 20, 2017 at 10:32 AM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> I believe you're getting  the warning because the threshold ended up
> not producing any output. If you can attach the state/data file, I may
> be able to can give more info.
>
> Utkarsh
>
> On Wed, Dec 20, 2017 at 10:15 AM, Stephen Wornom
> <stephen.wornom at inria.fr> wrote:
> > The geometry is a cylinder.
> > Using the calculator I do
> > rad =sqrt( x**2+y**2)
> > I would like to extract the cylinder surface which is rad = 0.1
> > I click on threshold then information to see rad 0.1<rad<7
> > I click on extract and enter the values min = 0.1 and max 0.1 for rad
> > I get this message
> > warning: In
> > /home/utkarsh/Dashboards/MyTests/NightlyMaster/
> ParaViewSuperbuild-Release/paraview/src/paraview/
> ParaViewCore/ServerManager/Rendering/vtkSMPVRepresentationProxy.cxx,
> > line 279
> >
> > vtkSMPVRepresentationProxy (0x359fd080): Could not determine array range.
> >
> >
> > Any ideas to the solution of my problem?
> > Thanks in advance,
> > Stephen
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > https://paraview.org/mailman/listinfo/paraview
> >
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/73593d44/attachment.html>

From wascott at sandia.gov  Wed Dec 20 12:49:39 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 20 Dec 2017 17:49:39 +0000
Subject: [Paraview] [EXTERNAL] Re:  getting Client Info
In-Reply-To: <CAB5Fpx7V83GX5jhZ-xXF76EF5pRsY3nm00Q3U=c_xCxCckP1Cw@mail.gmail.com>
References: <A78F1224-F0DB-4792-9649-A6257217535F@iu.edu>
 <CAB5Fpx7V83GX5jhZ-xXF76EF5pRsY3nm00Q3U=c_xCxCckP1Cw@mail.gmail.com>
Message-ID: <abc80a4720c84da39932baa388c99813@ES03AMSNLNT.srn.sandia.gov>

Good idea.  Thanks.  I wrote it up.

https://gitlab.kitware.com/paraview/paraview/issues/17902

Alan



From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cory Quammen
Sent: Wednesday, December 20, 2017 8:04 AM
To: Heiland, Randy <heiland at iu.edu>
Cc: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] getting Client Info

On my Mac, I can copy individual cells, but not the whole table.
It would be a nice feature. Feel free to write up a feature request in the issue tracker: gitlab.kitware.com/paraview/paraview/issues<http://gitlab.kitware.com/paraview/paraview/issues>
Thanks,
Cory

On Wed, Dec 20, 2017 at 8:26 AM, Heiland, Randy <heiland at iu.edu<mailto:heiland at iu.edu>> wrote:
On the ?About ParaView? popup window, there?s a ?Client Information? tab, but I can?t seem to copy/paste that info. Is there a way to easily get it? I happen to be on OS X, but interested for all OSes.

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

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

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

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

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview



--
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/63becbbd/attachment.html>

From chengdi123000 at gmail.com  Wed Dec 20 15:04:19 2017
From: chengdi123000 at gmail.com (=?UTF-8?B?56iL6L+q?=)
Date: Wed, 20 Dec 2017 15:04:19 -0500
Subject: [Paraview] paraview GUI entry point not found in win10,
 compiled with qt 5.10 and vs 2017.
In-Reply-To: <CAB5Fpx6B+hL7JGV-jHQ_Cv6VwkVn_y79eUxEtLGpEa_QPvx=ZQ@mail.gmail.com>
References: <CAMkQf0teAdCrtv2C_0VWwCAGjdMFB3pnDFYS35cSEd3tLYRD8w@mail.gmail.com>
 <CAB5Fpx6B+hL7JGV-jHQ_Cv6VwkVn_y79eUxEtLGpEa_QPvx=ZQ@mail.gmail.com>
Message-ID: <CAMkQf0s74_vM8p2wQ1CO_3pTcHTDQVOxGC2NxLNnmMBgnOZ3pQ@mail.gmail.com>

Thank you! it works! I found it conflict with my miniconda python, which
uses and contains qt5.6.2

Di Cheng
Engineer of Research and Development Center, visiting scholar at University
of Connecticut
China Academy of Aerospace Aerodynamics
Phone @ China: +86-l58Ol5949ll
Phone @ US: +l-86O-6l7-l886

Address: No.17, YunGang West Road, Fengtai District, Beijing, China

Zip Code?100074

On Wed, Dec 20, 2017 at 9:43 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Check your PATH environment variable to make sure nothing is inserting a
> path Qt DLLs different from the Qt with which you built ParaView. Note that
> CMake installs Qt DLLs, so if you have that installed, your PATH may be set
> to point to those DLLs.
>
> HTH,
> Cory
>
> On Tue, Dec 19, 2017 at 7:01 PM, ?? <chengdi123000 at gmail.com> wrote:
>
>> Hi everyone,
>>
>> I just compiled paraview 5.4.1 using vs 2017 in win 10 using qt 5.10.
>> The compilation works but only the `pvserver` works while the
>> `paraview.exe` cannot run.
>>
>> The error is :Entry Point Not Found:
>> [image: Inline image 1]
>> entry point  `?setSelectionModel at QListWidget ... ` could not be located
>> in the dynamic link library `C:\pv54_diy\bin\vtkpqComponents-pv5.4.dll`
>>
>>
>> Here is what I did:
>> - win10 64bit
>> - vs2017 community version
>> - MSMPI  8.1.12438.1091 runtime and SDK
>> - QT 5.10.0 using msvc2017_64/lib
>> - cmake version 3.10.1
>> - Python 3.6.3 :: Anaconda, Inc.
>> - I compiled the boost 1.66.0 myself
>> - I attached the `CMakeCache.txt` file in the email.
>>
>>
>> I tried to solve this problem like this:
>> - locate  `vtkpqComponents` in the vtk source code. I cannot locate where
>> it is, so I cannot find which file is responsible for this, I also cannot
>> identify what this `dll` file is used for.
>> - I searched the maillist archive, cannot find anything useful.
>> - I tried to read the successful build log on DashBoard:
>> https://open.cdash.org/buildSummary.php?buildid=5187747, However, I
>> cannot see essential difference.
>> - I can run `pvserver` and use the official release of paraview 5.4.1 gui
>> client to connect to it. I can open the head dataset and render it using
>> volume mode remotely.
>>
>> Could anyone help me?
>>
>> Di Cheng
>> Engineer of Research and Development Center, visiting scholar at
>> University of Connecticut
>> China Academy of Aerospace Aerodynamics
>> Phone @ China: +86-l58Ol5949ll
>> Phone @ US: +l-86O-6l7-l886
>>
>> Address: No.17, YunGang West Road, Fengtai District, Beijing, China
>> <https://maps.google.com/?q=No.17,+YunGang+West+Road,+Fengtai+District,+Beijing,+China+Zip+Code%EF%BC%9A100074&entry=gmail&source=g>
>>
>> Zip Code?100074
>> <https://maps.google.com/?q=No.17,+YunGang+West+Road,+Fengtai+District,+Beijing,+China+Zip+Code%EF%BC%9A100074&entry=gmail&source=g>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview
>>
>>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/21594c78/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 12306 bytes
Desc: not available
URL: <http://paraview.org/pipermail/paraview/attachments/20171220/21594c78/attachment.png>

From heiland at iu.edu  Wed Dec 20 16:30:55 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Wed, 20 Dec 2017 21:30:55 +0000
Subject: [Paraview] Python shell, os.environ
Message-ID: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>

I noticed the Python shell has a very limited os.environ, e.g.:
>>> os.environ
{'SHELL': '/bin/bash', 'SSH_AUTH_SOCK': '/private/tmp/com.apple.launchd.y86uYmHWFV/Listeners', 'XPC_FLAGS': '0x0', '__CF_USER_TEXT_ENCODING': '0x1F5:0x0:0x0', 'Apple_PubSub_Socket_Render': '/private/tmp/com.apple.launchd.CM4C6EMoE6/Render', 'LOGNAME': 'heiland', 'USER': 'heiland', 'XPC_SERVICE_NAME': 'org.paraview.ParaView.33336', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/Users/heiland', 'DISPLAY': '/private/tmp/com.apple.launchd.4ORv1l0yeN/org.macosforge.xquartz:0', 'TMPDIR': '/var/folders/l6/s467rzgs75n91gdbkn7vr0f40000gn/T/'}
>>> 

I?m guessing this is a security measure? Anyway, is there any way one can use an env var to pass in desirable info to PV?s Python, e.g., a dir path to data to be read by a Programmable Source? Or perhaps there?s some other entirely different way to do this?

thanks, Randy

From heiland at iu.edu  Wed Dec 20 17:50:50 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Wed, 20 Dec 2017 22:50:50 +0000
Subject: [Paraview] Python shell, os.environ
In-Reply-To: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>
References: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>
Message-ID: <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>

Ah, I see ?os? has been hijacked by PV. But something like this seems to accomplish what I want, maybe?

Create a new module for PV:

/Applications/ParaView-5.4.1.app/Contents/Python$ more envs.py
import os
os.environ['PHYSICELL_DATA']=?/fill_in_path?

and then in the PV Python shell, the os.environ will indeed contain this new env var.


> On Dec 20, 2017, at 4:30 PM, Heiland, Randy <heiland at iu.edu> wrote:
> 
> I noticed the Python shell has a very limited os.environ, e.g.:
>>>> os.environ
> {'SHELL': '/bin/bash', 'SSH_AUTH_SOCK': '/private/tmp/com.apple.launchd.y86uYmHWFV/Listeners', 'XPC_FLAGS': '0x0', '__CF_USER_TEXT_ENCODING': '0x1F5:0x0:0x0', 'Apple_PubSub_Socket_Render': '/private/tmp/com.apple.launchd.CM4C6EMoE6/Render', 'LOGNAME': 'heiland', 'USER': 'heiland', 'XPC_SERVICE_NAME': 'org.paraview.ParaView.33336', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/Users/heiland', 'DISPLAY': '/private/tmp/com.apple.launchd.4ORv1l0yeN/org.macosforge.xquartz:0', 'TMPDIR': '/var/folders/l6/s467rzgs75n91gdbkn7vr0f40000gn/T/'}
>>>> 
> 
> I?m guessing this is a security measure? Anyway, is there any way one can use an env var to pass in desirable info to PV?s Python, e.g., a dir path to data to be read by a Programmable Source? Or perhaps there?s some other entirely different way to do this?
> 
> thanks, Randy
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview


From utkarsh.ayachit at kitware.com  Wed Dec 20 21:16:20 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 20 Dec 2017 21:16:20 -0500
Subject: [Paraview] Python shell, os.environ
In-Reply-To: <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>
References: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>
 <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>
Message-ID: <CADHSJjA7=x0+4PLTAQ_GEwmsjprmk58mGvP57JgHjSjesn+gug@mail.gmail.com>

Randy,

No, `os` hasn't been hijacked by PV.  Here's what I get on Linux.

./bin/pvpython
Python 3.5.2 (default, Nov 23 2017, 16:37:01)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.environ["FOO"]
'12'


I suspect it's something to do with App bundles on macOS and what
environment variables they see based on how you launch them. I can't
remember that of the top of my head, but that's where I'd start
looking.

Utkarsh


On Wed, Dec 20, 2017 at 5:50 PM, Heiland, Randy <heiland at iu.edu> wrote:
> Ah, I see ?os? has been hijacked by PV. But something like this seems to accomplish what I want, maybe?
>
> Create a new module for PV:
>
> /Applications/ParaView-5.4.1.app/Contents/Python$ more envs.py
> import os
> os.environ['PHYSICELL_DATA']=?/fill_in_path?
>
> and then in the PV Python shell, the os.environ will indeed contain this new env var.
>
>
>> On Dec 20, 2017, at 4:30 PM, Heiland, Randy <heiland at iu.edu> wrote:
>>
>> I noticed the Python shell has a very limited os.environ, e.g.:
>>>>> os.environ
>> {'SHELL': '/bin/bash', 'SSH_AUTH_SOCK': '/private/tmp/com.apple.launchd.y86uYmHWFV/Listeners', 'XPC_FLAGS': '0x0', '__CF_USER_TEXT_ENCODING': '0x1F5:0x0:0x0', 'Apple_PubSub_Socket_Render': '/private/tmp/com.apple.launchd.CM4C6EMoE6/Render', 'LOGNAME': 'heiland', 'USER': 'heiland', 'XPC_SERVICE_NAME': 'org.paraview.ParaView.33336', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/Users/heiland', 'DISPLAY': '/private/tmp/com.apple.launchd.4ORv1l0yeN/org.macosforge.xquartz:0', 'TMPDIR': '/var/folders/l6/s467rzgs75n91gdbkn7vr0f40000gn/T/'}
>>>>>
>>
>> I?m guessing this is a security measure? Anyway, is there any way one can use an env var to pass in desirable info to PV?s Python, e.g., a dir path to data to be read by a Programmable Source? Or perhaps there?s some other entirely different way to do this?
>>
>> thanks, Randy
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview

From antech777 at gmail.com  Thu Dec 21 01:03:43 2017
From: antech777 at gmail.com (Andrew)
Date: Thu, 21 Dec 2017 09:03:43 +0300
Subject: [Paraview] PV4.10 extracting a surface
In-Reply-To: <CAMaOp+GUP=ajdB8snfpPzrKkNJ6x2mCbZYu90VsGin1m84BRAQ@mail.gmail.com>
References: <1937833022.27238202.1513782441836.JavaMail.zimbra@inria.fr>
 <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>
 <CADHSJjB-G7WE+FscxG=0CYWTdyWjMGPvTnYkrZTBdsfvwR80HQ@mail.gmail.com>
 <CAMaOp+GUP=ajdB8snfpPzrKkNJ6x2mCbZYu90VsGin1m84BRAQ@mail.gmail.com>
Message-ID: <CANMVBVzPJDRXK7gq1kQqfyT75Fr9ueLi_Xnm+4NV6=5gUj=g5A@mail.gmail.com>

Hello. Possibly the Slice filter with "Cylinder" and "Crinkle slice"
options will produce the required result (I checked in ParaView 5.2).

2017-12-20 18:46 GMT+03:00 Andy Bauer <andy.bauer at kitware.com>:

> The Threshold filter works by selecting cells that have cell data in the
> selected range. If you're requesting to do thresholding on a point data
> array then it will use the point data to cell data filter to create a cell
> data array and threshold on that. With this, it's very unlikely that any
> cell data ends up with exactly a value of .1. It sounds like what you want
> is to use the Contour filter on your rad array.
>
> On Wed, Dec 20, 2017 at 10:32 AM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> I believe you're getting  the warning because the threshold ended up
>> not producing any output. If you can attach the state/data file, I may
>> be able to can give more info.
>>
>> Utkarsh
>>
>> On Wed, Dec 20, 2017 at 10:15 AM, Stephen Wornom
>> <stephen.wornom at inria.fr> wrote:
>> > The geometry is a cylinder.
>> > Using the calculator I do
>> > rad =sqrt( x**2+y**2)
>> > I would like to extract the cylinder surface which is rad = 0.1
>> > I click on threshold then information to see rad 0.1<rad<7
>> > I click on extract and enter the values min = 0.1 and max 0.1 for rad
>> > I get this message
>> > warning: In
>> > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuper
>> build-Release/paraview/src/paraview/ParaViewCore/
>> ServerManager/Rendering/vtkSMPVRepresentationProxy.cxx,
>> > line 279
>> >
>> > vtkSMPVRepresentationProxy (0x359fd080): Could not determine array
>> range.
>> >
>> >
>> > Any ideas to the solution of my problem?
>> > Thanks in advance,
>> > Stephen
>> >
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at:
>> > http://paraview.org/Wiki/ParaView
>> >
>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > https://paraview.org/mailman/listinfo/paraview
>> >
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/5e749c00/attachment.html>

From heiland at iu.edu  Thu Dec 21 07:58:29 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Thu, 21 Dec 2017 12:58:29 +0000
Subject: [Paraview] Python shell, os.environ
In-Reply-To: <CADHSJjA7=x0+4PLTAQ_GEwmsjprmk58mGvP57JgHjSjesn+gug@mail.gmail.com>
References: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>
 <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>
 <CADHSJjA7=x0+4PLTAQ_GEwmsjprmk58mGvP57JgHjSjesn+gug@mail.gmail.com>
Message-ID: <26EE4C63-40B7-4EB5-95C1-8FCE6F105AA3@iu.edu>

Thanks Utkarsh. Yes, running pvpython from a Terminal is indeed different from running the Python Shell in the PV app (on OS X anyway), in terms of os.environ.

Regardless, hopefully my proposed approach of creating an envs.py module in the PV installation will work. I?m just looking for the simplest solution for our users.

-Randy
 
> On Dec 20, 2017, at 9:16 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
> 
> Randy,
> 
> No, `os` hasn't been hijacked by PV.  Here's what I get on Linux.
> 
> ./bin/pvpython
> Python 3.5.2 (default, Nov 23 2017, 16:37:01)
> [GCC 5.4.0 20160609] on linux
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import os
>>>> os.environ["FOO"]
> '12'
> 
> 
> I suspect it's something to do with App bundles on macOS and what
> environment variables they see based on how you launch them. I can't
> remember that of the top of my head, but that's where I'd start
> looking.
> 
> Utkarsh
> 
> 
> On Wed, Dec 20, 2017 at 5:50 PM, Heiland, Randy <heiland at iu.edu> wrote:
>> Ah, I see ?os? has been hijacked by PV. But something like this seems to accomplish what I want, maybe?
>> 
>> Create a new module for PV:
>> 
>> /Applications/ParaView-5.4.1.app/Contents/Python$ more envs.py
>> import os
>> os.environ['PHYSICELL_DATA']=?/fill_in_path?
>> 
>> and then in the PV Python shell, the os.environ will indeed contain this new env var.
>> 
>> 
>>> On Dec 20, 2017, at 4:30 PM, Heiland, Randy <heiland at iu.edu> wrote:
>>> 
>>> I noticed the Python shell has a very limited os.environ, e.g.:
>>>>>> os.environ
>>> {'SHELL': '/bin/bash', 'SSH_AUTH_SOCK': '/private/tmp/com.apple.launchd.y86uYmHWFV/Listeners', 'XPC_FLAGS': '0x0', '__CF_USER_TEXT_ENCODING': '0x1F5:0x0:0x0', 'Apple_PubSub_Socket_Render': '/private/tmp/com.apple.launchd.CM4C6EMoE6/Render', 'LOGNAME': 'heiland', 'USER': 'heiland', 'XPC_SERVICE_NAME': 'org.paraview.ParaView.33336', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/Users/heiland', 'DISPLAY': '/private/tmp/com.apple.launchd.4ORv1l0yeN/org.macosforge.xquartz:0', 'TMPDIR': '/var/folders/l6/s467rzgs75n91gdbkn7vr0f40000gn/T/'}
>>>>>> 
>>> 
>>> I?m guessing this is a security measure? Anyway, is there any way one can use an env var to pass in desirable info to PV?s Python, e.g., a dir path to data to be read by a Programmable Source? Or perhaps there?s some other entirely different way to do this?
>>> 
>>> thanks, Randy
>>> _______________________________________________
>>> Powered by www.kitware.com
>>> 
>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>> 
>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>>> 
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> https://paraview.org/mailman/listinfo/paraview
>> 
>> _______________________________________________
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>> 
>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> 
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview


From ben.boeckel at kitware.com  Thu Dec 21 09:34:03 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 21 Dec 2017 09:34:03 -0500
Subject: [Paraview] Python shell, os.environ
In-Reply-To: <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>
References: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>
 <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>
Message-ID: <20171221143403.GA18094@megas.kitware.com>

On Wed, Dec 20, 2017 at 22:50:50 +0000, Heiland, Randy wrote:
> Ah, I see ?os? has been hijacked by PV. But something like this seems
> to accomplish what I want, maybe?
> 
> Create a new module for PV:
> 
> /Applications/ParaView-5.4.1.app/Contents/Python$ more envs.py
> import os
> os.environ['PHYSICELL_DATA']=?/fill_in_path?
> 
> and then in the PV Python shell, the os.environ will indeed contain
> this new env var.

This can't be part of the package though since if it is installed
globally, users may not have write access to the .app directory.

It seems the way to do this is along these lines (in short, Apple isn't
making what you want to do easy):

    https://superuser.com/questions/476752/setting-environment-variables-in-os-x-for-gui-applications#541068
    https://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x/32405815#32405815

There seems to have been something like `~/.launchd.conf` at some point
and `~/.MacOSX/environment.plist` before that, but those has been
deprecated and no longer work.

--Ben

From grothausmann.roman at mh-hannover.de  Thu Dec 21 10:06:15 2017
From: grothausmann.roman at mh-hannover.de (Grothausmann, Roman Dr.)
Date: Thu, 21 Dec 2017 16:06:15 +0100
Subject: [Paraview] loading multiple state-files without hiding and
 resetting already loaded objects
In-Reply-To: <CAB5Fpx4Z8byiUEwteVfkb_DeZgiO6AbS5PaCqOYC9FmyMw8Q-g@mail.gmail.com>
References: <fc803504-8b2e-a854-ab34-a23fe09a8e81@mh-hannover.de>
 <CAB5Fpx7W04E6iE5FiU1buFtzKLnGuUz7s-1BV2TJzWx+7WdSTg@mail.gmail.com>
 <224968d6-0c63-b455-a190-366d6d39753d@mh-hannover.de>
 <CAB5Fpx5Pq4Ym+qakwQHifMeT-PAP2k3T+8DeuPCxOyE3sfsNcg@mail.gmail.com>
 <5b4ae0e6-cb38-f305-cea5-ba8b1632c715@mh-hannover.de>
 <194fcd7d-aacd-8c74-ce21-dec670dc6e3e@mh-hannover.de>
 <CAB5Fpx4Z8byiUEwteVfkb_DeZgiO6AbS5PaCqOYC9FmyMw8Q-g@mail.gmail.com>
Message-ID: <27bccc1f-9b05-cb8c-d073-bbd2eb9d7041@mh-hannover.de>

Hi Cory,

On 06/12/17 23:06, Cory Quammen wrote:
> Sorry I failed to follow up. Did you find a solution to this problem?

Many thanks for your reply. No, and I'm still stuck. I tried Your suggestion to 
remove [0] 
(https://github.com/romangrothausmann/ParaView_scripts/commit/e40d1016d698ee363500bb9bf04f29add89b99dd), 
which changed the reported error from:

   File 
"/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", 
line 375, in SetPropertyWithName
     prop.SetData(arg)
   File 
"/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", 
line 803, in SetData
     raise RuntimeError("This property requires %d values." % 
self.GetNumberOfElements())
RuntimeError: This property requires 3 values.

to:

   File 
"/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", 
line 375, in SetPropertyWithName
     prop.SetData(arg)
   File 
"/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py", 
line 1296, in SetData
     self.SMProperty.AddProxy(value_proxy)
TypeError: AddProxy argument 1: method requires a VTK object

Any ideas on this?
Would You say it is a general problem in the py-code or could it be caused by 
the content of the PVSMs I'm trying to combine?

Many thanks for looking into this.
Roman

> 
> This line in your script looks funny to me:
> 
> d[props] = pvs.GetProperty(repr, props[0])
> 
> Shouldn't props[0] just be props?
> 
> Thanks,
> Cory
> 
> On Fri, Nov 10, 2017 at 10:28 AM, Grothausmann, Roman Dr.
> <grothausmann.roman at mh-hannover.de> wrote:
>> Dear Cory,
>>
>> On 15/09/17 15:27, Grothausmann, Roman Dr. wrote:
>>>
>>> On 15/09/17 15:14, Cory Quammen wrote:
>>>>
>>>> Put a ** in front of reppro[i], e.g.,
>>>>
>>>> pvs.SetProperties(repr, **reppro[i])
>>>
>>> Hm, I now get:
>>> TypeError: SetProperties() argument after ** must be a mapping, not list
>>> Do I have to store the dict of object properties in another dict instead
>>> of a list?
>>
>>
>> With a dict of dicts
>> https://github.com/romangrothausmann/ParaView_scripts/commit/3b309cc603433f02afc3e50656bd99f8b7cd0aa8#diff-2804420278bfff084788b82c715c452e
>> I get:
>>
>>    File "/net/home/grothama/paraview/scripts/pvsm-multi.py", line 64, in main
>>      pvs.SetProperties(repr, **reppro[i]);
>>    File
>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/simple.py",
>> line 568, in SetProperties
>>      setattr(proxy, param, params[param])
>>    File
>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
>> line 317, in __setattr__
>>      setter(self, value)
>>    File
>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
>> line 2528, in setProperty
>>      return self.SetPropertyWithName(propName, value)
>>    File
>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
>> line 375, in SetPropertyWithName
>>      prop.SetData(arg)
>>    File
>> "/opt/paraview-5.3.0_GL1/lib/paraview-5.3/site-packages/paraview/servermanager.py",
>> line 803, in SetData
>>      raise RuntimeError("This property requires %d values." %
>> self.GetNumberOfElements())
>> RuntimeError: This property requires 3 values.
>>
>> Any ideas what could still be wrong?
>>
>>
>>>>> On 07/09/17 23:37, Cory Quammen wrote:
>>>>>>
>>>>>>
>>>>>> Hi Roman,
>>>>>>
>>>>>> It turns out ParaView was not designed for this use case because of
>>>>>> certain difficulties discussed here:
>>>>>>
>>>>>> https://gitlab.kitware.com/paraview/paraview/issues/17442
>>>>>>
>>>>>> In your Python script, you could manually cash all the properties of
>>>>>> the existing representations and restore them after loading the most
>>>>>> recent state file.
>>>>>>
>>>>>> The functions
>>>>>>
>>>>>> reprs = GetRepresentations()
>>>>>> repr = reprs.values()[0]
>>>>>> props = repr.ListProperties()
>>>>>> GetProperty(repr, props[0])
>>>>>>
>>>>>> would be helpful for this.
>>>>>>
>>>>>> Cory
>>>>>>
>>>>>>
>>>>>> On Mon, Sep 4, 2017 at 8:42 AM, Grothausmann, Roman Dr.
>>>>>> <grothausmann.roman at mh-hannover.de> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Dear mailing list members,
>>>>>>>
>>>>>>>
>>>>>>> It seems that PV (and paraview.simple.LoadState) by default hides
>>>>>>> already
>>>>>>> loaded objects (and resets e.g. their coloring) when another
>>>>>>> state-file
>>>>>>> is
>>>>>>> loaded.
>>>>>>> Is there a way to load multiple state-files after one another without
>>>>>>> hiding
>>>>>>> and resetting already existent objects? I.e. a way to concatenate
>>>>>>> multiple
>>>>>>> state-files and leave their objects in the state as they got loaded
>>>>>>> (e.g.
>>>>>>> colored, hidden/visible)?
>>>>>>> I do understand that loading a new state-file will reset the camera,
>>>>>>> but
>>>>>>> not
>>>>>>> the rest.
>>>>>>> Here's my initial attempt to achieve this with pvpython:
>>>>>>>
>>>>>>>
>>>>>>> https://github.com/romangrothausmann/ParaView_scripts/blob/90eb4ca8499070bed941d50b89ebea82fd6a9e23/pvsm-multi.py
>>>>>>>
>>>>>>> Any help or hints are very much appreciated
>>>>>>> Roman
>>>>>>>
>>>>>>> --
>>>>>>> Dr. Roman Grothausmann
>>>>>>>
>>>>>>> Tomographie und Digitale Bildverarbeitung
>>>>>>> Tomography and Digital Image Analysis
>>>>>>>
>>>>>>> Medizinische Hochschule Hannover
>>>>>>> Institut f?r Funktionelle und Angewandte Anatomie
>>>>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland
>>>>>>>
>>>>>>> Tel. +49 511 532-2900
>>>>>>> grothausmann.roman at mh-hannover.de
>>>>>>> http://www.mh-hannover.de/anatomie.html
>>>>>>> _______________________________________________
>>>>>>> Powered by www.kitware.com
>>>>>>>
>>>>>>> Visit other Kitware open-source projects at
>>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>>
>>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>>
>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>>>>
>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Dr. Roman Grothausmann
>>>>>
>>>>> Tomographie und Digitale Bildverarbeitung
>>>>> Tomography and Digital Image Analysis
>>>>>
>>>>> Medizinische Hochschule Hannover
>>>>> Institut f?r Funktionelle und Angewandte Anatomie
>>>>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland
>>>>>
>>>>> Tel. +49 511 532-2900
>>>>> grothausmann.roman at mh-hannover.de
>>>>> http://www.mh-hannover.de/anatomie.html
>>>>
>>>>
>>>>
>>>>
>>>
>>
>> --
>> Dr. Roman Grothausmann
>>
>> Tomographie und Digitale Bildverarbeitung
>> Tomography and Digital Image Analysis
>>
>> Medizinische Hochschule Hannover
>> Institut f?r Funktionelle und Angewandte Anatomie
>> OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland
>>
>> Tel. +49 511 532-2900
>> grothausmann.roman at mh-hannover.de
>> http://www.mh-hannover.de/anatomie.html
> 
> 
> 

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Medizinische Hochschule Hannover
Institut f?r Funktionelle und Angewandte Anatomie
OE 4120, Carl-Neuberg-Str. 1, 30625 Hannover, Deutschland

Tel. +49 511 532-2900
grothausmann.roman at mh-hannover.de
http://www.mh-hannover.de/anatomie.html

From andrey.andreyev at corvidtec.com  Thu Dec 21 10:08:38 2017
From: andrey.andreyev at corvidtec.com (Andreyev, Andrey)
Date: Thu, 21 Dec 2017 10:08:38 -0500
Subject: [Paraview] XDMF Part Grids sharing the same Geometry array
Message-ID: <CAD0qPxSmaFABhn9Sf7hsen0=1A7QHewAi2_hWPMw5YKA1bNDig@mail.gmail.com>

Hello,

I am currently converting our FEA code to write out a format that Paraview
can read natively. I chose XDMF because it seems like a fairly flexible
format. I have a question with regards to topology/geometry.

I need to split up my FEA mesh according to the part the elements belong to
and would like to keep XYZ (geometry) array shared between all the parts as
they're just coordinate data and just have the connectivity point to the
appropriate node. I have done this, but the problem is that Paraview seems
to load the entire geometry array instead of just the nodes that belong to
the part according to the connectivity. Is there a way to fix this behavior
or am I stuck also creating a separate geometry data set for each part?

Thank you!
Andrey

-- 

Andrey V. Andreyev
CORVID Technologies
145 Overhill Dr
Mooresville, NC 28117
704-799-6944 x172
andrey.andreyev at corvidtec.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/98d30c45/attachment.html>

From heiland at iu.edu  Thu Dec 21 10:14:01 2017
From: heiland at iu.edu (Heiland, Randy)
Date: Thu, 21 Dec 2017 15:14:01 +0000
Subject: [Paraview] Python shell, os.environ
In-Reply-To: <20171221143403.GA18094@megas.kitware.com>
References: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>
 <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>
 <20171221143403.GA18094@megas.kitware.com>
Message-ID: <0E572B2D-E18D-4B7D-A3D2-49FE5A41A9D6@iu.edu>


> On Dec 21, 2017, at 9:34 AM, Ben Boeckel <ben.boeckel at kitware.com> wrote:
> 
> On Wed, Dec 20, 2017 at 22:50:50 +0000, Heiland, Randy wrote:
>> Ah, I see ?os? has been hijacked by PV. But something like this seems
>> to accomplish what I want, maybe?
>> 
>> Create a new module for PV:
>> 
>> /Applications/ParaView-5.4.1.app/Contents/Python$ more envs.py
>> import os
>> os.environ['PHYSICELL_DATA']=?/fill_in_path?
>> 
>> and then in the PV Python shell, the os.environ will indeed contain
>> this new env var.
> 
> This can't be part of the package though since if it is installed
> globally, users may not have write access to the .app directory.
> 
> It seems the way to do this is along these lines (in short, Apple isn't
> making what you want to do easy):
> 
>    https://superuser.com/questions/476752/setting-environment-variables-in-os-x-for-gui-applications#541068
>    https://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x/32405815#32405815
> 
> There seems to have been something like `~/.launchd.conf` at some point
> and `~/.MacOSX/environment.plist` before that, but those has been
> deprecated and no longer work.
> 
> ?Ben

Thanks Ben.  You?re right, of course. Moreover, my idea for having (non-admin) users install additional Python modules (e.g., scipy) into PV?s dir, is a not going to go well.

Do we at least agree that if I ask users to start PV from the Terminal, PV?s Python will then pick up the user?s env vars?

-Randy  (who?s really liking: ?Step 1: Become an Admin? :)


From fbisetti at gmail.com  Thu Dec 21 11:02:12 2017
From: fbisetti at gmail.com (Fabrizio Bisetti)
Date: Thu, 21 Dec 2017 10:02:12 -0600
Subject: [Paraview] Confirming that pvserver runs with OSMesa + OpenSWR
 driver on cpu only compute nodes
Message-ID: <3F987627-6816-4466-8EDB-BC3C4DBDF9D4@gmail.com>

Hello there:

I've successfully built and installed the following OSMesa rendering stack (from source) for use on CPU only compute nodes of a small cluster

I've then built Paraview 5.4.0 (from source). The pvserver runs on a compute node and we connect to it from a remote Paraview client via forward connection with SSH tunneling.

I am having trouble confirming which driver the pvserver uses for rendering. My understanding is that OSMesa gets compiled with various cpu-based driver options, i.e. soft pipe (classic OSMesa), llvmpipe, and swr.

I would like to ensure that swr (OpenSWR) is being used.

Note that one complicating factor is that the CPU-based compute nodes do not have any X installed and I've compiled only OSMesa (see below). Thus, I cannot compile the GLUT based utility glinfo or gears, which could possibly tell me how the rendering is done.

Finally, while it seems that one can invoke paraview with a switch --mesa-swr-avx2, I am not sure that can be done with pvserver.

Also, even then, how would I confirm this is which driver is being used?

Thank you for any help/pointers.

Fabrizio




**HARDWARE**

Each compute node features two (x2) Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz for a total of 28 cores. The compute nodes do not have a GPU.

**SOFTWARE STACK**

Everything is compiled with gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) on a Linux 3.10.0-514.el7.x86_64 (Centos 7).

Here is the cpu-based rendering stack

1) LLVM 5.0.0

cmake3 -G "Unix Makefiles"  \
       -DCMAKE_BUILD_TYPE=Release \
       -DLLVM_TARGETS_TO_BUILD=X86 \
       -DLLVM_INSTALL_UTILS=TRUE \
       -DLLVM_ENABLE_RTTI=TRUE \
       -DBUILD_SHARED_LIBS=TRUE \
       -DCMAKE_INSTALL_PREFIX=$INSTALLDIR \
       ../llvm-5.0.0.src

2) Mesa3D 17.3.0

Note that the compute nodes do not have any X servers (X11) nor any other OpenGL implementation (e.g. repo based from a yum install)

./configure \
    --disable-xvmc \
    --disable-glx \
    --disable-dri \
    --with-dri-drivers= \
    --with-gallium-drivers=swrast,swr \
    --enable-texture-float \
    --disable-egl \
    --disable-gbm \
    --with-platforms= \
    --enable-gallium-osmesa \
    --enable-llvm \
    --prefix=$INSTALLDIR

3) GLU 9.0.0

SITE_MESA_LIB=/path/to/mesa/install/above

PKG_CONFIG_PATH="$SITE_MESA_LIB/pkgconfig" \
OSMESA_LIBS="-L$SITE_MESA_LIB -lOSMesa" \
    ./configure --prefix=$INSTALLDIR \
    --enable-osmesa \
    --enable-shared

4) ParaView 5.4.0

I've configured the basic ParaView build as recommended.
I am using OpenMPI 2.1.0 compiled with the system gcc.

The additional OSMesa options are as below:

VTK_USE_X=OFF
VTK_USE_OFFSCREEN:BOOL=ON

OPENGL_INCLUDE_DIR=/path/to/mesa/install/above/include
OPENGL_gl_LIBRARY:FILEPATH=/path/to/mesa/install/above/lib/libOSMesa.so
OPENGL_glu_LIBRARY:FILEPATH=/path/to/glu/install/above/lib/libGLU.so

VTK_OPENGL_HAS_OSMESA:BOOL=ON
OSMESA_INCLUDE_DIR:PATH=/path/to/mesa/install/above/include
OSMESA_LIBRARY:FILEPATH=/path/to/mesa/install/above/lib/libOSMesa.so

Note that I've set everything to point to the OSMesa install directory.

From timothy.a.beach at nasa.gov  Thu Dec 21 11:01:19 2017
From: timothy.a.beach at nasa.gov (Beach, Timothy A. (GRC-LTE0)[Vantage Partners, LLC])
Date: Thu, 21 Dec 2017 16:01:19 +0000
Subject: [Paraview] Paraview Custom Reader  issue - OS X 10.12.6
Message-ID: <967E249E-BECE-419A-B5F5-5AD9A0246DD0@contoso.com>

For some time I?ve used a custom reader in Paraview.  I?m having issues with my recently issued mac.   In the past I?ve recompiled the entire code but I?m having issues with QT so I?m trying to just get my reader working as a plugin as per the instructions on the paraview.org page ?ParaView/Plugin HowTo?.  I thought that would be easier.  I?ve been unable to get past the following cmake  error.  I?m not very knowledgable on cmake . I wish I had time to  figure it out but I don?t. Any help with the following would be apprecitated   Thanks ? I wasn?t   the best time to be given a new computer. Tim

CMake Error at CMakeLists.txt:1 (FIND_PACKAGE):
By not providing "FindParaView.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "ParaView",
but CMake did not find one.

Could not find a package configuration file provided by "ParaView" with any
of the following names:

ParaViewConfig.cmake
paraview-config.cmake

Add the installation prefix of "ParaView" to CMAKE_PREFIX_PATH or set
"ParaView_DIR" to a directory containing one of the above files. If
"ParaView" provides a separate development package or SDK, be sure it has
been installed.

My CmakeList.txt ? which may not be correct.  My reader is a clone of the Plot3d Reader
FIND_PACKAGE(ParaView REQUIRED)
INCLUDE(${PARAVIEW_USE_FILE})
ADD_PARAVIEW_PLUGIN(TURBO_Reader "1.0"
   SERVER_MANAGER_XML TURBO_Reader.xml
   SERVER_MANAGER_SOURCES vtkMultiBlockTURBOReader.cxx vtkMultiBlockTURBOReaderInternals.cxx
   REQUIRED_ON_SERVER)

set_source_files_properties(
  vtkMultiBlockTURBOReaderInternals
  PROPERTIES
    WRAP_EXCLUDE 1
    WRAP_EXCLUDE_PYTHON 1
  )


Thanks
Tim


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/7ec002ea/attachment.html>

From mathieu.westphal at kitware.com  Thu Dec 21 11:30:33 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Thu, 21 Dec 2017 17:30:33 +0100
Subject: [Paraview] Paraview Custom Reader issue - OS X 10.12.6
In-Reply-To: <967E249E-BECE-419A-B5F5-5AD9A0246DD0@contoso.com>
References: <967E249E-BECE-419A-B5F5-5AD9A0246DD0@contoso.com>
Message-ID: <CAC2t4USus2NVu-JUg=X++Z_F6m18c9JDbNY-MMoPBwyzbCfAHw@mail.gmail.com>

Hello

You have to set ParaView_DIR to your paraview build directory. You have to
do that in cmake, ccmake or cmake-gui.

Best,

Mathieu Westphal

On Thu, Dec 21, 2017 at 5:01 PM, Beach, Timothy A. (GRC-LTE0)[Vantage
Partners, LLC] <timothy.a.beach at nasa.gov> wrote:

> For some time I?ve used a custom reader in Paraview.  I?m having issues
> with my recently issued mac.   In the past I?ve recompiled the entire code
> but I?m having issues with QT so I?m trying to just get my reader working
> as a plugin as per the instructions on the paraview.org page ?ParaView/Plugin
> HowTo?.  I thought that would be easier.  I?ve been unable to get past the
> following cmake  error.  I?m not very knowledgable on cmake . I wish I had
> time to  figure it out but I don?t. Any help with the following would be
> apprecitated   Thanks ? I wasn?t   the best time to be given a new
> computer. Tim
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *CMake Error at CMakeLists.txt:1 (FIND_PACKAGE): By not providing
> "FindParaView.cmake" in CMAKE_MODULE_PATH this project has asked CMake to
> find a package configuration file provided by "ParaView", but CMake did not
> find one. Could not find a package configuration file provided by
> "ParaView" with any of the following names: ParaViewConfig.cmake
> paraview-config.cmake Add the installation prefix of "ParaView" to
> CMAKE_PREFIX_PATH or set "ParaView_DIR" to a directory containing one of
> the above files. If "ParaView" provides a separate development package or
> SDK, be sure it has been installed.*
>
>
>
> My CmakeList.txt ? which may not be correct.  My reader is a clone of the
> Plot3d Reader
>
> *FIND_PACKAGE(ParaView REQUIRED)*
>
> *INCLUDE(${PARAVIEW_USE_FILE})*
>
> *ADD_PARAVIEW_PLUGIN(TURBO_Reader "1.0" *
>
> *   SERVER_MANAGER_XML TURBO_Reader.xml*
>
> *   SERVER_MANAGER_SOURCES vtkMultiBlockTURBOReader.cxx
> vtkMultiBlockTURBOReaderInternals.cxx*
>
> *   REQUIRED_ON_SERVER)*
>
>
>
> *set_source_files_properties(*
>
> *  vtkMultiBlockTURBOReaderInternals*
>
> *  PROPERTIES*
>
> *    WRAP_EXCLUDE 1*
>
> *    WRAP_EXCLUDE_PYTHON 1*
>
> *  )*
>
>
>
>
>
> Thanks
>
> Tim
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/02d79e97/attachment.html>

From mathieu.westphal at kitware.com  Thu Dec 21 11:51:45 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Thu, 21 Dec 2017 17:51:45 +0100
Subject: [Paraview] Paraview Custom Reader issue - OS X 10.12.6
In-Reply-To: <3FC21C8C-3AD6-4D8B-8BE8-DF01C32A0EE6@nasa.gov>
References: <967E249E-BECE-419A-B5F5-5AD9A0246DD0@contoso.com>
 <CAC2t4USus2NVu-JUg=X++Z_F6m18c9JDbNY-MMoPBwyzbCfAHw@mail.gmail.com>
 <3FC21C8C-3AD6-4D8B-8BE8-DF01C32A0EE6@nasa.gov>
Message-ID: <CAC2t4US5wDJi_bnrSkUi_Ty0mShhiH06RghxrQsUbToG1VPwtg@mail.gmail.com>

Hello

To build a paraview plugin, one need first to build paraview from the
sources.
https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Writing_Plugins

Best,

Mathieu Westphal

On Thu, Dec 21, 2017 at 5:49 PM, Beach, Timothy A. (GRC-LTE0)[Vantage
Partners, LLC] <timothy.a.beach at nasa.gov> wrote:

> Thanks,
>
>
>
> I thought the idea of a plugin was that you make a shared library    to
> load int an existing executable.   At this point I don?t have a paraview
> build directory,  just the binary for version 5.4.  Am I mixing apples and
> oranges here.
>
> Thanks
>
> Tim
>
>
>
> *From: *Mathieu Westphal <mathieu.westphal at kitware.com>
> *Date: *Thursday, December 21, 2017 at 11:31 AM
> *To: *"Beach, Timothy A. (GRC-LTE0)[Vantage Partners, LLC]" <
> timothy.a.beach at nasa.gov>
> *Cc: *"paraview at paraview.org" <paraview at paraview.org>
> *Subject: *Re: [Paraview] Paraview Custom Reader issue - OS X 10.12.6
>
>
>
> Hello
>
> You have to set ParaView_DIR to your paraview build directory. You have to
> do that in cmake, ccmake or cmake-gui.
>
> Best,
>
>
> Mathieu Westphal
>
>
>
> On Thu, Dec 21, 2017 at 5:01 PM, Beach, Timothy A. (GRC-LTE0)[Vantage
> Partners, LLC] <timothy.a.beach at nasa.gov> wrote:
>
> For some time I?ve used a custom reader in Paraview.  I?m having issues
> with my recently issued mac.   In the past I?ve recompiled the entire code
> but I?m having issues with QT so I?m trying to just get my reader working
> as a plugin as per the instructions on the paraview.org page ?ParaView/Plugin
> HowTo?.  I thought that would be easier.  I?ve been unable to get past the
> following cmake  error.  I?m not very knowledgable on cmake . I wish I had
> time to  figure it out but I don?t. Any help with the following would be
> apprecitated   Thanks ? I wasn?t   the best time to be given a new
> computer. Tim
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *CMake Error at CMakeLists.txt:1 (FIND_PACKAGE): By not providing
> "FindParaView.cmake" in CMAKE_MODULE_PATH this project has asked CMake to
> find a package configuration file provided by "ParaView", but CMake did not
> find one. Could not find a package configuration file provided by
> "ParaView" with any of the following names: ParaViewConfig.cmake
> paraview-config.cmake Add the installation prefix of "ParaView" to
> CMAKE_PREFIX_PATH or set "ParaView_DIR" to a directory containing one of
> the above files. If "ParaView" provides a separate development package or
> SDK, be sure it has been installed.*
>
>
>
> My CmakeList.txt ? which may not be correct.  My reader is a clone of the
> Plot3d Reader
>
> *FIND_PACKAGE(ParaView REQUIRED)*
>
> *INCLUDE(${PARAVIEW_USE_FILE})*
>
> *ADD_PARAVIEW_PLUGIN(TURBO_Reader "1.0" *
>
> *   SERVER_MANAGER_XML TURBO_Reader.xml*
>
> *   SERVER_MANAGER_SOURCES vtkMultiBlockTURBOReader.cxx
> vtkMultiBlockTURBOReaderInternals.cxx*
>
> *   REQUIRED_ON_SERVER)*
>
>
>
> *set_source_files_properties(*
>
> *  vtkMultiBlockTURBOReaderInternals*
>
> *  PROPERTIES*
>
> *    WRAP_EXCLUDE 1*
>
> *    WRAP_EXCLUDE_PYTHON 1*
>
> *  )*
>
>
>
>
>
> Thanks
>
> Tim
>
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/f85af45d/attachment.html>

From sebastien.jourdain at kitware.com  Thu Dec 21 14:01:24 2017
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Thu, 21 Dec 2017 12:01:24 -0700
Subject: [Paraview] PV4.10 extracting a surface
In-Reply-To: <CANMVBVzPJDRXK7gq1kQqfyT75Fr9ueLi_Xnm+4NV6=5gUj=g5A@mail.gmail.com>
References: <1937833022.27238202.1513782441836.JavaMail.zimbra@inria.fr>
 <2125907590.27245212.1513782943775.JavaMail.zimbra@inria.fr>
 <CADHSJjB-G7WE+FscxG=0CYWTdyWjMGPvTnYkrZTBdsfvwR80HQ@mail.gmail.com>
 <CAMaOp+GUP=ajdB8snfpPzrKkNJ6x2mCbZYu90VsGin1m84BRAQ@mail.gmail.com>
 <CANMVBVzPJDRXK7gq1kQqfyT75Fr9ueLi_Xnm+4NV6=5gUj=g5A@mail.gmail.com>
Message-ID: <CABObKxd8Exu6oTZ9WJcBSBB4b-Gqf3M=ChMpzTwHAUr9aTcJJQ@mail.gmail.com>

Or two clip filter with scalar.

On Wed, Dec 20, 2017 at 11:03 PM, Andrew <antech777 at gmail.com> wrote:

> Hello. Possibly the Slice filter with "Cylinder" and "Crinkle slice"
> options will produce the required result (I checked in ParaView 5.2).
>
> 2017-12-20 18:46 GMT+03:00 Andy Bauer <andy.bauer at kitware.com>:
>
>> The Threshold filter works by selecting cells that have cell data in the
>> selected range. If you're requesting to do thresholding on a point data
>> array then it will use the point data to cell data filter to create a cell
>> data array and threshold on that. With this, it's very unlikely that any
>> cell data ends up with exactly a value of .1. It sounds like what you want
>> is to use the Contour filter on your rad array.
>>
>> On Wed, Dec 20, 2017 at 10:32 AM, Utkarsh Ayachit <
>> utkarsh.ayachit at kitware.com> wrote:
>>
>>> I believe you're getting  the warning because the threshold ended up
>>> not producing any output. If you can attach the state/data file, I may
>>> be able to can give more info.
>>>
>>> Utkarsh
>>>
>>> On Wed, Dec 20, 2017 at 10:15 AM, Stephen Wornom
>>> <stephen.wornom at inria.fr> wrote:
>>> > The geometry is a cylinder.
>>> > Using the calculator I do
>>> > rad =sqrt( x**2+y**2)
>>> > I would like to extract the cylinder surface which is rad = 0.1
>>> > I click on threshold then information to see rad 0.1<rad<7
>>> > I click on extract and enter the values min = 0.1 and max 0.1 for rad
>>> > I get this message
>>> > warning: In
>>> > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuper
>>> build-Release/paraview/src/paraview/ParaViewCore/ServerManag
>>> er/Rendering/vtkSMPVRepresentationProxy.cxx,
>>> > line 279
>>> >
>>> > vtkSMPVRepresentationProxy (0x359fd080): Could not determine array
>>> range.
>>> >
>>> >
>>> > Any ideas to the solution of my problem?
>>> > Thanks in advance,
>>> > Stephen
>>> >
>>> > _______________________________________________
>>> > Powered by www.kitware.com
>>> >
>>> > Visit other Kitware open-source projects at
>>> > http://www.kitware.com/opensource/opensource.html
>>> >
>>> > Please keep messages on-topic and check the ParaView Wiki at:
>>> > http://paraview.org/Wiki/ParaView
>>> >
>>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>>> >
>>> > Follow this link to subscribe/unsubscribe:
>>> > https://paraview.org/mailman/listinfo/paraview
>>> >
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> https://paraview.org/mailman/listinfo/paraview
>>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://paraview.org/mailman/listinfo/paraview
>>
>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/0c70e80e/attachment.html>

From keith.b.lewis.ctr at navy.mil  Thu Dec 21 15:05:53 2017
From: keith.b.lewis.ctr at navy.mil (Lewis, Keith B CTR NSWCDD, E22)
Date: Thu, 21 Dec 2017 20:05:53 +0000
Subject: [Paraview] Pointer graphical and actual locations misaligned
Message-ID: <4B4253B4C6E00E4095BAC05D681D979859B7C328@NAEANRFKXM02V.nadsusea.nads.navy.mil>

Hello, ParaView Community:
I'm using version 5.4.1 64-bit on Win10. The pull-down menu bar (File, Edit etc.) is hidden behind the window title bar. The upper row of buttons (Open, Save Data, Connect, etc.) are mostly visible, but the upper portion of the buttons are also behind the window title bar. The pointer appears to be in a different location than the window thinks it is. For example, if I put the pointer in the center of the Open button, the button is NOT highlighted and the hover-over help does NOT appear. If I move the pointer downward, the button highlights when the pointer is right near the bottom of the button. If I continue moving the pointer downward, the button stays highlighted for about button-height distance. So the pointer looks like it's active about a button height above where it appears. If I move the pointer back up to the center of the Open button and click and hold, the File menu is pulled down. It seems that ParaView is confused about whether or not there's a title bar and where the active portion of the window is. Also, the window is a little bit cut off left and right. Anyone know of a fix?
Thanks,
Keith
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5380 bytes
Desc: not available
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/296b15d3/attachment.bin>

From ben.boeckel at kitware.com  Thu Dec 21 15:31:30 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 21 Dec 2017 15:31:30 -0500
Subject: [Paraview] Python shell, os.environ
In-Reply-To: <0E572B2D-E18D-4B7D-A3D2-49FE5A41A9D6@iu.edu>
References: <EA85B313-68B1-4759-8C61-519227AB4A4B@iu.edu>
 <7D160F39-F03B-45BD-8109-64808B94F8E1@iu.edu>
 <20171221143403.GA18094@megas.kitware.com>
 <0E572B2D-E18D-4B7D-A3D2-49FE5A41A9D6@iu.edu>
Message-ID: <20171221203130.GA11326@megas.kitware.com>

On Thu, Dec 21, 2017 at 15:14:01 +0000, Heiland, Randy wrote:
> Thanks Ben.  You?re right, of course. Moreover, my idea for having
> (non-admin) users install additional Python modules (e.g., scipy) into
> PV?s dir, is a not going to go well.

Well, if `sys.path` or `PYTHONPATH` can be pointed to it, it *should*
work (though the `numpy` in the package may not be configured properly
for `scipy`).

> Do we at least agree that if I ask users to start PV from the
> Terminal, PV?s Python will then pick up the user?s env vars?

It should, but ParaView doesn't do anything to stop it. If it doesn't
work, it's probably some Apple framework thing that needs to be told not
to do silly things.

--Ben

From sdavyd at gmail.com  Thu Dec 21 15:36:26 2017
From: sdavyd at gmail.com (Sonya Davydycheva)
Date: Thu, 21 Dec 2017 14:36:26 -0600
Subject: [Paraview] 3D visualization of vectors as vtk-files
Message-ID: <CAMDHuzaA+tihvhCNV1YosQmetCHJ7aXQBwyChcS+XMooGBrfkg@mail.gmail.com>

Hello,

Can anybody please send me a sample *.vtk file containing VECTOR fields?

I need it to start study options how to 3D-visualize, say, electromagnetic
field or currents. I can visualize separate components as scalars using
"Glyph" and having each component as a separate vtk-file (coordinates &
values). Now I try to convert them in a vector vtk-file, if possible, and
see the whole field in 3D.

Thanks in advance,

Sonya Davydycheva <http://3demholding.com>
(713)498-6139
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/74eb9479/attachment.html>

From samuelkey at bresnan.net  Thu Dec 21 17:33:42 2017
From: samuelkey at bresnan.net (Samuel Key)
Date: Thu, 21 Dec 2017 15:33:42 -0700
Subject: [Paraview] 3D visualization of vectors as vtk-files
In-Reply-To: <CAMDHuzaA+tihvhCNV1YosQmetCHJ7aXQBwyChcS+XMooGBrfkg@mail.gmail.com>
References: <CAMDHuzaA+tihvhCNV1YosQmetCHJ7aXQBwyChcS+XMooGBrfkg@mail.gmail.com>
Message-ID: <bfdc4a12-d3a7-dc74-5d58-d330ba65a102@bresnan.net>

Sonya--

Attached are two files: (1) *.pvd, a ParaView data "mother" file, and 
(2) *.vtu with velocity vectors at each finite element vertx nodal point.

Hope this helps

--Sam


On 12/21/2017 1:36 PM, Sonya Davydycheva wrote:
> Hello,
>
> Can anybody please send me a sample *.vtk file containing VECTOR fields?
>
> I need it to start study options how to 3D-visualize, say, 
> electromagnetic field or currents. I can visualize separate components 
> as scalars using "Glyph" and having each component as a separate 
> vtk-file (coordinates & values). Now I try to convert them in a vector 
> vtk-file, if possible, and see the whole field in 3D.
>
> Thanks in advance,
>
> Sonya Davydycheva<http://3demholding.com>
> (713)498-6139
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/d7ddd67c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fmavto.msh0000.vtu
Type: text/xml
Size: 2462 bytes
Desc: not available
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/d7ddd67c/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fmavto.mesh.pvd
Type: text/xml
Size: 430 bytes
Desc: not available
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/d7ddd67c/attachment-0001.xml>

From timothy.a.beach at nasa.gov  Thu Dec 21 18:37:55 2017
From: timothy.a.beach at nasa.gov (Beach, Timothy A. (GRC-LTE0)[Vantage Partners, LLC])
Date: Thu, 21 Dec 2017 23:37:55 +0000
Subject: [Paraview] Parview Build Faulure on  Mac OS 10.12.6
Message-ID: <EF9C1EAD-D690-4C42-A061-3C1FCAF9ABC7@contoso.com>

Helo,  I?ve been working through some issues compiling on a new MAC but this one has me stuck.   I used CMAKE 3.10 to generate xcodebuild files for paraview 5.4. Any ideas?
Thanks
Tim

make: *** No rule to make target `/Users/?/lib/cmake/paraview-5.4/Modules/vtkCommonCoreHierarchy.txt', needed by `/Users/?/VTK/Wrapping/Python/vtkAbstractArrayPython.cxx'.  Stop.
Command /bin/sh failed with exit code 2

** BUILD FAILED **



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171221/5ac637a3/attachment.html>

From fabian.wein at fau.de  Thu Dec 21 18:54:13 2017
From: fabian.wein at fau.de (Fabian Wein)
Date: Fri, 22 Dec 2017 00:54:13 +0100
Subject: [Paraview] Parview Build Faulure on Mac OS 10.12.6
In-Reply-To: <EF9C1EAD-D690-4C42-A061-3C1FCAF9ABC7@contoso.com>
References: <EF9C1EAD-D690-4C42-A061-3C1FCAF9ABC7@contoso.com>
Message-ID: <f87fa4a5-345d-52e5-a718-afebb99f9257@fau.de>

First question: do you use the superbuild?

On 12/22/17 00:37, Beach, Timothy A. (GRC-LTE0)[Vantage Partners, LLC] wrote:
> Helo,? I?ve been working through some issues compiling on a new MAC but this one has me stuck. ??I used CMAKE 3.10 to generate xcodebuild files for paraview 5.4. Any ideas?
> 
> Thanks
> 
> Tim
> 
> /make: *** No rule to make target `/Users/?/lib/cmake/paraview-5.4/Modules/vtkCommonCoreHierarchy.txt', needed by `/Users/?/VTK/Wrapping/Python/vtkAbstractArrayPython.cxx'.? Stop./
> 
> /Command /bin/sh failed with exit code 2/
> 
> //
> 
> */** BUILD FAILED **/*//
> 

From aron.helser at kitware.com  Fri Dec 22 10:28:34 2017
From: aron.helser at kitware.com (Aron Helser)
Date: Fri, 22 Dec 2017 10:28:34 -0500
Subject: [Paraview] Pointer graphical and actual locations misaligned
In-Reply-To: <4B4253B4C6E00E4095BAC05D681D979859B7C328@NAEANRFKXM02V.nadsusea.nads.navy.mil>
References: <4B4253B4C6E00E4095BAC05D681D979859B7C328@NAEANRFKXM02V.nadsusea.nads.navy.mil>
Message-ID: <CAF2skS5kz0V5ELWRcnjMiMZjrwW8PWvndM2VTM5KWM6PxQeoqw@mail.gmail.com>

Hi Keith,
Yes, this is a known bug in some Intel graphics drivers, on Windows, and I
believe we've seen something similar on Linux, as well.
If your lucky enough to be running an Optimus laptop, just switching
ParaView to use the nvidia card fixes the problem.
Intel has also fixed the bug in their latest drivers, but my Dell laptop
hasn't picked up the fix in the official Dell drivers yet.

Here's the bug: https://gitlab.kitware.com/paraview/paraview/issues/17499

On Thu, Dec 21, 2017 at 3:05 PM, Lewis, Keith B CTR NSWCDD, E22 <
keith.b.lewis.ctr at navy.mil> wrote:

> Hello, ParaView Community:
> I'm using version 5.4.1 64-bit on Win10. The pull-down menu bar (File,
> Edit etc.) is hidden behind the window title bar. The upper row of buttons
> (Open, Save Data, Connect, etc.) are mostly visible, but the upper portion
> of the buttons are also behind the window title bar. The pointer appears to
> be in a different location than the window thinks it is. For example, if I
> put the pointer in the center of the Open button, the button is NOT
> highlighted and the hover-over help does NOT appear. If I move the pointer
> downward, the button highlights when the pointer is right near the bottom
> of the button. If I continue moving the pointer downward, the button stays
> highlighted for about button-height distance. So the pointer looks like
> it's active about a button height above where it appears. If I move the
> pointer back up to the center of the Open button and click and hold, the
> File menu is pulled down. It seems that ParaView is confused about whether
> or not there's a title bar and where the a
>  ctive portion of the window is. Also, the window is a little bit cut off
> left and right. Anyone know of a fix?
> Thanks,
> Keith
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://paraview.org/pipermail/paraview/attachments/20171222/9449d167/attachment.html>

From ben.boeckel at kitware.com  Fri Dec 22 11:18:22 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 22 Dec 2017 11:18:22 -0500
Subject: [Paraview] Parview Build Faulure on  Mac OS 10.12.6
In-Reply-To: <EF9C1EAD-D690-4C42-A061-3C1FCAF9ABC7@contoso.com>
References: <EF9C1EAD-D690-4C42-A061-3C1FCAF9ABC7@contoso.com>
Message-ID: <20171222161822.GD13083@megas.kitware.com>

On Thu, Dec 21, 2017 at 23:37:55 +0000, Beach, Timothy A. (GRC-LTE0)[Vantage Partners, LLC] wrote:
> Helo,  I?ve been working through some issues compiling on a new MAC
> but this one has me stuck.   I used CMAKE 3.10 to generate xcodebuild
> files for paraview 5.4. Any ideas?

Yep, Working on a fix right now actually :) . Progress can be seen here:

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

Using the Ninja generator is a workaround for right now.

--Ben

From seongmo.yeon at gmail.com  Wed Dec 27 11:36:27 2017
From: seongmo.yeon at gmail.com (SeongMo)
Date: Thu, 28 Dec 2017 01:36:27 +0900
Subject: [Paraview] Updated OpenFOAMReader supporting OpenFOAM 5.x
Message-ID: <9ad21887-9ef8-365b-57e3-df63de5ea28c@gmail.com>

Hi, All


I made a merge request for modified OpenFOAMReader classes for OpenFOAM 5.x.

The classes are tested in ascii and binary formatted dictionary files 
and working well.

I found that the reader has some problems when the dictionary file is 
gzipped either in ascii or binary formats.

It looks like gzipped files are not read correctly because the 
GetFieldNames member function failed to find out field files. I tried to 
fix that problem but could not.

The classes are uploaded in VTK gitlab repository but attached also so 
that you can freely test the classes and find out the problem.


Regards.

SeongMo


-- 
SeongMo Yeon, Ph.D, Senior Engineer
Offshore Hydrodynamics Research
SAMSUNG HEAVY INDUSTRIES CO., LTD.
Central Research Institute
E-mail : seongmo.yeon at gmail.com
Tel :
--------------------------------------------------------
Fluctuat nec mergitur

-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkOpenFOAMReader.cxx
Type: text/x-c++src
Size: 353905 bytes
Desc: not available
URL: <https://paraview.org/pipermail/paraview/attachments/20171228/8c1a8905/attachment-0002.cxx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkOpenFOAMReader.h
Type: text/x-chdr
Size: 13128 bytes
Desc: not available
URL: <https://paraview.org/pipermail/paraview/attachments/20171228/8c1a8905/attachment-0002.h>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkPOpenFOAMReader.cxx
Type: text/x-c++src
Size: 29832 bytes
Desc: not available
URL: <https://paraview.org/pipermail/paraview/attachments/20171228/8c1a8905/attachment-0003.cxx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkPOpenFOAMReader.h
Type: text/x-chdr
Size: 2800 bytes
Desc: not available
URL: <https://paraview.org/pipermail/paraview/attachments/20171228/8c1a8905/attachment-0003.h>