From kriolog at gmail.com Thu Jun 1 00:03:36 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Thu, 1 Jun 2017 00:03:36 -0400 Subject: [Paraview-developers] Paraview offscreen rendering and graphical unit tests In-Reply-To: References: Message-ID: And I've just verified, it doesn't work (18% tests passed, 210 tests failed out of 257) with the system libosmesa6-dev (13.0.6-1+b2). The output could be found here: https://gist.github.com/kriolog/10af62df8645bc61e30535023d2fb824 2017-05-31 23:48 GMT-04:00 Maxim Torgonskiy : > Thanks Shawn, > > I've launched 'ctest -R vtkRendering' in my docker image and it works > (99% tests passed, 1 tests failed out of 257). The only failed test is > ' 789 - vtkRenderingCoreCxx-TestFollowerPicking (Failed)'. > > If someone finds this helpful, I've build it in the docker > debian:stretch with the system llvm-dev, mesa 13.0.3 and paraview > 5.3.0 (release from archive). The configuration arguments are the > following: > > mesa (identical to wiki): > =================================== > CXXFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \ > CFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \ > --disable-xvmc \ > --disable-glx \ > --disable-dri \ > --with-dri-drivers="" \ > --with-gallium-drivers="swrast" \ > --disable-shared-glapi \ > --disable-egl \ > --with-egl-platforms="" \ > --enable-gallium-osmesa \ > --enable-gallium-llvm=yes \ > --enable-llvm-shared-libs \ > --disable-gles1 \ > --disable-gles2 \ > --prefix=$installdir > =================================== > > paraview: > =================================== > -DCMAKE_BUILD_TYPE:STRING=Release \ > -DCMAKE_INSTALL_PREFIX:PATH=$installdir \ > -DBUILD_SHARED_LIBS:BOOL=ON \ > -DBUILD_TESTING:BOOL=ON \ > \# -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > \ > -DPARAVIEW_ENABLE_PYTHON:BOOL=OFF \ > -DPARAVIEW_ENABLE_WEB:BOOL=OFF \ > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \ > -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=OFF \ > -DVTK_USE_X:BOOL=OFF \ > -DOPENGL_INCLUDE_DIR:PATH= \ > -DOPENGL_gl_LIBRARY:FILEPATH= \ > -DOPENGL_glu_LIBRARY:FILEPATH= \ > -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \ > -DOSMESA_INCLUDE_DIR:PATH=$installdir_osmesa/include \ > -DOSMESA_LIBRARY:FILEPATH=$installdir_osmesa/lib/libOSMesa.so > =================================== > > Thanks, > Maxim > > 2017-05-31 9:44 GMT-04:00 Shawn Waldon : >> Hi Maxim, >> >> The dashboard machine amber8 isn't a docker container. It is Ubuntu machine >> with an OSMesa built according to the instructions on the wiki. >> >> It would help if you would share the errors you are getting from the tests >> so we have a better idea of what is going wrong. Without having any hint >> what is wrong it is hard to guess. >> >> A way to test if your OSMesa is working in Docker? Try running `ctest -R >> vtkRendering` and see if those tests pass. If they do, then OSMesa is >> working and something else is going wrong. >> >> HTH, >> Shawn >> >> On Tue, May 30, 2017 at 11:59 PM, Maxim Torgonskiy >> wrote: >>> >>> Hello, >>> >>> I need to launch paraview graphical tests in a docker image (debian >>> stretch). I'm trying to perform this with osmesa and I use its custom >>> version from the manual >>> (http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D) as well >>> as the libosmesa6-dev package. When I launch ctest with the default >>> paraview test directory, the 800 (rendering-related) tests from 2100 >>> are failed. When I use cdash config from >>> https://open.cdash.org/buildSummary.php?buildid=4918000 the situation >>> is approximately the same. >>> If it's possible, could you please share me the missing part of the >>> puzzle (your current docker image, custom test direcrory >>> [/home/kitware/Dashboards/MyTests/ExternalData], etc) so that I can >>> repeat the result presented on the cdash board? And is there any >>> method to check that osmesa actually works in docker itself and with >>> paraview. A quick google search gives me nothing. >>> >>> Thanks, >>> Maxim >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> From chuck.atkins at kitware.com Thu Jun 1 10:10:46 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Thu, 1 Jun 2017 10:10:46 -0400 Subject: [Paraview-developers] Paraview offscreen rendering and graphical unit tests In-Reply-To: References: Message-ID: Hi Maxim, Try running the following script with pvpython and see what your results are: # CheckOpenGLInfo.py from vtk.vtkPVClientServerCoreRendering import vtkPVOpenGLInformation info = vtkPVOpenGLInformation() info.CopyFromObject(None) print("Vendor: %s" % info.GetVendor()) print("Version: %s" % info.GetVersion()) print("Renderer: %s" % info.GetRenderer()) With Mesa-13.0.3, using the build instructions from http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D, I get: Vendor: VMware, Inc. Version: 3.3 (Core Profile) Mesa 13.0.3 (git-bec0411) Renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) Or, if I explicitly set GALLIUM_DRIVER=swr: SWR detected AVX2 Vendor: Intel Corporation Version: 3.3 (Core Profile) Mesa 13.0.3 (git-bec0411) Renderer: Gallium 0.4 on SWR ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Thu, Jun 1, 2017 at 12:03 AM, Maxim Torgonskiy wrote: > And I've just verified, it doesn't work (18% tests passed, 210 tests > failed out of 257) with the system libosmesa6-dev (13.0.6-1+b2). The > output could be found here: > https://gist.github.com/kriolog/10af62df8645bc61e30535023d2fb824 > > 2017-05-31 23:48 GMT-04:00 Maxim Torgonskiy : > > Thanks Shawn, > > > > I've launched 'ctest -R vtkRendering' in my docker image and it works > > (99% tests passed, 1 tests failed out of 257). The only failed test is > > ' 789 - vtkRenderingCoreCxx-TestFollowerPicking (Failed)'. > > > > If someone finds this helpful, I've build it in the docker > > debian:stretch with the system llvm-dev, mesa 13.0.3 and paraview > > 5.3.0 (release from archive). The configuration arguments are the > > following: > > > > mesa (identical to wiki): > > =================================== > > CXXFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \ > > CFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \ > > --disable-xvmc \ > > --disable-glx \ > > --disable-dri \ > > --with-dri-drivers="" \ > > --with-gallium-drivers="swrast" \ > > --disable-shared-glapi \ > > --disable-egl \ > > --with-egl-platforms="" \ > > --enable-gallium-osmesa \ > > --enable-gallium-llvm=yes \ > > --enable-llvm-shared-libs \ > > --disable-gles1 \ > > --disable-gles2 \ > > --prefix=$installdir > > =================================== > > > > paraview: > > =================================== > > -DCMAKE_BUILD_TYPE:STRING=Release > \ > > -DCMAKE_INSTALL_PREFIX:PATH=$installdir > \ > > -DBUILD_SHARED_LIBS:BOOL=ON > \ > > -DBUILD_TESTING:BOOL=ON > \ > > \# -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > > \ > > -DPARAVIEW_ENABLE_PYTHON:BOOL=OFF > \ > > -DPARAVIEW_ENABLE_WEB:BOOL=OFF > \ > > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF > \ > > -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=OFF > \ > > -DVTK_USE_X:BOOL=OFF > \ > > -DOPENGL_INCLUDE_DIR:PATH= > \ > > -DOPENGL_gl_LIBRARY:FILEPATH= > \ > > -DOPENGL_glu_LIBRARY:FILEPATH= > \ > > -DVTK_OPENGL_HAS_OSMESA:BOOL=ON > \ > > -DOSMESA_INCLUDE_DIR:PATH=$installdir_osmesa/include > \ > > -DOSMESA_LIBRARY:FILEPATH=$installdir_osmesa/lib/libOSMesa.so > > =================================== > > > > Thanks, > > Maxim > > > > 2017-05-31 9:44 GMT-04:00 Shawn Waldon : > >> Hi Maxim, > >> > >> The dashboard machine amber8 isn't a docker container. It is Ubuntu > machine > >> with an OSMesa built according to the instructions on the wiki. > >> > >> It would help if you would share the errors you are getting from the > tests > >> so we have a better idea of what is going wrong. Without having any > hint > >> what is wrong it is hard to guess. > >> > >> A way to test if your OSMesa is working in Docker? Try running `ctest > -R > >> vtkRendering` and see if those tests pass. If they do, then OSMesa is > >> working and something else is going wrong. > >> > >> HTH, > >> Shawn > >> > >> On Tue, May 30, 2017 at 11:59 PM, Maxim Torgonskiy > >> wrote: > >>> > >>> Hello, > >>> > >>> I need to launch paraview graphical tests in a docker image (debian > >>> stretch). I'm trying to perform this with osmesa and I use its custom > >>> version from the manual > >>> (http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D) as well > >>> as the libosmesa6-dev package. When I launch ctest with the default > >>> paraview test directory, the 800 (rendering-related) tests from 2100 > >>> are failed. When I use cdash config from > >>> https://open.cdash.org/buildSummary.php?buildid=4918000 the situation > >>> is approximately the same. > >>> If it's possible, could you please share me the missing part of the > >>> puzzle (your current docker image, custom test direcrory > >>> [/home/kitware/Dashboards/MyTests/ExternalData], etc) so that I can > >>> repeat the result presented on the cdash board? And is there any > >>> method to check that osmesa actually works in docker itself and with > >>> paraview. A quick google search gives me nothing. > >>> > >>> Thanks, > >>> Maxim > >>> _______________________________________________ > >>> Powered by www.kitware.com > >>> > >>> Visit other Kitware open-source projects at > >>> http://www.kitware.com/opensource/opensource.html > >>> > >>> Search the list archives at: > >>> http://markmail.org/search/?q=Paraview-developers > >>> > >>> Follow this link to subscribe/unsubscribe: > >>> http://public.kitware.com/mailman/listinfo/paraview-developers > >> > >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Jun 1 11:19:54 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 1 Jun 2017 11:19:54 -0400 Subject: [Paraview-developers] Problem with superbuild for ParaView 5.4.0-RC3 and non internet attached systems In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91EA192D@UCOLHPUD.easf.csd.disa.mil> References: <10A03274360DCF47A6EE78C9952A31CA91EA192D@UCOLHPUD.easf.csd.disa.mil> Message-ID: Joe, Here's an MR that adds a tar-based option for vtk-m. Set `vtkm_SOURCE_SELECTION` to `stable` instead of default `git-stable`. https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/333 Acusolve is a non-free plugin and we're not able to share the source code. As a result, you should not be enabling it in your builds. Utkarsh On Wed, May 31, 2017 at 1:28 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote: > Hello, > > I have noticed that for vtk-m, in the superbuild, > there is no longer a compressed file for download, > instead there is only a git repository. This will cause > problems for those of us building on systems without > Internet access, as we will no longer be able to use > previously downloaded versions on those systems without > Internet access. (this is also the case for the aculsolve reader as well) > > Thanks, > > Joe > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Joseph G. Hennessey Ph.D., SAIC > Team SAIC > Army Research Lab > DOD Supercomputing Resource Center > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kriolog at gmail.com Thu Jun 1 11:43:09 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Thu, 1 Jun 2017 11:43:09 -0400 Subject: [Paraview-developers] Paraview offscreen rendering and graphical unit tests In-Reply-To: References: Message-ID: Thanks Chuck, I've run you script as following: export PYTHONPATH=/home/jenkins/local/lib/paraview/build/lib:/home/jenkins/local/lib/paraview/build/lib/site-packages export LD_LIBRARY_PATH=/home/jenkins/local/lib/paraview/build/lib:$LD_LIBRARY_PATH python CheckOpenGLInfo.py and it gives me a segfault at line 'info.CopyFromObject(None)' 2017-06-01 10:10 GMT-04:00 Chuck Atkins : > Hi Maxim, > Try running the following script with pvpython and see what your results > are: > # CheckOpenGLInfo.py > from vtk.vtkPVClientServerCoreRendering import vtkPVOpenGLInformation > info = vtkPVOpenGLInformation() > info.CopyFromObject(None) > print("Vendor: %s" % info.GetVendor()) > print("Version: %s" % info.GetVersion()) > print("Renderer: %s" % info.GetRenderer()) > > With Mesa-13.0.3, using the build instructions from > http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D, I get: > Vendor: VMware, Inc. > Version: 3.3 (Core Profile) Mesa 13.0.3 (git-bec0411) > Renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) > > Or, if I explicitly set GALLIUM_DRIVER=swr: > SWR detected AVX2 > Vendor: Intel Corporation > Version: 3.3 (Core Profile) Mesa 13.0.3 (git-bec0411) > Renderer: Gallium 0.4 on SWR > > ---------- > Chuck Atkins > Staff R&D Engineer, Scientific Computing > Kitware, Inc. > > On Thu, Jun 1, 2017 at 12:03 AM, Maxim Torgonskiy wrote: >> >> And I've just verified, it doesn't work (18% tests passed, 210 tests >> failed out of 257) with the system libosmesa6-dev (13.0.6-1+b2). The >> output could be found here: >> https://gist.github.com/kriolog/10af62df8645bc61e30535023d2fb824 >> >> 2017-05-31 23:48 GMT-04:00 Maxim Torgonskiy : >> > Thanks Shawn, >> > >> > I've launched 'ctest -R vtkRendering' in my docker image and it works >> > (99% tests passed, 1 tests failed out of 257). The only failed test is >> > ' 789 - vtkRenderingCoreCxx-TestFollowerPicking (Failed)'. >> > >> > If someone finds this helpful, I've build it in the docker >> > debian:stretch with the system llvm-dev, mesa 13.0.3 and paraview >> > 5.3.0 (release from archive). The configuration arguments are the >> > following: >> > >> > mesa (identical to wiki): >> > =================================== >> > CXXFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \ >> > CFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \ >> > --disable-xvmc \ >> > --disable-glx \ >> > --disable-dri \ >> > --with-dri-drivers="" \ >> > --with-gallium-drivers="swrast" \ >> > --disable-shared-glapi \ >> > --disable-egl \ >> > --with-egl-platforms="" \ >> > --enable-gallium-osmesa \ >> > --enable-gallium-llvm=yes \ >> > --enable-llvm-shared-libs \ >> > --disable-gles1 \ >> > --disable-gles2 \ >> > --prefix=$installdir >> > =================================== >> > >> > paraview: >> > =================================== >> > -DCMAKE_BUILD_TYPE:STRING=Release >> > \ >> > -DCMAKE_INSTALL_PREFIX:PATH=$installdir >> > \ >> > -DBUILD_SHARED_LIBS:BOOL=ON >> > \ >> > -DBUILD_TESTING:BOOL=ON >> > \ >> > \# -DPARAVIEW_ENABLE_PYTHON:BOOL=ON >> > \ >> > -DPARAVIEW_ENABLE_PYTHON:BOOL=OFF >> > \ >> > -DPARAVIEW_ENABLE_WEB:BOOL=OFF >> > \ >> > -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF >> > \ >> > -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=OFF >> > \ >> > -DVTK_USE_X:BOOL=OFF >> > \ >> > -DOPENGL_INCLUDE_DIR:PATH= >> > \ >> > -DOPENGL_gl_LIBRARY:FILEPATH= >> > \ >> > -DOPENGL_glu_LIBRARY:FILEPATH= >> > \ >> > -DVTK_OPENGL_HAS_OSMESA:BOOL=ON >> > \ >> > -DOSMESA_INCLUDE_DIR:PATH=$installdir_osmesa/include >> > \ >> > -DOSMESA_LIBRARY:FILEPATH=$installdir_osmesa/lib/libOSMesa.so >> > =================================== >> > >> > Thanks, >> > Maxim >> > >> > 2017-05-31 9:44 GMT-04:00 Shawn Waldon : >> >> Hi Maxim, >> >> >> >> The dashboard machine amber8 isn't a docker container. It is Ubuntu >> >> machine >> >> with an OSMesa built according to the instructions on the wiki. >> >> >> >> It would help if you would share the errors you are getting from the >> >> tests >> >> so we have a better idea of what is going wrong. Without having any >> >> hint >> >> what is wrong it is hard to guess. >> >> >> >> A way to test if your OSMesa is working in Docker? Try running `ctest >> >> -R >> >> vtkRendering` and see if those tests pass. If they do, then OSMesa is >> >> working and something else is going wrong. >> >> >> >> HTH, >> >> Shawn >> >> >> >> On Tue, May 30, 2017 at 11:59 PM, Maxim Torgonskiy >> >> wrote: >> >>> >> >>> Hello, >> >>> >> >>> I need to launch paraview graphical tests in a docker image (debian >> >>> stretch). I'm trying to perform this with osmesa and I use its custom >> >>> version from the manual >> >>> (http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D) as well >> >>> as the libosmesa6-dev package. When I launch ctest with the default >> >>> paraview test directory, the 800 (rendering-related) tests from 2100 >> >>> are failed. When I use cdash config from >> >>> https://open.cdash.org/buildSummary.php?buildid=4918000 the situation >> >>> is approximately the same. >> >>> If it's possible, could you please share me the missing part of the >> >>> puzzle (your current docker image, custom test direcrory >> >>> [/home/kitware/Dashboards/MyTests/ExternalData], etc) so that I can >> >>> repeat the result presented on the cdash board? And is there any >> >>> method to check that osmesa actually works in docker itself and with >> >>> paraview. A quick google search gives me nothing. >> >>> >> >>> Thanks, >> >>> Maxim >> >>> _______________________________________________ >> >>> Powered by www.kitware.com >> >>> >> >>> Visit other Kitware open-source projects at >> >>> http://www.kitware.com/opensource/opensource.html >> >>> >> >>> Search the list archives at: >> >>> http://markmail.org/search/?q=Paraview-developers >> >>> >> >>> Follow this link to subscribe/unsubscribe: >> >>> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > From sumeet.kumar507 at gmail.com Thu Jun 1 11:49:29 2017 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Thu, 1 Jun 2017 08:49:29 -0700 Subject: [Paraview-developers] How to distribute standalone reader plugins In-Reply-To: References: Message-ID: Hello, I have a reader plugin which need to be build from source along with paraview for it's integration with paraview. I see that paraview distributed executables for different operating systems like windows, Linux and apple. Is there any way.. I could compile and link my plugin to those executables only.. rather than building them all from source.. Or is there any way I can build executables which are distributable to different platforms. Best Regards Sumeet Computations Geomechanic Group University of California Davis USA -------------- next part -------------- An HTML attachment was scrubbed... URL: From joseph.g.hennessey2.ctr at mail.mil Thu Jun 1 11:49:03 2017 From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US)) Date: Thu, 1 Jun 2017 15:49:03 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: Problem with superbuild for ParaView 5.4.0-RC3 and non internet attached systems In-Reply-To: References: <10A03274360DCF47A6EE78C9952A31CA91EA192D@UCOLHPUD.easf.csd.disa.mil> Message-ID: <10A03274360DCF47A6EE78C9952A31CA91EA1C8D@UCOLHPUD.easf.csd.disa.mil> Utkarsh, Thanks, that will make building on our non- Internet connected systems much easier. Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Thursday, June 01, 2017 11:20 AM To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: [Non-DoD Source] Re: [Paraview-developers] Problem with superbuild for ParaView 5.4.0-RC3 and non internet attached systems All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ Joe, Here's an MR that adds a tar-based option for vtk-m. Set `vtkm_SOURCE_SELECTION` to `stable` instead of default `git-stable`. Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/333 < Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/333 > Acusolve is a non-free plugin and we're not able to share the source code. As a result, you should not be enabling it in your builds. Utkarsh On Wed, May 31, 2017 at 1:28 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) > wrote: Hello, I have noticed that for vtk-m, in the superbuild, there is no longer a compressed file for download, instead there is only a git repository. This will cause problems for those of us building on systems without Internet access, as we will no longer be able to use previously downloaded versions on those systems without Internet access. (this is also the case for the aculsolve reader as well) Thanks, Joe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joseph G. Hennessey Ph.D., SAIC Team SAIC Army Research Lab DOD Supercomputing Resource Center _______________________________________________ Powered by Caution-www.kitware.com < Caution-http://www.kitware.com > Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > Search the list archives at: Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5615 bytes Desc: not available URL: From chuck.atkins at kitware.com Thu Jun 1 13:37:32 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Thu, 1 Jun 2017 13:37:32 -0400 Subject: [Paraview-developers] Paraview offscreen rendering and graphical unit tests In-Reply-To: References: Message-ID: Can you run it from pvpython? - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From kriolog at gmail.com Thu Jun 1 13:55:35 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Thu, 1 Jun 2017 13:55:35 -0400 Subject: [Paraview-developers] Paraview offscreen rendering and graphical unit tests In-Reply-To: References: Message-ID: Sorry, I didn't notice the 'pv' prefix. :) The output is the following: Vendor: VMware, Inc. Version: 3.3 (Core Profile) Mesa 13.0.3 Renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) 2017-06-01 13:37 GMT-04:00 Chuck Atkins : > Can you run it from pvpython? > > - Chuck From kriolog at gmail.com Thu Jun 1 15:08:03 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Thu, 1 Jun 2017 15:08:03 -0400 Subject: [Paraview-developers] Paraview offscreen rendering and graphical unit tests In-Reply-To: References: Message-ID: Shawn, Chuck, thank you for your help. 2017-06-01 13:55 GMT-04:00 Maxim Torgonskiy : > Sorry, I didn't notice the 'pv' prefix. :) The output is the following: > > Vendor: VMware, Inc. > Version: 3.3 (Core Profile) Mesa 13.0.3 > Renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) > > 2017-06-01 13:37 GMT-04:00 Chuck Atkins : >> Can you run it from pvpython? >> >> - Chuck From m.schlottke-lakemper at aia.rwth-aachen.de Thu Jun 1 17:38:29 2017 From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael) Date: Thu, 1 Jun 2017 21:38:29 +0000 Subject: [Paraview-developers] Visualization issues after switching from PV 5.1.2 to 5.3 Message-ID: Hi folks, We just updated our local ParaView installation from 5.1.2 to 5.3.0 and also re-compiled our custom plugins. Now we experience the issue that for some of our reader plugins, after loading a solution/grid file we can actually see the grid and its cells, but the data is not correctly visualized. That is, when looking at the data range in the inspector (or at the range of the legend), one can see the correct minimum/maximum values and if when applying the threshold filter, it cuts the correct cells. However, the cells itself remain uni-colored. Is it possible that this is related to changes in the ParaView build process? Maybe some switch in some visualization-related CMake defaults? I?m really at a loss here. Regards, Michael P.S.: Here is an example: Original figure with PV 5.1.2 (this is what we expect): Same figure with PV 5.3.0 Same figure with PV 5.3.0 and threshold filter applied to show only positive values (to demonstrate that it is, in fact, related to the visualization and not just the data reading): -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv_512.jpeg Type: image/jpeg Size: 27039 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv_530_raw.jpeg Type: image/jpeg Size: 11726 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv_530_threshold.jpeg Type: image/jpeg Size: 135297 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP URL: From utkarsh.ayachit at kitware.com Thu Jun 1 19:15:15 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 1 Jun 2017 19:15:15 -0400 Subject: [Paraview-developers] Visualization issues after switching from PV 5.1.2 to 5.3 In-Reply-To: References: Message-ID: Odd. A good starting point is to save out the data opened in older and newer versions as one of the standard supported file formats and compare that they are indeed what's expected. At that point, if it possible to share the exported dataset (that way I won't need your plugin code), we could see if I can reproduce the issue and see what could be going on. Utkarsh On Thu, Jun 1, 2017 at 5:38 PM, Schlottke-Lakemper, Michael < m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > Hi folks, > > We just updated our local ParaView installation from 5.1.2 to 5.3.0 and > also re-compiled our custom plugins. Now we experience the issue that for > some of our reader plugins, after loading a solution/grid file we can > actually see the grid and its cells, but the data is not correctly > visualized. That is, when looking at the data range in the inspector (or at > the range of the legend), one can see the correct minimum/maximum values > and if when applying the threshold filter, it cuts the correct cells. > However, the cells itself remain uni-colored. > > Is it possible that this is related to changes in the ParaView build > process? Maybe some switch in some visualization-related CMake defaults? > I?m really at a loss here. > > Regards, > > Michael > > P.S.: Here is an example: > > Original figure with PV 5.1.2 (this is what we expect): > > Same figure with PV 5.3.0 > > Same figure with PV 5.3.0 and threshold filter applied to show only > positive values (to demonstrate that it is, in fact, related to the > visualization and not just the data reading): > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv_512.jpeg Type: image/jpeg Size: 27039 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv_530_threshold.jpeg Type: image/jpeg Size: 135297 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pv_530_raw.jpeg Type: image/jpeg Size: 11726 bytes Desc: not available URL: From felipebordeu at gmail.com Fri Jun 2 02:12:17 2017 From: felipebordeu at gmail.com (Felipe Bordeu) Date: Fri, 2 Jun 2017 08:12:17 +0200 Subject: [Paraview-developers] How to distribute standalone reader plugins In-Reply-To: References: Message-ID: Hi, if you use the superbuild to compile ParaView you will get binaries that are compatible. So if you compile your plugin using the superbuild the you can distribute it and use it with the binaries from the webpage. In all the cases you must compile ParaView yourself for each platform. Felipe Le 1 juin 2017 5:49 PM, "sumeet kumar" a ?crit : > Hello, > > I have a reader plugin which need to be build from source along with > paraview for it's integration with paraview. > > I see that paraview distributed executables for different operating > systems like windows, Linux and apple. > > Is there any way.. I could compile and link my plugin to those executables > only.. rather than building them all from source.. > > Or is there any way I can build executables which are distributable to > different platforms. > > > Best Regards > Sumeet > > Computations Geomechanic Group > University of California Davis > USA > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.schlottke-lakemper at aia.rwth-aachen.de Fri Jun 2 03:50:14 2017 From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael) Date: Fri, 2 Jun 2017 07:50:14 +0000 Subject: [Paraview-developers] Visualization issues after switching from PV 5.1.2 to 5.3 In-Reply-To: References: Message-ID: <4CB3B9F1-97AD-48EF-BBA5-8EDEFB9B8572@aia.rwth-aachen.de> Hi Utkarsh, Thank you for your reply. I followed your advice and indeed: Once I store the data loaded in PV 5.3 as a .vtu file, I am able to open it in PV 5.1.2 and it displays correctly. Furthermore, I think I have identified the culprit: It seems to be a problem with the OpenGL2 backend, which seems to be the default now and which I forgot about. Once I reinstalled ParaView with -DVTK_RENDERING_BACKEND=OpenGL, things resumed to work as usual. Now this raises other questions: What could create the problem that everything compiles and runs just fine, except for the visualization part? Maybe our OpenGL2 version is too old? Regards, Michael P.S.: Just in case it still might be helpful (although I doubt it, since it seems to be related to the rendering backend), I uploaded the two files generated once by ParaView 5.1.2 (OpenGL) and ParaView 5.3.0 (OpenGL2): monopole.pv512.vtu (41 MB) monopole.pv530.vtu (41 MB) > On Jun 2, 2017, at 01:15, Utkarsh Ayachit wrote: > > Odd. A good starting point is to save out the data opened in older and newer versions as one of the standard supported file formats and compare that they are indeed what's expected. At that point, if it possible to share the exported dataset (that way I won't need your plugin code), we could see if I can reproduce the issue and see what could be going on. > > Utkarsh > > > > On Thu, Jun 1, 2017 at 5:38 PM, Schlottke-Lakemper, Michael > wrote: > Hi folks, > > We just updated our local ParaView installation from 5.1.2 to 5.3.0 and also re-compiled our custom plugins. Now we experience the issue that for some of our reader plugins, after loading a solution/grid file we can actually see the grid and its cells, but the data is not correctly visualized. That is, when looking at the data range in the inspector (or at the range of the legend), one can see the correct minimum/maximum values and if when applying the threshold filter, it cuts the correct cells. However, the cells itself remain uni-colored. > > Is it possible that this is related to changes in the ParaView build process? Maybe some switch in some visualization-related CMake defaults? I?m really at a loss here. > > Regards, > > Michael > > P.S.: Here is an example: > > Original figure with PV 5.1.2 (this is what we expect): > > > Same figure with PV 5.3.0 > > > Same figure with PV 5.3.0 and threshold filter applied to show only positive values (to demonstrate that it is, in fact, related to the visualization and not just the data reading): > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP URL: From m.schlottke-lakemper at aia.rwth-aachen.de Fri Jun 2 03:52:29 2017 From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael) Date: Fri, 2 Jun 2017 07:52:29 +0000 Subject: [Paraview-developers] Disable warnings about deprecated VTK items Message-ID: Hi folks, Due to some visualization problems we needed to switch back to the OpenGL rendering backend. Now we get the following warnings when using some of our custom reader plugins to load a file: Generic Warning: In /pds/opt/install/paraview/ParaView-v5.3.0/VTK/Rendering/Volume/vtkVolumeTextureMapper3D.cxx, line 680 vtkVolumeTextureMapper3D::vtkVolumeTextureMapper3D was deprecated for VTK 7.0 and will be removed in a future version. Generic Warning: In /pds/opt/install/paraview/ParaView-v5.3.0/VTK/Rendering/VolumeOpenGL/vtkOpenGLVolumeTextureMapper3D.cxx, line 57 vtkOpenGLVolumeTextureMapper3D::vtkOpenGLVolumeTextureMapper3D was deprecated for VTK 7.0 and will be removed in a future version. What can we do to avoid this issue (or is it a non-issue that disappears when going forward to using OpenGL2)? And is there a way to mute these messages globally such that users do not get confused? Thanks a lot in advance Michael ? Dr.-Ing. Michael Schlottke-Lakemper Institute of Aerodynamics and Chair of Fluid Mechanics RWTH Aachen University W?llnerstra?e 5a 52062 Aachen Germany Phone (RWTH): +49 (241) 80-95188 (Mon, Wed-Fri) Phone (FZJ): +49 (2461) 61-2326 (Tue) Email: m.schlottke-lakemper at aia.rwth-aachen.de Web: http://www.aia.rwth-aachen.de -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP URL: From dave.demarle at kitware.com Fri Jun 2 06:59:07 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 2 Jun 2017 06:59:07 -0400 Subject: [Paraview-developers] Disable warnings about deprecated VTK items In-Reply-To: References: Message-ID: You can configure your builds with VTK_LEGACY_SILENT to be ON to silence these warnings. Under OpenGL2, these particular classes do not exist so they are not an issue there. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 <(518)%20881-4909> On Fri, Jun 2, 2017 at 3:52 AM, Schlottke-Lakemper, Michael < m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > Hi folks, > > Due to some visualization problems we needed to switch back to the OpenGL > rendering backend. Now we get the following warnings when using some of our > custom reader plugins to load a file: > > Generic Warning: In /pds/opt/install/paraview/Para > View-v5.3.0/VTK/Rendering/Volume/vtkVolumeTextureMapper3D.cxx, line 680 > vtkVolumeTextureMapper3D::vtkVolumeTextureMapper3D was deprecated for VTK > 7.0 and will be removed in a future version. > > > Generic Warning: In /pds/opt/install/paraview/Para > View-v5.3.0/VTK/Rendering/VolumeOpenGL/vtkOpenGLVolumeTextureMapper3D.cxx, > line 57 > vtkOpenGLVolumeTextureMapper3D::vtkOpenGLVolumeTextureMapper3D was > deprecated for VTK 7.0 and will be removed in a future version. > > What can we do to avoid this issue (or is it a non-issue that disappears > when going forward to using OpenGL2)? And is there a way to mute these > messages globally such that users do not get confused? > > Thanks a lot in advance > > Michael > > > ? > Dr.-Ing. Michael Schlottke-Lakemper > > Institute of Aerodynamics and Chair of Fluid Mechanics > RWTH Aachen University > W?llnerstra?e 5a > 52062 Aachen > Germany > > Phone (RWTH): +49 (241) 80-95188 <+49%20241%208095188> (Mon, Wed-Fri) > Phone (FZJ): +49 (2461) 61-2326 <+49%202461%20612326> (Tue) > Email: m.schlottke-lakemper at aia.rwth-aachen.de > Web: http://www.aia.rwth-aachen.de > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.schlottke-lakemper at aia.rwth-aachen.de Fri Jun 2 07:06:35 2017 From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael) Date: Fri, 2 Jun 2017 11:06:35 +0000 Subject: [Paraview-developers] Disable warnings about deprecated VTK items In-Reply-To: References: Message-ID: <0A24EF7A-FE24-4CED-9985-1035955E8AD2@aia.rwth-aachen.de> Hi David, Thanks a lot for the fast and comprehensive reply. Michael > On Jun 2, 2017, at 12:59, David E DeMarle wrote: > > You can configure your builds with VTK_LEGACY_SILENT to be ON to silence these warnings. > > Under OpenGL2, these particular classes do not exist so they are not an issue there. > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > On Fri, Jun 2, 2017 at 3:52 AM, Schlottke-Lakemper, Michael > wrote: > Hi folks, > > Due to some visualization problems we needed to switch back to the OpenGL rendering backend. Now we get the following warnings when using some of our custom reader plugins to load a file: > > Generic Warning: In /pds/opt/install/paraview/ParaView-v5.3.0/VTK/Rendering/Volume/vtkVolumeTextureMapper3D.cxx, line 680 > vtkVolumeTextureMapper3D::vtkVolumeTextureMapper3D was deprecated for VTK 7.0 and will be removed in a future version. > > > Generic Warning: In /pds/opt/install/paraview/ParaView-v5.3.0/VTK/Rendering/VolumeOpenGL/vtkOpenGLVolumeTextureMapper3D.cxx, line 57 > vtkOpenGLVolumeTextureMapper3D::vtkOpenGLVolumeTextureMapper3D was deprecated for VTK 7.0 and will be removed in a future version. > > What can we do to avoid this issue (or is it a non-issue that disappears when going forward to using OpenGL2)? And is there a way to mute these messages globally such that users do not get confused? > > Thanks a lot in advance > > Michael > > > ? > Dr.-Ing. Michael Schlottke-Lakemper > > Institute of Aerodynamics and Chair of Fluid Mechanics > RWTH Aachen University > W?llnerstra?e 5a > 52062 Aachen > Germany > > Phone (RWTH): +49 (241) 80-95188 (Mon, Wed-Fri) > Phone (FZJ): +49 (2461) 61-2326 (Tue) > Email: m.schlottke-lakemper at aia.rwth-aachen.de > Web: http://www.aia.rwth-aachen.de > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP URL: From dave.demarle at kitware.com Fri Jun 2 07:48:57 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 2 Jun 2017 07:48:57 -0400 Subject: [Paraview-developers] OSPRay Based Volume rendering In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F68438ED03A@MBX111.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F68438ED03A@MBX111.d.ethz.ch> Message-ID: It doesn't take effect because we neglected to hook that particular VTK control up to anything in the OSPRay volume rendering implementation. Jean, please file a bug report to help us remember to give some user control over it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Fri Jun 2 08:23:48 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 2 Jun 2017 08:23:48 -0400 Subject: [Paraview-developers] Visualization issues after switching from PV 5.1.2 to 5.3 In-Reply-To: References: <4CB3B9F1-97AD-48EF-BBA5-8EDEFB9B8572@aia.rwth-aachen.de> Message-ID: Using PV 5.4 RC2 with the OpenGL2 backend I get what looks like a correct rendering with either of those files. Might be worth trying with PV 5.4. (removed screen shot as it was being held up by our mailing list) (but picture here a nice screen shot) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jam.evan at yahoo.com Fri Jun 2 11:58:36 2017 From: jam.evan at yahoo.com (James Evans) Date: Fri, 2 Jun 2017 15:58:36 +0000 (UTC) Subject: [Paraview-developers] Conversion of data from dbl to vtk References: <119284194.896076.1496419116458.ref@mail.yahoo.com> Message-ID: <119284194.896076.1496419116458@mail.yahoo.com> Dear Sir or Madam, I'm James Evans PhD researcher in astrophysics, I have the pleasure to get in touch with you. Actually, I schedule to use Paraview for the first time as a visualization tool of my outputs. The format of my outputs is DBL and I think that I need to convert them to VTK format in order to be accessible by Paraview. I used dbl format in my simulations because it allows me to restart the PLUTO code from any integration step and therefore can control easily the run. Unfortunaltely, I have no idea about this conversion. ?Can you help me please. I look forward to hearing from you. Best regards, James -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Jun 2 13:25:36 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 2 Jun 2017 13:25:36 -0400 Subject: [Paraview-developers] Visualization issues after switching from PV 5.1.2 to 5.3 In-Reply-To: References: <4CB3B9F1-97AD-48EF-BBA5-8EDEFB9B8572@aia.rwth-aachen.de> Message-ID: On Fri, Jun 2, 2017 at 8:23 AM, Ken Martin wrote: > Using PV 5.4 RC2 with the OpenGL2 backend I get what looks like a correct > rendering with either of those files. Might be worth trying with PV 5.4. > Same for me. The new dataset render just fine on my my linux desktop with 5.4. -------------- next part -------------- An HTML attachment was scrubbed... URL: From MKAn at securemissionsolutions.com Fri Jun 2 14:15:39 2017 From: MKAn at securemissionsolutions.com (An, Michael K.) Date: Fri, 2 Jun 2017 18:15:39 +0000 Subject: [Paraview-developers] [Paraviewweb] Setting number of bins in InfoViz Diagrams Message-ID: <1496427339078.49659@securemissionsolutions.com> Hi Sebastien, and others, I have a couple questions regarding the customization of the number of histogram bins for InfoViz Diagrams. 1) How do you set the number of bins dynamically, after you have instantiated a diagram, e.g., HistogramSelector? The following doesn't work for me: const histSelectorObj = HistogramSelector.newInstance({provider}); histSelectorObj.setNumberOfBins(newValue); While this sets numberOfBins correctly for histSelectorObj, the diagram rendering seems to fail. Upon closer inspection, it looks like a call to subscribeToHistogram1D is made when first instantiating the histogram selector histSelectorObj. Because you must pass in metadata here, which includes numberOfBins, I would think that the data subscription always expects any incoming data updates to be consistent with this original metadata, and that the data subscription doesn't "know" that this value changed. Setting the value when calling newInstance seems to work fine: const histSelectorObj = HistogramSelector.newInstance({provider, numberOfBins: newValue});? Is there a way to change the metadata in the data subscription later on (or am I not understanding something)? 2) Following up on the first question, is there a way to have different histograms have different number of bins within one InfoViz diagram? Thanks a lot for your help. -Mike ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Fri Jun 2 14:41:53 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 2 Jun 2017 12:41:53 -0600 Subject: [Paraview-developers] [Paraviewweb] Setting number of bins in InfoViz Diagrams In-Reply-To: <1496427339078.49659@securemissionsolutions.com> References: <1496427339078.49659@securemissionsolutions.com> Message-ID: Hi Mike, More responses inlined below, but I think this conversation might be better suited to the paravieweb issue tracker on github? Just my $0.02. https://github.com/Kitware/paraviewweb On Fri, Jun 2, 2017 at 12:15 PM, An, Michael K. < MKAn at securemissionsolutions.com> wrote: > Hi Sebastien, and others, > > I have a couple questions regarding the customization of the number of > histogram bins for InfoViz Diagrams. > > 1) How do you set the number of bins dynamically, after you have > instantiated a diagram, e.g., HistogramSelector? The following doesn?t > work for me: > > const histSelectorObj = HistogramSelector.newInstance({provider}); > histSelectorObj.setNumberOfBins(newValue); > > While this sets numberOfBins correctly for histSelectorObj, the diagram > rendering seems to fail. Upon closer inspection, it looks like a call to > subscribeToHistogram1D is made when first instantiating the histogram > selector histSelectorObj. > Because you must pass in metadata here, which includes numberOfBins, I > would think that the data subscription always expects any incoming data > updates to be consistent with this original metadata, and that the data > subscription doesn?t ?know? that this value changed. > Setting the value when calling newInstance seems to work fine: > > const histSelectorObj = HistogramSelector.newInstance({provider, numberOfBins: newValue});? > > Is there a way to change the metadata in the data subscription later on > (or am I not understanding something)? > You are correct that currently, changing the number of bins once you have created the component is not supported. One approach to fix this is to implement the "setNumberOfBins" method in the HistogramSelector (rather than letting the CompositeClosureHelper generate that for us) and in that method update the histgram1d subscription. You can take a stab at that if you like, I'd be happy to review the change. > 2) Following up on the first question, is there a way to have different > histograms have different number of bins within one InfoViz diagram? > This is also not currently supported, and I do not think it would be straightforward to implement at the moment, but it's something we can keep in mind. Hope this helps, Scott > Thanks a lot for your help. > > -Mike > ? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire.guilbaud at gmail.com Mon Jun 5 05:36:46 2017 From: claire.guilbaud at gmail.com (Claire Guilbaud) Date: Mon, 5 Jun 2017 11:36:46 +0200 Subject: [Paraview-developers] VTK version in future ParaView 5.4 Message-ID: Hi all, Will ParaView 5.4 include VTK 8.0.0 even if it will be released mid-June ? Generally, is there a way to know the VTK version used in ParaView ? Thanks. Claire -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jun 5 10:46:57 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 5 Jun 2017 10:46:57 -0400 Subject: [Paraview-developers] VTK version in future ParaView 5.4 In-Reply-To: References: Message-ID: Claire. ParaView includes it's own VTK. It cannot work with external VTK yet. 5.4 will indeed be using a version older than the official VTK 8.0.0 release. Hope that helps. Utkarsh On Mon, Jun 5, 2017 at 5:36 AM, Claire Guilbaud wrote: > Hi all, > > Will ParaView 5.4 include VTK 8.0.0 even if it will be released mid-June ? > Generally, is there a way to know the VTK version used in ParaView ? > > Thanks. > > Claire > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jun 5 10:52:56 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 5 Jun 2017 10:52:56 -0400 Subject: [Paraview-developers] Conversion of data from dbl to vtk In-Reply-To: <119284194.896076.1496419116458@mail.yahoo.com> References: <119284194.896076.1496419116458.ref@mail.yahoo.com> <119284194.896076.1496419116458@mail.yahoo.com> Message-ID: James, I am not familiar with DBL, but going a quick search, it seems like PLUTO code should be generating a xml file too (*.xmf) that you should be able to open in ParaView. Here's the relevant extract from the docs ( http://plutocode.ph.unito.it/files/userguide.pdf) *11.1.2 HDF5 Output: dbl.h5 or flt.h5 data formats* HDF5 output format can be used in the static grid version if PLUTO has been succesfully compiled with the serial or parallel version of the HDF5 library, see ?3.2. The file extension is .h5 (and not .hdf5 as used by PLUTO-Chombo data files, ?12.4) and output files are written in Pixie format, a single-block, rectilinear mesh file using HDF5, may be related to the Polar Ionospheric X-Ray Imaging Experiment. The conventions used in writing .dbl.h5 or .flt.h5 files are the same ones adopted for the .dbl and .flt data formats. However, with HDF5, all variables are written to a single file. Pixie files can be opened and visualized directly by different softwares, like VisIt and Paraview. *Since we have found compatibility issues with some versions of these visualization softwares, each file comes along with a supplementary .xmf text file in XDMF format that describes the content of the corresponding HDF5 file and can be opened correctly by VisIt and Paraview, see ?11.3.5*. Restart can be performed from double precision HDF5 data files by invoking PLUTO with the -h5restart n command line option (?1.4.1), where n is the output file number from which to restart. In this case an additional file (restart.out) will be dumped to disk. Default: The default is to write ALL fields in .dbl.h5 format, whereas to exclude staggered magnetic field components (if any) from the .flt.h5 format. Hope that helps. Utkarsh On Fri, Jun 2, 2017 at 11:58 AM, James Evans via Paraview-developers < paraview-developers at paraview.org> wrote: > Dear Sir or Madam, > > I'm James Evans PhD researcher in astrophysics, I have the pleasure to get > in touch with you. > Actually, I schedule to use Paraview for the first time as a visualization > tool of my outputs. The format of my outputs is DBL and I think that I need > to convert them to VTK format in order to be accessible by Paraview. I used > dbl format in my simulations because it allows me to restart the PLUTO code > from any integration step and therefore can control easily the run. > Unfortunaltely, I have no idea about this conversion. > > Can you help me please. > > I look forward to hearing from you. > Best regards, > > James > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Jun 5 11:27:57 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 5 Jun 2017 11:27:57 -0400 Subject: [Paraview-developers] VTK version in future ParaView 5.4 In-Reply-To: References: Message-ID: Technically PV's VTK is actually a little bit newer than 8.0.0 as the VTK branch point happened a couple of weeks ago and PV's VTK was updated a couple of days ago. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 <(518)%20881-4909> On Mon, Jun 5, 2017 at 10:46 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Claire. > > ParaView includes it's own VTK. It cannot work with external VTK yet. 5.4 > will indeed be using a version older than the official VTK 8.0.0 release. > > Hope that helps. > Utkarsh > > On Mon, Jun 5, 2017 at 5:36 AM, Claire Guilbaud > wrote: > >> Hi all, >> >> Will ParaView 5.4 include VTK 8.0.0 even if it will be released mid-June ? >> Generally, is there a way to know the VTK version used in ParaView ? >> >> Thanks. >> >> Claire >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jun 5 11:33:47 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 5 Jun 2017 11:33:47 -0400 Subject: [Paraview-developers] VTK version in future ParaView 5.4 In-Reply-To: References: Message-ID: > > Technically PV's VTK is actually a little bit newer than 8.0.0 as the VTK > branch point happened a couple of weeks ago and PV's VTK was updated a > couple of days ago. > > Actually, that's arguable :). The 8.0.0 release may get new patches in upcoming days that won't be in the VTK that ParaView 5.4 brought in. It's best to say the two are different, I suppose. Utkarsh -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jun 6 15:34:25 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 6 Jun 2017 15:34:25 -0400 Subject: [Paraview-developers] ParaView 5.4.0 is now available for download Message-ID: On behalf of the ParaView development team, I am pleased to announce that ParaView 5.4.0 has been released and can be downloaded in both source and binary forms from http://www.paraview.org/download Release notes for ParaView 5.4.0 are available at https://blog.kitware.com/paraview-5-4-0-release-notes/ ParaView's superbuild has been updated to build 5.4.0 by default. Sincerely, Cory and the ParaView team -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Tue Jun 6 16:10:16 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 6 Jun 2017 16:10:16 -0400 Subject: [Paraview-developers] ParaView 5.4.0 is now available for download In-Reply-To: References: Message-ID: Please note that for the first time, we are providing signed macOS binaries in both disk image (.dmg) and package (.pkg) form. Please let us know if you run into any problems with these binaries. On another note, I have added the tag v5.4.0 to the paraview-superbuild repository. - Cory On Tue, Jun 6, 2017 at 3:34 PM, Cory Quammen wrote: > On behalf of the ParaView development team, I am pleased to announce > that ParaView 5.4.0 has been released and can be downloaded in both > source and binary forms from > > http://www.paraview.org/download > > Release notes for ParaView 5.4.0 are available at > > https://blog.kitware.com/paraview-5-4-0-release-notes/ > > ParaView's superbuild has been updated to build 5.4.0 by default. > > Sincerely, > Cory and the ParaView team > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From simon.m.su.civ at mail.mil Wed Jun 7 08:23:09 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Wed, 7 Jun 2017 12:23:09 +0000 Subject: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) Message-ID: CLASSIFICATION: UNCLASSIFIED Hello, On Windows 10 64bit, when I tried to use VS 2015 community for my ParaView superbuild build, the cmake is complaining ospray requires VS2013 even when I have the following set -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF Is there a way to use VS2015 community compiler to build ParaView superbuild? thank you much -simon CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Jun 7 08:47:29 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 7 Jun 2017 08:47:29 -0400 Subject: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) In-Reply-To: References: Message-ID: Turn off embree as well. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL (US) < simon.m.su.civ at mail.mil> wrote: > CLASSIFICATION: UNCLASSIFIED > > Hello, > > On Windows 10 64bit, when I tried to use VS 2015 community for my ParaView > superbuild build, the cmake is complaining ospray requires VS2013 even when > I have the following set > > -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF > > Is there a way to use VS2015 community compiler to build ParaView > superbuild? > > thank you much > -simon > > > CLASSIFICATION: UNCLASSIFIED > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.civ at mail.mil Wed Jun 7 09:59:21 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Wed, 7 Jun 2017 13:59:21 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: windows 10 superbuild VS2013 requirement (UNCLASSIFIED) In-Reply-To: References: Message-ID: CLASSIFICATION: UNCLASSIFIED Thank you David. But I think I also needed something else.... Please see below. thanks -simon c:\Users\one\build\pvsb-5.4\build>cmake -G Ninja -DCMAKE_INSTALL_PREFIX=ParaView-5.4.0 -DCMAKE_BUILD_TYPE=Release -DENABLE_mpi:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF -DENABLE_embree:BOOL=OFF -DENABLE_qt4:BOOL=OFF -DENABLE_qt5:BOOL=ON -DENABLE_cxx11:BOOL=ON -DENABLE_bzip2:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_paraviewtutorial:BOOL=ON -DENABLE_paraviewtutorialdata:BOOL=ON -DENABLE_paraviewusersguide:BOOL=ON -DENABLE_paraviewweb:BOOL=ON -DENABLE_paraviewweblightviz:BOOL=ON -DENABLE_paraviewwebvisualizer:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DENABLE_vrpn:BOOL=ON ..\paraview-superbuild -- The C compiler identification is MSVC 19.0.24215.1 -- The CXX compiler identification is MSVC 19.0.24215.1 -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Check size of void* -- Check size of void* - done -- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.10.2.windows.1") -- Determined source version for paraview: 5.4.0 CMake Error at projects/win32/ispc.cmake:2 (message): The ispc project requires Visual Studio 2013. Call Stack (most recent call first): superbuild/cmake/SuperbuildMacros.cmake:477 (include) superbuild/CMakeLists.txt:113 (_superbuild_discover_projects) -- Configuring incomplete, errors occurred! See also "C:/Users/one/build/pvsb-5.4/build/CMakeFiles/CMakeOutput.log". -----Original Message----- From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Wednesday, June 07, 2017 8:47 AM To: Su, Simon M CIV USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: [Non-DoD Source] Re: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ Turn off embree as well. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL (US) > wrote: CLASSIFICATION: UNCLASSIFIED Hello, On Windows 10 64bit, when I tried to use VS 2015 community for my ParaView superbuild build, the cmake is complaining ospray requires VS2013 even when I have the following set -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF Is there a way to use VS2015 community compiler to build ParaView superbuild? thank you much -simon CLASSIFICATION: UNCLASSIFIED _______________________________________________ Powered by Caution-www.kitware.com < Caution-http://www.kitware.com > Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > Search the list archives at: Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Jun 7 10:10:34 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 7 Jun 2017 10:10:34 -0400 Subject: [Paraview-developers] [Non-DoD Source] Re: windows 10 superbuild VS2013 requirement (UNCLASSIFIED) In-Reply-To: References: Message-ID: I don't know why your command to turn off the ispc subproject isn't being respected then. Is c:\Users\one\build\pvsb-5.4\build initially empty or does it still have the contents of a previous build? I would expect the above to work fine in a clean build. With a partial or old build, editing cmakecache (via cmake-gui or command line) to turn of ispc and configuring should also work. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 7, 2017 at 9:59 AM, Su, Simon M CIV USARMY RDECOM ARL (US) < simon.m.su.civ at mail.mil> wrote: > CLASSIFICATION: UNCLASSIFIED > > Thank you David. But I think I also needed something else.... Please see > below. > > thanks > -simon > > > c:\Users\one\build\pvsb-5.4\build>cmake -G > Ninja -DCMAKE_INSTALL_PREFIX=ParaView-5.4.0 -DCMAKE_BUILD_TYPE=Release > -DENABLE_mpi:BOOL=ON > -DENABLE_python:BOOL=ON -DENABLE_paraview:BOOL=ON > -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF > -DENABLE_embree:BOOL=OFF -DENABLE_qt4:BOOL=OFF -DENABLE_qt5:BOOL=ON > -DENABLE_cxx11:BOOL=ON > -DENABLE_bzip2:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_numpy:BOOL=ON > -DENABLE_paraviewtutorial:BOOL=ON > -DENABLE_paraviewtutorialdata:BOOL=ON -DENABLE_paraviewusersguide:BOOL=ON > -DENABLE_paraviewweb:BOOL=ON > -DENABLE_paraviewweblightviz:BOOL=ON -DENABLE_paraviewwebvisualizer:BOOL=ON > -DENABLE_visitbridge:BOOL=ON > -DENABLE_vrpn:BOOL=ON ..\paraview-superbuild > > -- The C compiler identification is MSVC 19.0.24215.1 > > -- The CXX compiler identification is MSVC 19.0.24215.1 > > -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual > Studio 14.0/VC/bin/amd64/cl.exe > > -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual > Studio 14.0/VC/bin/amd64/cl.exe -- works > > -- Detecting C compiler ABI info > > -- Detecting C compiler ABI info - done > > -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual > Studio 14.0/VC/bin/amd64/cl.exe > > -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual > Studio 14.0/VC/bin/amd64/cl.exe -- works > > -- Detecting CXX compiler ABI info > > -- Detecting CXX compiler ABI info - done > > -- Detecting CXX compile features > > -- Detecting CXX compile features - done > > -- Check size of void* > > -- Check size of void* - done > > -- Found Git: C:/Program Files/Git/cmd/git.exe (found version > "2.10.2.windows.1") > > -- Determined source version for paraview: 5.4.0 > > CMake Error at projects/win32/ispc.cmake:2 (message): > > The ispc project requires Visual Studio 2013. > > Call Stack (most recent call first): > > superbuild/cmake/SuperbuildMacros.cmake:477 (include) > > superbuild/CMakeLists.txt:113 (_superbuild_discover_projects) > > > > > > > > -- Configuring incomplete, errors occurred! > > See also "C:/Users/one/build/pvsb-5.4/build/CMakeFiles/CMakeOutput.log". > > > > > > -----Original Message----- > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Wednesday, June 07, 2017 8:47 AM > To: Su, Simon M CIV USARMY RDECOM ARL (US) > Cc: ParaView Developers > Subject: [Non-DoD Source] Re: [Paraview-developers] windows 10 superbuild > VS2013 requirement (UNCLASSIFIED) > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm the authenticity of all links contained > within the message prior to copying and pasting the address to a Web > browser. > > > ________________________________ > > > > Turn off embree as well. > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL (US) > > > wrote: > > > CLASSIFICATION: UNCLASSIFIED > > Hello, > > On Windows 10 64bit, when I tried to use VS 2015 community for my > ParaView > superbuild build, the cmake is complaining ospray requires VS2013 > even when > I have the following set > > -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF > > Is there a way to use VS2015 community compiler to build ParaView > superbuild? > > thank you much > -simon > > > CLASSIFICATION: UNCLASSIFIED > > _______________________________________________ > Powered by Caution-www.kitware.com < Caution- > http://www.kitware.com > > > Visit other Kitware open-source projects at > Caution-http://www.kitware.com/opensource/opensource.html < > Caution-http://www.kitware.com/opensource/opensource.html > > > Search the list archives at: > Caution-http://markmail.org/search/?q=Paraview-developers < > Caution-http://markmail.org/search/?q=Paraview-developers > > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview- > developers < > Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > > CLASSIFICATION: UNCLASSIFIED > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.civ at mail.mil Wed Jun 7 10:46:27 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Wed, 7 Jun 2017 14:46:27 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: windows 10 superbuild VS2013 requirement (UNCLASSIFIED) In-Reply-To: References: Message-ID: CLASSIFICATION: UNCLASSIFIED thank you David. It is on a clean build. I am equally puzzled. thanks -simon -----Original Message----- From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Wednesday, June 07, 2017 10:11 AM To: Su, Simon M CIV USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: Re: [Non-DoD Source] Re: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ I don't know why your command to turn off the ispc subproject isn't being respected then. Is c:\Users\one\build\pvsb-5.4\build initially empty or does it still have the contents of a previous build? I would expect the above to work fine in a clean build. With a partial or old build, editing cmakecache (via cmake-gui or command line) to turn of ispc and configuring should also work. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 7, 2017 at 9:59 AM, Su, Simon M CIV USARMY RDECOM ARL (US) > wrote: CLASSIFICATION: UNCLASSIFIED Thank you David. But I think I also needed something else.... Please see below. thanks -simon c:\Users\one\build\pvsb-5.4\build>cmake -G Ninja -DCMAKE_INSTALL_PREFIX=ParaView-5.4.0 -DCMAKE_BUILD_TYPE=Release -DENABLE_mpi:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF -DENABLE_embree:BOOL=OFF -DENABLE_qt4:BOOL=OFF -DENABLE_qt5:BOOL=ON -DENABLE_cxx11:BOOL=ON -DENABLE_bzip2:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_paraviewtutorial:BOOL=ON -DENABLE_paraviewtutorialdata:BOOL=ON -DENABLE_paraviewusersguide:BOOL=ON -DENABLE_paraviewweb:BOOL=ON -DENABLE_paraviewweblightviz:BOOL=ON -DENABLE_paraviewwebvisualizer:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DENABLE_vrpn:BOOL=ON ..\paraview-superbuild -- The C compiler identification is MSVC 19.0.24215.1 -- The CXX compiler identification is MSVC 19.0.24215.1 -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Check size of void* -- Check size of void* - done -- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.10.2.windows.1") -- Determined source version for paraview: 5.4.0 CMake Error at projects/win32/ispc.cmake:2 (message): The ispc project requires Visual Studio 2013. Call Stack (most recent call first): superbuild/cmake/SuperbuildMacros.cmake:477 (include) superbuild/CMakeLists.txt:113 (_superbuild_discover_projects) -- Configuring incomplete, errors occurred! See also "C:/Users/one/build/pvsb-5.4/build/CMakeFiles/CMakeOutput.log". -----Original Message----- From: David E DeMarle [Caution-mailto:dave.demarle at kitware.com < Caution-mailto:dave.demarle at kitware.com > ] Sent: Wednesday, June 07, 2017 8:47 AM To: Su, Simon M CIV USARMY RDECOM ARL (US) > Cc: ParaView Developers > Subject: [Non-DoD Source] Re: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ Turn off embree as well. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 < tel:518-881-4909 > On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL (US) < Caution-Caution-mailto:simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > > > wrote: CLASSIFICATION: UNCLASSIFIED Hello, On Windows 10 64bit, when I tried to use VS 2015 community for my ParaView superbuild build, the cmake is complaining ospray requires VS2013 even when I have the following set -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF Is there a way to use VS2015 community compiler to build ParaView superbuild? thank you much -simon CLASSIFICATION: UNCLASSIFIED _______________________________________________ Powered by Caution-Caution-www.kitware.com < Caution-http://Caution-Caution-www.kitware.com > < Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com > > Visit other Kitware open-source projects at Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > < Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > > Search the list archives at: Caution-Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > < Caution-Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > < Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > > CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Jun 7 11:37:15 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 7 Jun 2017 11:37:15 -0400 Subject: [Paraview-developers] [Non-DoD Source] Re: windows 10 superbuild VS2013 requirement (UNCLASSIFIED) In-Reply-To: References: Message-ID: Likely that the compiler check is happening before the flag to disable the subproject is setup. Would you mind removing the check (projects/win32/ispc.cmake) and telling me if condifuration continues? David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jun 7, 2017 at 10:46 AM, Su, Simon M CIV USARMY RDECOM ARL (US) < simon.m.su.civ at mail.mil> wrote: > CLASSIFICATION: UNCLASSIFIED > > thank you David. It is on a clean build. I am equally puzzled. > > thanks > -simon > > -----Original Message----- > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Wednesday, June 07, 2017 10:11 AM > To: Su, Simon M CIV USARMY RDECOM ARL (US) > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] windows 10 > superbuild > VS2013 requirement (UNCLASSIFIED) > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm the authenticity of all links contained > within the message prior to copying and pasting the address to a Web > browser. > > > ________________________________ > > > > I don't know why your command to turn off the ispc subproject isn't being > respected then. > > Is c:\Users\one\build\pvsb-5.4\build initially empty or does it still > have the > contents of a previous build? > > I would expect the above to work fine in a clean build. > > > With a partial or old build, editing cmakecache (via cmake-gui or command > line) to turn of ispc and configuring should also work. > > > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Jun 7, 2017 at 9:59 AM, Su, Simon M CIV USARMY RDECOM ARL (US) > > > wrote: > > > CLASSIFICATION: UNCLASSIFIED > > Thank you David. But I think I also needed something else.... > Please see > below. > > thanks > -simon > > > c:\Users\one\build\pvsb-5.4\build>cmake -G > Ninja -DCMAKE_INSTALL_PREFIX=ParaView-5.4.0 > -DCMAKE_BUILD_TYPE=Release -DENABLE_mpi:BOOL=ON > -DENABLE_python:BOOL=ON -DENABLE_paraview:BOOL=ON > -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF > -DENABLE_embree:BOOL=OFF -DENABLE_qt4:BOOL=OFF > -DENABLE_qt5:BOOL=ON -DENABLE_cxx11:BOOL=ON > -DENABLE_bzip2:BOOL=ON -DENABLE_png:BOOL=ON > -DENABLE_numpy:BOOL=ON -DENABLE_paraviewtutorial:BOOL=ON > -DENABLE_paraviewtutorialdata:BOOL=ON > -DENABLE_paraviewusersguide:BOOL=ON -DENABLE_paraviewweb:BOOL=ON > -DENABLE_paraviewweblightviz:BOOL=ON -DENABLE_ > paraviewwebvisualizer:BOOL=ON > -DENABLE_visitbridge:BOOL=ON > -DENABLE_vrpn:BOOL=ON ..\paraview-superbuild > > -- The C compiler identification is MSVC 19.0.24215.1 > > -- The CXX compiler identification is MSVC 19.0.24215.1 > > -- Check for working C compiler: C:/Program Files (x86)/Microsoft > Visual > Studio 14.0/VC/bin/amd64/cl.exe > > -- Check for working C compiler: C:/Program Files (x86)/Microsoft > Visual > Studio 14.0/VC/bin/amd64/cl.exe -- works > > -- Detecting C compiler ABI info > > -- Detecting C compiler ABI info - done > > -- Check for working CXX compiler: C:/Program Files > (x86)/Microsoft Visual > Studio 14.0/VC/bin/amd64/cl.exe > > -- Check for working CXX compiler: C:/Program Files > (x86)/Microsoft Visual > Studio 14.0/VC/bin/amd64/cl.exe -- works > > -- Detecting CXX compiler ABI info > > -- Detecting CXX compiler ABI info - done > > -- Detecting CXX compile features > > -- Detecting CXX compile features - done > > -- Check size of void* > > -- Check size of void* - done > > -- Found Git: C:/Program Files/Git/cmd/git.exe (found version > "2.10.2.windows.1") > > -- Determined source version for paraview: 5.4.0 > > CMake Error at projects/win32/ispc.cmake:2 (message): > > The ispc project requires Visual Studio 2013. > > Call Stack (most recent call first): > > superbuild/cmake/SuperbuildMacros.cmake:477 (include) > > superbuild/CMakeLists.txt:113 (_superbuild_discover_projects) > > > > > > > > -- Configuring incomplete, errors occurred! > > See also "C:/Users/one/build/pvsb-5.4/ > build/CMakeFiles/CMakeOutput.log". > > > > > > -----Original Message----- > From: David E DeMarle [Caution-mailto:dave.demarle at kitware.com < > Caution-mailto:dave.demarle at kitware.com > ] > Sent: Wednesday, June 07, 2017 8:47 AM > To: Su, Simon M CIV USARMY RDECOM ARL (US) < > simon.m.su.civ at mail.mil < > Caution-mailto:simon.m.su.civ at mail.mil > > > Cc: ParaView Developers Caution-mailto:paraview-developers at paraview.org > > > Subject: [Non-DoD Source] Re: [Paraview-developers] windows 10 > superbuild > VS2013 requirement (UNCLASSIFIED) > > All active links contained in this email were disabled. Please > verify the > identity of the sender, and confirm the authenticity of all links > contained > within the message prior to copying and pasting the address to a > Web browser. > > > ________________________________ > > > > Turn off embree as well. > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 < tel:518-881-4909 > > > On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL > (US) > > < > Caution-Caution-mailto:simon.m.su.civ at mail.mil < > Caution-mailto:simon.m.su.civ at mail.mil > > > wrote: > > > CLASSIFICATION: UNCLASSIFIED > > Hello, > > On Windows 10 64bit, when I tried to use VS 2015 community > for my > ParaView > superbuild build, the cmake is complaining ospray requires > VS2013 > even when > I have the following set > > -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF > > Is there a way to use VS2015 community compiler to build > ParaView > superbuild? > > thank you much > -simon > > > CLASSIFICATION: UNCLASSIFIED > > _______________________________________________ > Powered by Caution-Caution-www.kitware.com < > Caution-http://Caution-Caution-www.kitware.com > < > Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com > > > > > Visit other Kitware open-source projects at > Caution-Caution-http://www.kitware.com/opensource/opensource.html > < > Caution-http://www.kitware.com/opensource/opensource.html > < > Caution-Caution-http://www.kitware.com/opensource/opensource.html > < > Caution-http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > Caution-Caution-http://markmail.org/search/?q=Paraview-developers > < > Caution-http://markmail.org/search/?q=Paraview-developers > < > Caution-Caution-http://markmail.org/search/?q=Paraview-developers > < > Caution-http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > Caution-Caution-http://public. > kitware.com/mailman/listinfo/paraview-developers > < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > > < > Caution-Caution-http://public.kitware.com/mailman/listinfo/ > paraview-developers > < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > > > > CLASSIFICATION: UNCLASSIFIED > > > > > CLASSIFICATION: UNCLASSIFIED > -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.moser at rwth-aachen.de Wed Jun 7 18:24:59 2017 From: markus.moser at rwth-aachen.de (Mizael Moser, Markus Klaus) Date: Wed, 7 Jun 2017 22:24:59 +0000 Subject: [Paraview-developers] Parallel structured grid reader doesn"t produce subextent In-Reply-To: References: <1496097056093.19755@rwth-aachen.de>, Message-ID: <183ca299aa4e4753a679b8d2a44450e9@rwthex-s2-a.rwth-ad.de> Thank you, it works now. The extent is now perfectly divided. Markus Moser Student assistant Chair of Fluid Mechanics and Institute of Aerodynamics W?llnerstra?e 5a RWTH Aachen University 52062 Aachen Germany ________________________________________ Von: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Gesendet: Dienstag, 30. Mai 2017 16:30 An: Mizael Moser, Markus Klaus Cc: paraview-developers at paraview.org Betreff: Re: [Paraview-developers] Parallel structured grid reader doesn"t produce subextent Use outInfo->Set(CAN_PRODUCE_SUB_EXTENT(), 1) instead of outInfo->Set(CAN_HANDLE_PIECE_REQUEST(),1). Alternatively, you can create a vtkExtentTranslator instance yourself in RequestData to convert UPDATE_PIECE_NUMBER(), UPDATE_NUMBER_OF_PIECES() to sub-extents in RequestData. The latter may be better since it looks like your reader is producing a vtkMultiBlockDataSet. If I remember correctly, the extent-based request only works for structured datasets eg. vtkStructuredGrid, vtkImageData etc. Utkarsh On Tue, May 30, 2017 at 10:08 AM, Mizael Moser, Markus Klaus > wrote: Dear ParaView developers, I'm having trouble to parallelize my ParaView reader plugin. I want to read HDF5 files and the grid is a structured grid. The plugin works perfectly fine if run in serial, and if i run it in parallel the solution is also correct but instead of dividing the dataset in x subsets, it reads the whole dataset x times(for each processor 1 time). I found the wiki for a structured grid parallel reader (http://www.paraview.org/Wiki/Writing_ParaView_Readers) and used it as orientation. My RequestInformation looks like this: //Reading basic information //Reading in the extent from the file int extent[6]; //storing the extent in the array vtkInformation* outInfo=outputVector->GetInformationObject(0); outInfo->Set(CAN_HANDLE_PIECE_REQUEST(),1); outInfo ->Set(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),extent,6); RequestData looks like this: vtkProcessModule *ParInfo; vtkInformation *outInfo = outputVector->GetInformationObject(0); vtkMultiBlockDataSet* multiBlock = vtkMultiBlockDataSet::SafeDownCast(outInfo->Get(vtkDataObject::DATA_OBJECT())); int subext[6]; outInfo->Get(vtkStreamingDemandDrivenPipeline::UPDATE_EXTENT(),subext); cout<<"Num of Processors = "<GetNumberOfLocalPartitions()<GetPartitionId() << " " <Get(vtkStreamingDemandDrivenPipeline::UPDATE_EXTENT(),subext);" should produce the sub-extent for the rank or am i wrong? What am I doing wrong, or what do I have to do to get the sub-extent? Thank you very much in advance, Markus Moser Markus Moser Student assistant Chair of Fluid Mechanics and Institute of Aerodynamics W?llnerstra?e 5a RWTH Aachen University 52062 Aachen Germany _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers From wascott at sandia.gov Thu Jun 8 14:50:07 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 8 Jun 2017 18:50:07 +0000 Subject: [Paraview-developers] Superbuild swr Message-ID: <7b908f3cc94a4d8892d47f465c6d35ef@ES01AMSNLNT.srn.sandia.gov> Chuck ? Why is osmesa/ swr turned on by default? It requires C++14, which is not on any clusters here. Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jun 8 14:53:06 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 8 Jun 2017 14:53:06 -0400 Subject: [Paraview-developers] Superbuild swr In-Reply-To: <7b908f3cc94a4d8892d47f465c6d35ef@ES01AMSNLNT.srn.sandia.gov> References: <7b908f3cc94a4d8892d47f465c6d35ef@ES01AMSNLNT.srn.sandia.gov> Message-ID: The dependency on c++14 is a transient bug in mesa/swr. It was introduced only very recently (first appeared in 17.1.1) and is being removed as we speak. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jun 8, 2017 at 2:50 PM, Scott, W Alan wrote: > Chuck ? Why is osmesa/ swr turned on by default? It requires C++14, which > is not on any clusters here. > > > > Alan > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michal.wozniak at caboma.com Thu Jun 8 15:02:18 2017 From: michal.wozniak at caboma.com (Michal Wozniak) Date: Thu, 8 Jun 2017 19:02:18 +0000 Subject: [Paraview-developers] Panel property visibility Message-ID: Hi, I am trying to add a slider to my custom plugin but I am having trouble hiding some properties. https://www.paraview.org/Wiki/ParaView/Properties_Panel#Property_Groups:_For_Exposed_Properties I am trying to hide the max and min value, but it isn't working. I can hide the whole group if I add the panel_visibility="advanced" to the propertyGroup but I want to have the value property visible. Is there a way of hiding part of the exposed properties? Thank you Michal -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Thu Jun 8 15:10:33 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Thu, 8 Jun 2017 13:10:33 -0600 Subject: [Paraview-developers] Panel property visibility In-Reply-To: References: Message-ID: Hi Michal, Do you intend to never show the max and min properties? As you are probably aware, 'panel_visibility="advanced"' only hides those properties if the advanced toggled is off. If you never want to see certain properties, you could try changing the 'panel_visibility' attribute for those properties to 'never' instead of advanced. Hope this helps, Scott On Thu, Jun 8, 2017 at 1:02 PM, Michal Wozniak wrote: > Hi, > > > I am trying to add a slider to my custom plugin but I am having trouble > hiding some properties. > > > https://www.paraview.org/Wiki/ParaView/Properties_Panel# > Property_Groups:_For_Exposed_Properties > > > > > > > > > > panel_visibility="advanced"/> > panel_visibility="advanced"/> > > > > I am trying to hide the max and min value, but it isn't working. I can > hide the whole group if I add the panel_visibility="advanced" to the > propertyGroup but I want to have the value property visible. > > > Is there a way of hiding part of the exposed properties? > > > Thank you > > Michal > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Thu Jun 8 15:50:16 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Thu, 8 Jun 2017 13:50:16 -0600 Subject: [Paraview-developers] Panel property visibility In-Reply-To: References: Message-ID: Hi Michal, cc-ing back to developers list, as there are others who may know more or otherwise benefit from the discussion >From my understanding, PropertyGroup is designed to provide a way to customize how properties are displayed. However, your properties must be defined in more detail elsewhere, perhaps inside the same proxy xml definition. In your case, I would guess they are defined in the same proxy, or else the PropertyGroup you shared in your original email was inside an ExposedProperties element, but I didn't see that. The detailed property definition won't have the element name "Property", but rather, something like "IntVectorProperty" for example. But the "name" attribute in the detailed definition will match up with the "name" attribute on your Property within the PropertyGroup. Can you try putting the "panel_visibility" attribute on that detailed property definition instead of on the Property within the PropertyGroup and let us know the results? Hope this helps, Scott On Thu, Jun 8, 2017 at 1:27 PM, Michal Wozniak wrote: > Hi, > > > > I only wish to display the ?value property? on default. I want to hide > point1, point2, max, and min, therefore only viewing them if we have > toggled the advanced button. > > Currently, when I set panel_visibility=?advanced? or ?never? , it still > visible on default. > > > > When I add panel_visibility=?advanced? to a DoubleVectorProperty, it work > correctly. It will be visible only when advanced is toggle. > > > > Is this process different when we want to hide properties inside a > panel_widget? > > > > > > *From: *Scott Wittenburg > *Sent: *June 8, 2017 3:10 PM > *To: *Michal Wozniak > *Cc: *paraview-developers at paraview.org > *Subject: *Re: [Paraview-developers] Panel property visibility > > > > Hi Michal, > > > > Do you intend to never show the max and min properties? As you are > probably aware, 'panel_visibility="advanced"' only hides those properties > if the advanced toggled is off. If you never want to see certain > properties, you could try changing the 'panel_visibility' attribute for > those properties to 'never' instead of advanced. > > > > Hope this helps, > > Scott > > > > > > On Thu, Jun 8, 2017 at 1:02 PM, Michal Wozniak > wrote: > > Hi, > > > > I am trying to add a slider to my custom plugin but I am having trouble > hiding some properties. > > > > https://www.paraview.org/Wiki/ParaView/Properties_Panel# > Property_Groups:_For_Exposed_Properties > > > > > > > > > > > > > > > > > > panel_visibility="advanced"/> > > panel_visibility="advanced"/> > > > > > > I am trying to hide the max and min value, but it isn't working. I can > hide the whole group if I add the panel_visibility="advanced" to the > propertyGroup but I want to have the value property visible. > > > > Is there a way of hiding part of the exposed properties? > > > > Thank you > > Michal > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jun 8 16:56:00 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 8 Jun 2017 20:56:00 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild swr In-Reply-To: References: <7b908f3cc94a4d8892d47f465c6d35ef@ES01AMSNLNT.srn.sandia.gov> Message-ID: <5f6be065c3084bef9327fe014e17078a@ES01AMSNLNT.srn.sandia.gov> How would you recommend I proceed? Will this fix be pushed into the Superbuild? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, June 8, 2017 12:53 PM To: Scott, W Alan Cc: Atkins, Chuck (External Contacts) ; paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Superbuild swr The dependency on c++14 is a transient bug in mesa/swr. It was introduced only very recently (first appeared in 17.1.1) and is being removed as we speak. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jun 8, 2017 at 2:50 PM, Scott, W Alan > wrote: Chuck ? Why is osmesa/ swr turned on by default? It requires C++14, which is not on any clusters here. Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jun 8 17:02:08 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 8 Jun 2017 17:02:08 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild swr In-Reply-To: <5f6be065c3084bef9327fe014e17078a@ES01AMSNLNT.srn.sandia.gov> References: <7b908f3cc94a4d8892d47f465c6d35ef@ES01AMSNLNT.srn.sandia.gov> <5f6be065c3084bef9327fe014e17078a@ES01AMSNLNT.srn.sandia.gov> Message-ID: Chuck already pushed to Superbuild master (one commit beyond v5.4.0 tag) David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jun 8, 2017 at 4:56 PM, Scott, W Alan wrote: > How would you recommend I proceed? Will this fix be pushed into the > Superbuild? > > > > *From:* David E DeMarle [mailto:dave.demarle at kitware.com] > *Sent:* Thursday, June 8, 2017 12:53 PM > *To:* Scott, W Alan > *Cc:* Atkins, Chuck (External Contacts) ; > paraview-developers at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview-developers] Superbuild swr > > > > The dependency on c++14 is a transient bug in mesa/swr. It was introduced > only very recently (first appeared in 17.1.1) and is being removed as we > speak. > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > > > On Thu, Jun 8, 2017 at 2:50 PM, Scott, W Alan wrote: > > Chuck ? Why is osmesa/ swr turned on by default? It requires C++14, which > is not on any clusters here. > > > > Alan > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jun 8 17:25:17 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 8 Jun 2017 21:25:17 +0000 Subject: [Paraview-developers] gitlab Message-ID: <039c454a895645b796b2391be58024e5@ES01AMSNLNT.srn.sandia.gov> Hi guys, Gitlab (i.e., https://gitlab.kitware.com/paraview/paraview-superbuild.git) appears to be down. Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Thu Jun 8 17:28:35 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Thu, 8 Jun 2017 15:28:35 -0600 Subject: [Paraview-developers] gitlab In-Reply-To: <039c454a895645b796b2391be58024e5@ES01AMSNLNT.srn.sandia.gov> References: <039c454a895645b796b2391be58024e5@ES01AMSNLNT.srn.sandia.gov> Message-ID: I believe gitlab.kitware.com was scheduled to undergo a security update at 3:15 EDT today, so that's probably still going on. It should be back up soon, however. Sorry for the inconvenience. Cheers, Scott On Thu, Jun 8, 2017 at 3:25 PM, Scott, W Alan wrote: > Hi guys, > > Gitlab (i.e., https://gitlab.kitware.com/paraview/paraview-superbuild.git) > appears to be down. > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Thu Jun 8 17:28:31 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Thu, 8 Jun 2017 17:28:31 -0400 Subject: [Paraview-developers] gitlab In-Reply-To: <039c454a895645b796b2391be58024e5@ES01AMSNLNT.srn.sandia.gov> References: <039c454a895645b796b2391be58024e5@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi Alan, There was a security update released today and the sysadmins are updating it. Shawn On Thu, Jun 8, 2017 at 5:25 PM, Scott, W Alan wrote: > Hi guys, > > Gitlab (i.e., https://gitlab.kitware.com/paraview/paraview-superbuild.git) > appears to be down. > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Jun 8 20:06:45 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 8 Jun 2017 20:06:45 -0400 Subject: [Paraview-developers] [Paraview] ParaView 5.4.0 is now available for download In-Reply-To: References: Message-ID: Hi Bruno, It sounds like you are running into this issue: https://gitlab.kitware.com/paraview/paraview/issues/17461 We don't yet have a fix in hand, but your report adds another data point. Thanks, Cory On Thu, Jun 8, 2017 at 5:24 PM, bruno le hyaric wrote: > Hi Cory, > > I am interested to use Paraview 5.4 on Windows but it seems the render > view is broken. When I try to display something (a sphere for example) > I get a "black render view". > > I am running the build without MPI > (ParaView-5.4.0-Qt5-OpenGL2-Windows-64bit.exe) on Windows 7 SP1 64-bit > with Intel HD Graphics 5500 and OpenGL 4.3.0. > > > Regards, > > Bruno LE HYARIC. > > > On Tue, Jun 6, 2017 at 3:34 PM, Cory Quammen > wrote: > > On behalf of the ParaView development team, I am pleased to announce > > that ParaView 5.4.0 has been released and can be downloaded in both > > source and binary forms from > > > > http://www.paraview.org/download > > > > Release notes for ParaView 5.4.0 are available at > > > > https://blog.kitware.com/paraview-5-4-0-release-notes/ > > > > ParaView's superbuild has been updated to build 5.4.0 by default. > > > > Sincerely, > > Cory and the ParaView team > > > > -- > > Cory Quammen > > Staff R&D Engineer > > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Fri Jun 9 11:08:17 2017 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Fri, 9 Jun 2017 11:08:17 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild swr In-Reply-To: References: <7b908f3cc94a4d8892d47f465c6d35ef@ES01AMSNLNT.srn.sandia.gov> <5f6be065c3084bef9327fe014e17078a@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi Alan, > Chuck ? Why is osmesa/ swr turned on by default? It requires C++14, which >> is not on any clusters here. >> >> GCC >= 5 and Intel >= 15 from your modules should work for this. However, the C++14 requirement took me suprise and I didn't realize until after it had vbeen merged. Intel is getting a patch merged upstream right now to roll back the langiage requirement but I've already merged into the superbuild. So basically, try the superbuild's current master and it shouldn't be an issue anymore. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Jun 9 12:10:46 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 9 Jun 2017 16:10:46 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild swr In-Reply-To: References: <7b908f3cc94a4d8892d47f465c6d35ef@ES01AMSNLNT.srn.sandia.gov> <5f6be065c3084bef9327fe014e17078a@ES01AMSNLNT.srn.sandia.gov> Message-ID: <4112dc784fa44f3baf288cfdce6145b2@ES01AMSNLNT.srn.sandia.gov> Chuck, We don?t have GCC 5* available as a module, or in any other form. We do have Intel 15, but I have not tried Intel for quite some time. I just turned swr off, that appears to have worked. On production clusters, the tools are not always up to date... That is why I had issues with llvm for the longest time. Alan From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Friday, June 9, 2017 9:08 AM To: DeMarle, David E. (External Contacts) Cc: Scott, W Alan ; paraview-developers at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview-developers] Superbuild swr Hi Alan, Chuck ? Why is osmesa/ swr turned on by default? It requires C++14, which is not on any clusters here. GCC >= 5 and Intel >= 15 from your modules should work for this. However, the C++14 requirement took me suprise and I didn't realize until after it had vbeen merged. Intel is getting a patch merged upstream right now to roll back the langiage requirement but I've already merged into the superbuild. So basically, try the superbuild's current master and it shouldn't be an issue anymore. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kriolog at gmail.com Fri Jun 9 12:19:30 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Fri, 9 Jun 2017 12:19:30 -0400 Subject: [Paraview-developers] osMesa with QT GUI support Message-ID: Dear ParaView developers, I successfully configured ParaView with osMesa in my docker container (default configuration from wiki). Now I need to create some .pvsm state-based python regression visual tests. It works well if I launch a simple state like 'create a sphere -> make a transform'. However my state is more complex and it depends on some custom plugins which require activated PARAVIEW_BUILD_QT_GUI (but probably can work without it). Is there any possibility to compile ParaView with osMesa and with PARAVIEW_BUILD_QT_GUI=ON in order to be able to compile my plugins and launch my state? Now I have a compilation error: paraview/VTK/GUISupport/Qt/QVTKWidget.cxx:50:21: fatal error: QX11Info: No such file or directory # include Thanks, Maxim -------------- next part -------------- An HTML attachment was scrubbed... URL: From kriolog at gmail.com Fri Jun 9 16:31:51 2017 From: kriolog at gmail.com (Maxim Torgonskiy) Date: Fri, 9 Jun 2017 16:31:51 -0400 Subject: [Paraview-developers] osMesa with QT GUI support In-Reply-To: References: Message-ID: I reviewed a bit the code, header QX11Info is from the module x11extras and this module is included in the build iff VTK_USE_X is enabled. So, is it possible to configure osmesa to be able to activate together PARAVIEW_BUILD_QT_GUI and VTK_USE_X? Or maybe there's some other solution? 2017-06-09 12:19 GMT-04:00 Maxim Torgonskiy : > Dear ParaView developers, > > I successfully configured ParaView with osMesa in my docker container > (default configuration from wiki). Now I need to create some .pvsm > state-based python regression visual tests. It works well if I launch a > simple state like 'create a sphere -> make a transform'. > However my state is more complex and it depends on some custom plugins > which require activated PARAVIEW_BUILD_QT_GUI (but probably can work > without it). > Is there any possibility to compile ParaView with osMesa and > with PARAVIEW_BUILD_QT_GUI=ON in order to be able to compile my plugins and > launch my state? Now I have a compilation error: > > paraview/VTK/GUISupport/Qt/QVTKWidget.cxx:50:21: fatal error: QX11Info: > No such file or directory > # include > > Thanks, > Maxim > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Mon Jun 12 05:16:35 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 12 Jun 2017 11:16:35 +0200 Subject: [Paraview-developers] ParaView Course October 11 Message-ID: Hello Kitware will be holding a ParaView course on October 11th 2017 in Lyon, France. We will provide you with hands-on paraview experience, as well as introduce python-scripting and plugins. Please visit our web site for more information and registration details at ParaView (English) : http://training.kitware.fr/browse/156 ParaView (French) : http://formations.kitware.fr/browse/156 Note that the course will be taught in English. If you have any question, please contact us at formations at http://www.kitware.fr Best Regards, Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Mon Jun 12 08:25:08 2017 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Mon, 12 Jun 2017 05:25:08 -0700 Subject: [Paraview-developers] Dynamic Updating of Time Steps and Range in Paraview simulation. Message-ID: Hello all, I want to visualize in preview simultaneously running the analysis. I have met all the requirements and coded successfully to implement this feature. The only this that I am stuck is to update the time steps and range dynamically. Currently, at the top of the *Request Data* method, I added the following code thinking that it will update the paraview gui * vtkInformation *Node_Mesh_Info = outputVector->GetInformationObject(0); this->Update_Time_Steps(); double Time_range[2]={Time[0],Time[Number_of_Time_Steps-1]}; cout << "Number of Time Steps " << Number_of_Time_Steps << endl; cout << "Time Tange " << Time_range[1] << endl; Node_Mesh_Info->Set(vtkStreamingDemandDrivenPipeline::TIME_STEPS(),Time, this->Number_of_Time_Steps); Node_Mesh_Info->Set(vtkStreamingDemandDrivenPipeline::TIME_RANGE(),Time_range,2);* But, it does not update. Id there any way, I can dynamically update the paraview animation time steps and range. Best Regards Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From michal.wozniak at caboma.com Mon Jun 12 17:29:31 2017 From: michal.wozniak at caboma.com (Michal Wozniak) Date: Mon, 12 Jun 2017 21:29:31 +0000 Subject: [Paraview-developers] Paraview Plugin Python wrapped Message-ID: Hi, I would like to access my plugin?s class using a programmable filter. (import customPluginClass ...) I have been searching through the mailing list how to achieve this but I can?t seem to find a working example. https://www.paraview.org/pipermail/paraview/2012-May/024855.html I tried following this example but it isn?t working. Wrap-python.cmake doesn?t exist in the current version of ParaView. I found this macro ?WRAP_PLUGIN_FOR_PYTHON? https://github.com/Kitware/ParaView/blob/master/CMake/ParaViewPlugins.cmake Using this macro, I?m getting a error ?unknown cmake command Python_add_module?. I am compiling my custom plugin inside ParaView?s plugin folder Am I supposed to used this in my plugin cmakelist file to enable the python wrapping or is there another setting to activate ? Thank you Michal -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.civ at mail.mil Wed Jun 14 10:21:32 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Wed, 14 Jun 2017 14:21:32 +0000 Subject: [Paraview-developers] 64bit windows 10 ParaView Compile with VS2015 update 3 (UNCLASSIFIED) Message-ID: CLASSIFICATION: UNCLASSIFIED Hello, I am getting these errors with the plugin compilation..... Please see in the email below... tracking that down, for this error Plugins/VR/pqVRStarterImplementation.h(43): error : Undefined interface In that file, line 43 is one of the following.... --------------------- class pqVRStarterImplementation : public QObject, public pqAutoStartInterface { Q_OBJECT Q_INTERFACES(pqAutoStartInterface) public: pqVRStarterImplementation(QObject* p=0); virtual ~pqVRStarterImplementation(); ----------------------- I am only getting this when I am using QT5 instead of QT4 compiled with VS2015 update 3. QT4 built successfully. Thoughts? Thank you. thanks -simon Build FAILED. "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default target) (2) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata lystScriptGeneratorPlugin.vcxproj.metaproj" (default target) (580) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata lystScriptGeneratorPlugin.vcxproj" (default target) (591) -> (CustomBuild target) -> C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/CatalystScriptGenerator/pqCPA ctionsGroupImplementation.h(46): error : Undefined interface [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata lystScriptGeneratorPlug in.vcxproj] "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default target) (2) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La grangianParticleTracker.vcxproj.metaproj" ( default target) (602) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La grangianParticleTracker.vcxproj" (default t arget) (603) -> C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/LagrangianParticleTracker/pqI ntegrationModelSeedHelperWidgetPWIImpleme ntation.h(43): error : Undefined interface [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La grangianParticleTracker.vcxproj] "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default target) (2) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho gonalSource.vcxproj.metaproj" (default targ et) (606) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho gonalSource.vcxproj" (default target) (609) -> C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/NonOrthogonalSource/pqNonOrth ogonalAutoStartImplementation.h(43): erro r : Undefined interface [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho gonalSource.vcxproj ] "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default target) (2) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj. metaproj" (default target) (616) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj" (default target) (617) -> C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/SLACTools/pqSLACActionGroupIm plementation.h(46): error : Undefined int erface [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj] "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default target) (2) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo ols.vcxproj.metaproj" (default target) (618 ) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo ols.vcxproj" (default target) (619) -> C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/SierraPlotTools/pqSierraPlotT oolsActionGroupImplementation.h(46): erro r : Undefined interface [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo ols.vcxproj] "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default target) (2) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St reamLinesRepresentation.vcxproj.metaproj" ( default target) (622) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St reamLinesRepresentation.vcxproj" (default t arget) (623) -> C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/StreamLinesRepresentation/pqS treamLinesAnimationManagerImplementation. h(43): error : Undefined interface [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St reamLine sRepresentation.vcxproj] "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default target) (2) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj.metaproj " (default target) (634) -> "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj" (default target) (635) -> C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/VR/pqVRStarterImplementation. h(43): error : Undefined interface [c:\Us ers\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj] 0 Warning(s) 7 Error(s) CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Jun 14 11:51:01 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 14 Jun 2017 11:51:01 -0400 Subject: [Paraview-developers] [Non-DoD Source] Re: windows 10 superbuild VS2013 requirement (UNCLASSIFIED) In-Reply-To: References: Message-ID: This fixes it for me at least. https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/343 There is now an ispc binary for vs2015. Before the next release I'll try that out and then make that an option too. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 <(518)%20881-4909> On Wed, Jun 7, 2017 at 11:37 AM, David E DeMarle wrote: > Likely that the compiler check is happening before the flag to disable the > subproject is setup. > Would you mind removing the check (projects/win32/ispc.cmake) and telling > me if condifuration continues? > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > On Wed, Jun 7, 2017 at 10:46 AM, Su, Simon M CIV USARMY RDECOM ARL (US) < > simon.m.su.civ at mail.mil> wrote: > >> CLASSIFICATION: UNCLASSIFIED >> >> thank you David. It is on a clean build. I am equally puzzled. >> >> thanks >> -simon >> >> -----Original Message----- >> From: David E DeMarle [mailto:dave.demarle at kitware.com] >> Sent: Wednesday, June 07, 2017 10:11 AM >> To: Su, Simon M CIV USARMY RDECOM ARL (US) >> Cc: ParaView Developers >> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] windows 10 >> superbuild >> VS2013 requirement (UNCLASSIFIED) >> >> All active links contained in this email were disabled. Please verify the >> identity of the sender, and confirm the authenticity of all links >> contained >> within the message prior to copying and pasting the address to a Web >> browser. >> >> >> ________________________________ >> >> >> >> I don't know why your command to turn off the ispc subproject isn't being >> respected then. >> >> Is c:\Users\one\build\pvsb-5.4\build initially empty or does it still >> have the >> contents of a previous build? >> >> I would expect the above to work fine in a clean build. >> >> >> With a partial or old build, editing cmakecache (via cmake-gui or command >> line) to turn of ispc and configuring should also work. >> >> >> >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> On Wed, Jun 7, 2017 at 9:59 AM, Su, Simon M CIV USARMY RDECOM ARL (US) >> > >> wrote: >> >> >> CLASSIFICATION: UNCLASSIFIED >> >> Thank you David. But I think I also needed something else.... >> Please see >> below. >> >> thanks >> -simon >> >> >> c:\Users\one\build\pvsb-5.4\build>cmake -G >> Ninja -DCMAKE_INSTALL_PREFIX=ParaView-5.4.0 >> -DCMAKE_BUILD_TYPE=Release -DENABLE_mpi:BOOL=ON >> -DENABLE_python:BOOL=ON -DENABLE_paraview:BOOL=ON >> -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF >> -DENABLE_embree:BOOL=OFF -DENABLE_qt4:BOOL=OFF >> -DENABLE_qt5:BOOL=ON -DENABLE_cxx11:BOOL=ON >> -DENABLE_bzip2:BOOL=ON -DENABLE_png:BOOL=ON >> -DENABLE_numpy:BOOL=ON -DENABLE_paraviewtutorial:BOOL=ON >> -DENABLE_paraviewtutorialdata:BOOL=ON >> -DENABLE_paraviewusersguide:BOOL=ON -DENABLE_paraviewweb:BOOL=ON >> -DENABLE_paraviewweblightviz:BOOL=ON >> -DENABLE_paraviewwebvisualizer:BOOL=ON >> -DENABLE_visitbridge:BOOL=ON >> -DENABLE_vrpn:BOOL=ON ..\paraview-superbuild >> >> -- The C compiler identification is MSVC 19.0.24215.1 >> >> -- The CXX compiler identification is MSVC 19.0.24215.1 >> >> -- Check for working C compiler: C:/Program Files (x86)/Microsoft >> Visual >> Studio 14.0/VC/bin/amd64/cl.exe >> >> -- Check for working C compiler: C:/Program Files (x86)/Microsoft >> Visual >> Studio 14.0/VC/bin/amd64/cl.exe -- works >> >> -- Detecting C compiler ABI info >> >> -- Detecting C compiler ABI info - done >> >> -- Check for working CXX compiler: C:/Program Files >> (x86)/Microsoft Visual >> Studio 14.0/VC/bin/amd64/cl.exe >> >> -- Check for working CXX compiler: C:/Program Files >> (x86)/Microsoft Visual >> Studio 14.0/VC/bin/amd64/cl.exe -- works >> >> -- Detecting CXX compiler ABI info >> >> -- Detecting CXX compiler ABI info - done >> >> -- Detecting CXX compile features >> >> -- Detecting CXX compile features - done >> >> -- Check size of void* >> >> -- Check size of void* - done >> >> -- Found Git: C:/Program Files/Git/cmd/git.exe (found version >> "2.10.2.windows.1") >> >> -- Determined source version for paraview: 5.4.0 >> >> CMake Error at projects/win32/ispc.cmake:2 (message): >> >> The ispc project requires Visual Studio 2013. >> >> Call Stack (most recent call first): >> >> superbuild/cmake/SuperbuildMacros.cmake:477 (include) >> >> superbuild/CMakeLists.txt:113 (_superbuild_discover_projects) >> >> >> >> >> >> >> >> -- Configuring incomplete, errors occurred! >> >> See also "C:/Users/one/build/pvsb-5.4/b >> uild/CMakeFiles/CMakeOutput.log". >> >> >> >> >> >> -----Original Message----- >> From: David E DeMarle [Caution-mailto:dave.demarle at kitware.com < >> Caution-mailto:dave.demarle at kitware.com > ] >> Sent: Wednesday, June 07, 2017 8:47 AM >> To: Su, Simon M CIV USARMY RDECOM ARL (US) < >> simon.m.su.civ at mail.mil < >> Caution-mailto:simon.m.su.civ at mail.mil > > >> Cc: ParaView Developers > Caution-mailto:paraview-developers at paraview.org > > >> Subject: [Non-DoD Source] Re: [Paraview-developers] windows 10 >> superbuild >> VS2013 requirement (UNCLASSIFIED) >> >> All active links contained in this email were disabled. Please >> verify the >> identity of the sender, and confirm the authenticity of all links >> contained >> within the message prior to copying and pasting the address to a >> Web browser. >> >> >> ________________________________ >> >> >> >> Turn off embree as well. >> >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 < tel:518-881-4909 > >> >> On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL >> (US) >> > > < >> Caution-Caution-mailto:simon.m.su.civ at mail.mil < >> Caution-mailto:simon.m.su.civ at mail.mil > > > wrote: >> >> >> CLASSIFICATION: UNCLASSIFIED >> >> Hello, >> >> On Windows 10 64bit, when I tried to use VS 2015 >> community for my >> ParaView >> superbuild build, the cmake is complaining ospray >> requires VS2013 >> even when >> I have the following set >> >> -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF >> >> Is there a way to use VS2015 community compiler to build >> ParaView >> superbuild? >> >> thank you much >> -simon >> >> >> CLASSIFICATION: UNCLASSIFIED >> >> _______________________________________________ >> Powered by Caution-Caution-www.kitware.com < >> Caution-http://Caution-Caution-www.kitware.com > < >> Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com >> > > >> >> Visit other Kitware open-source projects at >> Caution-Caution-http://www.kitware.com/opensource/opensource.html >> < >> Caution-http://www.kitware.com/opensource/opensource.html > < >> Caution-Caution-http://www.kitware.com/opensource/opensource.html >> < >> Caution-http://www.kitware.com/opensource/opensource.html > > >> >> Search the list archives at: >> Caution-Caution-http://markmail.org/search/?q=Paraview-developers >> < >> Caution-http://markmail.org/search/?q=Paraview-developers > < >> Caution-Caution-http://markmail.org/search/?q=Paraview-developers >> < >> Caution-http://markmail.org/search/?q=Paraview-developers > > >> >> Follow this link to subscribe/unsubscribe: >> Caution-Caution-http://public. >> kitware.com/mailman/listinfo/paraview-developers >> < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers >> > < >> Caution-Caution-http://public.kitware.com/mailman/listinfo/p >> araview-developers >> < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers >> > > >> >> >> >> >> >> CLASSIFICATION: UNCLASSIFIED >> >> >> >> >> CLASSIFICATION: UNCLASSIFIED >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.civ at mail.mil Wed Jun 14 13:38:47 2017 From: simon.m.su.civ at mail.mil (Su, Simon M CIV USARMY RDECOM ARL (US)) Date: Wed, 14 Jun 2017 17:38:47 +0000 Subject: [Paraview-developers] [Non-DoD Source] Re: windows 10 superbuild VS2013 requirement (UNCLASSIFIED) In-Reply-To: References: Message-ID: CLASSIFICATION: UNCLASSIFIED David, With VS2015 and with QT4, removing projects/win32/ispc.cmake file and add in -DENABLE_embree:BOOL=OFF will work if I also add in -DENABLE_vtkm:BOOL=OFF as the next thing the build process will complain is the tbb. Since we are interested in looking at the VRPN plugin part, it will work for what we are doing now. QT5 is failing somehow as I am looking into that to make sure that our work will survive when QT4 is removed. But for the time being, we can move forward. Thank you. thanks -simon -----Original Message----- From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Wednesday, June 14, 2017 11:51 AM To: Su, Simon M CIV USARMY RDECOM ARL (US) Cc: ParaView Developers Subject: Re: [Non-DoD Source] Re: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ This fixes it for me at least. Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/343 < Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/343 > There is now an ispc binary for vs2015. Before the next release I'll try that out and then make that an option too. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 < tel:(518)%20881-4909 > On Wed, Jun 7, 2017 at 11:37 AM, David E DeMarle > wrote: Likely that the compiler check is happening before the flag to disable the subproject is setup. Would you mind removing the check (projects/win32/ispc.cmake) and telling me if condifuration continues? David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 < tel:(518)%20881-4909 > On Wed, Jun 7, 2017 at 10:46 AM, Su, Simon M CIV USARMY RDECOM ARL (US) > wrote: CLASSIFICATION: UNCLASSIFIED thank you David. It is on a clean build. I am equally puzzled. thanks -simon -----Original Message----- From: David E DeMarle [Caution-mailto:dave.demarle at kitware.com < Caution-mailto:dave.demarle at kitware.com > ] Sent: Wednesday, June 07, 2017 10:11 AM To: Su, Simon M CIV USARMY RDECOM ARL (US) > Cc: ParaView Developers > Subject: Re: [Non-DoD Source] Re: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ I don't know why your command to turn off the ispc subproject isn't being respected then. Is c:\Users\one\build\pvsb-5.4\build initially empty or does it still have the contents of a previous build? I would expect the above to work fine in a clean build. With a partial or old build, editing cmakecache (via cmake-gui or command line) to turn of ispc and configuring should also work. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 < tel:518-881-4909 > On Wed, Jun 7, 2017 at 9:59 AM, Su, Simon M CIV USARMY RDECOM ARL (US) < Caution-Caution-mailto:simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > > > wrote: CLASSIFICATION: UNCLASSIFIED Thank you David. But I think I also needed something else.... Please see below. thanks -simon c:\Users\one\build\pvsb-5.4\build>cmake -G Ninja -DCMAKE_INSTALL_PREFIX=ParaView-5.4.0 -DCMAKE_BUILD_TYPE=Release -DENABLE_mpi:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF -DENABLE_embree:BOOL=OFF -DENABLE_qt4:BOOL=OFF -DENABLE_qt5:BOOL=ON -DENABLE_cxx11:BOOL=ON -DENABLE_bzip2:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_paraviewtutorial:BOOL=ON -DENABLE_paraviewtutorialdata:BOOL=ON -DENABLE_paraviewusersguide:BOOL=ON -DENABLE_paraviewweb:BOOL=ON -DENABLE_paraviewweblightviz:BOOL=ON -DENABLE_paraviewwebvisualizer:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DENABLE_vrpn:BOOL=ON ..\paraview-superbuild -- The C compiler identification is MSVC 19.0.24215.1 -- The CXX compiler identification is MSVC 19.0.24215.1 -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/bin/amd64/cl.exe -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Check size of void* -- Check size of void* - done -- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.10.2.windows.1") -- Determined source version for paraview: 5.4.0 CMake Error at projects/win32/ispc.cmake:2 (message): The ispc project requires Visual Studio 2013. Call Stack (most recent call first): superbuild/cmake/SuperbuildMacros.cmake:477 (include) superbuild/CMakeLists.txt:113 (_superbuild_discover_projects) -- Configuring incomplete, errors occurred! See also "C:/Users/one/build/pvsb-5.4/build/CMakeFiles/CMakeOutput.log". -----Original Message----- From: David E DeMarle [Caution-Caution-mailto:dave.demarle at kitware.com < Caution-mailto:dave.demarle at kitware.com > < Caution-Caution-mailto:dave.demarle at kitware.com < Caution-mailto:dave.demarle at kitware.com > > ] Sent: Wednesday, June 07, 2017 8:47 AM To: Su, Simon M CIV USARMY RDECOM ARL (US) < Caution-Caution-mailto:simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > > > Cc: ParaView Developers < Caution-Caution-mailto:paraview-developers at paraview.org < Caution-mailto:paraview-developers at paraview.org > > > Subject: [Non-DoD Source] Re: [Paraview-developers] windows 10 superbuild VS2013 requirement (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ________________________________ Turn off embree as well. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 < tel:518-881-4909 > < tel:518-881-4909 < tel:518-881-4909 > > On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL (US) < Caution-Caution-mailto:simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > > < Caution-Caution-Caution-mailto:simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > < Caution-Caution-mailto:simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > > > > wrote: CLASSIFICATION: UNCLASSIFIED Hello, On Windows 10 64bit, when I tried to use VS 2015 community for my ParaView superbuild build, the cmake is complaining ospray requires VS2013 even when I have the following set -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF Is there a way to use VS2015 community compiler to build ParaView superbuild? thank you much -simon CLASSIFICATION: UNCLASSIFIED _______________________________________________ Powered by Caution-Caution-Caution-www.kitware.com < Caution-http://Caution-Caution-Caution-www.kitware.com > < Caution-Caution-http://Caution-Caution-Caution-www.kitware.com < Caution-http://Caution-Caution-Caution-www.kitware.com > > < Caution-Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com > < Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com > > > Visit other Kitware open-source projects at Caution-Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > < Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > > < Caution-Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > < Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html > > > Search the list archives at: Caution-Caution-Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > < Caution-Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > > < Caution-Caution-Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > < Caution-Caution-http://markmail.org/search/?q=Paraview-developers < Caution-http://markmail.org/search/?q=Paraview-developers > > > Follow this link to subscribe/unsubscribe: Caution-Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > < Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > > < Caution-Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > < Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview-developers < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers > > > CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED CLASSIFICATION: UNCLASSIFIED -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5567 bytes Desc: not available URL: From dlawrie at ara.co.uk Fri Jun 16 07:41:52 2017 From: dlawrie at ara.co.uk (David Lawrie) Date: Fri, 16 Jun 2017 11:41:52 +0000 Subject: [Paraview-developers] Custom menu's with sub-menus Message-ID: Hi, I have been looking at adding toolbars and menus to the ParaView GUI and have followed the SourceToolbarActions example. Using this I have been able to create a menu and populate it with some filters and get them running. My question is how would I add categories to further organise the filters? I cannot see how this would be possible using the mechanism the example uses. Is there an alternative approach I should be investigating (e.g. can I use pqParaViewMenuBuilders from a plugin?) Thanks. ********************************************************************** Please consider the environment. Only print this email if absolutely necessary. This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ********************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From hadrien.foucault at areva.com Fri Jun 16 11:47:07 2017 From: hadrien.foucault at areva.com (FOUCAULT Hadrien (AREVA)) Date: Fri, 16 Jun 2017 15:47:07 +0000 Subject: [Paraview-developers] Creation of a ParaView Python table reader plugin Message-ID: <2F2099B4FDF54249B115E840F54E9704B5C138@FFRMRCSMX15.fdom.ad.corp> Hi all, I am trying to create a ParaView reader for fort.11 data, a text format used in-house, I've attached a sample. The goal is to display those data first as a spreadsheetview and then to pick some of the variables to be plotted and modified with the calculator. I have tried different way to create a reader and I believe the best one is to use Python as described in this thread: http://markmail.org/message/2pnrmzkbx5n2u3ke So far I have successfully written a vtk script to load my data in a vtkTable and plot some of the variable. The script can be called from the python shell and open a new vtk window showing an test plot. In order to make the reader script into a plugin I have reused the RingleReader example from the mailing-list and adapted it a little for my needs. When I open a fort.11 file and apply nothing seems to be really happening and no error displayed if I leave "output=self.GetUnstructuredGridOutput()" (which is wrong) but if I only call "self.GetOutput()" an indentation error and missing request data error is thrown. To identify the issue I tried to make another simple csv reader based on https://www.paraview.org/Wiki/Python_calculator_and_programmable_filter#Programmable_Source and still the ringle reader and the result is the same, no data loaded and no error. If I change the output I find the same indentation and missing request data error. When using the vtk reader script in the python shell I am able to access my vtkTable with all the data loaded into it but I don't know how to put this data into a spreadsheetview wich is kind of infuriating. Does anyone have successfully made a ParaView Python Reader Plugin with a vtkTable output? I must be missing something when I output my data to ParaView since I don't really understand how the data are sent to views for vtkTable. I am using ParaView 5.0.1. Any suggestions gratefully accepted, Hadrien Foucault Intern at Areva NP -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CSVNumpyReader.xml Type: text/xml Size: 1761 bytes Desc: CSVNumpyReader.xml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fort.11 Type: application/octet-stream Size: 93970 bytes Desc: fort.11 URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fort_read.py Type: application/octet-stream Size: 2872 bytes Desc: fort_read.py URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fort11Reader.xml Type: text/xml Size: 3056 bytes Desc: Fort11Reader.xml URL: From Orlando.RIVERA at mtu.de Mon Jun 19 10:20:46 2017 From: Orlando.RIVERA at mtu.de (RIVERA ROLDAN, Jorge Orlando) Date: Mon, 19 Jun 2017 14:20:46 +0000 Subject: [Paraview-developers] paraview with mesa 3d Message-ID: HI I am trying to understand the system architecture of paraview with mesa I am building according to this page: https://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D using PV 5.3, LLVM 4.00 and Mesa 17.0.0 , and to be run on a 24-core machine with no graphic card- I have successfully built, however, as expected (-DPARAVIEW_BUILD_QT_GUI=OFF) I do not have the client. When I try to build the client (paraview ) I have undefined symbols errors coming form Xlib which I think, it is not a surprise , since I am also passing (-DVTK_USE_X=OFF) So my thoughts are; Do I need to build a server with mesa , and a client with native GL ? so far so good. What about our in-house readers ? Do I need to rebuild these twice, once for the server side and once for the client side? Would it be compatible ? Could it be possible to have the client built with mesa ? I would rather avoid the client/server architecture Thanks in advance Orlando Rivera Mit freundlichen Gruessen / Best Regards Orlando Rivera MTU Aero Engines AG Engineering Systems CAE (POEA) Dachauer Str. 665 80995 Muenchen Germany Tel +49 89 1489-6689 Fax +49 (0)89 14 89-96951 orlando.rivera at mtu.de http://www.mtu.de -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mark.Olesen at esi-group.com Mon Jun 19 10:40:06 2017 From: Mark.Olesen at esi-group.com (Mark Olesen) Date: Mon, 19 Jun 2017 14:40:06 +0000 Subject: [Paraview-developers] paraview with mesa 3d In-Reply-To: References: Message-ID: Hi Orlando, I posed a related question a few months back (http://public.kitware.com/pipermail/paraview/2017-January/039077.html) that might help you. cheers, /mark ________________________________________ From: Paraview-developers on behalf of RIVERA ROLDAN, Jorge Orlando Sent: Monday, June 19, 2017 4:20:46 PM To: paraview-developers at paraview.org Subject: [Paraview-developers] paraview with mesa 3d HI I am trying to understand the system architecture of paraview with mesa I am building according to this page: https://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D using PV 5.3, LLVM 4.00 and Mesa 17.0.0 , and to be run on a 24-core machine with no graphic card- I have successfully built, however, as expected (-DPARAVIEW_BUILD_QT_GUI=OFF) I do not have the client. When I try to build the client (paraview ) I have undefined symbols errors coming form Xlib which I think, it is not a surprise , since I am also passing (-DVTK_USE_X=OFF) So my thoughts are; Do I need to build a server with mesa , and a client with native GL ? so far so good. What about our in-house readers ? Do I need to rebuild these twice, once for the server side and once for the client side? Would it be compatible ? Could it be possible to have the client built with mesa ? I would rather avoid the client/server architecture Thanks in advance Orlando Rivera Mit freundlichen Gruessen / Best Regards Orlando Rivera MTU Aero Engines AG Engineering Systems CAE (POEA) Dachauer Str. 665 80995 Muenchen Germany Tel +49 89 1489-6689 Fax +49 (0)89 14 89-96951 orlando.rivera at mtu.de http://www.mtu.de -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From claire.guilbaud at gmail.com Tue Jun 20 06:07:18 2017 From: claire.guilbaud at gmail.com (Claire Guilbaud) Date: Tue, 20 Jun 2017 12:07:18 +0200 Subject: [Paraview-developers] PV5.4 from superbuild Message-ID: Hi all, I'm trying to install PV5.4 from superbuild in an offline environnement. Just for information, I have two troubles with the superbuild, that I easily bypass : 1. the make download-all command, download zlib1.2.7 but during compilation ask for version >= 1.2.8 ? 2. I'm using cmake 3.7.2, and the owner of the directory where I build is not respected (It takes my home group). It's an issue we've got 1 or 2 years ago when installing ParaView. Kitware France made a patch available in cmake 3.6 (or something like that) to resolve this issue. Have a good day Claire -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Tue Jun 20 09:53:36 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Tue, 20 Jun 2017 09:53:36 -0400 Subject: [Paraview-developers] PV5.4 from superbuild In-Reply-To: References: Message-ID: Hi Claire, I know the first issue (zlib version) is fixed in the superbuild's master branch (which can still build 5.4). I'm not sure about the second issue. HTH, Shawn On Tue, Jun 20, 2017 at 6:07 AM, Claire Guilbaud wrote: > Hi all, > > I'm trying to install PV5.4 from superbuild in an offline environnement. > Just for information, I have two troubles with the superbuild, that I > easily bypass : > > 1. the make download-all command, download zlib1.2.7 but during > compilation ask for version >= 1.2.8 ? > 2. I'm using cmake 3.7.2, and the owner of the directory where I build > is not respected (It takes my home group). It's an issue we've got 1 or 2 > years ago when installing ParaView. Kitware France made a patch available > in cmake 3.6 (or something like that) to resolve this issue. > > Have a good day > > Claire > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.moser at rwth-aachen.de Wed Jun 21 09:32:45 2017 From: markus.moser at rwth-aachen.de (Mizael Moser, Markus Klaus) Date: Wed, 21 Jun 2017 13:32:45 +0000 Subject: [Paraview-developers] Parallel Reader Plugin, Grid false Message-ID: <1497995702045.51195@rwth-aachen.de> Dear ParaView developers, I wrote a plugin to read in structured grid HDF5 fiels but I am having problems with running the plugin in parallel. The grid isn't loaded/visualized correctly when running the plugin in parallel. The grid is open at the end of the axis, where the extent is divided. It appears that ParaView doesn't know,when running in parallel, that the grid is finished there. The data is loaded correctly into the "false" grid. I get no error and it looks fine except for the grid part that is missing. If i run the plugin in serial everything is fine. The plugin inherits from vtkMultiBlockDataSet and looks like this: Request information: //Basic stuff //extent[6] //read the extent from the grid and store it in extent this->internalBlocks->Blocks[0]->SetExtent(0,extent[1], 0, extent[3],0, extent[5]); //outinfo GetInformationObject and CAN_PRODUCE_SUB_EXTENT outInfo ->Set(vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),extent,6); RequestData: vtkInformation *outInfo = outputVector->GetInformationObject(0); vtkMultiBlockDataSet* multiBlock = vtkMultiBlockDataSet::SafeDownCast(outInfo->Get(vtkDataObject::DATA_OBJECT())); vtkStructuredGrid* nthGrid = this->internalBlocks->Blocks[0]; int subext[6]; outInfo->Get(vtkStreamingDemandDrivenPipeline::UPDATE_EXTENT(),subext;) int size[3]={0,0,0}; size[0]=subext[5]-subext[4]+1; size[1]=subext[3]-subext[2]+1; size[2]=subext[1]-subext[0]+1; //stuff //reading the points in x,y,z for each process with the offset etc. vtkPoints *points = vtkPoints::New(); for(int k=0; kInsertNextPoint(x[pointId],y[pointId],z[pointId]); } } } nthGrid->SetPoints(points); //Loading the Data For example the dimension is 151x122x50, and i run it with 2 MPI processes then i get the following outputs for the grid: The extent from CPU0 is: 0-75, 0-122, 0-50 and the corresponding size is 76, 123, 51 The extent from CPU1 is 75-150, 0-122,0-50 and the corresponding size is 76, 123, 51 The data is divided correctly and the output looks fine, doesn't it? What am i doing wrong? Thanks in advance, Markus Moser Student Assistant Chair of Fluid Mechanics and Institute of Aerodynamics Aachen RWTH Aachen -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Wed Jun 21 09:57:34 2017 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 21 Jun 2017 13:57:34 +0000 Subject: [Paraview-developers] SPHDatasetInterpolator multi-threaded? Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6843915589@MBX111.d.ethz.ch> I have been testing the different versions of SPH*Interpolators in ParaView, with a TBB execution model. While the SPH{Line,Plane,Volume}Interpolators demonstrate nice multi-threading behavior, I am finding out that the newest edition, the generic SPHDatasetInterpolator which enables the use of any vtkDataset as sources, does not always use multi-threading. I have built a stand-alone test case which demonstrates that if a vtkImageData is giving as Source, then the execution switches back to a single thread, and takes much longer. Further, I demonstrated that if the same vtkImageData is passed to an "Extract Surface", and if the PolyData generated is used as the interpolator's source, then the multi-threading is restored. It seems strange since the source code of vtkSPHInterpolator.cxx shows that a different branch is coded for vtkImageData saying that it ought to be sligthly faster. I am finding out however, that the execution seems to drop the multi-threaded support. Has anyone seen this behavior? I am using v5.4. I have a python script demonstrator which does not require any external dataset, so it is easy to test. Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire.guilbaud at gmail.com Thu Jun 22 10:00:37 2017 From: claire.guilbaud at gmail.com (Claire Guilbaud) Date: Thu, 22 Jun 2017 16:00:37 +0200 Subject: [Paraview-developers] automatic data download behind a proxy Message-ID: Hi all, I have the same problem when building VTK or ParaView (superbuild) when there are automatic download (like in superbuild with command make download-all). At work, we are behind a proxy. I set http_proxy and https_proxy environment variables. I also add a ssh-keys in my account, and configure a host in .ssh/config as follow : Host gitlab.kitware.com User claireguilbaud RSAAuthentication no GSSAPIAuthentication no IdentityFile ~/.ssh/config/id_rsa_gitlab_kitware But I never achieve to download any files. I try other configurations, but neither works. I bypass the issue by downloading manually all the files, but for VTK, I have a trouble with the test images (make VTKData failed). Does anyone know how to solve this issue ? Thanks for your help. Claire -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jun 22 18:58:06 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 22 Jun 2017 22:58:06 +0000 Subject: [Paraview-developers] Surface LIC Message-ID: I asked before, but can't remember. Why isn't the surface LIC plugin enabled by default? Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Jun 23 09:10:01 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Jun 2017 09:10:01 -0400 Subject: [Paraview-developers] Surface LIC In-Reply-To: References: Message-ID: The plugin is enabled by default. Do you mean why is it a plugin at all? That was because when it was added, it only worked on modern GPUs. We should reevaluate that. I suspect we are now in a world where the GPUs are modern enough in general. On Thu, Jun 22, 2017 at 6:58 PM, Scott, W Alan wrote: > I asked before, but can?t remember. Why isn?t the surface LIC plugin > enabled by default? > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From wascott at sandia.gov Fri Jun 23 12:03:30 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 23 Jun 2017 16:03:30 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Surface LIC In-Reply-To: References: Message-ID: The SurfaceLIC is not loaded by default in the plugin manager, on either my Windows computer or Linux box. What am I missing? > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, June 23, 2017 7:10 AM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Surface LIC > > The plugin is enabled by default. Do you mean why is it a plugin at all? That > was because when it was added, it only worked on modern GPUs. We should > reevaluate that. I suspect we are now in a world where the GPUs are > modern enough in general. > > > > On Thu, Jun 22, 2017 at 6:58 PM, Scott, W Alan wrote: > > I asked before, but can?t remember. Why isn?t the surface LIC plugin > > enabled by default? > > > > > > > > Thanks, > > > > > > > > Alan > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0822 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > > > > > The most exciting phrase to hear in science > > > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > > > --------------------------------------------------------- > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- A non-text attachment was scrubbed... Name: junkScreenshot1.JPG Type: image/jpeg Size: 72758 bytes Desc: junkScreenshot1.JPG URL: From utkarsh.ayachit at kitware.com Fri Jun 23 12:07:37 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Jun 2017 12:07:37 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Surface LIC In-Reply-To: References: Message-ID: You mean "loaded", and not "enabled" :). It's enabled by default, but not loaded. If you think the plugin should be loaded by default, it's worthwhile thinking if it should even be a plugin and instead be incorporated into the standard application. On Fri, Jun 23, 2017 at 12:03 PM, Scott, W Alan wrote: > The SurfaceLIC is not loaded by default in the plugin manager, on either my Windows computer or Linux box. What am I missing? > > > >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, June 23, 2017 7:10 AM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org >> Subject: [EXTERNAL] Re: [Paraview-developers] Surface LIC >> >> The plugin is enabled by default. Do you mean why is it a plugin at all? That >> was because when it was added, it only worked on modern GPUs. We should >> reevaluate that. I suspect we are now in a world where the GPUs are >> modern enough in general. >> >> >> >> On Thu, Jun 22, 2017 at 6:58 PM, Scott, W Alan wrote: >> > I asked before, but can?t remember. Why isn?t the surface LIC plugin >> > enabled by default? >> > >> > >> > >> > Thanks, >> > >> > >> > >> > Alan >> > >> > >> > >> > -------------------------------------------------------- >> > >> > W. Alan Scott >> > >> > ParaView Support Manager >> > >> > >> > >> > SAIC >> > >> > Sandia National Laboratories, MS 0822 >> > >> > Org 9326 - Building 880 A1-K >> > >> > (505) 284-0932 FAX (505) 284-5619 >> > >> > >> > >> > The most exciting phrase to hear in science >> > >> > is not "Eureka!" but "That's funny..." -- Isaac Asimov >> > >> > --------------------------------------------------------- >> > >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > From wascott at sandia.gov Fri Jun 23 12:17:18 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 23 Jun 2017 16:17:18 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Surface LIC In-Reply-To: References: Message-ID: Ah, makes sense. OK, why don't we load it by default, whether as a built in functionality, or a plugin? My concern is that users will never load that plugin, thus a really neat functionality is never discovered. Alan > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Friday, June 23, 2017 10:08 AM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: Re: [EXTERNAL] Re: [Paraview-developers] Surface LIC > > You mean "loaded", and not "enabled" :). It's enabled by default, but not > loaded. If you think the plugin should be loaded by default, it's worthwhile > thinking if it should even be a plugin and instead be incorporated into the > standard application. > > On Fri, Jun 23, 2017 at 12:03 PM, Scott, W Alan wrote: > > The SurfaceLIC is not loaded by default in the plugin manager, on either my > Windows computer or Linux box. What am I missing? > > > > > > > >> -----Original Message----- > >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Sent: Friday, June 23, 2017 7:10 AM > >> To: Scott, W Alan > >> Cc: paraview-developers at paraview.org > >> Subject: [EXTERNAL] Re: [Paraview-developers] Surface LIC > >> > >> The plugin is enabled by default. Do you mean why is it a plugin at > >> all? That was because when it was added, it only worked on modern > >> GPUs. We should reevaluate that. I suspect we are now in a world > >> where the GPUs are modern enough in general. > >> > >> > >> > >> On Thu, Jun 22, 2017 at 6:58 PM, Scott, W Alan > wrote: > >> > I asked before, but can?t remember. Why isn?t the surface LIC > >> > plugin enabled by default? > >> > > >> > > >> > > >> > Thanks, > >> > > >> > > >> > > >> > Alan > >> > > >> > > >> > > >> > -------------------------------------------------------- > >> > > >> > W. Alan Scott > >> > > >> > ParaView Support Manager > >> > > >> > > >> > > >> > SAIC > >> > > >> > Sandia National Laboratories, MS 0822 > >> > > >> > Org 9326 - Building 880 A1-K > >> > > >> > (505) 284-0932 FAX (505) 284-5619 > >> > > >> > > >> > > >> > The most exciting phrase to hear in science > >> > > >> > is not "Eureka!" but "That's funny..." -- Isaac Asimov > >> > > >> > --------------------------------------------------------- > >> > > >> > > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Search the list archives at: > >> > http://markmail.org/search/?q=Paraview-developers > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > From utkarsh.ayachit at kitware.com Fri Jun 23 12:34:16 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Jun 2017 12:34:16 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Surface LIC In-Reply-To: References: Message-ID: As I mention earlier in this thread, originally (~6-7 years ago, when we added the plugin), that was because it only worked on modern GPUs. We should reevaluate that. I suspect we are now in a world where the GPUs are modern enough in general. On Fri, Jun 23, 2017 at 12:17 PM, Scott, W Alan wrote: > Ah, makes sense. OK, why don't we load it by default, whether as a built in functionality, or a plugin? My concern is that users will never load that plugin, thus a really neat functionality is never discovered. > > Alan > >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, June 23, 2017 10:08 AM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org >> Subject: Re: [EXTERNAL] Re: [Paraview-developers] Surface LIC >> >> You mean "loaded", and not "enabled" :). It's enabled by default, but not >> loaded. If you think the plugin should be loaded by default, it's worthwhile >> thinking if it should even be a plugin and instead be incorporated into the >> standard application. >> >> On Fri, Jun 23, 2017 at 12:03 PM, Scott, W Alan wrote: >> > The SurfaceLIC is not loaded by default in the plugin manager, on either my >> Windows computer or Linux box. What am I missing? >> > >> > >> > >> >> -----Original Message----- >> >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> >> Sent: Friday, June 23, 2017 7:10 AM >> >> To: Scott, W Alan >> >> Cc: paraview-developers at paraview.org >> >> Subject: [EXTERNAL] Re: [Paraview-developers] Surface LIC >> >> >> >> The plugin is enabled by default. Do you mean why is it a plugin at >> >> all? That was because when it was added, it only worked on modern >> >> GPUs. We should reevaluate that. I suspect we are now in a world >> >> where the GPUs are modern enough in general. >> >> >> >> >> >> >> >> On Thu, Jun 22, 2017 at 6:58 PM, Scott, W Alan >> wrote: >> >> > I asked before, but can?t remember. Why isn?t the surface LIC >> >> > plugin enabled by default? >> >> > >> >> > >> >> > >> >> > Thanks, >> >> > >> >> > >> >> > >> >> > Alan >> >> > >> >> > >> >> > >> >> > -------------------------------------------------------- >> >> > >> >> > W. Alan Scott >> >> > >> >> > ParaView Support Manager >> >> > >> >> > >> >> > >> >> > SAIC >> >> > >> >> > Sandia National Laboratories, MS 0822 >> >> > >> >> > Org 9326 - Building 880 A1-K >> >> > >> >> > (505) 284-0932 FAX (505) 284-5619 >> >> > >> >> > >> >> > >> >> > The most exciting phrase to hear in science >> >> > >> >> > is not "Eureka!" but "That's funny..." -- Isaac Asimov >> >> > >> >> > --------------------------------------------------------- >> >> > >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Search the list archives at: >> >> > http://markmail.org/search/?q=Paraview-developers >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > From wascott at sandia.gov Fri Jun 23 13:33:32 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 23 Jun 2017 17:33:32 +0000 Subject: [Paraview-developers] Example visualizations and data analysis Message-ID: I'm reading notes from a friend that watched me demo ParaView at SC15 (Lucy Nowell). A comment she made was to show off data analytics more. Could we get a plot over line as one of the Example Visualizations? How about adding the spreadsheet? Maybe add it to the Wavelet? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.JPG Type: image/jpeg Size: 171258 bytes Desc: Capture.JPG URL: From utkarsh.ayachit at kitware.com Fri Jun 23 13:50:13 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 23 Jun 2017 13:50:13 -0400 Subject: [Paraview-developers] Example visualizations and data analysis In-Reply-To: References: Message-ID: Surely. If you have a visualization in mind, feel free to send us the state file and any data files associated with it. Should be easy to add. On Fri, Jun 23, 2017 at 1:33 PM, Scott, W Alan wrote: > I?m reading notes from a friend that watched me demo ParaView at SC15 (Lucy > Nowell). A comment she made was to show off data analytics more. Could we > get a plot over line as one of the Example Visualizations? How about adding > the spreadsheet? Maybe add it to the Wavelet? > > > > Alan > > > > > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Tue Jun 27 15:53:12 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 27 Jun 2017 15:53:12 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Example visualizations and data analysis In-Reply-To: References: Message-ID: I like it! I'll go ahead and add it. On Fri, Jun 23, 2017 at 2:58 PM, Scott, W Alan wrote: > I wanted to keep the ParaView download as small as possible, so re-used disk_out_ref. How about this state file? Too busy? > > Alan > > > >> -----Original Message----- >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >> Sent: Friday, June 23, 2017 11:50 AM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org >> Subject: [EXTERNAL] Re: [Paraview-developers] Example visualizations and >> data analysis >> >> Surely. If you have a visualization in mind, feel free to send us the state file >> and any data files associated with it. Should be easy to add. >> >> On Fri, Jun 23, 2017 at 1:33 PM, Scott, W Alan wrote: >> > I?m reading notes from a friend that watched me demo ParaView at SC15 >> > (Lucy Nowell). A comment she made was to show off data analytics >> > more. Could we get a plot over line as one of the Example >> > Visualizations? How about adding the spreadsheet? Maybe add it to the >> Wavelet? >> > >> > >> > >> > Alan >> > >> > >> > >> > >> > >> > >> > >> > -------------------------------------------------------- >> > >> > W. Alan Scott >> > >> > ParaView Support Manager >> > >> > >> > >> > SAIC >> > >> > Sandia National Laboratories, MS 0822 >> > >> > Org 9326 - Building 880 A1-K >> > >> > (505) 284-0932 FAX (505) 284-5619 >> > >> > >> > >> > The most exciting phrase to hear in science >> > >> > is not "Eureka!" but "That's funny..." -- Isaac Asimov >> > >> > --------------------------------------------------------- >> > >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > From wascott at sandia.gov Tue Jun 27 15:56:10 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 27 Jun 2017 19:56:10 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Example visualizations and data analysis In-Reply-To: References: Message-ID: What a team... > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Tuesday, June 27, 2017 1:53 PM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: Re: [EXTERNAL] Re: [Paraview-developers] Example visualizations > and data analysis > > I like it! I'll go ahead and add it. > > On Fri, Jun 23, 2017 at 2:58 PM, Scott, W Alan wrote: > > I wanted to keep the ParaView download as small as possible, so re-used > disk_out_ref. How about this state file? Too busy? > > > > Alan > > > > > > > >> -----Original Message----- > >> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >> Sent: Friday, June 23, 2017 11:50 AM > >> To: Scott, W Alan > >> Cc: paraview-developers at paraview.org > >> Subject: [EXTERNAL] Re: [Paraview-developers] Example visualizations > >> and data analysis > >> > >> Surely. If you have a visualization in mind, feel free to send us the > >> state file and any data files associated with it. Should be easy to add. > >> > >> On Fri, Jun 23, 2017 at 1:33 PM, Scott, W Alan > wrote: > >> > I?m reading notes from a friend that watched me demo ParaView at > >> > SC15 (Lucy Nowell). A comment she made was to show off data > >> > analytics more. Could we get a plot over line as one of the > >> > Example Visualizations? How about adding the spreadsheet? Maybe > >> > add it to the > >> Wavelet? > >> > > >> > > >> > > >> > Alan > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > -------------------------------------------------------- > >> > > >> > W. Alan Scott > >> > > >> > ParaView Support Manager > >> > > >> > > >> > > >> > SAIC > >> > > >> > Sandia National Laboratories, MS 0822 > >> > > >> > Org 9326 - Building 880 A1-K > >> > > >> > (505) 284-0932 FAX (505) 284-5619 > >> > > >> > > >> > > >> > The most exciting phrase to hear in science > >> > > >> > is not "Eureka!" but "That's funny..." -- Isaac Asimov > >> > > >> > --------------------------------------------------------- > >> > > >> > > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Search the list archives at: > >> > http://markmail.org/search/?q=Paraview-developers > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > From david.thompson at kitware.com Tue Jun 27 19:12:01 2017 From: david.thompson at kitware.com (David Thompson) Date: Tue, 27 Jun 2017 19:12:01 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app Message-ID: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> Hi all, I'm working to turn CMB (a custom PV application) from a single, pqRenderView-based app into a multi-view app. I've changed its ".ui" file to create pqTabbedMultiViewWidget instead of just a QWidget, but I don't see a way to tell the application to use pqViewFrame with the title-bar and decorations enabled. Can anyone provide a hint on where to look? Thanks, Daviod From utkarsh.ayachit at kitware.com Wed Jun 28 14:17:36 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 28 Jun 2017 14:17:36 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app In-Reply-To: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> References: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> Message-ID: David, pqViewFrame will be automatically created if you create (and register) a RenderView proxy. Rather a Layout and then a RenderView proxy. `pqDefaultViewBehavior` ensure a view is created when application starts up, FYI. Also look at other behaviors in `pqParaViewBehaviors`. You may also need `pqStandardViewFrameActionsImplementation`. Utkarsh On Tue, Jun 27, 2017 at 7:12 PM, David Thompson wrote: > Hi all, > > I'm working to turn CMB (a custom PV application) from a single, pqRenderView-based app into a multi-view app. I've changed its ".ui" file to create pqTabbedMultiViewWidget instead of just a QWidget, but I don't see a way to tell the application to use pqViewFrame with the title-bar and decorations enabled. > > Can anyone provide a hint on where to look? > > Thanks, > Daviod > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From david.thompson at kitware.com Wed Jun 28 16:43:46 2017 From: david.thompson at kitware.com (David Thompson) Date: Wed, 28 Jun 2017 16:43:46 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app In-Reply-To: References: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> Message-ID: Hi Utkarsh, I fear that CMB has disabled view frame titlebar+decoration visibilty in some arcane manner. > pqViewFrame will be automatically created if you create (and register) > a RenderView proxy. Rather a Layout and then a RenderView proxy. I added breakpoints to the pqFrame constructor and it is being created. But when I add breakpoints to the destructor, it is being called as well (before the first render) inside pqMultiViewWidget::reload(). > `pqDefaultViewBehavior` ensure a view is created when application > starts up, FYI. Also look at other behaviors in `pqParaViewBehaviors`. > You may also need `pqStandardViewFrameActionsImplementation`. CMB creates a pqParaViewBehaviors instance. It was calling pqParaViewBehaviors::setEnableStandardViewFrameActions(false); before creating an instance, but changing this to true had no effect on the view frame. CMB does not explicitly create a layout proxy, and neither does it alter PV's XML ViewLayoutProxy. It just calls builder->createView( pqRenderView::renderViewType(), activeServer); inside a slot named onServerCreationFinished. Should I be asking the builder to create a layout proxy first? Thanks, David From utkarsh.ayachit at kitware.com Wed Jun 28 16:51:07 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 28 Jun 2017 16:51:07 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app In-Reply-To: References: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> Message-ID: > CMB does not explicitly create a layout proxy, and neither does it alter PV's XML ViewLayoutProxy. It just calls > builder->createView( > pqRenderView::renderViewType(), > activeServer); > inside a slot named onServerCreationFinished. Should I be asking the builder to create a layout proxy first? yes. See `pqDefaultViewBehavior::onServerCreation` for how that could be done. From gregory.zaccaro at gmail.com Wed Jun 28 18:52:31 2017 From: gregory.zaccaro at gmail.com (=?UTF-8?Q?Gr=C3=A9gory_Zaccaro?=) Date: Wed, 28 Jun 2017 18:52:31 -0400 Subject: [Paraview-developers] pvserver with multiple clients Message-ID: I'm trying to run a pvserver(Paraview 5.3) with multiple clients. I have a little problem when running the server. Here is how I launch locally all the processes on a .bat file : start mpiexec.exe -np 1 pvserver.exe --server-port=11111 start mpiexec.exe -np 1 pvserver.exe --server-port=11112 start pvbatch.exe script_box.py DESKTOP-HAFBULV 11111 start pvbatch.exe script_box.py DESKTOP-HAFBULV 11112 With "script_box.py" doing the connection and some stuff : from paraview.simple import * import sys server_name = sys.argv[1] server_port = int(sys.argv[2]) connection = servermanager.Connect(server_name, server_port) servermanager.LoadPlugin('...') # create a new 'Box' # create a new 'Triangulate' # create a new 'Clean' ... Whenever a client gets connected, the script is executed but the server exits immediately after that, the problem is that all the others clients lose connections and the server disconnect. I don't call servermanager.Disconnect() and I tried to run pvserver with --multi-clients but it has no effect, Is there is any specific way to manage multiple connections with a pvserver ? Any help would be appreciated ! -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Jun 29 09:15:42 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 29 Jun 2017 08:15:42 -0500 Subject: [Paraview-developers] Paraview Plugin Python wrapped In-Reply-To: References: Message-ID: > https://www.paraview.org/pipermail/paraview/2012-May/024855.html > > I tried following this example but it isn?t working. Wrap-python.cmake > doesn?t exist in the current version of ParaView. wrap-python.cmake does not come with ParaView - it's content is defined in Pat's email you cited: # wrap-python.cmake if(NOT DEFINED VTK_CMAKE_DIR) message(SEND_ERROR "VTK_CMAKE_DIR is not defined, cannot load vtkWrapPython.cmake") endif() if(NOT VTK_WRAP_PYTHON) message(FATAL_ERROR "VTK was built without Python enabled (VTK_WRAP_PYTHON=FALSE).") endif() include(${VTK_CMAKE_DIR}/vtkWrapPython.cmake) function(wrap_python library_name sources) vtk_wrap_python3(${library_name}Python generated_python_sources "${sources}") add_library(${library_name}PythonD ${generated_python_sources}) add_library(${library_name}Python MODULE ${library_name}PythonInit.cxx) target_link_libraries(${library_name}PythonD ${library_name}) foreach(c ${VTK_LIBRARIES}) target_link_libraries(${library_name}PythonD ${c}PythonD) endforeach(c) target_link_libraries(${library_name}Python ${library_name}PythonD) set_target_properties(${library_name}Python PROPERTIES PREFIX "") if(WIN32 AND NOT CYGWIN) set_target_properties(${library_name}Python PROPERTIES SUFFIX ".pyd") endif(WIN32 AND NOT CYGWIN) endfunction() I'm not sure if this will work, but I just wanted to clarify where wrap-python.cmake is defined. HTH, Cory > > > I found this macro ?WRAP_PLUGIN_FOR_PYTHON? > > https://github.com/Kitware/ParaView/blob/master/CMake/ParaViewPlugins.cmake > > Using this macro, I?m getting a error ?unknown cmake command > Python_add_module?. > > > > I am compiling my custom plugin inside ParaView?s plugin folder > > > > > > Am I supposed to used this in my plugin cmakelist file to enable the python > wrapping or is there another setting to activate ? > > > > Thank you > > Michal > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Thu Jun 29 09:28:32 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 29 Jun 2017 08:28:32 -0500 Subject: [Paraview-developers] 64bit windows 10 ParaView Compile with VS2015 update 3 (UNCLASSIFIED) In-Reply-To: References: Message-ID: Simon, Sounds like a bug. Would you mind reporting this as a bug on the GitLab bug tracker? https://gitlab.kitware.com/paraview/paraview/issues Thanks, Cory On Wed, Jun 14, 2017 at 9:21 AM, Su, Simon M CIV USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Hello, > > I am getting these errors with the plugin compilation..... Please see in the > email below... > > tracking that down, for this error > > Plugins/VR/pqVRStarterImplementation.h(43): error : Undefined interface > > In that file, line 43 is one of the following.... > > --------------------- > class pqVRStarterImplementation : public QObject, public > pqAutoStartInterface > { > Q_OBJECT > Q_INTERFACES(pqAutoStartInterface) > public: > pqVRStarterImplementation(QObject* p=0); > virtual ~pqVRStarterImplementation(); > ----------------------- > > I am only getting this when I am using QT5 instead of QT4 compiled with > VS2015 update 3. QT4 built successfully. > > Thoughts? Thank you. > > thanks > -simon > > > Build FAILED. > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata > lystScriptGeneratorPlugin.vcxproj.metaproj" > (default target) (580) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata > lystScriptGeneratorPlugin.vcxproj" (default > target) (591) -> > (CustomBuild target) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/CatalystScriptGenerator/pqCPA > ctionsGroupImplementation.h(46): error : > Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata > lystScriptGeneratorPlug > in.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La > grangianParticleTracker.vcxproj.metaproj" ( > default target) (602) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La > grangianParticleTracker.vcxproj" (default t > arget) (603) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/LagrangianParticleTracker/pqI > ntegrationModelSeedHelperWidgetPWIImpleme > ntation.h(43): error : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La > grangianParticleTracker.vcxproj] > > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho > gonalSource.vcxproj.metaproj" (default targ > et) (606) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho > gonalSource.vcxproj" (default target) (609) > -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/NonOrthogonalSource/pqNonOrth > ogonalAutoStartImplementation.h(43): erro > r : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho > gonalSource.vcxproj > ] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj. > metaproj" (default target) (616) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj" > (default target) (617) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/SLACTools/pqSLACActionGroupIm > plementation.h(46): error : Undefined int > erface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo > ols.vcxproj.metaproj" (default target) (618 > ) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo > ols.vcxproj" (default target) (619) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/SierraPlotTools/pqSierraPlotT > oolsActionGroupImplementation.h(46): erro > r : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo > ols.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St > reamLinesRepresentation.vcxproj.metaproj" ( > default target) (622) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St > reamLinesRepresentation.vcxproj" (default t > arget) (623) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/StreamLinesRepresentation/pqS > treamLinesAnimationManagerImplementation. > h(43): error : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St > reamLine > sRepresentation.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj.metaproj > " (default target) (634) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj" > (default target) (635) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/VR/pqVRStarterImplementation. > h(43): error : Undefined interface [c:\Us > ers\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj] > > 0 Warning(s) > 7 Error(s) > > > CLASSIFICATION: UNCLASSIFIED > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From utkarsh.ayachit at kitware.com Thu Jun 29 09:32:23 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 29 Jun 2017 09:32:23 -0400 Subject: [Paraview-developers] 64bit windows 10 ParaView Compile with VS2015 update 3 (UNCLASSIFIED) In-Reply-To: References: Message-ID: This is actually a Qt bug. See here: https://bugreports.qt.io/browse/QTBUG-59460 Here;s the fix:https://codereview.qt-project.org/#/c/184321/ You can manually patch the file in your QT installation to address this issue. Utkarsh On Wed, Jun 14, 2017 at 10:21 AM, Su, Simon M CIV USARMY RDECOM ARL (US) wrote: > CLASSIFICATION: UNCLASSIFIED > > Hello, > > I am getting these errors with the plugin compilation..... Please see in the > email below... > > tracking that down, for this error > > Plugins/VR/pqVRStarterImplementation.h(43): error : Undefined interface > > In that file, line 43 is one of the following.... > > --------------------- > class pqVRStarterImplementation : public QObject, public > pqAutoStartInterface > { > Q_OBJECT > Q_INTERFACES(pqAutoStartInterface) > public: > pqVRStarterImplementation(QObject* p=0); > virtual ~pqVRStarterImplementation(); > ----------------------- > > I am only getting this when I am using QT5 instead of QT4 compiled with > VS2015 update 3. QT4 built successfully. > > Thoughts? Thank you. > > thanks > -simon > > > Build FAILED. > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata > lystScriptGeneratorPlugin.vcxproj.metaproj" > (default target) (580) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata > lystScriptGeneratorPlugin.vcxproj" (default > target) (591) -> > (CustomBuild target) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/CatalystScriptGenerator/pqCPA > ctionsGroupImplementation.h(46): error : > Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\CatalystScriptGenerator\Cata > lystScriptGeneratorPlug > in.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La > grangianParticleTracker.vcxproj.metaproj" ( > default target) (602) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La > grangianParticleTracker.vcxproj" (default t > arget) (603) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/LagrangianParticleTracker/pqI > ntegrationModelSeedHelperWidgetPWIImpleme > ntation.h(43): error : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\LagrangianParticleTracker\La > grangianParticleTracker.vcxproj] > > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho > gonalSource.vcxproj.metaproj" (default targ > et) (606) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho > gonalSource.vcxproj" (default target) (609) > -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/NonOrthogonalSource/pqNonOrth > ogonalAutoStartImplementation.h(43): erro > r : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\NonOrthogonalSource\NonOrtho > gonalSource.vcxproj > ] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj. > metaproj" (default target) (616) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj" > (default target) (617) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/SLACTools/pqSLACActionGroupIm > plementation.h(46): error : Undefined int > erface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SLACTools\SLACTools.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo > ols.vcxproj.metaproj" (default target) (618 > ) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo > ols.vcxproj" (default target) (619) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/SierraPlotTools/pqSierraPlotT > oolsActionGroupImplementation.h(46): erro > r : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\SierraPlotTools\SierraPlotTo > ols.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St > reamLinesRepresentation.vcxproj.metaproj" ( > default target) (622) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St > reamLinesRepresentation.vcxproj" (default t > arget) (623) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/StreamLinesRepresentation/pqS > treamLinesAnimationManagerImplementation. > h(43): error : Undefined interface > [c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\StreamLinesRepresentation\St > reamLine > sRepresentation.vcxproj] > > "c:\Users\one\build\pvsb-5.4.0\build-pv\ParaView.sln" (default target) (1) > -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\ALL_BUILD.vcxproj.metaproj" (default > target) (2) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj.metaproj > " (default target) (634) -> > "c:\Users\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj" > (default target) (635) -> > > C:/Users/one/build/pvsb-5.4.0/build-pv/Plugins/VR/pqVRStarterImplementation. > h(43): error : Undefined interface [c:\Us > ers\one\build\pvsb-5.4.0\build-pv\Plugins\VR\VRPlugin.vcxproj] > > 0 Warning(s) > 7 Error(s) > > > CLASSIFICATION: UNCLASSIFIED > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From wascott at sandia.gov Thu Jun 29 12:43:53 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 29 Jun 2017 16:43:53 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: [Paraview] Use separate arrays for colormap and opacity In-Reply-To: References: Message-ID: <9f744eb4e6374381946b2bae45ac5434@ES01AMSNLNT.srn.sandia.gov> Moving to ParaView developers list. Is this something that we should implement in ParaView? Or, is it more of a one off request, with little value to the community? Alan > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cory > Quammen > Sent: Thursday, June 29, 2017 7:57 AM > To: Evan Kao > Cc: ParaView > Subject: [EXTERNAL] Re: [Paraview] Use separate arrays for colormap and > opacity > > > We would like to be able to visualize an object without tying the > > colormap to the same array as the opacity. Specifically, we would > > like to animate pathlines and color them by velocity, while setting > > their opacity according to particle age. Is this possible in Paraview? > > Unfortunately, this is not currently possible in ParaView. > > - Cory > > > Thanks, > > Evan Kao > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > 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 david.thompson at kitware.com Thu Jun 29 14:37:44 2017 From: david.thompson at kitware.com (David Thompson) Date: Thu, 29 Jun 2017 14:37:44 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app In-Reply-To: References: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> Message-ID: <29D6926B-6EEF-4FDB-AE3C-FA485FC6C35C@kitware.com> Hi Utkarsh, >> CMB does not explicitly create a layout proxy, and neither does it alter PV's XML ViewLayoutProxy. It just calls >> builder->createView( >> pqRenderView::renderViewType(), >> activeServer); >> inside a slot named onServerCreationFinished. Should I be asking the builder to create a layout proxy first? > > > yes. See `pqDefaultViewBehavior::onServerCreation` for how that could be done. Still no luck. CMB was using pqParaViewBehaviors without disabling pqDefaultViewBehavior plus it created another view in onServerCreationFinished, which I fixed so only one is used: I tried both + disabling CMB's view creation (leaving pqDefaultViewBehavior enabled) and + disabling pqDefaultViewBehavior and using CMB to create a layout + view after the server connection completes. Both of the above ensure there is a layout and then generate a view, but neither shows the titlebar/split-view buttons. In neither case does the "Layout 1" tab or any view titlebar appear. I verified that pqParaViewBehaviors::setEnableStandardViewFrameActions(true) was called just before creating the pqParaViewBehaviors instance. I also added a menu action to call the pqTabbedMultiViewWidget's toggleWidgetDecoration but it has no effect. Also I can see pqViewFrame instances being created but then destroyed in pqMultiViewWidget::reload() at line 627. Any ideas on how to debug further? David From utkarsh.ayachit at kitware.com Thu Jun 29 15:12:44 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 29 Jun 2017 15:12:44 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app In-Reply-To: <29D6926B-6EEF-4FDB-AE3C-FA485FC6C35C@kitware.com> References: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> <29D6926B-6EEF-4FDB-AE3C-FA485FC6C35C@kitware.com> Message-ID: Put a break point in `pqMultiViewWidget::newFrame` and step through the code. Do it in ParaView and CMB and maybe things will get clearer. Utkarsh On Thu, Jun 29, 2017 at 2:37 PM, David Thompson wrote: > Hi Utkarsh, > >>> CMB does not explicitly create a layout proxy, and neither does it alter PV's XML ViewLayoutProxy. It just calls >>> builder->createView( >>> pqRenderView::renderViewType(), >>> activeServer); >>> inside a slot named onServerCreationFinished. Should I be asking the builder to create a layout proxy first? >> >> >> yes. See `pqDefaultViewBehavior::onServerCreation` for how that could be done. > > Still no luck. > > CMB was using pqParaViewBehaviors without disabling pqDefaultViewBehavior plus it created another view in onServerCreationFinished, which I fixed so only one is used: I tried both > + disabling CMB's view creation (leaving pqDefaultViewBehavior enabled) and > + disabling pqDefaultViewBehavior and using CMB to create a layout + view after the server connection completes. > > Both of the above ensure there is a layout and then generate a view, but neither shows the titlebar/split-view buttons. > > In neither case does the "Layout 1" tab or any view titlebar appear. > > I verified that pqParaViewBehaviors::setEnableStandardViewFrameActions(true) was called just before creating the pqParaViewBehaviors instance. > > I also added a menu action to call the pqTabbedMultiViewWidget's toggleWidgetDecoration but it has no effect. > > Also I can see pqViewFrame instances being created but then destroyed in pqMultiViewWidget::reload() at line 627. > > Any ideas on how to debug further? > > David From david.thompson at kitware.com Thu Jun 29 15:17:45 2017 From: david.thompson at kitware.com (David Thompson) Date: Thu, 29 Jun 2017 15:17:45 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app In-Reply-To: References: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> <29D6926B-6EEF-4FDB-AE3C-FA485FC6C35C@kitware.com> Message-ID: <921B18AC-8F78-4FCB-AB90-B5A50E31A469@kitware.com> Hi Haocheng, > Earlier this month I have helped John rebasing his branch several times, and I have a successful build sitting on kerbin(Since it can be built on windows, I strongly assume that it should be able to build across all platforms.) > > I checked it just now and I do see the titlebar/split-view buttons in this CMB build. It might be helpful to you... Thanks, that did it! The difference was that setCentralWidget() in CMB/master was being called with the first render view created instead of the pqTabbedMultiViewWidget. On the plus side, I found of lot of cruft and unused code we can remove. :-) David From haocheng.liu at kitware.com Thu Jun 29 15:20:17 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Thu, 29 Jun 2017 15:20:17 -0400 Subject: [Paraview-developers] Enabling view splitting in a custom PV app In-Reply-To: <921B18AC-8F78-4FCB-AB90-B5A50E31A469@kitware.com> References: <4FCEB4E8-5536-400B-A588-6A62CDE084E1@kitware.com> <29D6926B-6EEF-4FDB-AE3C-FA485FC6C35C@kitware.com> <921B18AC-8F78-4FCB-AB90-B5A50E31A469@kitware.com> Message-ID: On Thu, Jun 29, 2017 at 3:17 PM, David Thompson wrote: > Hi Haocheng, > > > Earlier this month I have helped John rebasing his branch several times, > and I have a successful build sitting on kerbin(Since it can be built on > windows, I strongly assume that it should be able to build across all > platforms.) > > > > I checked it just now and I do see the titlebar/split-view buttons in > this CMB build. It might be helpful to you... > > Thanks, that did it! The difference was that setCentralWidget() in > CMB/master was being called with the first render view created instead of > the pqTabbedMultiViewWidget. > > On the plus side, I found of lot of cruft and unused code we can remove. > :-) > Bravo! > > David -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4421 <(518)%20881-4421> -------------- next part -------------- An HTML attachment was scrubbed... URL: