From lukas.kresta at gmail.com Tue Aug 1 06:23:29 2017 From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=) Date: Tue, 1 Aug 2017 12:23:29 +0200 Subject: [Paraview] Paraview Catalyst offscreen rendering In-Reply-To: References: Message-ID: Thank you. We are trying build it with that options. I will send you CMakeCache(finally i found it) to be sure that everything will be ok in ParaView. One more time, thank you. 2017-07-27 20:13 GMT+02:00 Andy Bauer : > I think what you're missing is -DVTK_USE_X=OFF and probably > -DVTK_USE_OFFSCREEN=ON. If that doesn't work, please send your > CMakeCache.txt from your build directory. > > On Thu, Jul 27, 2017 at 5:48 AM, Luk?? Kresta > wrote: > >> it was build with easybuild with these parametrs: >> >> cmake /apps/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay/ParaView-v5.4.0/ >> >> -DCMAKE_INSTALL_PREFIX=/apps/all/ParaView/5.4.0-intel-2017a-mpi-OSPRay >> >> -DCMAKE_C_COMPILER='mpiicc' -DCMAKE_Fortran_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' >> >> -DCMAKE_CXX_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' -DCMAKE_CXX_COMPILER='mpiicpc' >> >> DCMAKE_Fortran_COMPILER='mpiifort' -DCMAKE_C_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' >> >> -DCMAKE_VERBOSE_MAKEFILE=ON -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DVTK_OPENGL_HAS_OSMESA=ON >> >> -DPARAVIEW_USE_MPI=ON -DOPENGL_INCLUDE_DIR=$EBROOTMESA/include -DOPENGL_gl_LIBRARY=$EBROOTMESA/lib/libGL.so >> >> -DOSMESA_INCLUDE_DIR=$EBROOTMESA/include -DOSMESA_LIBRARY=$EBROOTMESA/lib/libOSMesa.so >> >> -DOPENGL_glu_LIBRARY=$EBROOTLIBGLU/lib/libGLU.so -DVTK_USE_SYSTEM_HDF5=ON -DPARAVIEW_ENABLE_PYTHON=ON -DBUILD_SHARED_LIBS=ON >> >> -DVTK_RENDERING_BACKEND=OpenGL2 -DPARAVIEW_USE_OSPRAY=ON -DOSPRAY_INSTALL_DIR=$EBROOT >> OSPRAY -DPARAVIEW_QT_VERSION=5 -DBUILD_TESTING=OFF >> >> >> I hope, it will help solve my problem. If you need, i can send you complete log. >> >> >> 2017-07-26 17:37 GMT+02:00 Andy Bauer : >> >>> Hi, >>> >>> It sounds like you didn't properly build with OSMesa. If you share your >>> CMakeCache.txt from your ParaView build I can see if I can track down the >>> problem. >>> >>> Best, >>> Andy >>> >>> On Wed, Jul 26, 2017 at 11:20 AM, Luk?? Kresta >>> wrote: >>> >>>> Thank you, but I have ParaView build with OSMesa without X. If I run >>>> program with Catalyst(genereted script from ParaView, with render views) on >>>> cluster with mpi, ussually one render view will show, but on anothers >>>> process it crash with this error: ERROR: In .../ParaView-v5.4.0/VTK/Render >>>> ing/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819 >>>> vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I >>>> have the same error with pvserver with or without --use-offscreen-rendering >>>> or without pvserver. >>>> >>>> If i run Catalyst with script only for live visualization then the >>>> program go without problem but i dont get pictures which i want. Is there >>>> some posibility how fix the error or how to get pictures(with offscreen >>>> rendering)? >>>> >>>> 2017-07-14 16:24 GMT+02:00 Andy Bauer : >>>> >>>>> Hi, >>>>> >>>>> If you're not memory constrained I suggest just doing a full ParaView >>>>> build with OSMesa and X11 disabled. There are quite a few discussions on >>>>> the PV mailing list on how to do that. >>>>> >>>>> If you're memory constrained then I would suggest building with all of >>>>> the Catalyst editions enabled and see if that works for you. >>>>> >>>>> Best, >>>>> Andy >>>>> >>>>> On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I would like to ask, which Paraview Catalyst (python) script use(with >>>>>> render view or live visualization). If i want save images with offscreen >>>>>> rendering on HPC. On cluster is no gpu. And how to properly use it? >>>>>> >>>>>> Thank you for your help. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj # It was generated by CMake: /apps/all/CMake/3.8.1/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //Dependencies for the target AcceleratedAlgorithms_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Dependencies for the target AnalyzeNIfTIIO_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkzlib; //Dependencies for the target ArrowGlyph_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Build the VTK documentation BUILD_DOCUMENTATION:BOOL=OFF BUILD_EXAMPLES:BOOL=OFF //Build IceT with shared libraries. BUILD_SHARED_LIBS:BOOL=ON //Build the testing tree. BUILD_TESTING:BOOL=OFF //Dependencies for the target CDIReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtknetcdfcpp; //Path to a program. CMAKE_AR:FILEPATH=/apps/all/binutils/2.27-GCCcore-6.3.0/bin/ar //For backwards compatibility, what version of CMake commands and // syntax should this version of CMake try to support. CMAKE_BACKWARDS_COMPATIBILITY:STRING=2.4 //Choose the type of build. CMAKE_BUILD_TYPE:STRING=Debug //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler CMAKE_CXX_COMPILER:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpiicpc //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING=-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler CMAKE_C_COMPILER:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpiicc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING=-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING=-L/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64 -L/apps/all/imkl/2017.1.132-iimpi-2017a/lib -L/apps/all/imkl/2017.1.132-iimpi-2017a/mkl/lib/intel64 -L/apps/all/imkl/2017.1.132-iimpi-2017a/lib -L/apps/all/X11/20170314/lib -L/apps/all/Mesa/17.0.2-intel-2017a/lib -L/apps/all/libGLU/9.0.0/lib -L/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib -L/apps/all/zlib/1.2.11/lib -L/apps/all/HDF5/1.8.17-intel-2017a/lib -L/apps/all/Python/2.7.13/lib -L/apps/all/OSPRay/1.3.0-intel-2017a/lib64 //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Fortran compiler CMAKE_Fortran_COMPILER:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpiifort //Flags for Fortran compiler. CMAKE_Fortran_FLAGS:STRING=-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC //Flags used by the compiler during debug builds. CMAKE_Fortran_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_Fortran_FLAGS_MINSIZEREL:STRING=-Os //Flags used by the compiler during release builds. CMAKE_Fortran_FLAGS_RELEASE:STRING=-O3 //Flags used by the compiler during release builds with debug info. CMAKE_Fortran_FLAGS_RELWITHDEBINFO:STRING=-O2 -g //User executables (bin) CMAKE_INSTALL_BINDIR:PATH=bin //Read-only architecture-independent data (DATAROOTDIR) CMAKE_INSTALL_DATADIR:PATH= //Read-only architecture-independent data root (share) CMAKE_INSTALL_DATAROOTDIR:PATH=share //Documentation root (DATAROOTDIR/doc/PROJECT_NAME) CMAKE_INSTALL_DOCDIR:PATH= //C header files (include) CMAKE_INSTALL_INCLUDEDIR:PATH=include //Info documentation (DATAROOTDIR/info) CMAKE_INSTALL_INFODIR:PATH= //Object code libraries (lib64) CMAKE_INSTALL_LIBDIR:PATH=lib64 //Program executables (libexec) CMAKE_INSTALL_LIBEXECDIR:PATH=libexec //Locale-dependent data (DATAROOTDIR/locale) CMAKE_INSTALL_LOCALEDIR:PATH= //Modifiable single-machine data (var) CMAKE_INSTALL_LOCALSTATEDIR:PATH=var //Man documentation (DATAROOTDIR/man) CMAKE_INSTALL_MANDIR:PATH= //C header files for non-gcc (/usr/include) CMAKE_INSTALL_OLDINCLUDEDIR:PATH=/usr/include //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/home/kre0214/.local/easybuild/software/ParaView/5.4.0-intel-2017a-mpi-OSPRay-TEST //System admin executables (sbin) CMAKE_INSTALL_SBINDIR:PATH=sbin //Modifiable architecture-independent data (com) CMAKE_INSTALL_SHAREDSTATEDIR:PATH=com //Read-only single-machine data (etc) CMAKE_INSTALL_SYSCONFDIR:PATH=etc //Path to a program. CMAKE_LINKER:FILEPATH=/apps/all/binutils/2.27-GCCcore-6.3.0/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING=-L/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64 -L/apps/all/imkl/2017.1.132-iimpi-2017a/lib -L/apps/all/imkl/2017.1.132-iimpi-2017a/mkl/lib/intel64 -L/apps/all/imkl/2017.1.132-iimpi-2017a/lib -L/apps/all/X11/20170314/lib -L/apps/all/Mesa/17.0.2-intel-2017a/lib -L/apps/all/libGLU/9.0.0/lib -L/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib -L/apps/all/zlib/1.2.11/lib -L/apps/all/HDF5/1.8.17-intel-2017a/lib -L/apps/all/Python/2.7.13/lib -L/apps/all/OSPRay/1.3.0-intel-2017a/lib64 //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/apps/all/binutils/2.27-GCCcore-6.3.0/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=/apps/all/binutils/2.27-GCCcore-6.3.0/bin/objcopy //Path to a program. CMAKE_OBJDUMP:FILEPATH=/apps/all/binutils/2.27-GCCcore-6.3.0/bin/objdump //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=ParaView //Path to a program. CMAKE_RANLIB:FILEPATH=/apps/all/binutils/2.27-GCCcore-6.3.0/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING=-L/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64 -L/apps/all/imkl/2017.1.132-iimpi-2017a/lib -L/apps/all/imkl/2017.1.132-iimpi-2017a/mkl/lib/intel64 -L/apps/all/imkl/2017.1.132-iimpi-2017a/lib -L/apps/all/X11/20170314/lib -L/apps/all/Mesa/17.0.2-intel-2017a/lib -L/apps/all/libGLU/9.0.0/lib -L/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib -L/apps/all/zlib/1.2.11/lib -L/apps/all/HDF5/1.8.17-intel-2017a/lib -L/apps/all/Python/2.7.13/lib -L/apps/all/OSPRay/1.3.0-intel-2017a/lib64 //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/apps/all/binutils/2.27-GCCcore-6.3.0/bin/strip //Thread library used. CMAKE_THREAD_LIBS:STRING= //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=ON //Enable to build Debian packages CPACK_BINARY_DEB:BOOL=OFF //Enable to build IFW packages CPACK_BINARY_IFW:BOOL=OFF //Enable to build NSIS packages CPACK_BINARY_NSIS:BOOL=OFF //Enable to build RPM packages CPACK_BINARY_RPM:BOOL=OFF //Enable to build STGZ packages CPACK_BINARY_STGZ:BOOL=ON //Enable to build TBZ2 packages CPACK_BINARY_TBZ2:BOOL=OFF //Enable to build TGZ packages CPACK_BINARY_TGZ:BOOL=ON //Enable to build TXZ packages CPACK_BINARY_TXZ:BOOL=OFF //Enable to build TZ packages CPACK_BINARY_TZ:BOOL=ON //Enable to build RPM source packages CPACK_SOURCE_RPM:BOOL=OFF //Enable to build TBZ2 source packages CPACK_SOURCE_TBZ2:BOOL=ON //Enable to build TGZ source packages CPACK_SOURCE_TGZ:BOOL=ON //Enable to build TXZ source packages CPACK_SOURCE_TXZ:BOOL=ON //Enable to build TZ source packages CPACK_SOURCE_TZ:BOOL=ON //Enable to build ZIP source packages CPACK_SOURCE_ZIP:BOOL=OFF //Value Computed by CMake CatalystScriptGeneratorPlugin_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/Plugins/CatalystScriptGenerator //Dependencies for the target CatalystScriptGeneratorPlugin_LIB_DEPENDS:STATIC=general;pqComponents;general;Qt5::Widgets;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;vtkPVServerManagerRendering; //Value Computed by CMake CatalystScriptGeneratorPlugin_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/Plugins/CatalystScriptGenerator //Value Computed by CMake DICOMParser_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/Utilities/DICOMParser //Value Computed by CMake DICOMParser_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Utilities/DICOMParser //Path to a library. EXECINFO_LIB:FILEPATH=EXECINFO_LIB-NOTFOUND //Disable compiler warnings EXODUSII_DISABLE_COMPILER_WARNINGS:BOOL=ON //Additional URL templates for the ExternalData CMake script to // look for testing data. E.g. //\nfile:///var/bigharddrive/%(algo)/%(hash) ExternalData_URL_TEMPLATES:STRING= //Dependencies for the target EyeDomeLightingView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Value Computed by CMake EyeDomeLighting_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/Plugins/EyeDomeLighting //Value Computed by CMake EyeDomeLighting_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/Plugins/EyeDomeLighting //Value Computed by CMake FmmMesh_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/Plugins/GeodesicMeasurementPlugin/FmmMesh //Dependencies for target FmmMesh_LIB_DEPENDS:STATIC= //Value Computed by CMake FmmMesh_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/Plugins/GeodesicMeasurementPlugin/FmmMesh //Git command line client GIT_EXECUTABLE:FILEPATH=/usr/bin/git //Dependencies for the target GMVReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtksys;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Calculate minimum and maximum of data arrays in RequestInformation // calls. //\n A feature inherited from AVSucdReader, but it seems this // information is //\n never queried by ParaView. GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS:BOOL=OFF //Value Computed by CMake GeodesicMeasurementPlugin_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/Plugins/GeodesicMeasurementPlugin //Value Computed by CMake GeodesicMeasurementPlugin_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/Plugins/GeodesicMeasurementPlugin //Dependencies for the target GeodesicMeasurement_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;FmmMesh; //IEEE floating point is available HAVE_IEEEFP:STRING=1 //HDF5 C Wrapper compiler. Used only to detect HDF5 compile flags. HDF5_C_COMPILER_EXECUTABLE:FILEPATH=/apps/all/HDF5/1.8.17-intel-2017a/bin/h5pcc //Path to a library. HDF5_C_LIBRARY_dl:FILEPATH=/usr/lib64/libdl.so //Path to a library. HDF5_C_LIBRARY_hdf5:FILEPATH=/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so //Path to a library. HDF5_C_LIBRARY_hdf5_hl:FILEPATH=/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so //Path to a library. HDF5_C_LIBRARY_iomp5:FILEPATH=/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so //Path to a library. HDF5_C_LIBRARY_m:FILEPATH=/usr/lib64/libm.so //Path to a library. HDF5_C_LIBRARY_pthread:FILEPATH=/usr/lib64/libpthread.so //Path to a library. HDF5_C_LIBRARY_sz:FILEPATH=/apps/all/Szip/2.1-intel-2017a/lib/libsz.so //Path to a library. HDF5_C_LIBRARY_z:FILEPATH=/apps/all/zlib/1.2.11/lib/libz.so //HDF5 file differencing tool. HDF5_DIFF_EXECUTABLE:FILEPATH=/apps/all/HDF5/1.8.17-intel-2017a/bin/h5diff //Native CPU bit order HOST_BIG_ENDIAN:STRING=OFF //Native CPU bit order HOST_FILLORDER:STRING=FILLORDER_LSB2MSB //Value Computed by CMake ICET_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/ThirdParty/IceT/vtkicet //Sets the preferred `k' value for the radix-k algorithm. This // is the amount of simultaneous messages each process receives. // A value of 8 is generally good on most architectures, but in // others that have slower computation with respect to network // (such as BlueGene), a larger value may give better performance. ICET_MAGIC_K:STRING=8 //Sets the preferred number of times an image may be split. Some // image compositing algorithms prefer to partition the images // such that each process gets a piece. Too many partitions, though, // and you end up spending more time collecting them than you save // balancing the compositing. ICET_MAX_IMAGE_SPLIT:STRING=512 //Value Computed by CMake ICET_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ThirdParty/IceT/vtkicet //Use MPE to trace MPI communications. This is helpful for developers // trying to measure the performance of parallel compositing algorithms. ICET_USE_MPE:BOOL=OFF //Build MPI communication layer for IceT. ICET_USE_MPI:BOOL=ON //Build OpenGL support layer for IceT. ICET_USE_OPENGL:BOOL=ON //Installation directory for executables INSTALL_BIN_DIR:PATH=/home/kre0214/.local/easybuild/software/ParaView/5.4.0-intel-2017a-mpi-OSPRay-TEST/bin //Installation directory for headers INSTALL_INC_DIR:PATH=/home/kre0214/.local/easybuild/software/ParaView/5.4.0-intel-2017a-mpi-OSPRay-TEST/include //Installation directory for libraries INSTALL_LIB_DIR:PATH=/home/kre0214/.local/easybuild/software/ParaView/5.4.0-intel-2017a-mpi-OSPRay-TEST/lib //Installation directory for manual pages INSTALL_MAN_DIR:PATH=/home/kre0214/.local/easybuild/software/ParaView/5.4.0-intel-2017a-mpi-OSPRay-TEST/share/man //Installation directory for pkgconfig (.pc) files INSTALL_PKGCONFIG_DIR:PATH=/home/kre0214/.local/easybuild/software/ParaView/5.4.0-intel-2017a-mpi-OSPRay-TEST/share/pkgconfig //Dependencies for the target IceTCore_LIB_DEPENDS:STATIC=general;m;general;m; //Dependencies for the target IceTGL_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target IceTMPI_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Value Computed by CMake JsonCpp_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake JsonCpp_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/jsoncpp/vtkjsoncpp //Value Computed by CMake LZ4_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/lz4/vtklz4 //Value Computed by CMake LZ4_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/lz4/vtklz4 //Dependencies for the target LagrangianParticleTracker_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkFiltersFlowPaths; //Executable for running MPI programs. MPIEXEC:FILEPATH=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpiexec //Maximum number of processors available to run MPI applications. MPIEXEC_MAX_NUMPROCS:STRING=2 //Flag used by MPI to specify the number of processes for MPIEXEC; // the next option will be the number of processes. MPIEXEC_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIEXEC. MPIEXEC_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by MPIEXEC. MPIEXEC_PREFLAGS:STRING= //Path to a program. MPI_CXX_COMPILER:FILEPATH=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpicxx //MPI CXX compilation flags MPI_CXX_COMPILE_FLAGS:STRING= //MPI CXX include path MPI_CXX_INCLUDE_PATH:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include //MPI CXX libraries to link against MPI_CXX_LIBRARIES:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;/usr/lib64/libdl.so;/usr/lib64/librt.so;/usr/lib64/libpthread.so //MPI CXX linking flags MPI_CXX_LINK_FLAGS:STRING= //Path to a program. MPI_C_COMPILER:FILEPATH=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpicc //MPI C compilation flags MPI_C_COMPILE_FLAGS:STRING= //MPI C include path MPI_C_INCLUDE_PATH:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include //MPI C libraries to link against MPI_C_LIBRARIES:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;/usr/lib64/libdl.so;/usr/lib64/librt.so;/usr/lib64/libpthread.so //MPI C linking flags MPI_C_LINK_FLAGS:STRING= //Extra MPI libraries to link against MPI_EXTRA_LIBRARY:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;/usr/lib64/libdl.so;/usr/lib64/librt.so;/usr/lib64/libpthread.so //Path to a program. MPI_Fortran_COMPILER:FILEPATH=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpif90 //MPI Fortran compilation flags MPI_Fortran_COMPILE_FLAGS:STRING= //MPI Fortran include path MPI_Fortran_INCLUDE_PATH:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include/gfortran/5.1.0;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include //MPI Fortran libraries to link against MPI_Fortran_LIBRARIES:STRING=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;/usr/lib64/libdl.so;/usr/lib64/librt.so;/usr/lib64/libpthread.so //MPI Fortran linking flags MPI_Fortran_LINK_FLAGS:STRING= //MPI library to link against MPI_LIBRARY:FILEPATH=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so //Path to a library. M_LIBRARY:FILEPATH=/usr/lib64/libm.so //Poisson Surface reconstruction from unorganized points Module_PoissonReconstruction:BOOL=OFF //Second rank tensor glyphs that visualize eigenvalue signs. Module_SignedTensor:BOOL=OFF //Spline Driven Image Slicer - http://www.vtkjournal.org/browse/publication/838 Module_SplineDrivenImageSlicer:BOOL=OFF //Request building VisItLib Module_VisItLib:BOOL=OFF //A collection of examples that illustrate how to use VTK. Module_WikiExamples:BOOL=OFF //Request building pqDeprecated Module_pqDeprecated:BOOL=OFF //Request building vtkAcceleratorsVTKm Module_vtkAcceleratorsVTKm:BOOL=OFF //Slicer additions to vtk Module_vtkAddon:BOOL=OFF //Request building vtkCosmoHaloFinder Module_vtkCosmoHaloFinder:BOOL=OFF //Dicom classes and utilities Module_vtkDICOM:BOOL=OFF //Request building vtkDomainsMicroscopy Module_vtkDomainsMicroscopy:BOOL=OFF //Request building vtkFiltersMatlab Module_vtkFiltersMatlab:BOOL=OFF //Request building vtkFiltersReebGraph Module_vtkFiltersReebGraph:BOOL=OFF //Request building vtkFiltersSMP Module_vtkFiltersSMP:BOOL=OFF //Request building vtkFiltersSelection Module_vtkFiltersSelection:BOOL=OFF //Request building vtkFiltersStatisticsGnuR Module_vtkFiltersStatisticsGnuR:BOOL=OFF //Request building vtkFiltersTopology Module_vtkFiltersTopology:BOOL=OFF //Request building vtkGUISupportQtOpenGL Module_vtkGUISupportQtOpenGL:BOOL=OFF //Request building vtkGUISupportQtSQL Module_vtkGUISupportQtSQL:BOOL=OFF //Request building vtkGUISupportQtWebkit Module_vtkGUISupportQtWebkit:BOOL=OFF //Request building vtkGeovisCore Module_vtkGeovisCore:BOOL=OFF //Request building vtkIOADIOS Module_vtkIOADIOS:BOOL=OFF //Request building vtkIOFFMPEG Module_vtkIOFFMPEG:BOOL=OFF //Request building vtkIOGDAL Module_vtkIOGDAL:BOOL=OFF //Request building vtkIOGeoJSON Module_vtkIOGeoJSON:BOOL=OFF //Request building vtkIOMINC Module_vtkIOMINC:BOOL=OFF //Request building vtkIOMySQL Module_vtkIOMySQL:BOOL=OFF //Request building vtkIOODBC Module_vtkIOODBC:BOOL=OFF //Request building vtkIOPostgreSQL Module_vtkIOPostgreSQL:BOOL=OFF //Request building vtkIOSQL Module_vtkIOSQL:BOOL=OFF //Request building vtkIOVideo Module_vtkIOVideo:BOOL=OFF //Request building vtkIOVisItBridge Module_vtkIOVisItBridge:BOOL=OFF //Request building vtkIOXdmf3 Module_vtkIOXdmf3:BOOL=OFF //Request building vtkImagingOpenGL2 Module_vtkImagingOpenGL2:BOOL=OFF //Request building vtkImagingStatistics Module_vtkImagingStatistics:BOOL=OFF //Request building vtkImagingStencil Module_vtkImagingStencil:BOOL=OFF //Request building vtkInfovisBoost Module_vtkInfovisBoost:BOOL=OFF //Request building vtkInfovisBoostGraphAlgorithms Module_vtkInfovisBoostGraphAlgorithms:BOOL=OFF //Request building vtkInfovisLayout Module_vtkInfovisLayout:BOOL=OFF //Request building vtkInfovisParallel Module_vtkInfovisParallel:BOOL=OFF //Request building vtkPVCatalystTestDriver Module_vtkPVCatalystTestDriver:BOOL=OFF //Request building vtkPVVTKExtensionsCosmoTools Module_vtkPVVTKExtensionsCosmoTools:BOOL=OFF //Request building vtkParseOGLExt Module_vtkParseOGLExt:BOOL=OFF //Request building vtkRenderingExternal Module_vtkRenderingExternal:BOOL=OFF //Request building vtkRenderingFreeTypeFontConfig Module_vtkRenderingFreeTypeFontConfig:BOOL=OFF //Request building vtkRenderingImage Module_vtkRenderingImage:BOOL=OFF //Request building vtkRenderingOculus Module_vtkRenderingOculus:BOOL=OFF //Request building vtkRenderingOpenVR Module_vtkRenderingOpenVR:BOOL=OFF //Request building vtkRenderingQt Module_vtkRenderingQt:BOOL=OFF //Request building vtkRenderingTk Module_vtkRenderingTk:BOOL=OFF //Request building vtkTclTk Module_vtkTclTk:BOOL=OFF //Request building vtkTestingGenericBridge Module_vtkTestingGenericBridge:BOOL=OFF //Request building vtkTestingIOSQL Module_vtkTestingIOSQL:BOOL=OFF //Request building vtkUtilitiesBenchmarks Module_vtkUtilitiesBenchmarks:BOOL=OFF //Request building vtkUtilitiesColorSeriesToXML Module_vtkUtilitiesColorSeriesToXML:BOOL=OFF //Request building vtkViewsGeovis Module_vtkViewsGeovis:BOOL=OFF //Request building vtkViewsInfovis Module_vtkViewsInfovis:BOOL=OFF //Request building vtkViewsQt Module_vtkViewsQt:BOOL=OFF //Request building vtkWrappingJava Module_vtkWrappingJava:BOOL=OFF //Request building vtkWrappingPythonCore Module_vtkWrappingPythonCore:BOOL=ON //Request building vtkWrappingTcl Module_vtkWrappingTcl:BOOL=OFF //Request building vtklibproj4 Module_vtklibproj4:BOOL=OFF //Request building vtksqlite Module_vtksqlite:BOOL=OFF //Request building vtkxdmf3 Module_vtkxdmf3:BOOL=OFF //Request building vtkzfp Module_vtkzfp:BOOL=OFF //Dependencies for the target Moments_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Specify default maximum number of elements in the file chunk // cache chunk for HDF5 files (should be prime number). NETCDF4_CHUNK_CACHE_NELEMS:STRING=1009 //Specify default file chunk cache preemption policy for HDF5 files // (a number between 0 and 1, inclusive). NETCDF4_CHUNK_CACHE_PREEMPTION:STRING=0.75 //Specify default file cache chunk size for HDF5 files in bytes. NETCDF4_CHUNK_CACHE_SIZE:STRING=4194304 //Specify the number of chunks to store in default per-variable // cache. NETCDF4_DEFAULT_CHUNKS_IN_CACHE:STRING=10 //Specify default size of chunks in bytes. NETCDF4_DEFAULT_CHUNK_SIZE:STRING=4194304 //Specify maximum size (in bytes) for the default per-var chunk // cache. NETCDF4_MAX_DEFAULT_CACHE_SIZE:STRING=67108864 //Disable compiler warnings NETCDF_DISABLE_COMPILER_WARNINGS:BOOL=ON //Dependencies for the target NonOrthogonalSource_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;pqApplicationComponents; //No help, variable specified on the command line. OPENGL_INCLUDE_DIR:UNINITIALIZED=/apps/all/Mesa/17.0.2-intel-2017a/include //No help, variable specified on the command line. OPENGL_gl_LIBRARY:UNINITIALIZED=/apps/all/Mesa/17.0.2-intel-2017a/lib/libGL.so //No help, variable specified on the command line. OPENGL_glu_LIBRARY:UNINITIALIZED=/apps/all/libGLU/9.0.0/lib/libGLU.so //No help, variable specified on the command line. OSMESA_INCLUDE_DIR:UNINITIALIZED=/apps/all/Mesa/17.0.2-intel-2017a/include //No help, variable specified on the command line. OSMESA_LIBRARY:UNINITIALIZED=/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so //build location of ospray OSPRAY_BUILD_DIR:PATH= //install location of ospray OSPRAY_INSTALL_DIR:PATH=/apps/all/OSPRay/1.3.0-intel-2017a //Load AcceleratedAlgorithms Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms:BOOL=OFF //Load AnalyzeNIfTIIO Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO:BOOL=OFF //Load ArrowGlyph Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph:BOOL=OFF //Load CDIReader Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_CDIReader:BOOL=OFF //Load CatalystScriptGeneratorPlugin Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin:BOOL=OFF //Load EyeDomeLighting Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting:BOOL=OFF //Load GMVReader Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_GMVReader:BOOL=OFF //Load GeodesicMeasurement Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement:BOOL=OFF //Load LagrangianParticleTracker Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_LagrangianParticleTracker:BOOL=OFF //Load Moments Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_Moments:BOOL=OFF //Load NonOrthogonalSource Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource:BOOL=OFF //Load PacMan Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_PacMan:BOOL=OFF //Load SLACTools Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SLACTools:BOOL=OFF //Load SierraPlotTools Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools:BOOL=OFF //Load StreamLinesRepresentation Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_StreamLinesRepresentation:BOOL=OFF //Load StreamingParticles Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles:BOOL=OFF //Load SurfaceLIC Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC:BOOL=OFF //Load ThickenLayeredCells Plugin Automatically PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells:BOOL=OFF //Build Adaptors for various simulation codes PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=OFF //Build AcceleratedAlgorithms Plugin PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms:BOOL=TRUE //Build AdiosReader Plugin PARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=FALSE //Build AdiosStagingReader Plugin PARAVIEW_BUILD_PLUGIN_AdiosStagingReader:BOOL=FALSE //Build AnalyzeNIfTIIO Plugin PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=TRUE //Build ArrowGlyph Plugin PARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=TRUE //Build CDIReader Plugin PARAVIEW_BUILD_PLUGIN_CDIReader:BOOL=TRUE //Build CatalystScriptGeneratorPlugin Plugin PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin:BOOL=TRUE //Build EyeDomeLighting Plugin PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=TRUE //Build GMVReader Plugin PARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=TRUE //Build GeodesicMeasurement Plugin PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement:BOOL=TRUE //Build InSituExodus Plugin PARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=FALSE //Build LagrangianParticleTracker Plugin PARAVIEW_BUILD_PLUGIN_LagrangianParticleTracker:BOOL=TRUE //Build Moments Plugin PARAVIEW_BUILD_PLUGIN_Moments:BOOL=TRUE //Build NonOrthogonalSource Plugin PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=TRUE //Build PacMan Plugin PARAVIEW_BUILD_PLUGIN_PacMan:BOOL=TRUE //Build PythonQtPlugin Plugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin:BOOL=FALSE //Build SLACTools Plugin PARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=TRUE //Build SierraPlotTools Plugin PARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=TRUE //Build StreamLinesRepresentation Plugin PARAVIEW_BUILD_PLUGIN_StreamLinesRepresentation:BOOL=TRUE //Build StreamingParticles Plugin PARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=TRUE //Build SurfaceLIC Plugin PARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=TRUE //Build TemporalParallelismScriptGenerator Plugin PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator:BOOL=FALSE //Build ThickenLayeredCells Plugin PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells:BOOL=TRUE //Build VRPlugin Plugin PARAVIEW_BUILD_PLUGIN_VRPlugin:BOOL=FALSE //Build VaporPlugin Plugin PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=FALSE //Enable ParaView Qt-based client PARAVIEW_BUILD_QT_GUI:BOOL=ON //Exclude test data download from default 'all' target. PARAVIEW_DATA_EXCLUDE_FROM_ALL:BOOL=OFF //Local directory holding ExternalData objects in the layout %(algo)/%(hash). PARAVIEW_DATA_STORE:PATH= //Enable Catalyst CoProcessing modules PARAVIEW_ENABLE_CATALYST:BOOL=ON //Build ParaView with CosmoTools VTK Extensions PARAVIEW_ENABLE_COSMOTOOLS:BOOL=OFF //Build the ParaView help menu documentation for ParaView and its // plugins PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION:BOOL=ON //Enable FFMPEG Support. PARAVIEW_ENABLE_FFMPEG:BOOL=OFF //Enable/Disable Python scripting support PARAVIEW_ENABLE_MATPLOTLIB:BOOL=ON //Enable/Disable Python scripting support PARAVIEW_ENABLE_PYTHON:BOOL=ON //Enables markers in the spyplot reader PARAVIEW_ENABLE_SPYPLOT_MARKERS:BOOL=ON //Turn off to avoid ParaView depending on all used VTK modules. PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=TRUE //Enable/Disable web support PARAVIEW_ENABLE_WEB:BOOL=ON //Enable Xdmf3 support (requires Boost). PARAVIEW_ENABLE_XDMF3:BOOL=OFF //Semicolon separated absolute paths to external directories containing // extra VTK/ParaView modules. PARAVIEW_EXTERNAL_MODULE_ROOTS:STRING= //Semi-colon seperated paths to extrenal plugin directories. PARAVIEW_EXTERNAL_PLUGIN_DIRS:STRING= //A list of plugins to autoload (but not built as part of ParaView // itself) PARAVIEW_EXTRA_EXTERNAL_PLUGINS:STRING= //Freeze Python packages/modules into the application. PARAVIEW_FREEZE_PYTHON:BOOL=OFF //Initialize MPI on client-processes by default. Can be overridden // using command line arguments PARAVIEW_INITIALIZE_MPI_ON_CLIENT:BOOL=OFF //When enabled, "make install" will install development files PARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON //Extra paths to search for plugins PARAVIEW_PLUGIN_LOADER_PATHS:STRING= //Select Qt version to use 4 or 5 PARAVIEW_QT_VERSION:STRING=5 //Link to Cray ATP library to enable debug features on Cray Systems PARAVIEW_USE_ATP:BOOL=OFF //Enable IceT (needed for parallel rendering) PARAVIEW_USE_ICE_T:BOOL=ON //Enable MPI support for parallel computing PARAVIEW_USE_MPI:BOOL=ON //Use MPI synchronous-send commands for communication PARAVIEW_USE_MPI_SSEND:BOOL=OFF //Build ParaView with OpenVR rendering PARAVIEW_USE_OPENVR:BOOL=OFF //Build ParaView with OSPRay Ray Traced rendering PARAVIEW_USE_OSPRAY:BOOL=ON //Use Qt Help infrastructure as needed. PARAVIEW_USE_QTHELP:BOOL=ON //Use Qt WebKit components as needed. PARAVIEW_USE_QTWEBKIT:BOOL=OFF //If enabled, Python bindings will back the ClientServer wrapping // implementation PARAVIEW_USE_UNIFIED_BINDINGS:BOOL=OFF //Build ParaView with VisIt readers. PARAVIEW_USE_VISITBRIDGE:BOOL=OFF //Build ParaView with VTKm many-core filters PARAVIEW_USE_VTKM:BOOL=OFF //Disable compiler warnings PROTOBUF_DISABLE_COMPILER_WARNINGS:BOOL=ON //Command to run after a failed test to cleanup processes. Example: // "killall -9 rsh paraview" PV_TEST_CLEAN_COMMAND:STRING= //Node which serves as the client node, used to connect from the // server side in reverse connection mode. PV_TEST_CLIENT:STRING=localhost //Command to run before a test begins. Multiple commands are separated // by ';'. PV_TEST_INIT_COMMAND:STRING= //Use random port numbers when testing client-server configurations. PV_TEST_USE_RANDOM_PORTS:BOOL=ON //Add module mpi4py.MPI PYTHON_ENABLE_MODULE_mpi4py.MPI:BOOL=ON //Add module mpi4py.dl PYTHON_ENABLE_MODULE_mpi4py.dl:BOOL=ON //Path to a program. PYTHON_EXECUTABLE:FILEPATH=/apps/all/Python/2.7.13/bin/python2 //Extra libraries to link when linking to python (such as "z" for // zlib). Separate multiple libraries with semicolons. PYTHON_EXTRA_LIBS:STRING= //Path to a file. PYTHON_INCLUDE_DIR:PATH=/apps/all/Python/2.7.13/include/python2.7 //Path to a library. PYTHON_LIBRARY:FILEPATH=/apps/all/Python/2.7.13/lib/libpython2.7.so //Add module mpi4py.MPI shared PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED:BOOL=ON //Add module mpi4py.dl shared PYTHON_MODULE_mpi4py.dl_BUILD_SHARED:BOOL=ON //Utility library needed for vtkpython PYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so //Dependencies for the target PacMan_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Value Computed by CMake ParaView_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj //Value Computed by CMake ParaView_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0 //qhelpgenerator used to compile Qt help project files QT_HELP_GENERATOR:FILEPATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/bin/qhelpgenerator //Delay between invocation of each testing event. QT_TESTING_EVENT_PLAYBACK_DELAY:STRING=100 //xmlpatterns used to generate html from Proxy documentation. QT_XMLPATTERNS_EXECUTABLE:FILEPATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/bin/xmlpatterns //The directory containing a CMake configuration file for Qt5Core. Qt5Core_DIR:PATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib/cmake/Qt5Core //The directory containing a CMake configuration file for Qt5Gui. Qt5Gui_DIR:PATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib/cmake/Qt5Gui //The directory containing a CMake configuration file for Qt5Help. Qt5Help_DIR:PATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib/cmake/Qt5Help //The directory containing a CMake configuration file for Qt5Network. Qt5Network_DIR:PATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib/cmake/Qt5Network //The directory containing a CMake configuration file for Qt5Widgets. Qt5Widgets_DIR:PATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib/cmake/Qt5Widgets //The directory containing a CMake configuration file for Qt5. Qt5_DIR:PATH=/apps/all/Qt5/5.8.0-GCC-6.3.0-2.27/lib/cmake/Qt5 //Value Computed by CMake QtTesting_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/ThirdParty/QtTesting/vtkqttesting //Dependencies for the target QtTesting_LIB_DEPENDS:STATIC=general;Qt5::Core;general;Qt5::Widgets; //Value Computed by CMake QtTesting_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ThirdParty/QtTesting/vtkqttesting //Dependencies for the target SLACTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Explicitly disable SurfaceLIC plugin ctests SURFACELIC_PLUGIN_TESTING:BOOL=ON //Dependencies for the target SierraPlotTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVVTKExtensionsDefault;general;Qt5::Widgets; //Dependencies for the target StreamLinesRepresentation_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so;general;pqApplicationComponents; //Dependencies for the target StreamingParticles_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Dependencies for the target SurfaceLIC_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkRenderingLICOpenGL2; //Path to a file. TBB_INCLUDE_DIR:PATH=/apps/all/tbb/2017.6.196/tbb/include //Path to a library. TBB_LIBRARY:FILEPATH=/apps/all/tbb/2017.6.196/tbb/lib/libtbb.so.2 //Path to a library. TBB_LIBRARY_DEBUG:FILEPATH=/apps/all/tbb/2017.6.196/tbb/lib/libtbb_debug.so.2 //Path to a library. TBB_LIBRARY_MALLOC:FILEPATH=/apps/all/tbb/2017.6.196/tbb/lib/libtbbmalloc.so.2 //Path to a library. TBB_LIBRARY_MALLOC_DEBUG:FILEPATH=/apps/all/tbb/2017.6.196/tbb/lib/libtbbmalloc_debug.so.2 //TBB Version TBB_VERSION:STRING=2017.0 //Dependencies for the target ThickenLayeredCells_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS; //Use HIDDEN visibility support if available. USE_COMPILER_HIDDEN_VISIBILITY:BOOL=ON //Value Computed by CMake VPIC_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/VPIC //Dependencies for the target VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Value Computed by CMake VPIC_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/VPIC //Value Computed by CMake VTKFREETYPE_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKFREETYPE_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/freetype/vtkfreetype //Value Computed by CMake VTKGL2PS_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGL2PS_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/gl2ps/vtkgl2ps //Value Computed by CMake VTKGLEW_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/glew/vtkglew //Value Computed by CMake VTKGLEW_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/glew/vtkglew //Value Computed by CMake VTKJPEG_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKJPEG_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/jpeg/vtkjpeg //Value Computed by CMake VTKNETCDF_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKNETCDF_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/netcdf/vtknetcdf //Value Computed by CMake VTKOGGTHEORA_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/oggtheora/vtkoggtheora //Disable assemby optimizations VTKOGGTHEORA_DISABLE_ASM:BOOL=OFF //Disable the use of floating point code in theora VTKOGGTHEORA_DISABLE_FLOAT:BOOL=OFF //Additional linker flags for vtkoggtheora when building as a shared // library VTKOGGTHEORA_SHARED_LINKER_FLAGS:STRING=-Wl,--version-script="/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/oggtheora/vtkoggtheora/vtkoggtheora.vscript" //Value Computed by CMake VTKOGGTHEORA_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/oggtheora/vtkoggtheora //Value Computed by CMake VTKPNG_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/png/vtkpng //Value Computed by CMake VTKPNG_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/png/vtkpng //Build all vtkObject derived classes with object factory new methods. VTK_ALL_NEW_OBJECT_FACTORY:BOOL=OFF //Build VTK for Android VTK_ANDROID_BUILD:BOOL=OFF //Value Computed by CMake VTK_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK //Request to build all modules VTK_BUILD_ALL_MODULES:BOOL=OFF //Build the VTK Qt plugin for the Qt Designer. VTK_BUILD_QT_DESIGNER_PLUGIN:BOOL=OFF //Local directory holding ExternalData objects in the layout %(algo)/%(hash). VTK_DATA_STORE:PATH= //Build leak checking support into VTK. VTK_DEBUG_LEAKS:BOOL=OFF //Include array-of-structs vtkDataArray subclasses in dispatcher. VTK_DISPATCH_AOS_ARRAYS:BOOL=ON //Include struct-of-arrays vtkDataArray subclasses in dispatcher. VTK_DISPATCH_SOA_ARRAYS:BOOL=OFF //Include vtkTypedDataArray subclasses (e.g. old mapped arrays) // in dispatcher. VTK_DISPATCH_TYPED_ARRAYS:BOOL=OFF //Index of the EGL device (graphics card) to use. VTK_EGL_DEVICE_INDEX:STRING=0 //Build VTK using kits instead of modules. VTK_ENABLE_KITS:BOOL=OFF //Enable vtkpython and pvtkpython binaries VTK_ENABLE_VTKPYTHON:BOOL=ON //Whether the HDF5 in use is shared or not VTK_EXTERNAL_HDF5_IS_SHARED:BOOL=OFF //Whether the system libharu in use is a shared library or not VTK_EXTERNAL_LIBHARU_IS_SHARED:BOOL=ON //Do not download source code or data from the network VTK_FORBID_DOWNLOADS:BOOL=OFF //Location of the OpenGL extensions header file (glext.h). VTK_GLEXT_FILE:FILEPATH=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Utilities/ParseOGLExt/headers/glext.h //Location of the GLX extensions header file (glxext.h). VTK_GLXEXT_FILE:FILEPATH=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Utilities/ParseOGLExt/headers/glxext.h //Request building Imaging modules VTK_Group_Imaging:BOOL=OFF //Request building MPI modules VTK_Group_MPI:BOOL=OFF //Request building ParaViewCore modules VTK_Group_ParaViewCore:BOOL=ON //Request building ParaViewQt modules VTK_Group_ParaViewQt:BOOL=OFF //Request building ParaViewRendering modules VTK_Group_ParaViewRendering:BOOL=ON //Request building Qt modules VTK_Group_Qt:BOOL=OFF //Request building Rendering modules VTK_Group_Rendering:BOOL=OFF //Request building of all stand alone modules (no external dependencies // required) VTK_Group_StandAlone:BOOL=OFF //Request building Tk modules VTK_Group_Tk:BOOL=OFF //Request building Views modules VTK_Group_Views:BOOL=OFF //Request building Web modules VTK_Group_Web:BOOL=OFF //Build vtk.framework for iOS VTK_IOS_BUILD:BOOL=OFF //Remove all legacy code completely. VTK_LEGACY_REMOVE:BOOL=OFF //Silence all legacy code messages. VTK_LEGACY_SILENT:BOOL=OFF //Should all modules build instantiators VTK_MAKE_INSTANTIATORS:BOOL=OFF //Max number of threads vktMultiThreader will allocate. VTK_MAX_THREADS:STRING=64 //The full path to mpirun command VTK_MPIRUN_EXE:FILEPATH=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpiexec //Maximum number of processors available to run parallel applications. // (see /home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_MAX_NUMPROCS:STRING=2 //Flag used by mpi to specify the number of processes, the next // option will be the number of processes. (see /home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIRun.(see /home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by VTK_MPIRUN_EXE. (see /home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PREFLAGS:STRING= //These flags will be directly before the number of processess // flag (see /home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Parallel/MPI/CMakeLists.txt // for more info.) VTK_MPI_PRENUMPROC_FLAGS:STRING= //Disable Python Threads support VTK_NO_PYTHON_THREADS:BOOL=ON //The OpenGL library being used supports off screen Mesa calls VTK_OPENGL_HAS_OSMESA:BOOL=ON //Python version to use: 2, 2.x, 3, 3.x, or empty VTK_PYTHON_VERSION:STRING=2 //enable parallel timers for the 2d line integral convolution VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER:BOOL=OFF //enable parallel timers for the surface lic painter VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER:BOOL=OFF //No help, variable specified on the command line. VTK_RENDERING_BACKEND:UNINITIALIZED=OpenGL2 //Enable OpenGL error check and report VTK_REPORT_OPENGL_ERRORS:BOOL=ON //Enable OpenGL error check and reporting in non-debug builds. VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS:BOOL=OFF //Which multi-threaded parallelism implementation to use. Options // are Sequential, OpenMP or TBB VTK_SMP_IMPLEMENTATION_TYPE:STRING=Sequential //Value Computed by CMake VTK_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK //Build VTK with 64 bit ids VTK_USE_64BIT_IDS:BOOL=ON //Enable tests requiring "large" data VTK_USE_LARGE_DATA:BOOL=OFF //Use off screen calls by default VTK_USE_OFFSCREEN:BOOL=ON //Use EGL for OpenGL client API for offscreen rendering. VTK_USE_OFFSCREEN_EGL:BOOL=OFF //Use system 'autobahn' Python package VTK_USE_SYSTEM_AUTOBAHN:BOOL=OFF //Use system-installed CGNS VTK_USE_SYSTEM_CGNS:BOOL=OFF //Use system 'cinema_python' Python package VTK_USE_SYSTEM_CINEMA_PYTHON:BOOL=OFF //Use system 'constantly' Python package VTK_USE_SYSTEM_CONSTANTLY:BOOL=OFF //Use system-installed diy2 VTK_USE_SYSTEM_DIY2:BOOL=OFF //Use system-installed EXPAT VTK_USE_SYSTEM_EXPAT:BOOL=OFF //Use system-installed Freetype VTK_USE_SYSTEM_FREETYPE:BOOL=OFF //Use system-installed GL2PS VTK_USE_SYSTEM_GL2PS:BOOL=OFF //Use system-installed GLEW VTK_USE_SYSTEM_GLEW:BOOL=OFF //Use system-installed HDF5 VTK_USE_SYSTEM_HDF5:BOOL=ON //Use system-installed icet VTK_USE_SYSTEM_ICET:BOOL=OFF //Use system 'incremental' Python package VTK_USE_SYSTEM_INCREMENTAL:BOOL=OFF //Use system-installed JPEG VTK_USE_SYSTEM_JPEG:BOOL=OFF //Use system-installed JsonCpp VTK_USE_SYSTEM_JSONCPP:BOOL=OFF //Use system-installed LibHaru VTK_USE_SYSTEM_LIBHARU:BOOL=OFF //Use the system's libraries by default. VTK_USE_SYSTEM_LIBRARIES:BOOL=OFF //Use system-installed LibXml2 VTK_USE_SYSTEM_LIBXML2:BOOL=OFF //Use system-installed LZ4 VTK_USE_SYSTEM_LZ4:BOOL=OFF //Use system 'mpi4py' Python package VTK_USE_SYSTEM_MPI4PY:BOOL=OFF //Use system-installed NetCDF VTK_USE_SYSTEM_NETCDF:BOOL=OFF //Use system-installed NetCDFCPP VTK_USE_SYSTEM_NETCDFCPP:BOOL=OFF //Use system-installed OGGTHEORA VTK_USE_SYSTEM_OGGTHEORA:BOOL=OFF //Use system-installed PNG VTK_USE_SYSTEM_PNG:BOOL=OFF //Use system-installed Protobuf VTK_USE_SYSTEM_PROTOBUF:BOOL=OFF //Use system-installed pugixml VTK_USE_SYSTEM_PUGIXML:BOOL=OFF //Use system 'pygments' Python package VTK_USE_SYSTEM_PYGMENTS:BOOL=OFF //Use system-installed qttesting VTK_USE_SYSTEM_QTTESTING:BOOL=OFF //Use system 'six' Python Module VTK_USE_SYSTEM_SIX:BOOL=OFF //Use system-installed TIFF VTK_USE_SYSTEM_TIFF:BOOL=OFF //Use system 'twisted' Python package VTK_USE_SYSTEM_TWISTED:BOOL=OFF //Use system-installed xdmf2 VTK_USE_SYSTEM_XDMF2:BOOL=OFF //Use system-installed ZLIB VTK_USE_SYSTEM_ZLIB:BOOL=OFF //Use system 'zope' Python package VTK_USE_SYSTEM_ZOPE:BOOL=OFF //Build VTK with Tk support VTK_USE_TK:BOOL=OFF //Use X for VTK render windows VTK_USE_X:BOOL=OFF //Build VPIC with MPI VTK_VPIC_USE_MPI:BOOL=ON //If enabled, vtkArrayDispatch will print a warning when a dispatch // fails. VTK_WARN_ON_DISPATCH_FAILURE:BOOL=OFF //Location of the WGL extensions header file (wglext.h). VTK_WGLEXT_FILE:FILEPATH=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Utilities/ParseOGLExt/headers/wglext.h //Path to a file. VTK_WRAP_HINTS:FILEPATH=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Wrapping/Tools/hints //Should VTK Java wrapping be built? VTK_WRAP_JAVA:BOOL=OFF //Should VTK Tcl wrapping be built? VTK_WRAP_TCL:BOOL=OFF //Build Xdmf with MPI VTK_XDMF_USE_MPI:BOOL=OFF //XDMF should use MPI XDMF_BUILD_MPI:BOOL=OFF //XDMF has Network Distributed Global Memory (NDGM) XDMF_HAS_NDGM:BOOL=OFF //Path to a file. XDMF_HAVE_FCNTL:PATH=/usr/include //Path to a file. XDMF_HAVE_MMAN:PATH=/usr/include/sys //Path to a file. XDMF_HAVE_NETINET:PATH=/usr/include/netinet //Use bzip2 XDMF_USE_BZIP2:BOOL=OFF //Build GZip Compression XDMF_USE_GZIP:BOOL=OFF //Build Support for MySQL DataItems XDMF_USE_MYSQL:BOOL=OFF //Path to a program. XIAR:FILEPATH=/apps/all/ifort/2017.1.132-GCC-6.3.0-2.27/compilers_and_libraries_2017.1.132/linux/bin/intel64/xiar //Value Computed by CMake alglib_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/alglib //Value Computed by CMake alglib_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/alglib //Value Computed by CMake cgns_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/ThirdParty/cgns/vtkcgns //Value Computed by CMake cgns_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ThirdParty/cgns/vtkcgns //Value Computed by CMake diy2_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/diy2/vtkdiy2 //Value Computed by CMake diy2_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/diy2/vtkdiy2 //The directory containing a CMake configuration file for embree. embree_DIR:PATH=/apps/all/Embree/2.16.2-intel-2017a/lib64/cmake/embree-2.16.2 //Value Computed by CMake expat_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/expat/vtkexpat //Value Computed by CMake expat_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/expat/vtkexpat //Dependencies for the target mpi4py.MPI_LIB_DEPENDS:STATIC=general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;dl; //Dependencies for the target mpi4py.dl_LIB_DEPENDS:STATIC=general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;dl; //Value Computed by CMake mpi4py_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake mpi4py_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/mpi4py/vtkmpi4py //Value Computed by CMake netcdf_libdispatch_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_libdispatch_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch //Value Computed by CMake netcdf_liblib_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_liblib_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/netcdf/vtknetcdf/liblib //Value Computed by CMake netcdf_libsrc4_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc4_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4 //Value Computed by CMake netcdf_libsrc_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //Value Computed by CMake netcdf_libsrc_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/netcdf/vtknetcdf/libsrc //The directory containing a CMake configuration file for ospray. ospray_DIR:PATH=/apps/all/OSPRay/1.3.0-intel-2017a/lib64/cmake/ospray-1.3.0 //Dependencies for the target pmpi-mpe_LIB_DEPENDS:STATIC=general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target pmpi-vt-hyb_LIB_DEPENDS:STATIC=general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target pmpi-vt-mpi_LIB_DEPENDS:STATIC=general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target pmpi-vt_LIB_DEPENDS:STATIC=general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target pqApplicationComponents_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkGUISupportQt;general;vtkjsoncpp;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;vtkPVCinemaReader;general;Qt5::Widgets;general;Qt5::Help; //Dependencies for the target pqComponents_LIB_DEPENDS:STATIC=general;pqCore;general;pqPython;general;vtkjsoncpp;general;vtkChartsCore;general;vtkIOImage;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;general;Qt5::Widgets;general;Qt5::Network; //Dependencies for the target pqCore_LIB_DEPENDS:STATIC=general;pqWidgets;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVClientServerCoreDefault;general;vtkPVServerManagerApplication;general;vtkPVServerManagerDefault;general;vtksys;general;vtkTestingRendering;general;Qt5::Help; //Dependencies for the target pqPython_LIB_DEPENDS:STATIC=general;pqCore;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;Qt5::Widgets; //Dependencies for the target pqWidgets_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkPVServerManagerCore;general;QtTesting;general;Qt5::Network;general;Qt5::Help;general;Qt5::Core;general;Qt5::Gui;general;Qt5::Widgets; //Dependencies for target protobuf-lite_LIB_DEPENDS:STATIC= //Value Computed by CMake protobuf_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/ThirdParty/protobuf/vtkprotobuf //Dependencies for target protobuf_LIB_DEPENDS:STATIC= //Value Computed by CMake protobuf_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ThirdParty/protobuf/vtkprotobuf //Value Computed by CMake tiff_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake tiff_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/tiff/vtktiff //Value Computed by CMake verdict_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/verdict/vtkverdict //Dependencies for target verdict_LIB_DEPENDS:STATIC= //Value Computed by CMake verdict_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/verdict/vtkverdict //Dependencies for the target vtkChartsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkChartsCore; //Dependencies for the target vtkChartsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkCommonColorPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkInfovisCorePythonD;general;vtkChartsCore; //Dependencies for the target vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD; //Dependencies for the target vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtksys;general;vtkCommonColor;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkInfovisCore; //Dependencies for the target vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;vtksys; //Dependencies for the target vtkCommonColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonColor; //Dependencies for the target vtkCommonColorPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonColor; //Dependencies for the target vtkCommonColorPython_LIB_DEPENDS:STATIC=general;vtkCommonColorPythonD; //Dependencies for the target vtkCommonColor_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkCommonComputationalGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonComputationalGeometry; //Dependencies for the target vtkCommonComputationalGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonComputationalGeometry; //Dependencies for the target vtkCommonComputationalGeometryPython_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometryPythonD; //Dependencies for the target vtkCommonComputationalGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkCommonCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore; //Dependencies for the target vtkCommonCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCore; //Dependencies for the target vtkCommonCorePython_LIB_DEPENDS:STATIC=general;vtkCommonCorePythonD; //Dependencies for the target vtkCommonCore_LIB_DEPENDS:STATIC=general;vtksys; //Dependencies for the target vtkCommonDataModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonDataModel; //Dependencies for the target vtkCommonDataModelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonDataModel; //Dependencies for the target vtkCommonDataModelPython_LIB_DEPENDS:STATIC=general;vtkCommonDataModelPythonD; //Dependencies for the target vtkCommonDataModel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkCommonMisc;general;vtkCommonSystem;general;vtksys; //Dependencies for the target vtkCommonExecutionModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonExecutionModel; //Dependencies for the target vtkCommonExecutionModelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonExecutionModel; //Dependencies for the target vtkCommonExecutionModelPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModelPythonD; //Dependencies for the target vtkCommonExecutionModel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem; //Dependencies for the target vtkCommonMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMath; //Dependencies for the target vtkCommonMathPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMath; //Dependencies for the target vtkCommonMathPython_LIB_DEPENDS:STATIC=general;vtkCommonMathPythonD; //Dependencies for the target vtkCommonMath_LIB_DEPENDS:STATIC=general;vtkCommonCore; //Dependencies for the target vtkCommonMiscCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMisc; //Dependencies for the target vtkCommonMiscPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonMisc; //Dependencies for the target vtkCommonMiscPython_LIB_DEPENDS:STATIC=general;vtkCommonMiscPythonD; //Dependencies for the target vtkCommonMisc_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath; //Dependencies for the target vtkCommonSystemCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonSystem; //Dependencies for the target vtkCommonSystemPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonSystem; //Dependencies for the target vtkCommonSystemPython_LIB_DEPENDS:STATIC=general;vtkCommonSystemPythonD; //Dependencies for the target vtkCommonSystem_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys; //Dependencies for the target vtkCommonTransformsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonTransforms; //Dependencies for the target vtkCommonTransformsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransforms; //Dependencies for the target vtkCommonTransformsPython_LIB_DEPENDS:STATIC=general;vtkCommonTransformsPythonD; //Dependencies for the target vtkCommonTransforms_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath; //Dependencies for target vtkDICOMParser_LIB_DEPENDS:STATIC= //Dependencies for the target vtkDomainsChemistryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistry; //Dependencies for the target vtkDomainsChemistryOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistryOpenGL2; //Dependencies for the target vtkDomainsChemistryOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkDomainsChemistryPythonD;general;vtkDomainsChemistryPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkRenderingCorePythonD;general;vtkDomainsChemistryOpenGL2; //Dependencies for the target vtkDomainsChemistryOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryOpenGL2PythonD; //Dependencies for the target vtkDomainsChemistryOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkDomainsChemistry;general;vtkDomainsChemistry;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkglew;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkDomainsChemistryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLParserPythonD;general;vtkRenderingCorePythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkDomainsChemistry; //Dependencies for the target vtkDomainsChemistryPython_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryPythonD; //Dependencies for the target vtkDomainsChemistry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXMLParser;general;vtkRenderingCore;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys; //Value Computed by CMake vtkExodus2_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/exodusII/vtkexodusII //Value Computed by CMake vtkExodus2_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/exodusII/vtkexodusII //Dependencies for the target vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;general;vtkFiltersAMR; //Dependencies for the target vtkFiltersAMRPython_LIB_DEPENDS:STATIC=general;vtkFiltersAMRPythonD; //Dependencies for the target vtkFiltersAMR_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkIOXML;general;vtkParallelCore; //Dependencies for the target vtkFiltersCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersCore; //Dependencies for the target vtkFiltersCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCore; //Dependencies for the target vtkFiltersCorePython_LIB_DEPENDS:STATIC=general;vtkFiltersCorePythonD; //Dependencies for the target vtkFiltersCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersExtractionCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersExtraction; //Dependencies for the target vtkFiltersExtractionPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersStatisticsPythonD;general;vtkFiltersExtraction; //Dependencies for the target vtkFiltersExtractionPython_LIB_DEPENDS:STATIC=general;vtkFiltersExtractionPythonD; //Dependencies for the target vtkFiltersExtraction_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkFiltersCore;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersFlowPaths; //Dependencies for the target vtkFiltersFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOCorePythonD;general;vtkFiltersFlowPaths; //Dependencies for the target vtkFiltersFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPathsPythonD; //Dependencies for the target vtkFiltersFlowPaths_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkFiltersGeometry;general;vtkFiltersSources;general;vtkIOCore; //Dependencies for the target vtkFiltersGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersCorePythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersGeneralPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeneralPythonD; //Dependencies for the target vtkFiltersGeneral_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonComputationalGeometry;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersGenericCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneric; //Dependencies for the target vtkFiltersGenericPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersGeneric; //Dependencies for the target vtkFiltersGenericPython_LIB_DEPENDS:STATIC=general;vtkFiltersGenericPythonD; //Dependencies for the target vtkFiltersGeneric_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersSources; //Dependencies for the target vtkFiltersGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeometry; //Dependencies for the target vtkFiltersGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometry; //Dependencies for the target vtkFiltersGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeometryPythonD; //Dependencies for the target vtkFiltersGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore; //Dependencies for the target vtkFiltersHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHybrid; //Dependencies for the target vtkFiltersHybridPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkFiltersHybrid; //Dependencies for the target vtkFiltersHybridPython_LIB_DEPENDS:STATIC=general;vtkFiltersHybridPythonD; //Dependencies for the target vtkFiltersHybrid_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkCommonMath;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkImagingCore;general;vtkImagingSources;general;vtkRenderingCore;general;vtksys; //Dependencies for the target vtkFiltersHyperTreeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHyperTree; //Dependencies for the target vtkFiltersHyperTreePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonSystemPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersHyperTree; //Dependencies for the target vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD; //Dependencies for the target vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersCore;general;vtkCommonCore;general;vtkCommonSystem;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersImaging; //Dependencies for the target vtkFiltersImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersStatisticsPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkImagingGeneralPythonD;general;vtkFiltersImaging; //Dependencies for the target vtkFiltersImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersImagingPythonD; //Dependencies for the target vtkFiltersImaging_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersStatistics;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkImagingGeneral; //Dependencies for the target vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling; //Dependencies for the target vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkFiltersGeneralPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersModeling; //Dependencies for the target vtkFiltersModelingPython_LIB_DEPENDS:STATIC=general;vtkFiltersModelingPythonD; //Dependencies for the target vtkFiltersModeling_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkFiltersGeneral;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersSources; //Dependencies for the target vtkFiltersParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallel; //Dependencies for the target vtkFiltersParallelDIY2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelDIY2; //Dependencies for the target vtkFiltersParallelDIY2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelDIY2; //Dependencies for the target vtkFiltersParallelDIY2Python_LIB_DEPENDS:STATIC=general;vtkFiltersParallelDIY2PythonD; //Dependencies for the target vtkFiltersParallelDIY2_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkFiltersCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkParallelMPI;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkFiltersParallelFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelFlowPaths; //Dependencies for the target vtkFiltersParallelFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersFlowPathsPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkIOCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelFlowPaths; //Dependencies for the target vtkFiltersParallelFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelFlowPathsPythonD; //Dependencies for the target vtkFiltersParallelFlowPaths_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkFiltersFlowPaths;general;vtkFiltersFlowPaths;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkIOCore;general;vtkParallelCore;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelGeometry; //Dependencies for the target vtkFiltersParallelGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeometryPythonD;general;vtkParallelMPIPythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelGeometry; //Dependencies for the target vtkFiltersParallelGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelGeometryPythonD; //Dependencies for the target vtkFiltersParallelGeometry_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeometry;general;vtkParallelMPI;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkIOLegacy;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallelImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersImagingPythonD;general;vtkFiltersParallelPythonD;general;vtkImagingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersStatisticsPythonD;general;vtkImagingGeneralPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelImaging; //Dependencies for the target vtkFiltersParallelImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImagingPythonD; //Dependencies for the target vtkFiltersParallelImaging_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersImaging;general;vtkFiltersParallel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersStatistics;general;vtkImagingGeneral;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelMPI; //Dependencies for the target vtkFiltersParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkImagingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkFiltersParallelMPI; //Dependencies for the target vtkFiltersParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelMPIPythonD; //Dependencies for the target vtkFiltersParallelMPI_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkImagingCore;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkFiltersParallel;general;vtkIOLegacy;general;vtkParallelCore;general;vtkParallelMPI; //Dependencies for the target vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersSourcesPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkFiltersParallel; //Dependencies for the target vtkFiltersParallelPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelPythonD; //Dependencies for the target vtkFiltersParallelStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelStatistics; //Dependencies for the target vtkFiltersParallelStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersStatisticsPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkParallelCorePythonD;general;vtkFiltersParallelStatistics; //Dependencies for the target vtkFiltersParallelStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelStatisticsPythonD; //Dependencies for the target vtkFiltersParallelStatistics_LIB_DEPENDS:STATIC=general;vtkFiltersStatistics;general;vtkalglib;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkParallelCore; //Dependencies for the target vtkFiltersParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersModeling;general;vtkFiltersSources;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOLegacy;general;vtkParallelCore;general;vtkRenderingCore; //Dependencies for the target vtkFiltersPointsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPoints; //Dependencies for the target vtkFiltersPointsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersPoints; //Dependencies for the target vtkFiltersPointsPython_LIB_DEPENDS:STATIC=general;vtkFiltersPointsPythonD; //Dependencies for the target vtkFiltersPoints_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel; //Dependencies for the target vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersProgrammable; //Dependencies for the target vtkFiltersProgrammablePython_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammablePythonD; //Dependencies for the target vtkFiltersProgrammable_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms; //Dependencies for the target vtkFiltersPythonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPython; //Dependencies for the target vtkFiltersPythonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkFiltersPython; //Dependencies for the target vtkFiltersPythonPython_LIB_DEPENDS:STATIC=general;vtkFiltersPythonPythonD; //Dependencies for the target vtkFiltersPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkWrappingPythonCore; //Dependencies for the target vtkFiltersSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersSources; //Dependencies for the target vtkFiltersSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonCorePythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSources; //Dependencies for the target vtkFiltersSourcesPython_LIB_DEPENDS:STATIC=general;vtkFiltersSourcesPythonD; //Dependencies for the target vtkFiltersSources_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonComputationalGeometry;general;vtkCommonCore;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkImagingFourierPythonD;general;vtkFiltersStatistics; //Dependencies for the target vtkFiltersStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersStatisticsPythonD; //Dependencies for the target vtkFiltersStatistics_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkalglib;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkImagingFourier; //Dependencies for the target vtkFiltersTextureCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersTexture; //Dependencies for the target vtkFiltersTexturePython_LIB_DEPENDS:STATIC=general;vtkFiltersTexturePythonD; //Dependencies for the target vtkFiltersTexture_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersGeneral; //Dependencies for the target vtkFiltersVerdictCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersVerdict; //Dependencies for the target vtkFiltersVerdictPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersVerdict; //Dependencies for the target vtkFiltersVerdictPython_LIB_DEPENDS:STATIC=general;vtkFiltersVerdictPythonD; //Dependencies for the target vtkFiltersVerdict_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;verdict;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkGUISupportQt_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkCommonDataModel;general;vtkFiltersExtraction;general;vtkInteractionStyle;general;Qt5::Widgets; //Dependencies for the target vtkIOAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOAMR; //Dependencies for the target vtkIOAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;general;vtkIOAMR; //Dependencies for the target vtkIOAMRPython_LIB_DEPENDS:STATIC=general;vtkIOAMRPythonD; //Dependencies for the target vtkIOAMR_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkParallelCore;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so;general;/apps/all/Szip/2.1-intel-2017a/lib/libsz.so;general;/apps/all/zlib/1.2.11/lib/libz.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;vtksys; //Dependencies for the target vtkIOCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOCore; //Dependencies for the target vtkIOCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCore; //Dependencies for the target vtkIOCorePython_LIB_DEPENDS:STATIC=general;vtkIOCorePythonD; //Dependencies for the target vtkIOCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtklz4;general;vtksys;general;vtkzlib; //Dependencies for the target vtkIOEnSightCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOEnSight; //Dependencies for the target vtkIOEnSightPython_LIB_DEPENDS:STATIC=general;vtkIOEnSightPythonD; //Dependencies for the target vtkIOEnSight_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkIOExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkFiltersCorePythonD;general;vtkIOExodus; //Dependencies for the target vtkIOExodusPython_LIB_DEPENDS:STATIC=general;vtkIOExodusPythonD; //Dependencies for the target vtkIOExodus_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOXMLParser;general;vtkexoIIc;general;vtkFiltersCore;general;vtksys; //Dependencies for the target vtkIOExportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExport; //Dependencies for the target vtkIOExportOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExportOpenGL2; //Dependencies for the target vtkIOExportOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOExportPythonD;general;vtkIOExportPythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkIOExportOpenGL2; //Dependencies for the target vtkIOExportOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkIOExportOpenGL2PythonD; //Dependencies for the target vtkIOExportOpenGL2_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtkIOExport;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkRenderingCore;general;vtkgl2ps;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingGL2PSOpenGL2PythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeometryPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkIOExport; //Dependencies for the target vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD; //Dependencies for the target vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingGL2PSOpenGL2;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeometry;general;vtkIOImage;general;vtkImagingCore;general;vtklibharu;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkCommonCorePythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOGeometry; //Dependencies for the target vtkIOGeometryPython_LIB_DEPENDS:STATIC=general;vtkIOGeometryPythonD; //Dependencies for the target vtkIOGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOLegacy;general;vtkCommonCore;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtksys;general;vtkzlib; //Dependencies for the target vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage; //Dependencies for the target vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOImage; //Dependencies for the target vtkIOImagePython_LIB_DEPENDS:STATIC=general;vtkIOImagePythonD; //Dependencies for the target vtkIOImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkDICOMParser;general;vtkmetaio;general;vtkjpeg;general;vtkpng;general;vtksys;general;vtktiff;general;vtkzlib; //Dependencies for the target vtkIOImportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImport; //Dependencies for the target vtkIOImportPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkIOImagePythonD;general;vtkIOImport; //Dependencies for the target vtkIOImportPython_LIB_DEPENDS:STATIC=general;vtkIOImportPythonD; //Dependencies for the target vtkIOImport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkRenderingCore;general;vtksys;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersSources;general;vtkIOImage; //Dependencies for the target vtkIOInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOInfovis; //Dependencies for the target vtkIOInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParserPythonD;general;vtkInfovisCorePythonD;general;vtkIOInfovis; //Dependencies for the target vtkIOInfovisPython_LIB_DEPENDS:STATIC=general;vtkIOInfovisPythonD; //Dependencies for the target vtkIOInfovis_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkIOXML;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkIOCore;general;vtkIOXMLParser;general;vtkInfovisCore;general;vtklibxml2;general;vtksys; //Dependencies for the target vtkIOLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLSDyna; //Dependencies for the target vtkIOLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLParserPythonD;general;vtkCommonDataModelPythonD;general;vtkIOLSDyna; //Dependencies for the target vtkIOLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOLSDynaPythonD; //Dependencies for the target vtkIOLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;general;vtksys; //Dependencies for the target vtkIOLegacyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLegacy; //Dependencies for the target vtkIOLegacyPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkCommonMiscPythonD;general;vtkIOLegacy; //Dependencies for the target vtkIOLegacyPython_LIB_DEPENDS:STATIC=general;vtkIOLegacyPythonD; //Dependencies for the target vtkIOLegacy_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkCommonMisc;general;vtksys; //Dependencies for the target vtkIOMPIImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIImage; //Dependencies for the target vtkIOMPIImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;general;vtkIOMPIImage; //Dependencies for the target vtkIOMPIImagePython_LIB_DEPENDS:STATIC=general;vtkIOMPIImagePythonD; //Dependencies for the target vtkIOMPIImage_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkIOImage;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkParallelCore;general;vtkParallelMPI;general;vtksys;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkIOMPIParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIParallel; //Dependencies for the target vtkIOMPIParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOGeometryPythonD;general;vtkIOGeometryPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkParallelMPIPythonD;general;vtkIOMPIParallel; //Dependencies for the target vtkIOMPIParallelPython_LIB_DEPENDS:STATIC=general;vtkIOMPIParallelPythonD; //Dependencies for the target vtkIOMPIParallel_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkIOGeometry;general;vtkIOParallel;general;vtkIOParallel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelMPI;general;vtksys;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOMovie; //Dependencies for the target vtkIOMoviePython_LIB_DEPENDS:STATIC=general;vtkIOMoviePythonD; //Dependencies for the target vtkIOMovie_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkoggtheora;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem; //Dependencies for the target vtkIONetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkIONetCDF; //Dependencies for the target vtkIONetCDFPython_LIB_DEPENDS:STATIC=general;vtkIONetCDFPythonD; //Dependencies for the target vtkIONetCDF_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkNetCDF;general;vtknetcdfcpp;general;vtksys; //Dependencies for the target vtkIOPLYCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOPLY; //Dependencies for the target vtkIOPLYPython_LIB_DEPENDS:STATIC=general;vtkIOPLYPythonD; //Dependencies for the target vtkIOPLY_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOCore;general;vtkCommonDataModel;general;vtkCommonMisc; //Dependencies for the target vtkIOParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallel; //Dependencies for the target vtkIOParallelExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelExodus; //Dependencies for the target vtkIOParallelExodusPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOExodusPythonD;general;vtkIOExodusPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkParallelCorePythonD;general;vtkIOParallelExodus; //Dependencies for the target vtkIOParallelExodusPython_LIB_DEPENDS:STATIC=general;vtkIOParallelExodusPythonD; //Dependencies for the target vtkIOParallelExodus_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOExodus;general;vtkIOExodus;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkParallelCore;general;vtkexoIIc;general;vtksys; //Dependencies for the target vtkIOParallelLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelLSDyna; //Dependencies for the target vtkIOParallelLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOLSDynaPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkParallelCorePythonD;general;vtkIOParallelLSDyna; //Dependencies for the target vtkIOParallelLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOParallelLSDynaPythonD; //Dependencies for the target vtkIOParallelLSDyna_LIB_DEPENDS:STATIC=general;vtkIOLSDyna;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkParallelCore; //Dependencies for the target vtkIOParallelNetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelNetCDF; //Dependencies for the target vtkIOParallelNetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelMPIPythonD;general;vtkIOParallelNetCDF; //Dependencies for the target vtkIOParallelNetCDFPython_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDFPythonD; //Dependencies for the target vtkIOParallelNetCDF_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkNetCDF;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOCorePythonD;general;vtkIOGeometryPythonD;general;vtkIOImagePythonD;general;vtkIOLegacyPythonD;general;vtkIONetCDFPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkParallelCorePythonD;general;vtkIOParallel; //Dependencies for the target vtkIOParallelPython_LIB_DEPENDS:STATIC=general;vtkIOParallelPythonD; //Dependencies for the target vtkIOParallelXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelXML; //Dependencies for the target vtkIOParallelXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkIOXMLPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkParallelCorePythonD;general;vtkIOParallelXML; //Dependencies for the target vtkIOParallelXMLPython_LIB_DEPENDS:STATIC=general;vtkIOParallelXMLPythonD; //Dependencies for the target vtkIOParallelXML_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkParallelCore;general;vtksys; //Dependencies for the target vtkIOParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOCore;general;vtkIOGeometry;general;vtkIOImage;general;vtkIOLegacy;general;vtkIONetCDF;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkParallelCore;general;vtkexoIIc;general;vtkjsoncpp;general;vtkNetCDF;general;vtksys; //Dependencies for the target vtkIOTRUCHASCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOTRUCHAS; //Dependencies for the target vtkIOTRUCHASPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkIOTRUCHAS; //Dependencies for the target vtkIOTRUCHASPython_LIB_DEPENDS:STATIC=general;vtkIOTRUCHASPythonD; //Dependencies for the target vtkIOTRUCHAS_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so;general;/apps/all/Szip/2.1-intel-2017a/lib/libsz.so;general;/apps/all/zlib/1.2.11/lib/libz.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkIOTecplotTableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOTecplotTable; //Dependencies for the target vtkIOTecplotTablePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkIOCorePythonD;general;vtkIOTecplotTable; //Dependencies for the target vtkIOTecplotTablePython_LIB_DEPENDS:STATIC=general;vtkIOTecplotTablePythonD; //Dependencies for the target vtkIOTecplotTable_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOCore;general;vtksys; //Dependencies for the target vtkIOVPICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOVPIC; //Dependencies for the target vtkIOVPICPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkParallelCorePythonD;general;vtkIOVPIC; //Dependencies for the target vtkIOVPICPython_LIB_DEPENDS:STATIC=general;vtkIOVPICPythonD; //Dependencies for the target vtkIOVPIC_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;VPIC;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkParallelCore; //Dependencies for the target vtkIOXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXML; //Dependencies for the target vtkIOXMLParserCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXMLParser; //Dependencies for the target vtkIOXMLParserPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkIOCorePythonD;general;vtkIOXMLParser; //Dependencies for the target vtkIOXMLParserPython_LIB_DEPENDS:STATIC=general;vtkIOXMLParserPythonD; //Dependencies for the target vtkIOXMLParser_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkIOCore;general;vtkexpat;general;vtksys; //Dependencies for the target vtkIOXMLPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLParserPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOXML; //Dependencies for the target vtkIOXMLPython_LIB_DEPENDS:STATIC=general;vtkIOXMLPythonD; //Dependencies for the target vtkIOXML_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkIOXMLParser;general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtksys; //Dependencies for the target vtkIOXdmf2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXdmf2; //Dependencies for the target vtkIOXdmf2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkIOLegacyPythonD;general;vtkFiltersExtractionPythonD;general;vtkIOXMLParserPythonD;general;vtkIOXdmf2; //Dependencies for the target vtkIOXdmf2Python_LIB_DEPENDS:STATIC=general;vtkIOXdmf2PythonD; //Dependencies for the target vtkIOXdmf2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkIOLegacy;general;vtkFiltersExtraction;general;vtkIOXMLParser;general;vtksys;general;vtkxdmf2; //Dependencies for the target vtkImagingColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingColor; //Dependencies for the target vtkImagingColorPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkImagingColor; //Dependencies for the target vtkImagingColorPython_LIB_DEPENDS:STATIC=general;vtkImagingColorPythonD; //Dependencies for the target vtkImagingColor_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem; //Dependencies for the target vtkImagingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCore; //Dependencies for the target vtkImagingCorePython_LIB_DEPENDS:STATIC=general;vtkImagingCorePythonD; //Dependencies for the target vtkImagingCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonTransforms; //Dependencies for the target vtkImagingFourierCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingFourier; //Dependencies for the target vtkImagingFourierPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingFourier; //Dependencies for the target vtkImagingFourierPython_LIB_DEPENDS:STATIC=general;vtkImagingFourierPythonD; //Dependencies for the target vtkImagingFourier_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonDataModel;general;vtksys; //Dependencies for the target vtkImagingGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingGeneral; //Dependencies for the target vtkImagingGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingSourcesPythonD;general;vtkImagingGeneral; //Dependencies for the target vtkImagingGeneralPython_LIB_DEPENDS:STATIC=general;vtkImagingGeneralPythonD; //Dependencies for the target vtkImagingGeneral_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingSources; //Dependencies for the target vtkImagingHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingHybrid; //Dependencies for the target vtkImagingHybridPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonDataModelPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkImagingHybrid; //Dependencies for the target vtkImagingHybridPython_LIB_DEPENDS:STATIC=general;vtkImagingHybridPythonD; //Dependencies for the target vtkImagingHybrid_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkCommonDataModel;general;vtkIOImage;general;vtkImagingCore; //Dependencies for the target vtkImagingMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMath; //Dependencies for the target vtkImagingMathPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingMath; //Dependencies for the target vtkImagingMathPython_LIB_DEPENDS:STATIC=general;vtkImagingMathPythonD; //Dependencies for the target vtkImagingMath_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel; //Dependencies for the target vtkImagingMorphologicalCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkImagingMorphological; //Dependencies for the target vtkImagingMorphologicalPython_LIB_DEPENDS:STATIC=general;vtkImagingMorphologicalPythonD; //Dependencies for the target vtkImagingMorphological_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkImagingGeneral;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingSources; //Dependencies for the target vtkImagingSourcesPython_LIB_DEPENDS:STATIC=general;vtkImagingSourcesPythonD; //Dependencies for the target vtkImagingSources_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore; //Dependencies for the target vtkInfovisCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInfovisCore; //Dependencies for the target vtkInfovisCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkInfovisCore; //Dependencies for the target vtkInfovisCorePython_LIB_DEPENDS:STATIC=general;vtkInfovisCorePythonD; //Dependencies for the target vtkInfovisCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkFiltersGeneral; //Dependencies for the target vtkInteractionImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionImage; //Dependencies for the target vtkInteractionImagePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkInteractionImage; //Dependencies for the target vtkInteractionImagePython_LIB_DEPENDS:STATIC=general;vtkInteractionImagePythonD; //Dependencies for the target vtkInteractionImage_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkImagingColor;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionStyleCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkInteractionStyle; //Dependencies for the target vtkInteractionStylePython_LIB_DEPENDS:STATIC=general;vtkInteractionStylePythonD; //Dependencies for the target vtkInteractionStyle_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersExtraction;general;vtkFiltersSources; //Dependencies for the target vtkInteractionWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkImagingColorPythonD;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingVolumePythonD;general;vtkInteractionWidgets; //Dependencies for the target vtkInteractionWidgetsPython_LIB_DEPENDS:STATIC=general;vtkInteractionWidgetsPythonD; //Dependencies for the target vtkInteractionWidgets_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkRenderingCore;general;vtkCommonComputationalGeometry;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersHybrid;general;vtkFiltersModeling;general;vtkImagingColor;general;vtkImagingCore;general;vtkImagingGeneral;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingVolume; //Dependencies for the target vtkNetCDF_LIB_DEPENDS:STATIC=general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so;general;/apps/all/Szip/2.1-intel-2017a/lib/libsz.so;general;/apps/all/zlib/1.2.11/lib/libz.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;m; //Dependencies for the target vtkPVAnimationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVAnimation; //Dependencies for the target vtkPVAnimationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkIOMoviePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkPVAnimation; //Dependencies for the target vtkPVAnimationPython_LIB_DEPENDS:STATIC=general;vtkPVAnimationPythonD; //Dependencies for the target vtkPVAnimation_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtkPVVTKExtensionsDefault;general;vtksys;general;vtkIOMovie;general;vtkPVServerManagerDefault; //Dependencies for the target vtkPVCatalystCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalyst; //Dependencies for the target vtkPVCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerApplicationPythonD;general;vtkPVCatalyst; //Dependencies for the target vtkPVCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystPythonD; //Dependencies for the target vtkPVCatalyst_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtksys;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkPVCinemaReaderCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCinemaReader; //Dependencies for the target vtkPVCinemaReaderPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkPVServerManagerCorePythonD;general;vtkRenderingCorePythonD;general;vtkPVAnimationPythonD;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerManagerRenderingPythonD;general;vtkPythonInterpreterPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkPVCinemaReader; //Dependencies for the target vtkPVCinemaReaderPython_LIB_DEPENDS:STATIC=general;vtkPVCinemaReaderPythonD; //Dependencies for the target vtkPVCinemaReader_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkPVServerManagerCore;general;vtkRenderingCore;general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;vtkPVAnimation;general;vtkPVClientServerCoreRendering;general;vtkPVServerManagerRendering;general;vtkPythonInterpreter;general;vtkRenderingOpenGL2;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore; //Dependencies for the target vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkIOLegacyPythonD;general;vtkPVCommonPythonD;general;vtkPVCommonPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkPythonInterpreterPythonD;general;vtkPVClientServerCoreCore; //Dependencies for the target vtkPVClientServerCoreCorePython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCorePythonD; //Dependencies for the target vtkPVClientServerCoreCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkFiltersProgrammable;general;vtkIOLegacy;general;vtkPVCommon;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkPythonInterpreter;general;vtksys;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkPVClientServerCoreDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreDefault; //Dependencies for the target vtkPVClientServerCoreDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkIOInfovisPythonD;general;vtkPVClientServerCoreDefault; //Dependencies for the target vtkPVClientServerCoreDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefaultPythonD; //Dependencies for the target vtkPVClientServerCoreDefault_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVVTKExtensionsDefault;general;vtksys;general;vtkIOInfovis; //Dependencies for the target vtkPVClientServerCoreRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreRendering; //Dependencies for the target vtkPVClientServerCoreRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkPVClientServerCoreCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingOSPRayPythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;general;vtkPVClientServerCoreRendering; //Dependencies for the target vtkPVClientServerCoreRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRenderingPythonD; //Dependencies for the target vtkPVClientServerCoreRendering_LIB_DEPENDS:STATIC=general;vtkDomainsChemistry;general;vtkFiltersAMR;general;vtkPVClientServerCoreCore;general;vtkPVVTKExtensionsDefault;general;vtkPVVTKExtensionsRendering;general;vtkRenderingLabel;general;vtkRenderingOSPRay;general;vtkRenderingVolumeOpenGL2;general;vtkViewsContext2D;general;vtkViewsCore;general;vtksys;general;vtkzlib;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkPVCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCommon; //Dependencies for the target vtkPVCommonPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOXMLParserPythonD;general;vtkPVCommon; //Dependencies for the target vtkPVCommonPython_LIB_DEPENDS:STATIC=general;vtkPVCommonPythonD; //Dependencies for the target vtkPVCommon_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;general;vtkIOXMLParser;general;vtksys; //Dependencies for the target vtkPVPythonCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;general;vtkPythonInterpreterPythonD;general;vtkPVPythonCatalyst; //Dependencies for the target vtkPVPythonCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVPythonCatalystPythonD; //Dependencies for the target vtkPVPythonCatalyst_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;general;vtkPythonInterpreter;general;vtkUtilitiesPythonInitializer; //Dependencies for the target vtkPVServerImplementationCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationCore; //Dependencies for the target vtkPVServerImplementationCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreCorePythonD;general;vtkPVServerImplementationCore; //Dependencies for the target vtkPVServerImplementationCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCorePythonD; //Dependencies for the target vtkPVServerImplementationCore_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;protobuf;general;vtksys; //Dependencies for the target vtkPVServerImplementationRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationRendering; //Dependencies for the target vtkPVServerImplementationRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPVServerImplementationRendering; //Dependencies for the target vtkPVServerImplementationRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRenderingPythonD; //Dependencies for the target vtkPVServerImplementationRendering_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVServerImplementationCore; //Dependencies for the target vtkPVServerManagerApplicationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerApplication; //Dependencies for the target vtkPVServerManagerApplicationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerApplication; //Dependencies for the target vtkPVServerManagerApplicationPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplicationPythonD; //Dependencies for the target vtkPVServerManagerApplication_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtksys;general;vtkCommonCoreCS;general;vtkCommonMathCS;general;vtkCommonMiscCS;general;vtkCommonSystemCS;general;vtkCommonTransformsCS;general;vtkCommonDataModelCS;general;vtkCommonExecutionModelCS;general;vtkFiltersCoreCS;general;vtkCommonComputationalGeometryCS;general;vtkFiltersGeneralCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkFiltersSourcesCS;general;vtkCommonColorCS;general;vtkFiltersGeometryCS;general;vtkRenderingCoreCS;general;vtkInteractionStyleCS;general;vtkRenderingOpenGL2CS;general;vtkFiltersModelingCS;general;vtkIOCoreCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersParallelCS;general;vtkFiltersProgrammableCS;general;vtkPythonInterpreterCS;general;vtkIOXMLParserCS;general;vtkPVCommonCS;general;vtkIOImageCS;general;vtkPVVTKExtensionsCoreCS;general;vtkParallelMPICS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkIOMovieCS;general;vtkIOXMLCS;general;vtkInfovisCoreCS;general;vtkIOInfovisCS;general;vtkDomainsChemistryCS;general;vtkFiltersAMRCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersParallelFlowPathsCS;general;vtkFiltersParallelStatisticsCS;general;vtkIOEnSightCS;general;vtkIOImportCS;general;vtkIOMPIImageCS;general;vtkIOPLYCS;general;vtkIOGeometryCS;general;vtkIONetCDFCS;general;vtkIOParallelCS;general;vtkIOExodusCS;general;vtkIOParallelExodusCS;general;vtkIOParallelXMLCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkImagingColorCS;general;vtkImagingGeneralCS;general;vtkImagingHybridCS;general;vtkRenderingAnnotationCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkFiltersGenericCS;general;vtkFiltersHyperTreeCS;general;vtkFiltersParallelMPICS;general;vtkRenderingGL2PSOpenGL2CS;general;vtkIOExportCS;general;vtkIOExportOpenGL2CS;general;vtkRenderingContextOpenGL2CS;general;vtkRenderingMatplotlibCS;general;vtkRenderingSceneGraphCS;general;vtkRenderingOSPRayCS;general;vtkRenderingParallelCS;general;vtkImagingMathCS;general;vtkRenderingVolumeOpenGL2CS;general;vtkRenderingVolumeAMRCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingLabelCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkDomainsChemistryOpenGL2CS;general;vtkFiltersParallelDIY2CS;general;vtkFiltersParallelGeometryCS;general;vtkFiltersImagingCS;general;vtkFiltersParallelImagingCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOMPIParallelCS;general;vtkIOLSDynaCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelNetCDFCS;general;vtkIOTRUCHASCS;general;vtkIOTecplotTableCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionImageCS;general;vtkPVCinemaReaderCS;general;vtkPVVTKExtensionsCGNSReaderCS;general;vtkPVVTKExtensionsH5PartReaderCS;general;vtkFiltersPointsCS;general;vtkPVVTKExtensionsPointsCS;general;vtkParallelMPI4PyCS;general;vtkRenderingLICOpenGL2CS;general;vtkRenderingLODCS;general;vtkRenderingParallelLICCS;general;vtkWebGLExporterCS;general;vtkWebCoreCS;general;vtkParaViewWebCoreCS;general;vtkPVServerManagerCore; //Dependencies for the target vtkPVServerManagerCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerCore; //Dependencies for the target vtkPVServerManagerCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPVServerImplementationCorePythonD;general;vtkPythonInterpreterPythonD;general;vtkPVServerManagerCore; //Dependencies for the target vtkPVServerManagerCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCorePythonD; //Dependencies for the target vtkPVServerManagerCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkPVServerImplementationCore;general;vtkjsoncpp;general;vtksys;general;vtkpugixml;general;vtkPythonInterpreter; //Dependencies for the target vtkPVServerManagerDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerDefault; //Dependencies for the target vtkPVServerManagerDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerRenderingPythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkTestingRenderingPythonD;general;vtkPVClientServerCoreDefaultPythonD;general;vtkPVServerManagerDefault; //Dependencies for the target vtkPVServerManagerDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefaultPythonD; //Dependencies for the target vtkPVServerManagerDefault_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRendering;general;vtksys;general;vtkpugixml;general;vtkRenderingVolumeOpenGL2;general;vtkTestingRendering;general;vtkPVClientServerCoreDefault; //Dependencies for the target vtkPVServerManagerRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerRendering; //Dependencies for the target vtkPVServerManagerRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerImplementationRenderingPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerCorePythonD;general;vtkCommonColorPythonD;general;vtkPVServerManagerRendering; //Dependencies for the target vtkPVServerManagerRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRenderingPythonD; //Dependencies for the target vtkPVServerManagerRendering_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRendering;general;vtkPVServerManagerCore;general;vtkPVServerManagerCore;general;vtkjsoncpp;general;vtkCommonColor;general;vtksys; //Dependencies for the target vtkPVVTKExtensionsCGNSReaderCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCGNSReader; //Dependencies for the target vtkPVVTKExtensionsCGNSReaderPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkPVVTKExtensionsCGNSReader; //Dependencies for the target vtkPVVTKExtensionsCGNSReaderPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCGNSReaderPythonD; //Dependencies for the target vtkPVVTKExtensionsCGNSReader_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkPVVTKExtensionsCore;general;vtkParallelCore;general;vtkcgns;general;vtksys;general;vtkParallelCore;general;vtkFiltersExtraction; //Dependencies for the target vtkPVVTKExtensionsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCore; //Dependencies for the target vtkPVVTKExtensionsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkIOImagePythonD;general;vtkPVCommonPythonD;general;vtkParallelCorePythonD;general;vtkPVVTKExtensionsCore; //Dependencies for the target vtkPVVTKExtensionsCorePython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCorePythonD; //Dependencies for the target vtkPVVTKExtensionsCore_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkFiltersSources;general;vtkIOImage;general;vtkPVCommon;general;vtkParallelCore;general;vtksys; //Dependencies for the target vtkPVVTKExtensionsDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsDefault; //Dependencies for the target vtkPVVTKExtensionsDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelFlowPathsPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkIOEnSightPythonD;general;vtkIOImportPythonD;general;vtkIOMPIImagePythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelXMLPythonD;general;vtkImagingFourierPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkIOInfovisPythonD;general;vtkChartsCorePythonD;general;vtkIOPLYPythonD;general;vtkPVVTKExtensionsDefault; //Dependencies for the target vtkPVVTKExtensionsDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefaultPythonD; //Dependencies for the target vtkPVVTKExtensionsDefault_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersParallelFlowPaths;general;vtkFiltersParallelStatistics;general;vtkIOEnSight;general;vtkIOImport;general;vtkIOMPIImage;general;vtkIOParallel;general;vtkIOParallelExodus;general;vtkIOParallelXML;general;vtkImagingFourier;general;vtkImagingSources;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkPVVTKExtensionsRendering;general;vtkIOInfovis;general;vtknetcdfcpp;general;vtksys;general;vtkChartsCore;general;vtkIOPLY;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkPVVTKExtensionsH5PartReaderCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsH5PartReader; //Dependencies for the target vtkPVVTKExtensionsH5PartReaderPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelCorePythonD;general;vtkPVVTKExtensionsH5PartReader; //Dependencies for the target vtkPVVTKExtensionsH5PartReaderPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsH5PartReaderPythonD; //Dependencies for the target vtkPVVTKExtensionsH5PartReader_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkPVVTKExtensionsCore;general;vtkParallelCore;general;vtkcgns;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so;general;/apps/all/Szip/2.1-intel-2017a/lib/libsz.so;general;/apps/all/zlib/1.2.11/lib/libz.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;vtksys;general;vtkParallelCore;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkPVVTKExtensionsPointsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsPoints; //Dependencies for the target vtkPVVTKExtensionsPointsPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkFiltersPointsPythonD;general;vtkFiltersCorePythonD;general;vtkPVVTKExtensionsPoints; //Dependencies for the target vtkPVVTKExtensionsPointsPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsPointsPythonD; //Dependencies for the target vtkPVVTKExtensionsPoints_LIB_DEPENDS:STATIC=general;vtkFiltersPoints;general;vtkFiltersCore; //Dependencies for the target vtkPVVTKExtensionsRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsRendering; //Dependencies for the target vtkPVVTKExtensionsRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkIOExportPythonD;general;vtkIOExportOpenGL2PythonD;general;vtkIOImagePythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContextOpenGL2PythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingMatplotlibPythonD;general;vtkRenderingOSPRayPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingVolumeAMRPythonD;general;vtkCommonColorPythonD;general;vtkPVVTKExtensionsRendering; //Dependencies for the target vtkPVVTKExtensionsRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRenderingPythonD; //Dependencies for the target vtkPVVTKExtensionsRendering_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersGeneric;general;vtkFiltersHyperTree;general;vtkFiltersParallel;general;vtkFiltersParallelMPI;general;vtkGUISupportQt;general;vtkIOExport;general;vtkIOExportOpenGL2;general;vtkIOImage;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkRenderingAnnotation;general;vtkRenderingContextOpenGL2;general;vtkRenderingFreeType;general;vtkRenderingMatplotlib;general;vtkRenderingOSPRay;general;vtkRenderingOpenGL2;general;vtkRenderingParallel;general;vtkRenderingVolumeAMR;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkCommonColor;general;vtkglew;general;vtkzlib;general;vtklz4;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkParaViewDocumentation_LIB_DEPENDS:STATIC=general;Qt5::Widgets; //Dependencies for the target vtkParaViewWebCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParaViewWebCore; //Dependencies for the target vtkParaViewWebCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPVServerManagerDefaultPythonD;general;vtkWebCorePythonD;general;vtkWebGLExporterPythonD;general;vtkParaViewWebCore; //Dependencies for the target vtkParaViewWebCorePython_LIB_DEPENDS:STATIC=general;vtkParaViewWebCorePythonD; //Dependencies for the target vtkParaViewWebCore_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefault;general;vtkWebCore;general;vtkWebGLExporter; //Dependencies for the target vtkParallelCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelCore; //Dependencies for the target vtkParallelCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOLegacyPythonD;general;vtkParallelCore; //Dependencies for the target vtkParallelCorePython_LIB_DEPENDS:STATIC=general;vtkParallelCorePythonD; //Dependencies for the target vtkParallelCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkIOLegacy;general;vtksys; //Dependencies for the target vtkParallelMPI4PyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI4Py; //Dependencies for the target vtkParallelMPI4PyPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkParallelMPIPythonD;general;vtkParallelMPIPythonD;general;vtkParallelMPI4Py; //Dependencies for the target vtkParallelMPI4PyPython_LIB_DEPENDS:STATIC=general;vtkParallelMPI4PyPythonD; //Dependencies for the target vtkParallelMPI4Py_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelMPI;general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;vtkParallelMPI;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkParallelCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelMPI; //Dependencies for the target vtkParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkParallelMPIPythonD; //Dependencies for the target vtkParallelMPI_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelCore;general;vtkCommonDataModel;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkPythonInterpreterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPythonInterpreter; //Dependencies for the target vtkPythonInterpreterPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPythonInterpreter; //Dependencies for the target vtkPythonInterpreterPython_LIB_DEPENDS:STATIC=general;vtkPythonInterpreterPythonD; //Dependencies for the target vtkPythonInterpreter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;vtksys; //Dependencies for the target vtkRenderingAnnotationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingAnnotation; //Dependencies for the target vtkRenderingAnnotationPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingAnnotation; //Dependencies for the target vtkRenderingAnnotationPython_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotationPythonD; //Dependencies for the target vtkRenderingAnnotation_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkImagingColor;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContext2D; //Dependencies for the target vtkRenderingContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingContext2D; //Dependencies for the target vtkRenderingContext2DPython_LIB_DEPENDS:STATIC=general;vtkRenderingContext2DPythonD; //Dependencies for the target vtkRenderingContext2D_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingContextOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContextOpenGL2; //Dependencies for the target vtkRenderingContextOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkRenderingContextOpenGL2; //Dependencies for the target vtkRenderingContextOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL2PythonD; //Dependencies for the target vtkRenderingContextOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingContext2D;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkImagingCore;general;vtkglew;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkRenderingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingCore; //Dependencies for the target vtkRenderingCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;general;vtkCommonColorPythonD;general;vtkCommonComputationalGeometryPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCore; //Dependencies for the target vtkRenderingCorePython_LIB_DEPENDS:STATIC=general;vtkRenderingCorePythonD; //Dependencies for the target vtkRenderingCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkCommonColor;general;vtkCommonComputationalGeometry;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkFiltersSources;general;vtksys; //Dependencies for the target vtkRenderingFreeTypeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingFreeTypePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingFreeType; //Dependencies for the target vtkRenderingFreeTypePython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypePythonD; //Dependencies for the target vtkRenderingFreeType_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkfreetype;general;vtkCommonDataModel;general;vtkFiltersGeneral; //Dependencies for the target vtkRenderingGL2PSOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PSOpenGL2; //Dependencies for the target vtkRenderingGL2PSOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingGL2PSOpenGL2; //Dependencies for the target vtkRenderingGL2PSOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PSOpenGL2PythonD; //Dependencies for the target vtkRenderingGL2PSOpenGL2_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2;general;vtkRenderingOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkgl2ps;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkRenderingLICOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLICOpenGL2; //Dependencies for the target vtkRenderingLICOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingCorePythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingLICOpenGL2; //Dependencies for the target vtkRenderingLICOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingLICOpenGL2PythonD; //Dependencies for the target vtkRenderingLICOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingOpenGL2;general;vtkCommonMath;general;vtkCommonSystem;general;vtkIOCore;general;vtkIOLegacy;general;vtkIOXML;general;vtkImagingCore;general;vtkImagingSources;general;vtkRenderingCore;general;vtkglew;general;vtksys;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD; //Dependencies for the target vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersModelingPythonD;general;vtkRenderingLOD; //Dependencies for the target vtkRenderingLODPython_LIB_DEPENDS:STATIC=general;vtkRenderingLODPythonD; //Dependencies for the target vtkRenderingLOD_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersCore;general;vtkFiltersModeling; //Dependencies for the target vtkRenderingLabelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingLabel; //Dependencies for the target vtkRenderingLabelPython_LIB_DEPENDS:STATIC=general;vtkRenderingLabelPythonD; //Dependencies for the target vtkRenderingLabel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersGeneral; //Dependencies for the target vtkRenderingMatplotlibCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkPythonInterpreterPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingMatplotlib; //Dependencies for the target vtkRenderingMatplotlibPython_LIB_DEPENDS:STATIC=general;vtkRenderingMatplotlibPythonD; //Dependencies for the target vtkRenderingMatplotlib_LIB_DEPENDS:STATIC=general;vtkPythonInterpreter;general;vtkRenderingFreeType;general;vtkRenderingFreeType;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonTransforms;general;vtkImagingCore;general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;vtkRenderingCore;general;vtkWrappingPythonCore; //Dependencies for the target vtkRenderingOSPRayCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOSPRay; //Dependencies for the target vtkRenderingOSPRayPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingSceneGraphPythonD;general;vtkRenderingVolumePythonD;general;vtkCommonCorePythonD;general;vtkIOImagePythonD;general;vtkIOLegacyPythonD;general;vtkRenderingOSPRay; //Dependencies for the target vtkRenderingOSPRayPython_LIB_DEPENDS:STATIC=general;vtkRenderingOSPRayPythonD; //Dependencies for the target vtkRenderingOSPRay_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkRenderingSceneGraph;general;vtkRenderingVolume;general;vtkCommonCore;general;vtkIOImage;general;vtkIOLegacy;optimized;/apps/all/tbb/2017.6.196/tbb/lib/libtbb.so.2;optimized;/apps/all/tbb/2017.6.196/tbb/lib/libtbbmalloc.so.2;debug;/apps/all/tbb/2017.6.196/tbb/lib/libtbb_debug.so.2;debug;/apps/all/tbb/2017.6.196/tbb/lib/libtbbmalloc_debug.so.2;general;/apps/all/Embree/2.16.2-intel-2017a/lib64/cmake/embree-2.16.2/../../../lib64/libembree.so;general;/apps/all/OSPRay/1.3.0-intel-2017a/lib64/libospray.so;general;/apps/all/OSPRay/1.3.0-intel-2017a/lib64/libospray_common.so;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkRenderingOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOpenGL2; //Dependencies for the target vtkRenderingOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkRenderingOpenGL2; //Dependencies for the target vtkRenderingOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL2PythonD; //Dependencies for the target vtkRenderingOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkRenderingCore;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkglew;general;vtksys;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkRenderingParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallel; //Dependencies for the target vtkRenderingParallelLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallelLIC; //Dependencies for the target vtkRenderingParallelLICPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkParallelMPIPythonD;general;vtkRenderingLICOpenGL2PythonD;general;vtkRenderingOpenGL2PythonD;general;vtkIOLegacyPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingParallelLIC; //Dependencies for the target vtkRenderingParallelLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLICPythonD; //Dependencies for the target vtkRenderingParallelLIC_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkParallelMPI;general;vtkRenderingLICOpenGL2;general;vtkRenderingOpenGL2;general;vtkIOLegacy;general;vtkParallelCore;general;vtkRenderingCore;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkRenderingParallel; //Dependencies for the target vtkRenderingParallelPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelPythonD; //Dependencies for the target vtkRenderingParallel_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkglew;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersParallel;general;vtkIOImage;general;vtkImagingCore;general;vtkParallelCore;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkRenderingSceneGraphCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingSceneGraph; //Dependencies for the target vtkRenderingSceneGraphPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingSceneGraph; //Dependencies for the target vtkRenderingSceneGraphPython_LIB_DEPENDS:STATIC=general;vtkRenderingSceneGraphPythonD; //Dependencies for the target vtkRenderingSceneGraph_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkRenderingCore; //Dependencies for the target vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGL2PythonD;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersAMRPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingVolumeAMR; //Dependencies for the target vtkRenderingVolumeAMRPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMRPythonD; //Dependencies for the target vtkRenderingVolumeAMR_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingVolume;general;vtkRenderingVolumeOpenGL2;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersAMR;general;vtkRenderingCore; //Dependencies for the target vtkRenderingVolumeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolume; //Dependencies for the target vtkRenderingVolumeOpenGL2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeOpenGL2; //Dependencies for the target vtkRenderingVolumeOpenGL2PythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkImagingCorePythonD;general;vtkImagingMathPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingOpenGL2PythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumePythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingVolumeOpenGL2; //Dependencies for the target vtkRenderingVolumeOpenGL2Python_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGL2PythonD; //Dependencies for the target vtkRenderingVolumeOpenGL2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkImagingCore;general;vtkImagingMath;general;vtkRenderingCore;general;vtkRenderingOpenGL2;general;vtkRenderingVolume;general;vtkRenderingVolume;general;vtkglew;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtksys;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so; //Dependencies for the target vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOXMLPythonD;general;vtkImagingCorePythonD;general;vtkRenderingVolume; //Dependencies for the target vtkRenderingVolumePython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumePythonD; //Dependencies for the target vtkRenderingVolume_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOXML;general;vtkImagingCore; //Dependencies for the target vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering; //Dependencies for the target vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkTestingRendering; //Dependencies for the target vtkTestingRenderingPython_LIB_DEPENDS:STATIC=general;vtkTestingRenderingPythonD; //Dependencies for the target vtkTestingRendering_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkIOImage;general;vtkImagingCore;general;vtksys; //Dependencies for the target vtkUtilitiesPythonInitializer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkWrappingPythonCore;general;vtkWrappingPythonCore;general;vtkCommonCore; //Dependencies for the target vtkViewsContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsContext2D; //Dependencies for the target vtkViewsContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkRenderingCorePythonD;general;vtkViewsCorePythonD;general;vtkRenderingContext2DPythonD;general;vtkViewsContext2D; //Dependencies for the target vtkViewsContext2DPython_LIB_DEPENDS:STATIC=general;vtkViewsContext2DPythonD; //Dependencies for the target vtkViewsContext2D_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkViewsCore;general;vtkRenderingContext2D; //Dependencies for the target vtkViewsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsCore; //Dependencies for the target vtkViewsCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkInteractionWidgetsPythonD;general;vtkCommonDataModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkRenderingCorePythonD;general;vtkViewsCore; //Dependencies for the target vtkViewsCorePython_LIB_DEPENDS:STATIC=general;vtkViewsCorePythonD; //Dependencies for the target vtkViewsCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonExecutionModel;general;vtkInteractionWidgets;general;vtkCommonDataModel;general;vtkFiltersGeneral;general;vtkRenderingCore; //Dependencies for the target vtkWebCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebCore; //Dependencies for the target vtkWebCorePythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGeometryPythonD;general;vtkIOCorePythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;general;vtkWebGLExporterPythonD;general;vtkWebCore; //Dependencies for the target vtkWebCorePython_LIB_DEPENDS:STATIC=general;vtkWebCorePythonD; //Dependencies for the target vtkWebCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersGeneral;general;vtkFiltersGeometry;general;vtkIOCore;general;vtkIOImage;general;vtkParallelCore;general;/apps/all/Python/2.7.13/lib/libpython2.7.so;general;vtkRenderingCore;general;vtkWebGLExporter;general;vtksys; //Dependencies for the target vtkWebGLExporterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterPythonD_LIB_DEPENDS:STATIC=general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOExportPythonD;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkIOCorePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingCorePythonD;general;vtkWebGLExporter; //Dependencies for the target vtkWebGLExporterPython_LIB_DEPENDS:STATIC=general;vtkWebGLExporterPythonD; //Dependencies for the target vtkWebGLExporter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOExport;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkFiltersCore;general;vtkFiltersGeometry;general;vtkIOCore;general;vtkInteractionWidgets;general;vtkRenderingAnnotation;general;vtkRenderingCore;general;vtksys; //Dependencies for the target vtkWrappingPythonCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys; //Dependencies for target vtkWrappingTools_LIB_DEPENDS:STATIC= //Dependencies for target vtkalglib_LIB_DEPENDS:STATIC= //Dependencies for the target vtkcgns_LIB_DEPENDS:STATIC=general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so;general;/apps/all/Szip/2.1-intel-2017a/lib/libsz.so;general;/apps/all/zlib/1.2.11/lib/libz.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for the target vtkexoIIc_LIB_DEPENDS:STATIC=general;vtkNetCDF; //Dependencies for target vtkexpat_LIB_DEPENDS:STATIC= //Dependencies for the target vtkfreetype_LIB_DEPENDS:STATIC=general;vtkzlib; //Dependencies for the target vtkgl2ps_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkpng;general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so;general;m; //Dependencies for the target vtkglew_LIB_DEPENDS:STATIC=general;/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so;general;dl; //Dependencies for target vtkjpeg_LIB_DEPENDS:STATIC= //Dependencies for target vtkjsoncpp_LIB_DEPENDS:STATIC= //Value Computed by CMake vtklibharu_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/libharu/vtklibharu //Dependencies for the target vtklibharu_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkpng;general;m; //Value Computed by CMake vtklibharu_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/libharu/vtklibharu //Value Computed by CMake vtklibxml2_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/libxml2/vtklibxml2 //Dependencies for the target vtklibxml2_LIB_DEPENDS:STATIC=general;vtkzlib;general;dl;general;dl;general;m; //Value Computed by CMake vtklibxml2_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/libxml2/vtklibxml2 //Dependencies for target vtklz4_LIB_DEPENDS:STATIC= //Value Computed by CMake vtkmetaio_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/Utilities/MetaIO/vtkmetaio //Dependencies for the target vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib; //Value Computed by CMake vtkmetaio_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Utilities/MetaIO/vtkmetaio //Value Computed by CMake vtknetcdfcpp_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/netcdfcpp/vtknetcdfcpp //Dependencies for the target vtknetcdfcpp_LIB_DEPENDS:STATIC=general;vtkNetCDF; //Value Computed by CMake vtknetcdfcpp_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/netcdfcpp/vtknetcdfcpp //Dependencies for target vtkoggtheora_LIB_DEPENDS:STATIC= //Dependencies for the target vtkpng_LIB_DEPENDS:STATIC=general;vtkzlib;general;-lm; //Dependencies for target vtkpugixml_LIB_DEPENDS:STATIC= //Value Computed by CMake vtksys_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtksys_LIB_DEPENDS:STATIC=general;dl;general;dl; //Value Computed by CMake vtksys_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Utilities/KWSys/vtksys //Dependencies for the target vtktiff_LIB_DEPENDS:STATIC=general;/usr/lib64/libm.so;general;vtkzlib;general;vtkjpeg; //Dependencies for the target vtkxdmf2_LIB_DEPENDS:STATIC=general;vtklibxml2;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so;general;/apps/all/Szip/2.1-intel-2017a/lib/libsz.so;general;/apps/all/zlib/1.2.11/lib/libz.so;general;/usr/lib64/libdl.so;general;/usr/lib64/libm.so;general;/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;general;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;general;/usr/lib64/libdl.so;general;/usr/lib64/librt.so;general;/usr/lib64/libpthread.so; //Dependencies for target vtkzlib_LIB_DEPENDS:STATIC= //Value Computed by CMake xdmf2_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake xdmf2_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/xdmf2/vtkxdmf2 //Value Computed by CMake zlib_BINARY_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/ThirdParty/zlib/vtkzlib //Value Computed by CMake zlib_SOURCE_DIR:STATIC=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/ThirdParty/zlib/vtkzlib ######################## # INTERNAL cache entries ######################## ALGLIB_SHARED_LIB:INTERNAL=ON //Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN ARCH_TO_BUILD:INTERNAL=Linux //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //STRINGS property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Debug;Release;MinSizeRel;RelWithDebInfo //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=8 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=1 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/apps/all/CMake/3.8.1/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/apps/all/CMake/3.8.1/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/apps/all/CMake/3.8.1/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/apps/all/CMake/3.8.1/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of external makefile project generator. CMAKE_EXTRA_GENERATOR:INTERNAL= //ADVANCED property for variable: CMAKE_Fortran_COMPILER CMAKE_Fortran_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS CMAKE_Fortran_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_DEBUG CMAKE_Fortran_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_MINSIZEREL CMAKE_Fortran_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELEASE CMAKE_Fortran_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_Fortran_FLAGS_RELWITHDEBINFO CMAKE_Fortran_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator platform. CMAKE_GENERATOR_PLATFORM:INTERNAL= //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Have symbol pthread_create CMAKE_HAVE_LIBC_CREATE:INTERNAL=1 //Have include pthread.h CMAKE_HAVE_PTHREAD_H:INTERNAL=1 //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0 //ADVANCED property for variable: CMAKE_INSTALL_BINDIR CMAKE_INSTALL_BINDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DATADIR CMAKE_INSTALL_DATADIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DATAROOTDIR CMAKE_INSTALL_DATAROOTDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_DOCDIR CMAKE_INSTALL_DOCDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_INCLUDEDIR CMAKE_INSTALL_INCLUDEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_INFODIR CMAKE_INSTALL_INFODIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LIBDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LIBEXECDIR CMAKE_INSTALL_LIBEXECDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LOCALEDIR CMAKE_INSTALL_LOCALEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_LOCALSTATEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_MANDIR CMAKE_INSTALL_MANDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_OLDINCLUDEDIR CMAKE_INSTALL_OLDINCLUDEDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_SBINDIR CMAKE_INSTALL_SBINDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_INSTALL_SHAREDSTATEDIR CMAKE_INSTALL_SHAREDSTATEDIR-ADVANCED:INTERNAL=1 //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0 //ADVANCED property for variable: CMAKE_INSTALL_SYSCONFDIR CMAKE_INSTALL_SYSCONFDIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //number of local generators CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=262 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //Platform information initialized CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Test Support for 64 bit file systems CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/apps/all/CMake/3.8.1/share/cmake-3.8 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(unsigned short) CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=2 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_THREAD_LIBS CMAKE_THREAD_LIBS-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/bin/uname //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //Result of TEST_BIG_ENDIAN CMAKE_WORDS_BIGENDIAN:INTERNAL=0 //Compiler support for a deprecated attribute COMPILER_HAS_DEPRECATED:INTERNAL=1 //Test COMPILER_HAS_DEPRECATED_ATTR COMPILER_HAS_DEPRECATED_ATTR:INTERNAL=1 //Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY COMPILER_HAS_HIDDEN_INLINE_VISIBILITY:INTERNAL=1 //Test COMPILER_HAS_HIDDEN_VISIBILITY COMPILER_HAS_HIDDEN_VISIBILITY:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_DEB CPACK_BINARY_DEB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_IFW CPACK_BINARY_IFW-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_NSIS CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_RPM CPACK_BINARY_RPM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_STGZ CPACK_BINARY_STGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TBZ2 CPACK_BINARY_TBZ2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TGZ CPACK_BINARY_TGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TXZ CPACK_BINARY_TXZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_BINARY_TZ CPACK_BINARY_TZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_RPM CPACK_SOURCE_RPM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TBZ2 CPACK_SOURCE_TBZ2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TGZ CPACK_SOURCE_TGZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TXZ CPACK_SOURCE_TXZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_TZ CPACK_SOURCE_TZ-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CPACK_SOURCE_ZIP CPACK_SOURCE_ZIP-ADVANCED:INTERNAL=1 //Test C_HAS_inline C_HAS_inline:INTERNAL=1 //ADVANCED property for variable: EXECINFO_LIB EXECINFO_LIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: EXECUTABLE_OUTPUT_PATH EXECUTABLE_OUTPUT_PATH-ADVANCED:INTERNAL=1 EXECUTABLE_OUTPUT_PATH:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/ThirdParty/protobuf/vtkprotobuf/bin //ADVANCED property for variable: EXODUSII_DISABLE_COMPILER_WARNINGS EXODUSII_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //Have include malloc.h EX_HAVE_MALLOC_H:INTERNAL=1 //ADVANCED property for variable: ExternalData_URL_TEMPLATES ExternalData_URL_TEMPLATES-ADVANCED:INTERNAL=1 //Details about finding Git FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/usr/bin/git][v1.7.1()] //Details about finding HDF5 FIND_PACKAGE_MESSAGE_DETAILS_HDF5:INTERNAL=[/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5.so;/apps/all/Szip/2.1-intel-2017a/lib/libsz.so;/apps/all/zlib/1.2.11/lib/libz.so;/usr/lib64/libdl.so;/usr/lib64/libm.so;/apps/all/icc/2017.1.132-GCC-6.3.0-2.27/lib/intel64/libiomp5.so;/usr/lib64/libpthread.so][/apps/all/HDF5/1.8.17-intel-2017a/lib/libhdf5_hl.so][cfound components: C HL ][v1.8.17()] //Details about finding MPI_C FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;/usr/lib64/libdl.so;/usr/lib64/librt.so;/usr/lib64/libpthread.so][/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include][v()] //Details about finding MPI_CXX FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpicxx.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;/usr/lib64/libdl.so;/usr/lib64/librt.so;/usr/lib64/libpthread.so][/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include][v()] //Details about finding MPI_Fortran FIND_PACKAGE_MESSAGE_DETAILS_MPI_Fortran:INTERNAL=[/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpifort.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/release_mt/libmpi.so;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/lib/libmpigi.a;/usr/lib64/libdl.so;/usr/lib64/librt.so;/usr/lib64/libpthread.so][/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include/gfortran/5.1.0;/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/intel64/include][v()] //Details about finding OSMesa FIND_PACKAGE_MESSAGE_DETAILS_OSMesa:INTERNAL=[/apps/all/Mesa/17.0.2-intel-2017a/lib/libOSMesa.so][/apps/all/Mesa/17.0.2-intel-2017a/include][v()] //Details about finding PythonInterp FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[/apps/all/Python/2.7.13/bin/python2][v2.7.13()] //Details about finding PythonLibs FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/apps/all/Python/2.7.13/lib/libpython2.7.so][/apps/all/Python/2.7.13/include/python2.7][v()] //Details about finding TBB FIND_PACKAGE_MESSAGE_DETAILS_TBB:INTERNAL=[/apps/all/tbb/2017.6.196/tbb/include][/apps/all/tbb/2017.6.196/tbb/lib/libtbb.so.2][/apps/all/tbb/2017.6.196/tbb/lib/libtbbmalloc.so.2][v()] //Details about finding Threads FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()] //Details about finding ospray FIND_PACKAGE_MESSAGE_DETAILS_ospray:INTERNAL=[/apps/all/OSPRay/1.3.0-intel-2017a/include;/apps/all/OSPRay/1.3.0-intel-2017a/include/ospray;/apps/all/OSPRay/1.3.0-intel-2017a/include/ospray/SDK;/apps/all/Embree/2.16.2-intel-2017a/lib64/cmake/embree-2.16.2/../../../include] //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS-ADVANCED:INTERNAL=1 HASH_MAP_CLASS:INTERNAL=unordered_map HASH_MAP_H:INTERNAL=tr1/unordered_map HASH_NAMESPACE:INTERNAL=std::tr1 HASH_SET_CLASS:INTERNAL=unordered_set HASH_SET_H:INTERNAL=tr1/unordered_set //Have symbol alloca HAVE_ALLOCA:INTERNAL=1 //Have include ;alloca.h HAVE_ALLOCA_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h HAVE_ANSIDECL_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h HAVE_ARPA_INET_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h HAVE_ARPA_NAMESER_H:INTERNAL=1 //Have include assert.h HAVE_ASSERT_H:INTERNAL=1 //Have function bcopy HAVE_BCOPY:INTERNAL=1 //Result of TRY_COMPILE HAVE_CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_CMAKE_WORDS_BIGENDIAN:INTERNAL=TRUE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h HAVE_CTYPE_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h HAVE_DIRENT_H:INTERNAL=1 //Have include dlfcn.h HAVE_DLFCN_H:INTERNAL=1 //Have library dl;dl;m HAVE_DLOPEN:INTERNAL=1 //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;dl.h HAVE_DL_H:INTERNAL= //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h HAVE_ERRNO_H:INTERNAL=1 //Have include fcntl.h HAVE_FCNTL_H:INTERNAL=1 //Have include fenv.h HAVE_FENV_H:INTERNAL=1 //Have symbol finite HAVE_FINITE:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h HAVE_FLOAT_H:INTERNAL=1 //Have function floor HAVE_FLOOR:INTERNAL=1 //Have symbol fpclass HAVE_FPCLASS:INTERNAL= //Have symbol fprintf HAVE_FPRINTF:INTERNAL=1 //Have symbol fp_class HAVE_FP_CLASS:INTERNAL= //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;fp_class.h HAVE_FP_CLASS_H:INTERNAL= //Have function fseeko HAVE_FSEEKO:INTERNAL=1 //Have symbol ftime HAVE_FTIME:INTERNAL=1 //NetCDF test HAVE_FTRUNCATE:INTERNAL=1 //Result of TRY_COMPILE HAVE_GETADDRINFO_COMPILED:INTERNAL=TRUE //Have function getopt HAVE_GETOPT:INTERNAL=1 //Have function getpagesize HAVE_GETPAGESIZE:INTERNAL=1 //Have symbol gettimeofday HAVE_GETTIMEOFDAY:INTERNAL=1 HAVE_HASH_MAP:INTERNAL=1 HAVE_HASH_SET:INTERNAL=1 //Result of TRY_COMPILE HAVE_ICET_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF_VOID_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_ICET_SIZEOF___INT64:INTERNAL=TRUE //ADVANCED property for variable: HAVE_IEEEFP HAVE_IEEEFP-ADVANCED:INTERNAL=1 //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;ieeefp.h HAVE_IEEEFP_H:INTERNAL= //Have include inttypes.h HAVE_INTTYPES_H:INTERNAL=1 //Have include io.h HAVE_IO_H:INTERNAL= //Have function isascii HAVE_ISASCII:INTERNAL=1 //Have function jbg_newlen HAVE_JBG_NEWLEN:INTERNAL= //Test HAVE_LD_VERSION_SCRIPT HAVE_LD_VERSION_SCRIPT:INTERNAL=1 //Have function lfind HAVE_LFIND:INTERNAL=1 //Have library dl; HAVE_LIBDL:INTERNAL=1 //Have include limits.h HAVE_LIMITS_H:INTERNAL=1 //Have symbol localtime HAVE_LOCALTIME:INTERNAL=1 //Have include malloc.h HAVE_MALLOC_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h HAVE_MATH_H:INTERNAL=1 //Have symbol memmove HAVE_MEMMOVE:INTERNAL=1 //Have include memory.h HAVE_MEMORY_H:INTERNAL=1 //Have function memset HAVE_MEMSET:INTERNAL=1 //Have function mmap HAVE_MMAP:INTERNAL=1 //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;nan.h HAVE_NAN_H:INTERNAL= //Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;ndir.h HAVE_NDIR_H:INTERNAL= //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h HAVE_NETDB_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h HAVE_NETINET_IN_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_NO_ICC_IDYNAMIC_NEEDED:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_OFF64_T:INTERNAL=TRUE //Have function pow HAVE_POW:INTERNAL=1 //Have symbol printf HAVE_PRINTF:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h HAVE_PTHREAD_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h HAVE_RESOLV_H:INTERNAL=1 //Have include search.h HAVE_SEARCH_H:INTERNAL=1 //Have function setmode HAVE_SETMODE:INTERNAL= //Have library dld;dl HAVE_SHLLOAD:INTERNAL= //Have symbol signal HAVE_SIGNAL:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h HAVE_SIGNAL_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_OFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_PTRDIFF_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIGNED_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_SSIZE_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UCHAR:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_CHAR_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF_VOID_P:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZEOF__BOOL:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_SIZE_OF_LONG:INTERNAL=TRUE //Test HAVE_SNPRINTF HAVE_SNPRINTF:INTERNAL=1 //Result of TRY_COMPILE HAVE_SOCKLEN_T_COMPILED:INTERNAL=TRUE //Have symbol sprintf HAVE_SPRINTF:INTERNAL=1 //Have function sqrt HAVE_SQRT:INTERNAL=1 //Have symbol sscanf HAVE_SSCANF:INTERNAL=1 //Have symbol stat HAVE_STAT:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h HAVE_STDARG_H:INTERNAL=1 //Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h;unistd.h;fcntl.h;stdio.h;string.h;stddef.h;stdint.h;inttypes.h;stdbool.h HAVE_STDBOOL_H:INTERNAL=1 //Have include stddef.h HAVE_STDDEF_H:INTERNAL=1 //Have include stdint.h HAVE_STDINT_H:INTERNAL=1 //Have include ;stdio.h HAVE_STDIO_H:INTERNAL=1 //Have include stdlib.h HAVE_STDLIB_H:INTERNAL=1 //Have function strcasecmp HAVE_STRCASECMP:INTERNAL=1 //Have function strchr HAVE_STRCHR:INTERNAL=1 //Have symbol strdup HAVE_STRDUP:INTERNAL=1 //Have symbol strerror HAVE_STRERROR:INTERNAL=1 //Have symbol strftime HAVE_STRFTIME:INTERNAL=1 //Have include strings.h HAVE_STRINGS_H:INTERNAL=1 //Have include string.h HAVE_STRING_H:INTERNAL=1 //Have symbol strndup HAVE_STRNDUP:INTERNAL=1 //Have function strrchr HAVE_STRRCHR:INTERNAL=1 //Have function strstr HAVE_STRSTR:INTERNAL=1 //Have function strtol HAVE_STRTOL:INTERNAL=1 //Have function strtoll HAVE_STRTOLL:INTERNAL=1 //Have function strtol HAVE_STRTOUL:INTERNAL=1 //Have function strtoull HAVE_STRTOULL:INTERNAL=1 //NetCDF test HAVE_ST_BLKSIZE:INTERNAL=1 //Result of TRY_COMPILE HAVE_SYS_DIR_H_COMPILED:INTERNAL=TRUE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h HAVE_SYS_MMAN_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_SYS_NDIR_H_COMPILED:INTERNAL=FALSE //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h HAVE_SYS_SELECT_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h HAVE_SYS_SOCKET_H:INTERNAL=1 //Have include sys/stat.h HAVE_SYS_STAT_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h;sys/timeb.h HAVE_SYS_TIMEB_H:INTERNAL=1 //Have include sys/time.h HAVE_SYS_TIME_H:INTERNAL=1 //Have include sys/types.h HAVE_SYS_TYPES_H:INTERNAL=1 //Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h HAVE_TIME_H:INTERNAL=1 //Have include unistd.h HAVE_UNISTD_H:INTERNAL=1 //Result of TRY_COMPILE HAVE_VA_COPY_COMPILED:INTERNAL=TRUE //Have symbol vfprintf HAVE_VFPRINTF:INTERNAL=1 //Have symbol vsnprintf HAVE_VSNPRINTF:INTERNAL=1 //Have symbol vsprintf HAVE_VSPRINTF:INTERNAL=1 //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_INT64_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_LONG_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_SHORT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_UINT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_UINT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_U_INT16_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_VTKOGGTHEORA_U_INT32_T:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_WORDS_BIGENDIAN:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_CHAR:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_DOUBLE:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_FLOAT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_INT:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_LONG:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_XDMF_SIZEOF_SHORT:INTERNAL=TRUE //Have symbol _stat HAVE__STAT:INTERNAL= //Result of TRY_COMPILE HAVE___VA_COPY_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_bigendian:INTERNAL=TRUE //Result of TRY_COMPILE HAVE_int16:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_int32:INTERNAL=FALSE //Result of TRY_COMPILE HAVE_int8:INTERNAL=FALSE //ADVANCED property for variable: HDF5_C_COMPILER_EXECUTABLE HDF5_C_COMPILER_EXECUTABLE-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE HDF5_C_COMPILER_NO_INTERROGATE:INTERNAL=FALSE //ADVANCED property for variable: HDF5_DIFF_EXECUTABLE HDF5_DIFF_EXECUTABLE-ADVANCED:INTERNAL=1 //Have symbol H5_HAVE_PARALLEL HDF5_IS_PARALLEL:INTERNAL=1 //ADVANCED property for variable: HOST_BIG_ENDIAN HOST_BIG_ENDIAN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: HOST_FILLORDER HOST_FILLORDER-ADVANCED:INTERNAL=1 ICET_INSTALL_TARGETS:INTERNAL=IceTCore;IceTMPI;IceTGL //ADVANCED property for variable: ICET_MAGIC_K ICET_MAGIC_K-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_MAX_IMAGE_SPLIT ICET_MAX_IMAGE_SPLIT-ADVANCED:INTERNAL=1 //This is set from VTK_MPIRUN_EXE. ICET_MPIRUN_EXE:INTERNAL=/apps/all/impi/2017.1.132-iccifort-2017.1.132-GCC-6.3.0-2.27/bin64/mpiexec //ADVANCED property for variable: ICET_MPI_MAX_NUMPROCS ICET_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //This is set from VTK_MPI_MAX_NUMPROCS. ICET_MPI_MAX_NUMPROCS:INTERNAL=2 //This is set from a combination of VTK_MPI_PRENUMPROC_FLAGS and // VTK_MPI_NUMPROC_FLAG ICET_MPI_NUMPROC_FLAG:INTERNAL=;-np //This is set from VTK_MPI_POSTFLAGS. ICET_MPI_POSTFLAGS:INTERNAL= //This is set from VTK_MPI_PREFLAGS. ICET_MPI_PREFLAGS:INTERNAL= //CHECK_TYPE_SIZE: sizeof(char) ICET_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) ICET_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) ICET_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) ICET_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) ICET_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) ICET_SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) ICET_SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(void*) ICET_SIZEOF_VOID_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(__int64) ICET_SIZEOF___INT64:INTERNAL=8 //ADVANCED property for variable: ICET_USE_MPE ICET_USE_MPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ICET_USE_MPI ICET_USE_MPI-ADVANCED:INTERNAL=1 //Use OffScreen rendering through EGL ICET_USE_OFFSCREEN_EGL:INTERNAL=OFF //ADVANCED property for variable: ICET_USE_OPENGL ICET_USE_OPENGL-ADVANCED:INTERNAL=1 //Use OffScreen Mesa ICET_USE_OSMESA:INTERNAL=ON //ADVANCED property for variable: INSTALL_BIN_DIR INSTALL_BIN_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_INC_DIR INSTALL_INC_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_LIB_DIR INSTALL_LIB_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_MAN_DIR INSTALL_MAN_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: INSTALL_PKGCONFIG_DIR INSTALL_PKGCONFIG_DIR-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_ATOLL_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_ATOL_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_BACKTRACE_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_CSTDIO_COMPILED:INTERNAL=TRUE //Have include cxxabi.h KWSYS_CXX_HAS_CXXABIH:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_CXXABI_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_DLADDR_COMPILED:INTERNAL=TRUE //Have include dlfcn.h KWSYS_CXX_HAS_DLFCNH:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_ENVIRON_IN_STDLIB_H_COMPILED:INTERNAL=FALSE //Have include execinfo.h KWSYS_CXX_HAS_EXECINFOH:INTERNAL=1 //Result of TRY_COMPILE KWSYS_CXX_HAS_EXT_STDIO_FILEBUF_H_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_GETLOADAVG_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_LONG_LONG_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_RLIMIT64_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_SETENV_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_UNSETENV_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_UTIMENSAT_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS_UTIMES_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_HAS__ATOI64_COMPILED:INTERNAL=FALSE //Result of TRY_COMPILE KWSYS_CXX_HAS___INT64_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_SAME_LONG_AND___INT64_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_CXX_SAME_LONG_LONG_AND___INT64_COMPILED:INTERNAL=FALSE //Result of TRY_COMPILE KWSYS_CXX_STAT_HAS_ST_MTIMESPEC_COMPILED:INTERNAL=FALSE //Result of TRY_COMPILE KWSYS_CXX_STAT_HAS_ST_MTIM_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_C_HAS_PTRDIFF_T_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_C_HAS_SSIZE_T_COMPILED:INTERNAL=TRUE //Result of TRY_RUN KWSYS_LFS_WORKS:INTERNAL=0 //Result of TRY_COMPILE KWSYS_LFS_WORKS_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE KWSYS_STL_HAS_WSTRING_COMPILED:INTERNAL=TRUE //Have include sys/types.h;ifaddrs.h KWSYS_SYS_HAS_IFADDRS_H:INTERNAL=1 //Have include dlfcn.h LIBHPDF_HAVE_DLFCN_H:INTERNAL=1 //Have include inttypes.h LIBHPDF_HAVE_INTTYPES_H:INTERNAL=1 //Have include memory.h LIBHPDF_HAVE_MEMORY_H:INTERNAL=1 //Have include stdint.h LIBHPDF_HAVE_STDINT_H:INTERNAL=1 //Have include stdlib.h LIBHPDF_HAVE_STDLIB_H:INTERNAL=1 //Have include strings.h LIBHPDF_HAVE_STRINGS_H:INTERNAL=1 //Have include string.h LIBHPDF_HAVE_STRING_H:INTERNAL=1 //Have include sys/stat.h LIBHPDF_HAVE_SYS_STAT_H:INTERNAL=1 //Have include sys/types.h LIBHPDF_HAVE_SYS_TYPES_H:INTERNAL=1 //Have include unistd.h LIBHPDF_HAVE_UNISTD_H:INTERNAL=1 //ADVANCED property for variable: LIBRARY_OUTPUT_PATH LIBRARY_OUTPUT_PATH-ADVANCED:INTERNAL=1 LIBRARY_OUTPUT_PATH:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/ThirdParty/protobuf/vtkprotobuf/bin //ADVANCED property for variable: MPIEXEC MPIEXEC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_POSTFLAGS MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_PREFLAGS MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_COMPILER MPI_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_INCLUDE_PATH MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_LIBRARIES MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_LINK_FLAGS MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_COMPILER MPI_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_COMPILE_FLAGS MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_INCLUDE_PATH MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=0 //ADVANCED property for variable: MPI_C_LIBRARIES MPI_C_LIBRARIES-ADVANCED:INTERNAL=0 //ADVANCED property for variable: MPI_C_LINK_FLAGS MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_EXTRA_LIBRARY MPI_EXTRA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_COMPILER MPI_Fortran_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_COMPILE_FLAGS MPI_Fortran_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_INCLUDE_PATH MPI_Fortran_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_LIBRARIES MPI_Fortran_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_Fortran_LINK_FLAGS MPI_Fortran_LINK_FLAGS-ADVANCED:INTERNAL=1 //Scratch variable for MPI header detection MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND //Scratch variable for MPI lib detection MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND //ADVANCED property for variable: MPI_LIBRARY MPI_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: M_LIBRARY M_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_AutobahnPython Module_AutobahnPython-ADVANCED:INTERNAL=1 //Request building AutobahnPython Module_AutobahnPython:INTERNAL=OFF //ADVANCED property for variable: Module_CinemaPython Module_CinemaPython-ADVANCED:INTERNAL=1 //Request building CinemaPython Module_CinemaPython:INTERNAL=OFF //ADVANCED property for variable: Module_PoissonReconstruction Module_PoissonReconstruction-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_Pygments Module_Pygments-ADVANCED:INTERNAL=1 //Request building Pygments Module_Pygments:INTERNAL=OFF //ADVANCED property for variable: Module_SignedTensor Module_SignedTensor-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_SixPython Module_SixPython-ADVANCED:INTERNAL=1 //Request building SixPython Module_SixPython:INTERNAL=OFF //ADVANCED property for variable: Module_SplineDrivenImageSlicer Module_SplineDrivenImageSlicer-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_Twisted Module_Twisted-ADVANCED:INTERNAL=1 //Request building Twisted Module_Twisted:INTERNAL=OFF //ADVANCED property for variable: Module_VisItLib Module_VisItLib-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_WikiExamples Module_WikiExamples-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_ZopeInterface Module_ZopeInterface-ADVANCED:INTERNAL=1 //Request building ZopeInterface Module_ZopeInterface:INTERNAL=OFF //ADVANCED property for variable: Module_constantly Module_constantly-ADVANCED:INTERNAL=1 //Request building constantly Module_constantly:INTERNAL=OFF //ADVANCED property for variable: Module_incremental Module_incremental-ADVANCED:INTERNAL=1 //Request building incremental Module_incremental:INTERNAL=OFF //ADVANCED property for variable: Module_pqApplicationComponents Module_pqApplicationComponents-ADVANCED:INTERNAL=1 //Request building pqApplicationComponents Module_pqApplicationComponents:INTERNAL=OFF //ADVANCED property for variable: Module_pqComponents Module_pqComponents-ADVANCED:INTERNAL=1 //Request building pqComponents Module_pqComponents:INTERNAL=OFF //ADVANCED property for variable: Module_pqCore Module_pqCore-ADVANCED:INTERNAL=1 //Request building pqCore Module_pqCore:INTERNAL=OFF //ADVANCED property for variable: Module_pqDeprecated Module_pqDeprecated-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_pqPython Module_pqPython-ADVANCED:INTERNAL=1 //Request building pqPython Module_pqPython:INTERNAL=OFF //ADVANCED property for variable: Module_pqWidgets Module_pqWidgets-ADVANCED:INTERNAL=1 //Request building pqWidgets Module_pqWidgets:INTERNAL=OFF //ADVANCED property for variable: Module_smTestDriver Module_smTestDriver-ADVANCED:INTERNAL=1 //Request building smTestDriver Module_smTestDriver:INTERNAL=OFF //ADVANCED property for variable: Module_vtkAcceleratorsVTKm Module_vtkAcceleratorsVTKm-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkAddon Module_vtkAddon-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkChartsCore Module_vtkChartsCore-ADVANCED:INTERNAL=1 //Request building vtkChartsCore Module_vtkChartsCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkClientServer Module_vtkClientServer-ADVANCED:INTERNAL=1 //Request building vtkClientServer Module_vtkClientServer:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonColor Module_vtkCommonColor-ADVANCED:INTERNAL=1 //Request building vtkCommonColor Module_vtkCommonColor:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonComputationalGeometry Module_vtkCommonComputationalGeometry-ADVANCED:INTERNAL=1 //Request building vtkCommonComputationalGeometry Module_vtkCommonComputationalGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonCore Module_vtkCommonCore-ADVANCED:INTERNAL=1 //Request building vtkCommonCore Module_vtkCommonCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonDataModel Module_vtkCommonDataModel-ADVANCED:INTERNAL=1 //Request building vtkCommonDataModel Module_vtkCommonDataModel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonExecutionModel Module_vtkCommonExecutionModel-ADVANCED:INTERNAL=1 //Request building vtkCommonExecutionModel Module_vtkCommonExecutionModel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonMath Module_vtkCommonMath-ADVANCED:INTERNAL=1 //Request building vtkCommonMath Module_vtkCommonMath:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonMisc Module_vtkCommonMisc-ADVANCED:INTERNAL=1 //Request building vtkCommonMisc Module_vtkCommonMisc:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonSystem Module_vtkCommonSystem-ADVANCED:INTERNAL=1 //Request building vtkCommonSystem Module_vtkCommonSystem:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCommonTransforms Module_vtkCommonTransforms-ADVANCED:INTERNAL=1 //Request building vtkCommonTransforms Module_vtkCommonTransforms:INTERNAL=OFF //ADVANCED property for variable: Module_vtkCosmoHaloFinder Module_vtkCosmoHaloFinder-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkDICOM Module_vtkDICOM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkDICOMParser Module_vtkDICOMParser-ADVANCED:INTERNAL=1 //Request building vtkDICOMParser Module_vtkDICOMParser:INTERNAL=OFF //ADVANCED property for variable: Module_vtkDomainsChemistry Module_vtkDomainsChemistry-ADVANCED:INTERNAL=1 //Request building vtkDomainsChemistry Module_vtkDomainsChemistry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkDomainsChemistryOpenGL2 Module_vtkDomainsChemistryOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkDomainsChemistryOpenGL2 Module_vtkDomainsChemistryOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkDomainsMicroscopy Module_vtkDomainsMicroscopy-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersAMR Module_vtkFiltersAMR-ADVANCED:INTERNAL=1 //Request building vtkFiltersAMR Module_vtkFiltersAMR:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersCore Module_vtkFiltersCore-ADVANCED:INTERNAL=1 //Request building vtkFiltersCore Module_vtkFiltersCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersExtraction Module_vtkFiltersExtraction-ADVANCED:INTERNAL=1 //Request building vtkFiltersExtraction Module_vtkFiltersExtraction:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersFlowPaths Module_vtkFiltersFlowPaths-ADVANCED:INTERNAL=1 //Request building vtkFiltersFlowPaths Module_vtkFiltersFlowPaths:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersGeneral Module_vtkFiltersGeneral-ADVANCED:INTERNAL=1 //Request building vtkFiltersGeneral Module_vtkFiltersGeneral:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersGeneric Module_vtkFiltersGeneric-ADVANCED:INTERNAL=1 //Request building vtkFiltersGeneric Module_vtkFiltersGeneric:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersGeometry Module_vtkFiltersGeometry-ADVANCED:INTERNAL=1 //Request building vtkFiltersGeometry Module_vtkFiltersGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersHybrid Module_vtkFiltersHybrid-ADVANCED:INTERNAL=1 //Request building vtkFiltersHybrid Module_vtkFiltersHybrid:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersHyperTree Module_vtkFiltersHyperTree-ADVANCED:INTERNAL=1 //Request building vtkFiltersHyperTree Module_vtkFiltersHyperTree:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersImaging Module_vtkFiltersImaging-ADVANCED:INTERNAL=1 //Request building vtkFiltersImaging Module_vtkFiltersImaging:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersMatlab Module_vtkFiltersMatlab-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersModeling Module_vtkFiltersModeling-ADVANCED:INTERNAL=1 //Request building vtkFiltersModeling Module_vtkFiltersModeling:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallel Module_vtkFiltersParallel-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallel Module_vtkFiltersParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelDIY2 Module_vtkFiltersParallelDIY2-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelDIY2 Module_vtkFiltersParallelDIY2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelFlowPaths Module_vtkFiltersParallelFlowPaths-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelFlowPaths Module_vtkFiltersParallelFlowPaths:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelGeometry Module_vtkFiltersParallelGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelImaging Module_vtkFiltersParallelImaging-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelImaging Module_vtkFiltersParallelImaging:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelMPI Module_vtkFiltersParallelMPI-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelMPI Module_vtkFiltersParallelMPI:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersParallelStatistics Module_vtkFiltersParallelStatistics-ADVANCED:INTERNAL=1 //Request building vtkFiltersParallelStatistics Module_vtkFiltersParallelStatistics:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersPoints Module_vtkFiltersPoints-ADVANCED:INTERNAL=1 //Request building vtkFiltersPoints Module_vtkFiltersPoints:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersProgrammable Module_vtkFiltersProgrammable-ADVANCED:INTERNAL=1 //Request building vtkFiltersProgrammable Module_vtkFiltersProgrammable:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersPython Module_vtkFiltersPython-ADVANCED:INTERNAL=1 //Request building vtkFiltersPython Module_vtkFiltersPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersReebGraph Module_vtkFiltersReebGraph-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersSMP Module_vtkFiltersSMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersSelection Module_vtkFiltersSelection-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersSources Module_vtkFiltersSources-ADVANCED:INTERNAL=1 //Request building vtkFiltersSources Module_vtkFiltersSources:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersStatistics Module_vtkFiltersStatistics-ADVANCED:INTERNAL=1 //Request building vtkFiltersStatistics Module_vtkFiltersStatistics:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersStatisticsGnuR Module_vtkFiltersStatisticsGnuR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersTexture Module_vtkFiltersTexture-ADVANCED:INTERNAL=1 //Request building vtkFiltersTexture Module_vtkFiltersTexture:INTERNAL=OFF //ADVANCED property for variable: Module_vtkFiltersTopology Module_vtkFiltersTopology-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkFiltersVerdict Module_vtkFiltersVerdict-ADVANCED:INTERNAL=1 //Request building vtkFiltersVerdict Module_vtkFiltersVerdict:INTERNAL=OFF //ADVANCED property for variable: Module_vtkGUISupportQt Module_vtkGUISupportQt-ADVANCED:INTERNAL=1 //Request building vtkGUISupportQt Module_vtkGUISupportQt:INTERNAL=OFF //ADVANCED property for variable: Module_vtkGUISupportQtOpenGL Module_vtkGUISupportQtOpenGL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkGUISupportQtSQL Module_vtkGUISupportQtSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkGUISupportQtWebkit Module_vtkGUISupportQtWebkit-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkGeovisCore Module_vtkGeovisCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOADIOS Module_vtkIOADIOS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOAMR Module_vtkIOAMR-ADVANCED:INTERNAL=1 //Request building vtkIOAMR Module_vtkIOAMR:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOCore Module_vtkIOCore-ADVANCED:INTERNAL=1 //Request building vtkIOCore Module_vtkIOCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOEnSight Module_vtkIOEnSight-ADVANCED:INTERNAL=1 //Request building vtkIOEnSight Module_vtkIOEnSight:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExodus Module_vtkIOExodus-ADVANCED:INTERNAL=1 //Request building vtkIOExodus Module_vtkIOExodus:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExport Module_vtkIOExport-ADVANCED:INTERNAL=1 //Request building vtkIOExport Module_vtkIOExport:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExportOpenGL Module_vtkIOExportOpenGL-ADVANCED:INTERNAL=1 //Request building vtkIOExportOpenGL Module_vtkIOExportOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOExportOpenGL2 Module_vtkIOExportOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkIOExportOpenGL2 Module_vtkIOExportOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOFFMPEG Module_vtkIOFFMPEG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOGDAL Module_vtkIOGDAL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOGeoJSON Module_vtkIOGeoJSON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOGeometry Module_vtkIOGeometry-ADVANCED:INTERNAL=1 //Request building vtkIOGeometry Module_vtkIOGeometry:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOImage Module_vtkIOImage-ADVANCED:INTERNAL=1 //Request building vtkIOImage Module_vtkIOImage:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOImport Module_vtkIOImport-ADVANCED:INTERNAL=1 //Request building vtkIOImport Module_vtkIOImport:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOInfovis Module_vtkIOInfovis-ADVANCED:INTERNAL=1 //Request building vtkIOInfovis Module_vtkIOInfovis:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOLSDyna Module_vtkIOLSDyna-ADVANCED:INTERNAL=1 //Request building vtkIOLSDyna Module_vtkIOLSDyna:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOLegacy Module_vtkIOLegacy-ADVANCED:INTERNAL=1 //Request building vtkIOLegacy Module_vtkIOLegacy:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMINC Module_vtkIOMINC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOMPIImage Module_vtkIOMPIImage-ADVANCED:INTERNAL=1 //Request building vtkIOMPIImage Module_vtkIOMPIImage:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMPIParallel Module_vtkIOMPIParallel-ADVANCED:INTERNAL=1 //Request building vtkIOMPIParallel Module_vtkIOMPIParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMovie Module_vtkIOMovie-ADVANCED:INTERNAL=1 //Request building vtkIOMovie Module_vtkIOMovie:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOMySQL Module_vtkIOMySQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIONetCDF Module_vtkIONetCDF-ADVANCED:INTERNAL=1 //Request building vtkIONetCDF Module_vtkIONetCDF:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOODBC Module_vtkIOODBC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOPLY Module_vtkIOPLY-ADVANCED:INTERNAL=1 //Request building vtkIOPLY Module_vtkIOPLY:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallel Module_vtkIOParallel-ADVANCED:INTERNAL=1 //Request building vtkIOParallel Module_vtkIOParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelExodus Module_vtkIOParallelExodus-ADVANCED:INTERNAL=1 //Request building vtkIOParallelExodus Module_vtkIOParallelExodus:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelLSDyna Module_vtkIOParallelLSDyna-ADVANCED:INTERNAL=1 //Request building vtkIOParallelLSDyna Module_vtkIOParallelLSDyna:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelNetCDF Module_vtkIOParallelNetCDF-ADVANCED:INTERNAL=1 //Request building vtkIOParallelNetCDF Module_vtkIOParallelNetCDF:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOParallelXML Module_vtkIOParallelXML-ADVANCED:INTERNAL=1 //Request building vtkIOParallelXML Module_vtkIOParallelXML:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOPostgreSQL Module_vtkIOPostgreSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOSQL Module_vtkIOSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOTRUCHAS Module_vtkIOTRUCHAS-ADVANCED:INTERNAL=1 //Request building vtkIOTRUCHAS Module_vtkIOTRUCHAS:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOTecplotTable Module_vtkIOTecplotTable-ADVANCED:INTERNAL=1 //Request building vtkIOTecplotTable Module_vtkIOTecplotTable:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOVPIC Module_vtkIOVPIC-ADVANCED:INTERNAL=1 //Request building vtkIOVPIC Module_vtkIOVPIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOVideo Module_vtkIOVideo-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOVisItBridge Module_vtkIOVisItBridge-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkIOXML Module_vtkIOXML-ADVANCED:INTERNAL=1 //Request building vtkIOXML Module_vtkIOXML:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOXMLParser Module_vtkIOXMLParser-ADVANCED:INTERNAL=1 //Request building vtkIOXMLParser Module_vtkIOXMLParser:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOXdmf2 Module_vtkIOXdmf2-ADVANCED:INTERNAL=1 //Request building vtkIOXdmf2 Module_vtkIOXdmf2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkIOXdmf3 Module_vtkIOXdmf3-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkImagingColor Module_vtkImagingColor-ADVANCED:INTERNAL=1 //Request building vtkImagingColor Module_vtkImagingColor:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingCore Module_vtkImagingCore-ADVANCED:INTERNAL=1 //Request building vtkImagingCore Module_vtkImagingCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingFourier Module_vtkImagingFourier-ADVANCED:INTERNAL=1 //Request building vtkImagingFourier Module_vtkImagingFourier:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingGeneral Module_vtkImagingGeneral-ADVANCED:INTERNAL=1 //Request building vtkImagingGeneral Module_vtkImagingGeneral:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingHybrid Module_vtkImagingHybrid-ADVANCED:INTERNAL=1 //Request building vtkImagingHybrid Module_vtkImagingHybrid:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingMath Module_vtkImagingMath-ADVANCED:INTERNAL=1 //Request building vtkImagingMath Module_vtkImagingMath:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingMorphological Module_vtkImagingMorphological-ADVANCED:INTERNAL=1 //Request building vtkImagingMorphological Module_vtkImagingMorphological:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingOpenGL2 Module_vtkImagingOpenGL2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkImagingSources Module_vtkImagingSources-ADVANCED:INTERNAL=1 //Request building vtkImagingSources Module_vtkImagingSources:INTERNAL=OFF //ADVANCED property for variable: Module_vtkImagingStatistics Module_vtkImagingStatistics-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkImagingStencil Module_vtkImagingStencil-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisBoost Module_vtkInfovisBoost-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisBoostGraphAlgorithms Module_vtkInfovisBoostGraphAlgorithms-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisCore Module_vtkInfovisCore-ADVANCED:INTERNAL=1 //Request building vtkInfovisCore Module_vtkInfovisCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkInfovisLayout Module_vtkInfovisLayout-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInfovisParallel Module_vtkInfovisParallel-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkInteractionImage Module_vtkInteractionImage-ADVANCED:INTERNAL=1 //Request building vtkInteractionImage Module_vtkInteractionImage:INTERNAL=OFF //ADVANCED property for variable: Module_vtkInteractionStyle Module_vtkInteractionStyle-ADVANCED:INTERNAL=1 //Request building vtkInteractionStyle Module_vtkInteractionStyle:INTERNAL=OFF //ADVANCED property for variable: Module_vtkInteractionWidgets Module_vtkInteractionWidgets-ADVANCED:INTERNAL=1 //Request building vtkInteractionWidgets Module_vtkInteractionWidgets:INTERNAL=OFF //ADVANCED property for variable: Module_vtkMetaIO Module_vtkMetaIO-ADVANCED:INTERNAL=1 //Request building vtkMetaIO Module_vtkMetaIO:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVAnimation Module_vtkPVAnimation-ADVANCED:INTERNAL=1 //Request building vtkPVAnimation Module_vtkPVAnimation:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVCatalyst Module_vtkPVCatalyst-ADVANCED:INTERNAL=1 //Request building vtkPVCatalyst Module_vtkPVCatalyst:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVCatalystTestDriver Module_vtkPVCatalystTestDriver-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPVCinemaReader Module_vtkPVCinemaReader-ADVANCED:INTERNAL=1 //Request building vtkPVCinemaReader Module_vtkPVCinemaReader:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVClientServerCoreCore Module_vtkPVClientServerCoreCore-ADVANCED:INTERNAL=1 //Request building vtkPVClientServerCoreCore Module_vtkPVClientServerCoreCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVClientServerCoreDefault Module_vtkPVClientServerCoreDefault-ADVANCED:INTERNAL=1 //Request building vtkPVClientServerCoreDefault Module_vtkPVClientServerCoreDefault:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVClientServerCoreRendering Module_vtkPVClientServerCoreRendering-ADVANCED:INTERNAL=1 //Request building vtkPVClientServerCoreRendering Module_vtkPVClientServerCoreRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVCommon Module_vtkPVCommon-ADVANCED:INTERNAL=1 //Request building vtkPVCommon Module_vtkPVCommon:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerImplementationCore Module_vtkPVServerImplementationCore-ADVANCED:INTERNAL=1 //Request building vtkPVServerImplementationCore Module_vtkPVServerImplementationCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerImplementationRendering Module_vtkPVServerImplementationRendering-ADVANCED:INTERNAL=1 //Request building vtkPVServerImplementationRendering Module_vtkPVServerImplementationRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerApplication Module_vtkPVServerManagerApplication-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerApplication Module_vtkPVServerManagerApplication:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerCore Module_vtkPVServerManagerCore-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerCore Module_vtkPVServerManagerCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerDefault Module_vtkPVServerManagerDefault-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerDefault Module_vtkPVServerManagerDefault:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVServerManagerRendering Module_vtkPVServerManagerRendering-ADVANCED:INTERNAL=1 //Request building vtkPVServerManagerRendering Module_vtkPVServerManagerRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsCGNSReader Module_vtkPVVTKExtensionsCGNSReader-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsCGNSReader Module_vtkPVVTKExtensionsCGNSReader:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsCore Module_vtkPVVTKExtensionsCore-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsCore Module_vtkPVVTKExtensionsCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsCosmoTools Module_vtkPVVTKExtensionsCosmoTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPVVTKExtensionsDefault Module_vtkPVVTKExtensionsDefault-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsDefault Module_vtkPVVTKExtensionsDefault:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsH5PartReader Module_vtkPVVTKExtensionsH5PartReader-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsH5PartReader Module_vtkPVVTKExtensionsH5PartReader:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsPoints Module_vtkPVVTKExtensionsPoints-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsPoints Module_vtkPVVTKExtensionsPoints:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPVVTKExtensionsRendering Module_vtkPVVTKExtensionsRendering-ADVANCED:INTERNAL=1 //Request building vtkPVVTKExtensionsRendering Module_vtkPVVTKExtensionsRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWeb Module_vtkParaViewWeb-ADVANCED:INTERNAL=1 //Request building vtkParaViewWeb Module_vtkParaViewWeb:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebCore Module_vtkParaViewWebCore-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebCore Module_vtkParaViewWebCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebPython Module_vtkParaViewWebPython-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebPython Module_vtkParaViewWebPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParaViewWebPython2 Module_vtkParaViewWebPython2-ADVANCED:INTERNAL=1 //Request building vtkParaViewWebPython2 Module_vtkParaViewWebPython2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParallelCore Module_vtkParallelCore-ADVANCED:INTERNAL=1 //Request building vtkParallelCore Module_vtkParallelCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParallelMPI Module_vtkParallelMPI-ADVANCED:INTERNAL=1 //Request building vtkParallelMPI Module_vtkParallelMPI:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParallelMPI4Py Module_vtkParallelMPI4Py-ADVANCED:INTERNAL=1 //Request building vtkParallelMPI4Py Module_vtkParallelMPI4Py:INTERNAL=OFF //ADVANCED property for variable: Module_vtkParseOGLExt Module_vtkParseOGLExt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPython Module_vtkPython-ADVANCED:INTERNAL=1 //Request building vtkPython Module_vtkPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkPythonInterpreter Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1 //Request building vtkPythonInterpreter Module_vtkPythonInterpreter:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingAnnotation Module_vtkRenderingAnnotation-ADVANCED:INTERNAL=1 //Request building vtkRenderingAnnotation Module_vtkRenderingAnnotation:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingContext2D Module_vtkRenderingContext2D-ADVANCED:INTERNAL=1 //Request building vtkRenderingContext2D Module_vtkRenderingContext2D:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingContextOpenGL Module_vtkRenderingContextOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingContextOpenGL Module_vtkRenderingContextOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingContextOpenGL2 Module_vtkRenderingContextOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingContextOpenGL2 Module_vtkRenderingContextOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingCore Module_vtkRenderingCore-ADVANCED:INTERNAL=1 //Request building vtkRenderingCore Module_vtkRenderingCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingExternal Module_vtkRenderingExternal-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingFreeType Module_vtkRenderingFreeType-ADVANCED:INTERNAL=1 //Request building vtkRenderingFreeType Module_vtkRenderingFreeType:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingFreeTypeFontConfig Module_vtkRenderingFreeTypeFontConfig-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingGL2PS Module_vtkRenderingGL2PS-ADVANCED:INTERNAL=1 //Request building vtkRenderingGL2PS Module_vtkRenderingGL2PS:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingGL2PSOpenGL2 Module_vtkRenderingGL2PSOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingGL2PSOpenGL2 Module_vtkRenderingGL2PSOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingImage Module_vtkRenderingImage-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingLIC Module_vtkRenderingLIC-ADVANCED:INTERNAL=1 //Request building vtkRenderingLIC Module_vtkRenderingLIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingLICOpenGL2 Module_vtkRenderingLICOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingLICOpenGL2 Module_vtkRenderingLICOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingLOD Module_vtkRenderingLOD-ADVANCED:INTERNAL=1 //Request building vtkRenderingLOD Module_vtkRenderingLOD:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingLabel Module_vtkRenderingLabel-ADVANCED:INTERNAL=1 //Request building vtkRenderingLabel Module_vtkRenderingLabel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingMatplotlib Module_vtkRenderingMatplotlib-ADVANCED:INTERNAL=1 //Request building vtkRenderingMatplotlib Module_vtkRenderingMatplotlib:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingOSPRay Module_vtkRenderingOSPRay-ADVANCED:INTERNAL=1 //Request building vtkRenderingOSPRay Module_vtkRenderingOSPRay:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingOculus Module_vtkRenderingOculus-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingOpenGL Module_vtkRenderingOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingOpenGL Module_vtkRenderingOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingOpenGL2 Module_vtkRenderingOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingOpenGL2 Module_vtkRenderingOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingOpenVR Module_vtkRenderingOpenVR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingParallel Module_vtkRenderingParallel-ADVANCED:INTERNAL=1 //Request building vtkRenderingParallel Module_vtkRenderingParallel:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingParallelLIC Module_vtkRenderingParallelLIC-ADVANCED:INTERNAL=1 //Request building vtkRenderingParallelLIC Module_vtkRenderingParallelLIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingQt Module_vtkRenderingQt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingSceneGraph Module_vtkRenderingSceneGraph-ADVANCED:INTERNAL=1 //Request building vtkRenderingSceneGraph Module_vtkRenderingSceneGraph:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingTk Module_vtkRenderingTk-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkRenderingVolume Module_vtkRenderingVolume-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolume Module_vtkRenderingVolume:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingVolumeAMR Module_vtkRenderingVolumeAMR-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolumeAMR Module_vtkRenderingVolumeAMR:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL Module_vtkRenderingVolumeOpenGL-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolumeOpenGL Module_vtkRenderingVolumeOpenGL:INTERNAL=OFF //ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL2 Module_vtkRenderingVolumeOpenGL2-ADVANCED:INTERNAL=1 //Request building vtkRenderingVolumeOpenGL2 Module_vtkRenderingVolumeOpenGL2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkTclTk Module_vtkTclTk-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkTestingCore Module_vtkTestingCore-ADVANCED:INTERNAL=1 //Request building vtkTestingCore Module_vtkTestingCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkTestingGenericBridge Module_vtkTestingGenericBridge-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkTestingIOSQL Module_vtkTestingIOSQL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkTestingRendering Module_vtkTestingRendering-ADVANCED:INTERNAL=1 //Request building vtkTestingRendering Module_vtkTestingRendering:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesBenchmarks Module_vtkUtilitiesBenchmarks-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkUtilitiesColorSeriesToXML Module_vtkUtilitiesColorSeriesToXML-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkUtilitiesEncodeString Module_vtkUtilitiesEncodeString-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesEncodeString Module_vtkUtilitiesEncodeString:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesHashSource Module_vtkUtilitiesHashSource-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesHashSource Module_vtkUtilitiesHashSource:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesLegacyColorMapXMLToJSON Module_vtkUtilitiesLegacyColorMapXMLToJSON-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesLegacyColorMapXMLToJSON Module_vtkUtilitiesLegacyColorMapXMLToJSON:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesProcessXML Module_vtkUtilitiesProcessXML-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesProcessXML Module_vtkUtilitiesProcessXML:INTERNAL=OFF //ADVANCED property for variable: Module_vtkUtilitiesWrapClientServer Module_vtkUtilitiesWrapClientServer-ADVANCED:INTERNAL=1 //Request building vtkUtilitiesWrapClientServer Module_vtkUtilitiesWrapClientServer:INTERNAL=OFF //ADVANCED property for variable: Module_vtkVPIC Module_vtkVPIC-ADVANCED:INTERNAL=1 //Request building vtkVPIC Module_vtkVPIC:INTERNAL=OFF //ADVANCED property for variable: Module_vtkViewsContext2D Module_vtkViewsContext2D-ADVANCED:INTERNAL=1 //Request building vtkViewsContext2D Module_vtkViewsContext2D:INTERNAL=OFF //ADVANCED property for variable: Module_vtkViewsCore Module_vtkViewsCore-ADVANCED:INTERNAL=1 //Request building vtkViewsCore Module_vtkViewsCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkViewsGeovis Module_vtkViewsGeovis-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkViewsInfovis Module_vtkViewsInfovis-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkViewsQt Module_vtkViewsQt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWebCore Module_vtkWebCore-ADVANCED:INTERNAL=1 //Request building vtkWebCore Module_vtkWebCore:INTERNAL=OFF //ADVANCED property for variable: Module_vtkWebGLExporter Module_vtkWebGLExporter-ADVANCED:INTERNAL=1 //Request building vtkWebGLExporter Module_vtkWebGLExporter:INTERNAL=OFF //ADVANCED property for variable: Module_vtkWebPython Module_vtkWebPython-ADVANCED:INTERNAL=1 //Request building vtkWebPython Module_vtkWebPython:INTERNAL=OFF //ADVANCED property for variable: Module_vtkWrappingJava Module_vtkWrappingJava-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWrappingPythonCore Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWrappingTcl Module_vtkWrappingTcl-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWrappingTools Module_vtkWrappingTools-ADVANCED:INTERNAL=1 //Request building vtkWrappingTools Module_vtkWrappingTools:INTERNAL=OFF //ADVANCED property for variable: Module_vtkalglib Module_vtkalglib-ADVANCED:INTERNAL=1 //Request building vtkalglib Module_vtkalglib:INTERNAL=OFF //ADVANCED property for variable: Module_vtkcgns Module_vtkcgns-ADVANCED:INTERNAL=1 //Request building vtkcgns Module_vtkcgns:INTERNAL=OFF //ADVANCED property for variable: Module_vtkdiy2 Module_vtkdiy2-ADVANCED:INTERNAL=1 //Request building vtkdiy2 Module_vtkdiy2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkexodusII Module_vtkexodusII-ADVANCED:INTERNAL=1 //Request building vtkexodusII Module_vtkexodusII:INTERNAL=OFF //ADVANCED property for variable: Module_vtkexpat Module_vtkexpat-ADVANCED:INTERNAL=1 //Request building vtkexpat Module_vtkexpat:INTERNAL=OFF //ADVANCED property for variable: Module_vtkfreetype Module_vtkfreetype-ADVANCED:INTERNAL=1 //Request building vtkfreetype Module_vtkfreetype:INTERNAL=OFF //ADVANCED property for variable: Module_vtkgl2ps Module_vtkgl2ps-ADVANCED:INTERNAL=1 //Request building vtkgl2ps Module_vtkgl2ps:INTERNAL=OFF //ADVANCED property for variable: Module_vtkglew Module_vtkglew-ADVANCED:INTERNAL=1 //Request building vtkglew Module_vtkglew:INTERNAL=OFF //ADVANCED property for variable: Module_vtkhdf5 Module_vtkhdf5-ADVANCED:INTERNAL=1 //Request building vtkhdf5 Module_vtkhdf5:INTERNAL=OFF //ADVANCED property for variable: Module_vtkicet Module_vtkicet-ADVANCED:INTERNAL=1 //Request building vtkicet Module_vtkicet:INTERNAL=OFF //ADVANCED property for variable: Module_vtkjpeg Module_vtkjpeg-ADVANCED:INTERNAL=1 //Request building vtkjpeg Module_vtkjpeg:INTERNAL=OFF //ADVANCED property for variable: Module_vtkjsoncpp Module_vtkjsoncpp-ADVANCED:INTERNAL=1 //Request building vtkjsoncpp Module_vtkjsoncpp:INTERNAL=OFF //ADVANCED property for variable: Module_vtkkwiml Module_vtkkwiml-ADVANCED:INTERNAL=1 //Request building vtkkwiml Module_vtkkwiml:INTERNAL=OFF //ADVANCED property for variable: Module_vtklibharu Module_vtklibharu-ADVANCED:INTERNAL=1 //Request building vtklibharu Module_vtklibharu:INTERNAL=OFF //ADVANCED property for variable: Module_vtklibproj4 Module_vtklibproj4-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtklibxml2 Module_vtklibxml2-ADVANCED:INTERNAL=1 //Request building vtklibxml2 Module_vtklibxml2:INTERNAL=OFF //ADVANCED property for variable: Module_vtklz4 Module_vtklz4-ADVANCED:INTERNAL=1 //Request building vtklz4 Module_vtklz4:INTERNAL=OFF //ADVANCED property for variable: Module_vtkmpi4py Module_vtkmpi4py-ADVANCED:INTERNAL=1 //Request building vtkmpi4py Module_vtkmpi4py:INTERNAL=OFF //ADVANCED property for variable: Module_vtknetcdf Module_vtknetcdf-ADVANCED:INTERNAL=1 //Request building vtknetcdf Module_vtknetcdf:INTERNAL=OFF //ADVANCED property for variable: Module_vtknetcdfcpp Module_vtknetcdfcpp-ADVANCED:INTERNAL=1 //Request building vtknetcdfcpp Module_vtknetcdfcpp:INTERNAL=OFF //ADVANCED property for variable: Module_vtkoggtheora Module_vtkoggtheora-ADVANCED:INTERNAL=1 //Request building vtkoggtheora Module_vtkoggtheora:INTERNAL=OFF //ADVANCED property for variable: Module_vtkpng Module_vtkpng-ADVANCED:INTERNAL=1 //Request building vtkpng Module_vtkpng:INTERNAL=OFF //ADVANCED property for variable: Module_vtkprotobuf Module_vtkprotobuf-ADVANCED:INTERNAL=1 //Request building vtkprotobuf Module_vtkprotobuf:INTERNAL=OFF //ADVANCED property for variable: Module_vtkpugixml Module_vtkpugixml-ADVANCED:INTERNAL=1 //Request building vtkpugixml Module_vtkpugixml:INTERNAL=OFF //ADVANCED property for variable: Module_vtkqttesting Module_vtkqttesting-ADVANCED:INTERNAL=1 //Request building vtkqttesting Module_vtkqttesting:INTERNAL=OFF //ADVANCED property for variable: Module_vtksqlite Module_vtksqlite-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtksys Module_vtksys-ADVANCED:INTERNAL=1 //Request building vtksys Module_vtksys:INTERNAL=OFF //ADVANCED property for variable: Module_vtktiff Module_vtktiff-ADVANCED:INTERNAL=1 //Request building vtktiff Module_vtktiff:INTERNAL=OFF //ADVANCED property for variable: Module_vtkverdict Module_vtkverdict-ADVANCED:INTERNAL=1 //Request building vtkverdict Module_vtkverdict:INTERNAL=OFF //ADVANCED property for variable: Module_vtkxdmf2 Module_vtkxdmf2-ADVANCED:INTERNAL=1 //Request building vtkxdmf2 Module_vtkxdmf2:INTERNAL=OFF //ADVANCED property for variable: Module_vtkxdmf3 Module_vtkxdmf3-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkzfp Module_vtkzfp-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkzlib Module_vtkzlib-ADVANCED:INTERNAL=1 //Request building vtkzlib Module_vtkzlib:INTERNAL=OFF //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_NELEMS NETCDF4_CHUNK_CACHE_NELEMS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_PREEMPTION NETCDF4_CHUNK_CACHE_PREEMPTION-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_CHUNK_CACHE_SIZE NETCDF4_CHUNK_CACHE_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_DEFAULT_CHUNKS_IN_CACHE NETCDF4_DEFAULT_CHUNKS_IN_CACHE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_DEFAULT_CHUNK_SIZE NETCDF4_DEFAULT_CHUNK_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF4_MAX_DEFAULT_CACHE_SIZE NETCDF4_MAX_DEFAULT_CACHE_SIZE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: NETCDF_DISABLE_COMPILER_WARNINGS NETCDF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //Result of TRY_RUN NO_ICC_IDYNAMIC_NEEDED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(off64_t) OFF64_T:INTERNAL=8 //Have symbol off_t OFF_T:INTERNAL= //ADVANCED property for variable: OSMESA_INCLUDE_DIR OSMESA_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OSMESA_LIBRARY OSMESA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OSPRAY_BUILD_DIR OSPRAY_BUILD_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: OSPRAY_INSTALL_DIR OSPRAY_INSTALL_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms PARAVIEW_AUTOLOAD_PLUGIN_AcceleratedAlgorithms-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO PARAVIEW_AUTOLOAD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph PARAVIEW_AUTOLOAD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_CDIReader PARAVIEW_AUTOLOAD_PLUGIN_CDIReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin PARAVIEW_AUTOLOAD_PLUGIN_CatalystScriptGeneratorPlugin-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting PARAVIEW_AUTOLOAD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_GMVReader PARAVIEW_AUTOLOAD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement PARAVIEW_AUTOLOAD_PLUGIN_GeodesicMeasurement-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_LagrangianParticleTracker PARAVIEW_AUTOLOAD_PLUGIN_LagrangianParticleTracker-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_Moments PARAVIEW_AUTOLOAD_PLUGIN_Moments-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource PARAVIEW_AUTOLOAD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_PacMan PARAVIEW_AUTOLOAD_PLUGIN_PacMan-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SLACTools PARAVIEW_AUTOLOAD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools PARAVIEW_AUTOLOAD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_StreamLinesRepresentation PARAVIEW_AUTOLOAD_PLUGIN_StreamLinesRepresentation-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles PARAVIEW_AUTOLOAD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC PARAVIEW_AUTOLOAD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells PARAVIEW_AUTOLOAD_PLUGIN_ThickenLayeredCells-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_CATALYST_ADAPTORS PARAVIEW_BUILD_CATALYST_ADAPTORS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms PARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AdiosReader PARAVIEW_BUILD_PLUGIN_AdiosReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AdiosStagingReader PARAVIEW_BUILD_PLUGIN_AdiosStagingReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ArrowGlyph PARAVIEW_BUILD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_CDIReader PARAVIEW_BUILD_PLUGIN_CDIReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin PARAVIEW_BUILD_PLUGIN_CatalystScriptGeneratorPlugin-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_EyeDomeLighting PARAVIEW_BUILD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GMVReader PARAVIEW_BUILD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement PARAVIEW_BUILD_PLUGIN_GeodesicMeasurement-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_InSituExodus PARAVIEW_BUILD_PLUGIN_InSituExodus-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_LagrangianParticleTracker PARAVIEW_BUILD_PLUGIN_LagrangianParticleTracker-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Moments PARAVIEW_BUILD_PLUGIN_Moments-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PacMan PARAVIEW_BUILD_PLUGIN_PacMan-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PythonQtPlugin PARAVIEW_BUILD_PLUGIN_PythonQtPlugin-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SLACTools PARAVIEW_BUILD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SierraPlotTools PARAVIEW_BUILD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamLinesRepresentation PARAVIEW_BUILD_PLUGIN_StreamLinesRepresentation-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamingParticles PARAVIEW_BUILD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SurfaceLIC PARAVIEW_BUILD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells PARAVIEW_BUILD_PLUGIN_ThickenLayeredCells-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VRPlugin PARAVIEW_BUILD_PLUGIN_VRPlugin-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1 //List of modules to CS wrap PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonExecutionModel;vtkFiltersCore;vtkCommonComputationalGeometry;vtkFiltersGeneral;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkFiltersSources;vtkCommonColor;vtkFiltersGeometry;vtkRenderingCore;vtkInteractionStyle;vtkRenderingOpenGL2;vtkFiltersModeling;vtkIOCore;vtkIOLegacy;vtkParallelCore;vtkFiltersParallel;vtkFiltersProgrammable;vtkPythonInterpreter;vtkIOXMLParser;vtkPVCommon;vtkIOImage;vtkPVVTKExtensionsCore;vtkParallelMPI;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkIOMovie;vtkIOXML;vtkInfovisCore;vtkIOInfovis;vtkDomainsChemistry;vtkFiltersAMR;vtkRenderingFreeType;vtkRenderingContext2D;vtkChartsCore;vtkFiltersFlowPaths;vtkFiltersParallelFlowPaths;vtkFiltersParallelStatistics;vtkIOEnSight;vtkIOImport;vtkIOMPIImage;vtkIOPLY;vtkIOGeometry;vtkIONetCDF;vtkIOParallel;vtkIOExodus;vtkIOParallelExodus;vtkIOParallelXML;vtkImagingSources;vtkFiltersHybrid;vtkImagingColor;vtkImagingGeneral;vtkImagingHybrid;vtkRenderingAnnotation;vtkRenderingVolume;vtkInteractionWidgets;vtkFiltersGeneric;vtkFiltersHyperTree;vtkFiltersParallelMPI;vtkRenderingGL2PSOpenGL2;vtkIOExport;vtkIOExportOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingMatplotlib;vtkRenderingSceneGraph;vtkRenderingOSPRay;vtkRenderingParallel;vtkImagingMath;vtkRenderingVolumeOpenGL2;vtkRenderingVolumeAMR;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingLabel;vtkViewsCore;vtkViewsContext2D;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkDomainsChemistryOpenGL2;vtkFiltersParallelDIY2;vtkFiltersParallelGeometry;vtkFiltersImaging;vtkFiltersParallelImaging;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOMPIParallel;vtkIOLSDyna;vtkIOParallelLSDyna;vtkIOParallelNetCDF;vtkIOTRUCHAS;vtkIOTecplotTable;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionImage;vtkPVCinemaReader;vtkPVVTKExtensionsCGNSReader;vtkPVVTKExtensionsH5PartReader;vtkFiltersPoints;vtkPVVTKExtensionsPoints;vtkParallelMPI4Py;vtkRenderingLICOpenGL2;vtkRenderingLOD;vtkRenderingParallelLIC;vtkPVServerManagerApplication;vtkPVCatalyst;vtkWebGLExporter;vtkWebCore;vtkParaViewWebCore //ADVANCED property for variable: PARAVIEW_DATA_EXCLUDE_FROM_ALL PARAVIEW_DATA_EXCLUDE_FROM_ALL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_DATA_STORE PARAVIEW_DATA_STORE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_COSMOTOOLS PARAVIEW_ENABLE_COSMOTOOLS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION PARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_MATPLOTLIB PARAVIEW_ENABLE_MATPLOTLIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_SPYPLOT_MARKERS PARAVIEW_ENABLE_SPYPLOT_MARKERS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_ENABLE_WEB PARAVIEW_ENABLE_WEB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTERNAL_MODULE_ROOTS PARAVIEW_EXTERNAL_MODULE_ROOTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTERNAL_PLUGIN_DIRS PARAVIEW_EXTERNAL_PLUGIN_DIRS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTRA_EXTERNAL_PLUGINS PARAVIEW_EXTRA_EXTERNAL_PLUGINS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_FREEZE_PYTHON PARAVIEW_FREEZE_PYTHON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_INITIALIZE_MPI_ON_CLIENT PARAVIEW_INITIALIZE_MPI_ON_CLIENT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_PLUGIN_LOADER_PATHS PARAVIEW_PLUGIN_LOADER_PATHS-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_QT_VERSION PARAVIEW_QT_VERSION-STRINGS:INTERNAL=4;5 //Server Manager XMLs PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/Default/settings.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/Animation/animation.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/CinemaReader/cinemareader.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/VTKExtensions/CGNSReader/resources/CGNSReader.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/VTKExtensions/H5PartReader/H5PartServerManager.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/VTKExtensions/Points/points.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/proxies_mpi.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/proxies_opengl2.xml;/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml //ADVANCED property for variable: PARAVIEW_USE_ATP PARAVIEW_USE_ATP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_ICE_T PARAVIEW_USE_ICE_T-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_MPI_SSEND PARAVIEW_USE_MPI_SSEND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_QTHELP PARAVIEW_USE_QTHELP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_QTWEBKIT PARAVIEW_USE_QTWEBKIT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_USE_UNIFIED_BINDINGS PARAVIEW_USE_UNIFIED_BINDINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PROTOBUF_DISABLE_COMPILER_WARNINGS PROTOBUF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_CLEAN_COMMAND PV_TEST_CLEAN_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_CLIENT PV_TEST_CLIENT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_INIT_COMMAND PV_TEST_INIT_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PV_TEST_USE_RANDOM_PORTS PV_TEST_USE_RANDOM_PORTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_ENABLE_MODULE_mpi4py.MPI PYTHON_ENABLE_MODULE_mpi4py.MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_ENABLE_MODULE_mpi4py.dl PYTHON_ENABLE_MODULE_mpi4py.dl-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_EXECUTABLE PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_EXTRA_LIBS PYTHON_EXTRA_LIBS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_INCLUDE_DIR PYTHON_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_LIBRARY PYTHON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED PYTHON_MODULE_mpi4py.MPI_BUILD_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_MODULE_mpi4py.dl_BUILD_SHARED PYTHON_MODULE_mpi4py.dl_BUILD_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_UTIL_LIBRARY PYTHON_UTIL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_HELP_GENERATOR QT_HELP_GENERATOR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TESTING_EVENT_PLAYBACK_DELAY QT_TESTING_EVENT_PLAYBACK_DELAY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_XMLPATTERNS_EXECUTABLE QT_XMLPATTERNS_EXECUTABLE-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) SIZEOF_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(off_t) SIZEOF_OFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ptrdiff_t) SIZEOF_PTRDIFF_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) SIZEOF_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(signed int) SIZEOF_SIGNED_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(signed long) SIZEOF_SIGNED_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(signed long long) SIZEOF_SIGNED_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(signed short) SIZEOF_SIGNED_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(size_t) SIZEOF_SIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(ssize_t) SIZEOF_SSIZE_T:INTERNAL=8 //CHECK_TYPE_SIZE: uchar unknown SIZEOF_UCHAR:INTERNAL= //CHECK_TYPE_SIZE: sizeof(unsigned char *) SIZEOF_UNSIGNED_CHAR_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned int) SIZEOF_UNSIGNED_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(unsigned long) SIZEOF_UNSIGNED_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned long long) SIZEOF_UNSIGNED_LONG_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(unsigned short) SIZEOF_UNSIGNED_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(void *) SIZEOF_VOID_P:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(_Bool) SIZEOF__BOOL:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(long) SIZE_OF_LONG:INTERNAL=8 //Have symbol size_t SIZE_T:INTERNAL= //Have include stdlib.h;stdarg.h;string.h;float.h STDC_HEADERS:INTERNAL=1 //Result of TRY_COMPILE SUCCEED:INTERNAL=TRUE //Result of TRY_COMPILE SUCCEED_MAP:INTERNAL=TRUE //Result of TRY_COMPILE SUCCEED_SET:INTERNAL=TRUE //Result of TRY_COMPILE SUPPORT_IP6_COMPILED:INTERNAL=TRUE //ADVANCED property for variable: SURFACELIC_PLUGIN_TESTING SURFACELIC_PLUGIN_TESTING-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_INCLUDE_DIR TBB_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_LIBRARY TBB_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_LIBRARY_DEBUG TBB_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_LIBRARY_MALLOC TBB_LIBRARY_MALLOC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: TBB_LIBRARY_MALLOC_DEBUG TBB_LIBRARY_MALLOC_DEBUG-ADVANCED:INTERNAL=1 //Last value of TBB_ROOT to detect changes TBB_ROOT_LAST:INTERNAL=/apps/all/tbb/2017.6.196/tbb //ADVANCED property for variable: TBB_VERSION TBB_VERSION-ADVANCED:INTERNAL=1 //Test TIME_WITH_SYS_TIME TIME_WITH_SYS_TIME:INTERNAL=1 //Test TM_IN_SYS_TIME TM_IN_SYS_TIME:INTERNAL=1 //ADVANCED property for variable: USE_COMPILER_HIDDEN_VISIBILITY USE_COMPILER_HIDDEN_VISIBILITY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VERDICT_BUILD_DOC VERDICT_BUILD_DOC-ADVANCED:INTERNAL=1 //Build the 2007 Verdict User Manual VERDICT_BUILD_DOC:INTERNAL=OFF //ADVANCED property for variable: VERDICT_ENABLE_TESTING VERDICT_ENABLE_TESTING-ADVANCED:INTERNAL=1 //Should tests of the VERDICT library be built? VERDICT_ENABLE_TESTING:INTERNAL=OFF //ADVANCED property for variable: VERDICT_MANGLE VERDICT_MANGLE-ADVANCED:INTERNAL=1 //Mangle verdict names for inclusion in a larger library? VERDICT_MANGLE:INTERNAL=OFF //A string to prepend to all verdict function names and classes. VERDICT_MANGLE_PREFIX:INTERNAL= VTKFTGL_BINARY_DIR:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/VTK/Utilities/ftgl VTKFTGL_SOURCE_DIR:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/VTK/Utilities/ftgl //ADVANCED property for variable: VTKOGGTHEORA_DISABLE_ASM VTKOGGTHEORA_DISABLE_ASM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTKOGGTHEORA_DISABLE_FLOAT VTKOGGTHEORA_DISABLE_FLOAT-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(int) VTKOGGTHEORA_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int16_t) VTKOGGTHEORA_INT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(int32_t) VTKOGGTHEORA_INT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int64_t) VTKOGGTHEORA_INT64_T:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long) VTKOGGTHEORA_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(long long) VTKOGGTHEORA_LONG_LONG:INTERNAL=8 //ADVANCED property for variable: VTKOGGTHEORA_SHARED_LINKER_FLAGS VTKOGGTHEORA_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(short) VTKOGGTHEORA_SHORT:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint16_t) VTKOGGTHEORA_UINT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(uint32_t) VTKOGGTHEORA_UINT32_T:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(u_int16_t) VTKOGGTHEORA_U_INT16_T:INTERNAL=2 //CHECK_TYPE_SIZE: sizeof(u_int32_t) VTKOGGTHEORA_U_INT32_T:INTERNAL=4 //ADVANCED property for variable: VTK_ALL_NEW_OBJECT_FACTORY VTK_ALL_NEW_OBJECT_FACTORY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_ANDROID_BUILD VTK_ANDROID_BUILD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_BUILD_ALL_MODULES VTK_BUILD_ALL_MODULES-ADVANCED:INTERNAL=1 //Directory where python modules will be built VTK_BUILD_PYTHON_MODULE_DIR:INTERNAL=/home/kre0214/.local/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/easybuild_obj/lib/site-packages //ADVANCED property for variable: VTK_BUILD_QT_DESIGNER_PLUGIN VTK_BUILD_QT_DESIGNER_PLUGIN-ADVANCED:INTERNAL=1 //Test VTK_CONST_REVERSE_ITERATOR_COMPARISON VTK_CONST_REVERSE_ITERATOR_COMPARISON:INTERNAL=1 //ADVANCED property for variable: VTK_DATA_STORE VTK_DATA_STORE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DEBUG_LEAKS VTK_DEBUG_LEAKS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DISPATCH_AOS_ARRAYS VTK_DISPATCH_AOS_ARRAYS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DISPATCH_SOA_ARRAYS VTK_DISPATCH_SOA_ARRAYS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_DISPATCH_TYPED_ARRAYS VTK_DISPATCH_TYPED_ARRAYS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_EGL_DEVICE_INDEX VTK_EGL_DEVICE_INDEX-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_ENABLE_KITS VTK_ENABLE_KITS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_ENABLE_VTKPYTHON VTK_ENABLE_VTKPYTHON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_EXTERNAL_HDF5_IS_SHARED VTK_EXTERNAL_HDF5_IS_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_EXTERNAL_LIBHARU_IS_SHARED VTK_EXTERNAL_LIBHARU_IS_SHARED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_FORBID_DOWNLOADS VTK_FORBID_DOWNLOADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Imaging VTK_Group_Imaging-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_MPI VTK_Group_MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_ParaViewCore VTK_Group_ParaViewCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_ParaViewQt VTK_Group_ParaViewQt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_ParaViewRendering VTK_Group_ParaViewRendering-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Qt VTK_Group_Qt-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Rendering VTK_Group_Rendering-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_StandAlone VTK_Group_StandAlone-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Tk VTK_Group_Tk-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Views VTK_Group_Views-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_Group_Web VTK_Group_Web-ADVANCED:INTERNAL=1 //Have symbol feenableexcept VTK_HAS_FEENABLEEXCEPT:INTERNAL=1 //Have symbol finite VTK_HAS_FINITE:INTERNAL=1 //Have symbol isfinite VTK_HAS_ISFINITE:INTERNAL=1 //Have symbol isinf VTK_HAS_ISINF:INTERNAL=1 //Have symbol isnan VTK_HAS_ISNAN:INTERNAL=1 //Test VTK_HAS_STD_ISFINITE VTK_HAS_STD_ISFINITE:INTERNAL=1 //Test VTK_HAS_STD_ISINF VTK_HAS_STD_ISINF:INTERNAL=1 //Test VTK_HAS_STD_ISNAN VTK_HAS_STD_ISNAN:INTERNAL=1 //Support for getsockname with socklen_t VTK_HAVE_GETSOCKNAME_WITH_SOCKLEN_T:INTERNAL=1 //Have library socket VTK_HAVE_LIBSOCKET:INTERNAL= //Have symbol SO_REUSEADDR VTK_HAVE_SO_REUSEADDR:INTERNAL=1 //For __sync atomic builtins. VTK_HAVE_SYNC_BUILTINS:INTERNAL=1 //Directory where python modules will be installed VTK_INSTALL_PYTHON_MODULE_DIR:INTERNAL=lib/paraview-5.4/site-packages //ADVANCED property for variable: VTK_IOS_BUILD VTK_IOS_BUILD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_LEGACY_REMOVE VTK_LEGACY_REMOVE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_LEGACY_SILENT VTK_LEGACY_SILENT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MAKE_INSTANTIATORS VTK_MAKE_INSTANTIATORS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MAX_THREADS VTK_MAX_THREADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPIRUN_EXE VTK_MPIRUN_EXE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_MAX_NUMPROCS VTK_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_NUMPROC_FLAG VTK_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_POSTFLAGS VTK_MPI_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PREFLAGS VTK_MPI_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_MPI_PRENUMPROC_FLAGS VTK_MPI_PRENUMPROC_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_NO_PYTHON_THREADS VTK_NO_PYTHON_THREADS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_OPENGL_HAS_OSMESA VTK_OPENGL_HAS_OSMESA-ADVANCED:INTERNAL=1 //ParaView requires the OpenVR factory be disabled VTK_OPENVR_OBJECT_FACTORY:INTERNAL=OFF //ADVANCED property for variable: VTK_PYTHON_VERSION VTK_PYTHON_VERSION-ADVANCED:INTERNAL=1 //STRINGS property for variable: VTK_QT_VERSION VTK_QT_VERSION-STRINGS:INTERNAL=4;5 VTK_QT_VERSION:INTERNAL=5 //ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS VTK_REPORT_OPENGL_ERRORS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS VTK_REPORT_OPENGL_ERRORS_IN_RELEASE_BUILDS-ADVANCED:INTERNAL=1 //STRINGS property for variable: VTK_SMP_IMPLEMENTATION_TYPE VTK_SMP_IMPLEMENTATION_TYPE-STRINGS:INTERNAL=Sequential;OpenMP;TBB //Result of TRY_COMPILE VTK_TEST_SYNC_BUILTINS_COMPILED:INTERNAL=TRUE //Result of TRY_COMPILE VTK_UNDEFINED_SYMBOLS_ALLOWED:INTERNAL=TRUE //hashed try_compile flags VTK_UNDEFINED_SYMBOLS_ALLOWED_hash:INTERNAL=9512b375c08c23cb252d40d83e21b1ba //ADVANCED property for variable: VTK_USE_64BIT_IDS VTK_USE_64BIT_IDS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_LARGE_DATA VTK_USE_LARGE_DATA-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_OFFSCREEN VTK_USE_OFFSCREEN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_OFFSCREEN_EGL VTK_USE_OFFSCREEN_EGL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_AUTOBAHN VTK_USE_SYSTEM_AUTOBAHN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_CGNS VTK_USE_SYSTEM_CGNS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_CINEMA_PYTHON VTK_USE_SYSTEM_CINEMA_PYTHON-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_CONSTANTLY VTK_USE_SYSTEM_CONSTANTLY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_DIY2 VTK_USE_SYSTEM_DIY2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_EXPAT VTK_USE_SYSTEM_EXPAT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_FREETYPE VTK_USE_SYSTEM_FREETYPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_GL2PS VTK_USE_SYSTEM_GL2PS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_GLEW VTK_USE_SYSTEM_GLEW-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_HDF5 VTK_USE_SYSTEM_HDF5-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_ICET VTK_USE_SYSTEM_ICET-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_INCREMENTAL VTK_USE_SYSTEM_INCREMENTAL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_JPEG VTK_USE_SYSTEM_JPEG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_JSONCPP VTK_USE_SYSTEM_JSONCPP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_LIBHARU VTK_USE_SYSTEM_LIBHARU-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_LIBRARIES VTK_USE_SYSTEM_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_LIBXML2 VTK_USE_SYSTEM_LIBXML2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_LZ4 VTK_USE_SYSTEM_LZ4-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_MPI4PY VTK_USE_SYSTEM_MPI4PY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_NETCDF VTK_USE_SYSTEM_NETCDF-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_NETCDFCPP VTK_USE_SYSTEM_NETCDFCPP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_OGGTHEORA VTK_USE_SYSTEM_OGGTHEORA-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_PNG VTK_USE_SYSTEM_PNG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_PROTOBUF VTK_USE_SYSTEM_PROTOBUF-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_PUGIXML VTK_USE_SYSTEM_PUGIXML-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_PYGMENTS VTK_USE_SYSTEM_PYGMENTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_QTTESTING VTK_USE_SYSTEM_QTTESTING-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_SIX VTK_USE_SYSTEM_SIX-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_TIFF VTK_USE_SYSTEM_TIFF-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_TWISTED VTK_USE_SYSTEM_TWISTED-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_XDMF2 VTK_USE_SYSTEM_XDMF2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_ZLIB VTK_USE_SYSTEM_ZLIB-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_SYSTEM_ZOPE VTK_USE_SYSTEM_ZOPE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_TK VTK_USE_TK-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_USE_X VTK_USE_X-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_VPIC_USE_MPI VTK_VPIC_USE_MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_WARN_ON_DISPATCH_FAILURE VTK_WARN_ON_DISPATCH_FAILURE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_WRAP_HINTS VTK_WRAP_HINTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_WRAP_JAVA VTK_WRAP_JAVA-ADVANCED:INTERNAL=1 //Should VTK Python wrapping be built? VTK_WRAP_PYTHON:INTERNAL=ON //ADVANCED property for variable: VTK_WRAP_TCL VTK_WRAP_TCL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_XDMF_USE_MPI VTK_XDMF_USE_MPI-ADVANCED:INTERNAL=1 //Result of TEST_BIG_ENDIAN WORDS_BIGENDIAN:INTERNAL=0 //ADVANCED property for variable: XDMF_BUILD_MPI XDMF_BUILD_MPI-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_HAS_NDGM XDMF_HAS_NDGM-ADVANCED:INTERNAL=1 //Whether streams support 64-bit types XDMF_HAVE_64BIT_STREAMS:INTERNAL=1 //ADVANCED property for variable: XDMF_HAVE_FCNTL XDMF_HAVE_FCNTL-ADVANCED:INTERNAL=1 //Have include malloc.h XDMF_HAVE_MALLOC_H:INTERNAL=1 //ADVANCED property for variable: XDMF_HAVE_MMAN XDMF_HAVE_MMAN-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_HAVE_NETINET XDMF_HAVE_NETINET-ADVANCED:INTERNAL=1 XDMF_REGENERATE_WRAPPERS:INTERNAL=OFF XDMF_REGENERATE_YACCLEX:INTERNAL=OFF //CHECK_TYPE_SIZE: sizeof(char) XDMF_SIZEOF_CHAR:INTERNAL=1 //CHECK_TYPE_SIZE: sizeof(double) XDMF_SIZEOF_DOUBLE:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(float) XDMF_SIZEOF_FLOAT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(int) XDMF_SIZEOF_INT:INTERNAL=4 //CHECK_TYPE_SIZE: sizeof(long) XDMF_SIZEOF_LONG:INTERNAL=8 //CHECK_TYPE_SIZE: sizeof(short) XDMF_SIZEOF_SHORT:INTERNAL=2 //ADVANCED property for variable: XDMF_USE_BZIP2 XDMF_USE_BZIP2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_USE_GZIP XDMF_USE_GZIP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: XDMF_USE_MYSQL XDMF_USE_MYSQL-ADVANCED:INTERNAL=1 XDMF_WRAP_CSHARP:INTERNAL=OFF XDMF_WRAP_PYTHON:INTERNAL=OFF XDMF_WRAP_TCL:INTERNAL=OFF //ADVANCED property for variable: XIAR XIAR-ADVANCED:INTERNAL=1 //Have include unistd.h Z_HAVE_UNISTD_H:INTERNAL=1 //CMAKE_INSTALL_PREFIX during last run _GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX:INTERNAL=/home/kre0214/.local/easybuild/software/ParaView/5.4.0-intel-2017a-mpi-OSPRay-TEST //ParaView has been configured __paraview_configured:INTERNAL=TRUE //Result of TEST_BIG_ENDIAN bigendian:INTERNAL=0 //ADVANCED property for variable: embree_DIR embree_DIR-ADVANCED:INTERNAL=1 //Have function MPI_Status_fc2 f2c_defined:INTERNAL= //Have function MPI_Type_create_f90_integer f90_integer_defined:INTERNAL=1 //CHECK_TYPE_SIZE: INT16 unknown int16:INTERNAL= //CHECK_TYPE_SIZE: INT32 unknown int32:INTERNAL= //CHECK_TYPE_SIZE: INT8 unknown int8:INTERNAL= protobut_determine_hash_namespace_done:INTERNAL=TRUE protobut_pthread_test_done:INTERNAL=TRUE pthread_test_result:INTERNAL=PTHREAD_CREATE_JOINABLE From anna.baburin at web.de Tue Aug 1 09:18:14 2017 From: anna.baburin at web.de (Anna Baburin) Date: Tue, 1 Aug 2017 15:18:14 +0200 Subject: [Paraview] Carrier deformation ParaView Message-ID: An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 1 10:00:05 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 1 Aug 2017 10:00:05 -0400 Subject: [Paraview] Carrier deformation ParaView In-Reply-To: References: Message-ID: Do you have sample dataset that you can share? That'll make it easier. Thanks. Utkarsh On Tue, Aug 1, 2017 at 9:18 AM, Anna Baburin wrote: > Hello, > > I?m using a ParaView Version 4.3.1. > > I'm trying to figure out how to measure the carrier deformation of an bolt > (in x, y and z axis). > > Can somebody help me? > > Thank you > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nqfrench9 at gmail.com Tue Aug 1 10:42:32 2017 From: nqfrench9 at gmail.com (Nick French) Date: Tue, 1 Aug 2017 09:42:32 -0500 Subject: [Paraview] Python View Visualization Message-ID: Hi, I've created a ParaView plugin (.xml file) that takes an input .txt file and creates an image (similar to this example: https://www.paraview.org/Wiki/Python_Programmable_Filter#Gen erating_Data_.28Programmable_Source.29). Now I want add some script to my python code that will allow for matplotlib plots to be made in a separate window. It seems like this is possible from Figure 4.15 of the most recent guide. Is there any easy way to do this? I made up the following script to add to the end of my code to just generate a simple histogram, but so far nothing shows up. I've also tested it in the Programmable Source python script box with no luck. from paraview import python_view figure = python_view.matplotlib_figure (100 , 100) ax = figure.add_subplot(1,1,1) ax.hist([4, 21, 4, 5, 2, 5, 6, 23, 21, 12, 11, 5], bins =10) python_view.figure_to_image(figure) I've also tried to create a 'PythonView', but all that does is create a black screen. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric.lynch at gmail.com Tue Aug 1 13:16:29 2017 From: eric.lynch at gmail.com (Eric Lynch) Date: Tue, 1 Aug 2017 13:16:29 -0400 Subject: [Paraview] Bug in PLOT3D meta reader Message-ID: I believe there is a bug in the PLOT3D metafile reader. I've attached two PLOT3D meshes and a metafile. Version 5.4.1 appears to read the metafile successfully. After reading it, I can see the outline of the two blocks in the first mesh file. If I advance to the next time step, I can see the outline of the three blocks in the second mesh. If I then go back to the previous time step, I get an error message saying: ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/IO/Parallel/vtkMultiBlockPLOT3DReader.cxx, line 1397 vtkMPIMultiBlockPLOT3DReader (0x6b53260): Encountered premature end-of-file while reading the geometry file (or the file is corrupt). ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784 vtkCompositeDataPipeline (0x6946da0): Algorithm vtkMPIMultiBlockPLOT3DReader(0x6b53260) returned failure for request: vtkInformation (0x68935b0) Debug: Off Modified Time: 982828 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA ALGORITHM_AFTER_FORWARD: 1 FROM_OUTPUT_PORT: 0 FORWARD_DIRECTION: 0 To my knowledge, the last version without this bug was 4.3.1. Thanks, Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cart01.x Type: application/octet-stream Size: 42620 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cart02.x Type: application/octet-stream Size: 48120 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paraview.p3d Type: application/octet-stream Size: 136 bytes Desc: not available URL: From rccm.kyoshimi at gmail.com Wed Aug 2 00:28:39 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Wed, 2 Aug 2017 13:28:39 +0900 Subject: [Paraview] Bug in PLOT3D meta reader In-Reply-To: References: Message-ID: Hello Eric, If the number of blocks in dataset decreases over time steps then vtkMultiBlockPLOT3DReader seems to fail to count it. For your information, I tried commenting out the line 822 in ParaView-v5.4.0/VTK/IO/Parallel/vtkMultiBlockPLOT3DReader.cxx and this worked with your data. ----- if ( numGrid > (int)this->Internal->Dimensions.size() ) { this->Internal->Dimensions.resize(numGrid); } => //if ( numGrid > (int)this->Internal->Dimensions.size() ) { this->Internal->Dimensions.resize(numGrid); } ----- Thanks, yoshimi 2017-08-02 2:16 GMT+09:00 Eric Lynch : > I believe there is a bug in the PLOT3D metafile reader. I've attached two > PLOT3D meshes and a metafile. Version 5.4.1 appears to read the metafile > successfully. After reading it, I can see the outline of the two blocks in > the first mesh file. If I advance to the next time step, I can see the > outline of the three blocks in the second mesh. If I then go back to the > previous time step, I get an error message saying: > > > > ERROR: In > /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/IO/Parallel/vtkMultiBlockPLOT3DReader.cxx, > line 1397 vtkMPIMultiBlockPLOT3DReader (0x6b53260): Encountered premature > end-of-file while reading the geometry file (or the file is corrupt). > > > > ERROR: In > /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, > line 784 vtkCompositeDataPipeline (0x6946da0): Algorithm > vtkMPIMultiBlockPLOT3DReader(0x6b53260) returned failure for request: > vtkInformation (0x68935b0) > > Debug: Off > > Modified Time: 982828 > > Reference Count: 1 > > Registered Events: (none) > > Request: REQUEST_DATA > > ALGORITHM_AFTER_FORWARD: 1 > > FROM_OUTPUT_PORT: 0 > > FORWARD_DIRECTION: 0 > > > > To my knowledge, the last version without this bug was 4.3.1. > > > > Thanks, > > Eric > > > _______________________________________________ > 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 daibane at sandia.gov Wed Aug 2 11:14:31 2017 From: daibane at sandia.gov (Ibanez, Daniel Alejandro) Date: Wed, 2 Aug 2017 15:14:31 +0000 Subject: [Paraview] Building Catalyst for Albany Message-ID: <20601BFD-D6F9-4871-880A-19C7B2C81830@contoso.com> Hello, I?m trying to revive the integration of Catalyst into the Albany application. I?ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and configured like this: #!/bin/bash -ex $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \ -DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \ -DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \ -DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \ 2>&1 | tee config_log But the install directory doesn?t contain any headers or ParaViewConfig.cmake files. In Albany, the following is done: find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst) include("${PARAVIEW_USE_FILE}") target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst) Where am I going wrong? What is it I should be installing? Thanks! Dan Ibanez -------------- next part -------------- An HTML attachment was scrubbed... URL: From daibane at sandia.gov Wed Aug 2 11:19:09 2017 From: daibane at sandia.gov (Ibanez, Daniel Alejandro) Date: Wed, 2 Aug 2017 15:19:09 +0000 Subject: [Paraview] [EXTERNAL] Building Catalyst for Albany In-Reply-To: <20601BFD-D6F9-4871-880A-19C7B2C81830@contoso.com> References: <20601BFD-D6F9-4871-880A-19C7B2C81830@contoso.com> Message-ID: <1B0519A6-609B-4CC8-ACFD-C4BC85C0B3D8@sandia.gov> It seems I can point Albany at my build directory of Catalyst, although I wonder why these things aren?t available in the install directory. From: ParaView on behalf of "Ibanez, Daniel Alejandro" Date: Wednesday, August 2, 2017 at 9:14 AM To: "paraview at paraview.org" Subject: [EXTERNAL] [Paraview] Building Catalyst for Albany Hello, I?m trying to revive the integration of Catalyst into the Albany application. I?ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and configured like this: #!/bin/bash -ex $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \ -DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \ -DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \ -DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \ 2>&1 | tee config_log But the install directory doesn?t contain any headers or ParaViewConfig.cmake files. In Albany, the following is done: find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst) include("${PARAVIEW_USE_FILE}") target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst) Where am I going wrong? What is it I should be installing? Thanks! Dan Ibanez -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Aug 2 12:27:24 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 2 Aug 2017 12:27:24 -0400 Subject: [Paraview] [EXTERNAL] Building Catalyst for Albany In-Reply-To: <1B0519A6-609B-4CC8-ACFD-C4BC85C0B3D8@sandia.gov> References: <20601BFD-D6F9-4871-880A-19C7B2C81830@contoso.com> <1B0519A6-609B-4CC8-ACFD-C4BC85C0B3D8@sandia.gov> Message-ID: Hi Dan, In order to work with an install directory you need to enable PARAVIEW_INSTALL_DEVELOPMENT_FILES during your CMake configuration. I personally just use my build directory for linking simulations with Catalyst though. Best, Andy On Wed, Aug 2, 2017 at 11:19 AM, Ibanez, Daniel Alejandro < daibane at sandia.gov> wrote: > It seems I can point Albany at my *build* directory of Catalyst, although > I wonder why these things aren?t available in the *install* directory. > > > > *From: *ParaView on behalf of "Ibanez, > Daniel Alejandro" > *Date: *Wednesday, August 2, 2017 at 9:14 AM > *To: *"paraview at paraview.org" > *Subject: *[EXTERNAL] [Paraview] Building Catalyst for Albany > > > > Hello, > > > > I?m trying to revive the integration of Catalyst into the Albany > application. > > I?ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and > configured like this: > > > > #!/bin/bash -ex > > $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh > $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \ > > -DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \ > > -DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \ > > -DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \ > > 2>&1 | tee config_log > > > > But the install directory doesn?t contain any headers or > ParaViewConfig.cmake files. > > In Albany, the following is done: > > > > find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst) > > include("${PARAVIEW_USE_FILE}") > > > > target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst) > > > > > > Where am I going wrong? What is it I should be installing? > > > > Thanks! > > > > Dan Ibanez > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daibane at sandia.gov Wed Aug 2 12:30:18 2017 From: daibane at sandia.gov (Ibanez, Daniel Alejandro) Date: Wed, 2 Aug 2017 16:30:18 +0000 Subject: [Paraview] [EXTERNAL] Building Catalyst for Albany In-Reply-To: References: <20601BFD-D6F9-4871-880A-19C7B2C81830@contoso.com> <1B0519A6-609B-4CC8-ACFD-C4BC85C0B3D8@sandia.gov> Message-ID: Ah, that?s the magic flag. Thanks, Andy! From: Andy Bauer Date: Wednesday, August 2, 2017 at 10:27 AM To: "Ibanez, Daniel Alejandro" Cc: "paraview at paraview.org" Subject: Re: [Paraview] [EXTERNAL] Building Catalyst for Albany Hi Dan, In order to work with an install directory you need to enable PARAVIEW_INSTALL_DEVELOPMENT_FILES during your CMake configuration. I personally just use my build directory for linking simulations with Catalyst though. Best, Andy On Wed, Aug 2, 2017 at 11:19 AM, Ibanez, Daniel Alejandro > wrote: It seems I can point Albany at my build directory of Catalyst, although I wonder why these things aren?t available in the install directory. From: ParaView > on behalf of "Ibanez, Daniel Alejandro" > Date: Wednesday, August 2, 2017 at 9:14 AM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Building Catalyst for Albany Hello, I?m trying to revive the integration of Catalyst into the Albany application. I?ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and configured like this: #!/bin/bash -ex $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \ -DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \ -DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \ -DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \ 2>&1 | tee config_log But the install directory doesn?t contain any headers or ParaViewConfig.cmake files. In Albany, the following is done: find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst) include("${PARAVIEW_USE_FILE}") target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst) Where am I going wrong? What is it I should be installing? Thanks! Dan Ibanez _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From jie.cheng at kitware.com Wed Aug 2 13:58:36 2017 From: jie.cheng at kitware.com (Jie Cheng) Date: Wed, 2 Aug 2017 13:58:36 -0400 Subject: [Paraview] Fix PLOT3D reader Message-ID: Hi Eric Thank you for reporting this bug with a nice example! You can find the cause and fix of this bug in this merge request . Thanks Jie Cheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Aug 2 16:01:12 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 2 Aug 2017 16:01:12 -0400 Subject: [Paraview] ParaView 5.4.1-RC3 available for download Message-ID: On behalf of the ParaView development team, I am happy to announce that ParaView 5.4.1-RC3 is available for download. Binaries and source code are available from www.paraview.org/download The 5.4.1-RC3 bug fix release candidate features a couple improvements over 5.4.1-RC2: * A bug in the color mapping that in some cases incorrectly mapped some data values to the above-range color was fixed. * OSPRay can now be compiled in Cray programming environments and for the first time has support for Intel Skylake processors. Additional fixes since the release of ParaView 5.4.0 include: * The black render window observed on some systems when FXAA was enabled or an object's opacity was less than 1 has been fixed. * Field output for cells with non-straight edges has been corrected. * Derivatives for quadratic triangles are now computed correctly. * A bug that occurred when generating a Catalyst script with no images output has been fixed. * A problem with writing animations as AVIs was fixed. * Logic in the CGNS reader was updated to correctly read all solution nodes for each centering type when FlowSolutionPointers are missing. * Fixed crash in CGNS reader when moving forward in time. * Fixed problem with long-running animations not advancing past a certain number of time steps. * Resolved issue where changing one file path in the state file loader "Choose File Names" dialog also changed the file paths of other files with the same type. * Addressed problem with enumerated property dependencies in ParaViewWeb. * Added ability to change the font size in the ParaView user interface. * Fixed BoxLib3D file reader. * State files now properly support files with relative paths. * Removed inappropriate scalar bar scaling when saving large screen shots. Please report any problems you find with this release candidate on the mailing list or on the bug tracker at https://gitlab.kitware.com/paraview/paraview/issues Thanks! Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From lukas.kresta at gmail.com Thu Aug 3 07:46:18 2017 From: lukas.kresta at gmail.com (=?UTF-8?B?THVrw6HFoSBLcmVzdGE=?=) Date: Thu, 3 Aug 2017 13:46:18 +0200 Subject: [Paraview] Paraview Catalyst offscreen rendering In-Reply-To: References: Message-ID: Thank you. With new build from support I got new error: ERROR: In /apps/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 413 vtkTCPNetworkAccessManager (0x6edc60): Should I try to rebuild ParaView or now it is problem with firewall or something like that? 2017-07-27 20:13 GMT+02:00 Andy Bauer : > I think what you're missing is -DVTK_USE_X=OFF and probably > -DVTK_USE_OFFSCREEN=ON. If that doesn't work, please send your > CMakeCache.txt from your build directory. > > On Thu, Jul 27, 2017 at 5:48 AM, Luk?? Kresta > wrote: > >> it was build with easybuild with these parametrs: >> >> cmake /apps/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay/ParaView-v5.4.0/ >> >> -DCMAKE_INSTALL_PREFIX=/apps/all/ParaView/5.4.0-intel-2017a-mpi-OSPRay >> >> -DCMAKE_C_COMPILER='mpiicc' -DCMAKE_Fortran_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' >> >> -DCMAKE_CXX_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' -DCMAKE_CXX_COMPILER='mpiicpc' >> >> DCMAKE_Fortran_COMPILER='mpiifort' -DCMAKE_C_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' >> >> -DCMAKE_VERBOSE_MAKEFILE=ON -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DVTK_OPENGL_HAS_OSMESA=ON >> >> -DPARAVIEW_USE_MPI=ON -DOPENGL_INCLUDE_DIR=$EBROOTMESA/include -DOPENGL_gl_LIBRARY=$EBROOTMESA/lib/libGL.so >> >> -DOSMESA_INCLUDE_DIR=$EBROOTMESA/include -DOSMESA_LIBRARY=$EBROOTMESA/lib/libOSMesa.so >> >> -DOPENGL_glu_LIBRARY=$EBROOTLIBGLU/lib/libGLU.so -DVTK_USE_SYSTEM_HDF5=ON -DPARAVIEW_ENABLE_PYTHON=ON -DBUILD_SHARED_LIBS=ON >> >> -DVTK_RENDERING_BACKEND=OpenGL2 -DPARAVIEW_USE_OSPRAY=ON -DOSPRAY_INSTALL_DIR=$EBROOT >> OSPRAY -DPARAVIEW_QT_VERSION=5 -DBUILD_TESTING=OFF >> >> >> I hope, it will help solve my problem. If you need, i can send you complete log. >> >> >> 2017-07-26 17:37 GMT+02:00 Andy Bauer : >> >>> Hi, >>> >>> It sounds like you didn't properly build with OSMesa. If you share your >>> CMakeCache.txt from your ParaView build I can see if I can track down the >>> problem. >>> >>> Best, >>> Andy >>> >>> On Wed, Jul 26, 2017 at 11:20 AM, Luk?? Kresta >>> wrote: >>> >>>> Thank you, but I have ParaView build with OSMesa without X. If I run >>>> program with Catalyst(genereted script from ParaView, with render views) on >>>> cluster with mpi, ussually one render view will show, but on anothers >>>> process it crash with this error: ERROR: In .../ParaView-v5.4.0/VTK/Render >>>> ing/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819 >>>> vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I >>>> have the same error with pvserver with or without --use-offscreen-rendering >>>> or without pvserver. >>>> >>>> If i run Catalyst with script only for live visualization then the >>>> program go without problem but i dont get pictures which i want. Is there >>>> some posibility how fix the error or how to get pictures(with offscreen >>>> rendering)? >>>> >>>> 2017-07-14 16:24 GMT+02:00 Andy Bauer : >>>> >>>>> Hi, >>>>> >>>>> If you're not memory constrained I suggest just doing a full ParaView >>>>> build with OSMesa and X11 disabled. There are quite a few discussions on >>>>> the PV mailing list on how to do that. >>>>> >>>>> If you're memory constrained then I would suggest building with all of >>>>> the Catalyst editions enabled and see if that works for you. >>>>> >>>>> Best, >>>>> Andy >>>>> >>>>> On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I would like to ask, which Paraview Catalyst (python) script use(with >>>>>> render view or live visualization). If i want save images with offscreen >>>>>> rendering on HPC. On cluster is no gpu. And how to properly use it? >>>>>> >>>>>> Thank you for your help. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yzhzhang at ipe.ac.cn Thu Aug 3 08:51:26 2017 From: yzhzhang at ipe.ac.cn (=?GBK?B?1cXUptbe?=) Date: Thu, 3 Aug 2017 20:51:26 +0800 (GMT+08:00) Subject: [Paraview] What is the file format of vtkMolecule data type? Message-ID: Hello, I want to write a vtkMolecule data file using my code (not the API of VTK), but I don't know the format of this kind of data type. I can find detailed file format of Polydata, Structured Grid, etc. but I don't find anything about the vtkMolecule data type in the vtk user guide. I want to know where I can find something introducing the file format of vtkMolecule data type, or could you please send me some examples of this kind of data file? Thanks a lot! -Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Thu Aug 3 15:49:54 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Thu, 3 Aug 2017 16:49:54 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: Thank you, Sebastien. I will give a try! Do you believe it's best to rollback webpack to 1.x or to change the webpack.config.js in order to fit webpack 2.x API? Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > Based on the path given in the setup guide, you should copy the example > you want to reproduce inside ${ROOT}/src/* where the main example file > should be named index.js. > > Then you should be able to build your example using the npm command: "npm > run build". > > Maybe the vtk.js explanation might be easier to follow ( > https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_dependency.html), > but the concept is exactly the same. > As it is picking the example available here https://kitware.github. > io/vtk-js/examples/Cone.html | https://github.com/Kitware/ > vtk-js/tree/master/Examples/WebGL/Cone > and making a standalone application from it. > > Just be aware that vtk.js is using webpack2 which is not the case for > ParaViewWeb. > > Hope that helps, > > Seb > > > On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < > leonardopessanha74 at gmail.com> wrote: > >> Hi! >> >> I would like to know the steps in order to run simple example like the >> following one: >> >> https://kitware.github.io/paraviewweb/examples/Composite/index.html >> >> It doesn't need to be a really elaborated tutorial, but a simple one with >> the main things. >> I have little to no background in web development. >> >> What I managed to do so far was to create my own project and add >> paraviewweb to it like its described in https://kitware.github.io/para >> viewweb/docs/setup.html . >> >> I don't know what to do next but I believe that a great start would be to >> know where to put the source code in the example and how to run it. >> >> Thanks in advance, >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> _______________________________________________ >> 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 >> >> > > On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < > leonardopessanha74 at gmail.com> wrote: > >> Hi! >> >> I would like to know the steps in order to run simple example like the >> following one: >> >> https://kitware.github.io/paraviewweb/examples/Composite/index.html >> >> It doesn't need to be a really elaborated tutorial, but a simple one with >> the main things. >> I have little to no background in web development. >> >> What I managed to do so far was to create my own project and add >> paraviewweb to it like its described in https://kitware.github.io/para >> viewweb/docs/setup.html . >> >> I don't know what to do next but I believe that a great start would be to >> know where to put the source code in the example and how to run it. >> >> Thanks in advance, >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wink at saville.com Thu Aug 3 16:26:58 2017 From: wink at saville.com (Wink Saville) Date: Thu, 03 Aug 2017 20:26:58 +0000 Subject: [Paraview] An exported csv file is bad Message-ID: In this directory is a simulation of a left femur I opened sim_0_screws_everything_moderate_first_order.vtm in to paraview v5.4.0 running on Linux and then opened the spreadsheet view and exported the data as sim_0_screws_etmfo.csv (49MB). Looking at the data I notice that some data is incorrect, see sim_0_screws_etmfo.bad-1022-1027.csv , snippet below: 2,1022,46,0.0434841,0.0168761,-0.0693468,0, ... ,-3.55276e-07,1.38283e+06,-547066 2,1023,46,0.0434874,0.0183288,-0.0683755,0, ... ,-1.01147e-07,1.35185e+06,-804654 -210794,126838,259957,-389825,518195, ... ,-0.0697033,1024,0,2 -269021,165638,423761,-428135,564983, ... ,-0.0680892,1025,0,2 The correct data, see sim_0_screws_etmfo-1022-1027.csv , snippet below: 2,1022,46,0.0434841,0.0168761,-0.0693468,0, ... ,1.38283e+06,-547066 2,1023,46,0.0434874,0.0183288,-0.0683755,0, ... ,1.35185e+06,-804654 2,1024,46,0.0447487,0.0182134,-0.0697033,0, ... ,1.22664e+06,551217 2,1025,46,0.0450036,0.0176967,-0.0680892,0, ... ,1.41211e+06,892762 2,1026,46,0.0545377,-0.0139687,-0.0666425,0, ... ,1.2249e+06,1.2249e+06 Is this a known problem or have I done something wrong? -- Wink -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Thu Aug 3 16:42:05 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 3 Aug 2017 14:42:05 -0600 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: If I get to it, I'll do what I've done with vtk.js to support both. See: https://github.com/Kitware/vtk-js/blob/master/Utilities/config/dependency.js On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha wrote: > Thank you, Sebastien. I will give a try! > > Do you believe it's best to rollback webpack to 1.x or to change the > webpack.config.js in order to fit webpack 2.x API? > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain com>: > >> Based on the path given in the setup guide, you should copy the example >> you want to reproduce inside ${ROOT}/src/* where the main example file >> should be named index.js. >> >> Then you should be able to build your example using the npm command: "npm >> run build". >> >> Maybe the vtk.js explanation might be easier to follow ( >> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_dependency.html), >> but the concept is exactly the same. >> As it is picking the example available here https://kitware.github.io >> /vtk-js/examples/Cone.html | https://github.com/Kitware/v >> tk-js/tree/master/Examples/WebGL/Cone >> and making a standalone application from it. >> >> Just be aware that vtk.js is using webpack2 which is not the case for >> ParaViewWeb. >> >> Hope that helps, >> >> Seb >> >> >> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> Hi! >>> >>> I would like to know the steps in order to run simple example like the >>> following one: >>> >>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>> >>> It doesn't need to be a really elaborated tutorial, but a simple one >>> with the main things. >>> I have little to no background in web development. >>> >>> What I managed to do so far was to create my own project and add >>> paraviewweb to it like its described in https://kitware.github.io/para >>> viewweb/docs/setup.html . >>> >>> I don't know what to do next but I believe that a great start would be >>> to know where to put the source code in the example and how to run it. >>> >>> Thanks in advance, >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> _______________________________________________ >>> 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 >>> >>> >> >> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> Hi! >>> >>> I would like to know the steps in order to run simple example like the >>> following one: >>> >>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>> >>> It doesn't need to be a really elaborated tutorial, but a simple one >>> with the main things. >>> I have little to no background in web development. >>> >>> What I managed to do so far was to create my own project and add >>> paraviewweb to it like its described in https://kitware.github.io/para >>> viewweb/docs/setup.html . >>> >>> I don't know what to do next but I believe that a great start would be >>> to know where to put the source code in the example and how to run it. >>> >>> Thanks in advance, >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From smikhaylov_2011 at mail.ru Fri Aug 4 00:32:49 2017 From: smikhaylov_2011 at mail.ru (=?UTF-8?B?0KHQtdGA0LPQtdC5INCc0LjRhdCw0LnQu9C+0LI=?=) Date: Fri, 04 Aug 2017 07:32:49 +0300 Subject: [Paraview] =?utf-8?q?question_about_using_ParaView?= Message-ID: <1501821169.931088454@f175.i.mail.ru> Hello ! We have the following ?3D object: ? I want to? left cylinder in the center of the object and delete another part of the object. The result of such operation is cylinder. How can I do it? ? ? Best regards, Mikhaylov Sergey Company JSC " RN - UfaNIPIneft " Tel: (347) 293-60-10 ex. 2734 ? ---------------------------------------------------------------------- ---------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 143984 bytes Desc: not available URL: From u.utku.turuncoglu at be.itu.edu.tr Fri Aug 4 03:40:16 2017 From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE)) Date: Fri, 4 Aug 2017 10:40:16 +0300 Subject: [Paraview] question about using ParaView In-Reply-To: <1501821169.931088454@f175.i.mail.ru> References: <1501821169.931088454@f175.i.mail.ru> Message-ID: <743ba806-a8d2-2ad0-65e4-53bf264c613c@be.itu.edu.tr> Hi Mikhaylov, Did you try threshold filter? You could set a threshold value to extract specific region. Another possibility is to write a programmable filter (in Python) to perform more complex modifications in the object. I hope it helps. Regards, --ufuk On 04/08/2017 07:32, ?????? ???????? via ParaView wrote: > > Hello! > > We have the following 3D object: > > I want to left cylinder in the center of the object and delete > another part of the object. The result of such operation is cylinder. > > How can I do it? > > Best regards, Mikhaylov Sergey > > Company JSC"RN-UfaNIPIneft" > > Tel: (347) 293-60-10 ex. 2734 > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 143984 bytes Desc: not available URL: From cory.quammen at kitware.com Fri Aug 4 14:35:36 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 4 Aug 2017 14:35:36 -0400 Subject: [Paraview] [EXTERNAL] Excel Pivot Table like functionality In-Reply-To: <8aa51ddaf34849e2958d92bad7a27015@ES01AMSNLNT.srn.sandia.gov> References: <8aa51ddaf34849e2958d92bad7a27015@ES01AMSNLNT.srn.sandia.gov> Message-ID: Dennis, That's a fairly complex operation that you describe. I'm afraid there isn't anything canned to do this in ParaView. It should be possible with a fairly impressive Programmable Filter, though. Best regards, Cory On Mon, Jul 31, 2017 at 12:52 PM, Scott, W Alan wrote: > Kitware ? Ping? > > > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Dennis > Conklin > Sent: Monday, July 24, 2017 2:34 PM > To: Paraview (paraview at paraview.org) > Subject: [EXTERNAL] [Paraview] Excel Pivot Table like functionality > > > > All, > > > > So, I have a multi-block dataset (Exodus). Within each block, I have sets > of 360 elements which have a common index. So, in Block 1, elements 0-359 > have a cell variable called N_RING, which is 1. Elements 360-719, have > N_RING=2, etc. > > > > What I really want is the ability to operate on these sets. Imagine I have > an element variable called Ying, which is different for each element in the > model. I would like every element with N_RING=1 to have an element variable > of Ying_max assigned, which is the maximum value of Ying for any element > with N_RING=1. So, for example, elements 0-359 would be assigned a value > of Ying_max which is the maximum value of Ying in any of elements 0-359. > Elements 360-719 would be assigned a value of Ying_max which is the maximum > value for any element with N_RING=2. I would ideally also like to get min > and average. > > > > Is there any way to get max/min/average of a group consisting of a cell > variable index? - and to assign the output as element variables so I can > color by? > > > > Thanks for any hints. > > > > Dennis > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From shayan.nikoohemat at gmail.com Fri Aug 4 15:27:10 2017 From: shayan.nikoohemat at gmail.com (Shayan Nikoohemat) Date: Fri, 4 Aug 2017 21:27:10 +0200 Subject: [Paraview] add a field with a custom attribute to selected points Message-ID: I have a dataset of points, I select several points and I want to add an attribute to them and extract them. Then repeat this for some other selected points from the same dataset. At the end I append the selected datasets, and then from the field that I added and gave them attribute I should be able to discriminate the selections. I managed to select points and extract them, but I cannot add a field to them with a custom attribute. How is it possible? Thanks. Shayan -------------- next part -------------- An HTML attachment was scrubbed... URL: From rccm.kyoshimi at gmail.com Sat Aug 5 02:36:17 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Sat, 5 Aug 2017 15:36:17 +0900 Subject: [Paraview] An exported csv file is bad In-Reply-To: References: Message-ID: Hi Wink, This problem has already been reported as a bug. https://gitlab.kitware.com/paraview/paraview/issues/17169 https://gitlab.kitware.com/paraview/paraview/issues/17203 Thanks 2017-08-04 5:26 GMT+09:00 Wink Saville : > In this directory is a simulation of a left femur I opened > sim_0_screws_everything_moderate_first_order.vtm in to paraview v5.4.0 > running on Linux and then opened the spreadsheet view and exported the data > as sim_0_screws_etmfo.csv (49MB). Looking at the data I notice that some > data is incorrect, see sim_0_screws_etmfo.bad-1022-1027.csv, snippet below: > > 2,1022,46,0.0434841,0.0168761,-0.0693468,0, ... > ,-3.55276e-07,1.38283e+06,-547066 > 2,1023,46,0.0434874,0.0183288,-0.0683755,0, ... > ,-1.01147e-07,1.35185e+06,-804654 > -210794,126838,259957,-389825,518195, ... ,-0.0697033,1024,0,2 > -269021,165638,423761,-428135,564983, ... ,-0.0680892,1025,0,2 > > The correct data, see sim_0_screws_etmfo-1022-1027.csv, snippet below: > > 2,1022,46,0.0434841,0.0168761,-0.0693468,0, ... ,1.38283e+06,-547066 > 2,1023,46,0.0434874,0.0183288,-0.0683755,0, ... ,1.35185e+06,-804654 > 2,1024,46,0.0447487,0.0182134,-0.0697033,0, ... ,1.22664e+06,551217 > 2,1025,46,0.0450036,0.0176967,-0.0680892,0, ... ,1.41211e+06,892762 > 2,1026,46,0.0545377,-0.0139687,-0.0666425,0, ... ,1.2249e+06,1.2249e+06 > > Is this a known problem or have I done something wrong? > > -- Wink > > _______________________________________________ > 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 smikhaylov_2011 at mail.ru Sat Aug 5 04:24:20 2017 From: smikhaylov_2011 at mail.ru (=?UTF-8?B?0KHQtdGA0LPQtdC5INCc0LjRhdCw0LnQu9C+0LI=?=) Date: Sat, 05 Aug 2017 11:24:20 +0300 Subject: [Paraview] =?utf-8?q?question_about_programmable_filter?= Message-ID: <1501921460.743151962@f363.i.mail.ru> Hello ! We have the following ?3D object: ? I want to? left cylinder in the center of the object and delete another part of the object. The result of such operation is cylinder. Help me please write? a programmable filter (in Python)? to perform this modification in the object. ? ? Best regards, Sergey ? ---------------------------------------------------------------------- ---------------------------------------------------------------------- ---------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 143984 bytes Desc: not available URL: From aron.helser at kitware.com Sat Aug 5 13:19:12 2017 From: aron.helser at kitware.com (Aron Helser) Date: Sat, 5 Aug 2017 13:19:12 -0400 Subject: [Paraview] question about programmable filter In-Reply-To: <1501921460.743151962@f363.i.mail.ru> References: <1501921460.743151962@f363.i.mail.ru> Message-ID: Sergey, A good way to start writing something in Python is to use the 'start trace' in the Tools menu in ParaView. If you can perform the operation you want with the GUI in ParaView, this will show equivalent Python commands to perform those operations. Regards, Aron On Sat, Aug 5, 2017 at 4:24 AM, ?????? ???????? via ParaView < paraview at paraview.org> wrote: > Hello! > > We have the following 3D object: > > I want to left cylinder in the center of the object and delete another > part of the object. The result of such operation is cylinder. > > Help me please write a programmable filter (in Python) to perform this > modification in the object. > > > > > > Best regards, Sergey > > > > ------------------------------ > > ------------------------------ > > ------------------------------ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 143984 bytes Desc: not available URL: From rrossi at red-fluid.com Sat Aug 5 19:18:56 2017 From: rrossi at red-fluid.com (Riccardo Rossi) Date: Sun, 6 Aug 2017 01:18:56 +0200 Subject: [Paraview] Link between objects Message-ID: <000201d30e41$36d94c70$a48be550$@red-fluid.com> Hi. I'm a little confused about how links between objects are supposed to work. For example, if I create two clip filters and make a link between the "plane" property of the two objects, everything works fine. However, if I make the link between the two objects I would expect all the the properties to be updated automatically in the child object (as reported in the wiki) but this time the link seems not to work at all. Am I missing something? Thanks, Riccardo --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From juha_kortelainen at welho.net Sun Aug 6 13:30:32 2017 From: juha_kortelainen at welho.net (Juha Kortelainen) Date: Sun, 6 Aug 2017 20:30:32 +0300 Subject: [Paraview] Dynamic colouring of the geometry in the animation of warped eigenmodes Message-ID: <16ba2ed8-3177-4fa6-a879-375c150e5e36@welho.net> Hi all, I?m using the warp filter to visualise the computed eigenmodes of a structure (computed using a FEM code). Animating the eigenmodes works fine with the WarpByVector filter using the ScalarFactor as the animation variable. In addition to animating the deformation of the structure, I would like to apply colouring of the deformation vector field on the geometry so that the colour would change dynamically according to the magnitude of deformation during the animation. This can be done with the Salome platform?s ParaViS modile (a modified version of ParaView), which has an additional ScaleVector filter to do the colouring trick. Can this dynamic colouring be done with standard ParaView and if so, how is it done? - Juha - -------------- next part -------------- An HTML attachment was scrubbed... URL: From dennis_conklin at goodyear.com Sun Aug 6 14:00:39 2017 From: dennis_conklin at goodyear.com (Dennis Conklin) Date: Sun, 6 Aug 2017 18:00:39 +0000 Subject: [Paraview] [EXT] Re: [EXTERNAL] Excel Pivot Table like functionality In-Reply-To: References: <8aa51ddaf34849e2958d92bad7a27015@ES01AMSNLNT.srn.sandia.gov> Message-ID: Cory, I'm heading off on a month of vacation, but I'm looking at using the pivot table functionality in pandas within a Programmable filter. I'm not sure when I will get time to get back into this! Dennis -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Friday, August 04, 2017 2:36 PM To: Scott, W Alan Cc: Dennis Conklin ; Paraview (paraview at paraview.org) Subject: [EXT] Re: [Paraview] [EXTERNAL] Excel Pivot Table like functionality WARNING - External email; exercise caution. Dennis, That's a fairly complex operation that you describe. I'm afraid there isn't anything canned to do this in ParaView. It should be possible with a fairly impressive Programmable Filter, though. Best regards, Cory On Mon, Jul 31, 2017 at 12:52 PM, Scott, W Alan wrote: > Kitware ? Ping? > > > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of > Dennis Conklin > Sent: Monday, July 24, 2017 2:34 PM > To: Paraview (paraview at paraview.org) > Subject: [EXTERNAL] [Paraview] Excel Pivot Table like functionality > > > > All, > > > > So, I have a multi-block dataset (Exodus). Within each block, I have sets > of 360 elements which have a common index. So, in Block 1, elements 0-359 > have a cell variable called N_RING, which is 1. Elements 360-719, have > N_RING=2, etc. > > > > What I really want is the ability to operate on these sets. Imagine I have > an element variable called Ying, which is different for each element > in the model. I would like every element with N_RING=1 to have an > element variable of Ying_max assigned, which is the maximum value of Ying for any element > with N_RING=1. So, for example, elements 0-359 would be assigned a value > of Ying_max which is the maximum value of Ying in any of elements 0-359. > Elements 360-719 would be assigned a value of Ying_max which is the maximum > value for any element with N_RING=2. I would ideally also like to get min > and average. > > > > Is there any way to get max/min/average of a group consisting of a > cell variable index? - and to assign the output as element variables > so I can color by? > > > > Thanks for any hints. > > > > Dennis > > > _______________________________________________ > Powered by > https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&dat > a=01%7C01%7Cdennis_conklin%40goodyear.com%7Cd72609f7e8a64e94edb808d4db > 679a10%7C939e896692854a9a9f040887efe8aae0%7C0&sdata=FcCoY8cIzamH%2Bcah > p8rx2XTw%2BeOQkr1hcrbiar6eABk%3D&reserved=0 > > Visit other Kitware open-source projects at > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ki > tware.com%2Fopensource%2Fopensource.html&data=01%7C01%7Cdennis_conklin > %40goodyear.com%7Cd72609f7e8a64e94edb808d4db679a10%7C939e896692854a9a9 > f040887efe8aae0%7C0&sdata=rzMOj5ESh3oHjuW%2BHDedetSsbgzqMSexh0jpwvsPKR > Q%3D&reserved=0 > > Please keep messages on-topic and check the ParaView Wiki at: > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fparavi > ew.org%2FWiki%2FParaView&data=01%7C01%7Cdennis_conklin%40goodyear.com% > 7Cd72609f7e8a64e94edb808d4db679a10%7C939e896692854a9a9f040887efe8aae0% > 7C0&sdata=rAlabLkAZmggru4zAy1Iuk48lrUn0HTRO9wSVAp5ooU%3D&reserved=0 > > Search the list archives at: > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkma > il.org%2Fsearch%2F%3Fq%3DParaView&data=01%7C01%7Cdennis_conklin%40good > year.com%7Cd72609f7e8a64e94edb808d4db679a10%7C939e896692854a9a9f040887 > efe8aae0%7C0&sdata=W95mxbW6LD2LVm%2BAoXRGA4gq2PFzHBY3h8pQhKkpr4Q%3D&re > served=0 > > Follow this link to subscribe/unsubscribe: > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic > .kitware.com%2Fmailman%2Flistinfo%2Fparaview&data=01%7C01%7Cdennis_con > klin%40goodyear.com%7Cd72609f7e8a64e94edb808d4db679a10%7C939e896692854 > a9a9f040887efe8aae0%7C0&sdata=IlNNte5Ru4gJgZfjWFYSaA5OwLgYRxMt7UbnZ3XC > hWA%3D&reserved=0 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From mathieu.westphal at kitware.com Mon Aug 7 03:00:41 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 7 Aug 2017 09:00:41 +0200 Subject: [Paraview] Link between objects In-Reply-To: <000201d30e41$36d94c70$a48be550$@red-fluid.com> References: <000201d30e41$36d94c70$a48be550$@red-fluid.com> Message-ID: Hello Riccardo It should work and it does in most cases (not in yours though). You can try the following. - Create a Box - Create another Box - "Object" Link both box - Change a parameter in one box, *Apply* - Same parameter is changed in the other box as well As for your example with the slice (or clip, or any filter using a ProxyProperty) this does not seems to work and you indeed need to link the proxy property itself in order to obtain this. In terms of usability, it means that "Object" Link will not go down the object tree visible in the manager, but only link all property at the level of the object. I am unsure if this is a missing feature or a bug, in any case, feel free to open an issue in the bugtracker, I see that you've already created an account. Thanks for your report. Regards, Mathieu Westphal On Sun, Aug 6, 2017 at 1:18 AM, Riccardo Rossi wrote: > Hi. > > > > I?m a little confused about how links between objects are supposed to work. > > > > For example, if I create two clip filters and make a link between the > ?plane? property of the two objects, everything works fine. > > > > However, if I make the link between the two objects I would expect all the > the properties to be updated automatically in the child object (as reported > in the wiki) but this time the link seems not to work at all. > > > Am I missing something? > > > > Thanks, > > > > Riccardo > > > Virus-free. > www.avast.com > > <#m_950079471057631188_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrossi at red-fluid.com Mon Aug 7 03:51:26 2017 From: rrossi at red-fluid.com (Riccardo Rossi) Date: Mon, 7 Aug 2017 09:51:26 +0200 Subject: [Paraview] Link between objects In-Reply-To: References: <000201d30e41$36d94c70$a48be550$@red-fluid.com> Message-ID: <000201d30f51$fc63c180$f52b4480$@red-fluid.com> Hi Mathieu. I gave the box a try and works indeed. It would be nice though being able to link ?fully? any other object as clips or slices when comparing multiple dataset and spare the user from changing manually the properties of the filters in each dataset. As for the bugtracker, I?ve already opened a ticket concerning an issue when linking the proxy property ?plane? of the ?Plot over intersection curve? filter, which systematically crashes. Thanks for the feedback, Riccardo From: Mathieu Westphal [mailto:mathieu.westphal at kitware.com] Sent: Monday, August 07, 2017 9:01 AM To: Riccardo Rossi Cc: ParaView Subject: Re: [Paraview] Link between objects Hello Riccardo It should work and it does in most cases (not in yours though). You can try the following. - Create a Box - Create another Box - "Object" Link both box - Change a parameter in one box, Apply - Same parameter is changed in the other box as well As for your example with the slice (or clip, or any filter using a ProxyProperty) this does not seems to work and you indeed need to link the proxy property itself in order to obtain this. In terms of usability, it means that "Object" Link will not go down the object tree visible in the manager, but only link all property at the level of the object. I am unsure if this is a missing feature or a bug, in any case, feel free to open an issue in the bugtracker, I see that you've already created an account. Thanks for your report. Regards, Mathieu Westphal On Sun, Aug 6, 2017 at 1:18 AM, Riccardo Rossi > wrote: Hi. I?m a little confused about how links between objects are supposed to work. For example, if I create two clip filters and make a link between the ?plane? property of the two objects, everything works fine. However, if I make the link between the two objects I would expect all the the properties to be updated automatically in the child object (as reported in the wiki) but this time the link seems not to work at all. Am I missing something? Thanks, Riccardo Virus-free. www.avast.com _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 350 bytes Desc: not available URL: From cory.quammen at kitware.com Mon Aug 7 09:14:35 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 7 Aug 2017 09:14:35 -0400 Subject: [Paraview] question about programmable filter In-Reply-To: References: <1501921460.743151962@f363.i.mail.ru> Message-ID: Sergey, While Aron is correct about learning how to do Python scripting of the ParaView application via tracing, doing so won't necessarily help you write a Programmable Filter, which operates entirely without knowing that it is executing inside of ParaView. Tracing doesn't record the internal VTK operations that you would need to write in a programmable filter. Instead, it records the ParaView-level execution, which is higher level. Someone may help you with the filter if you provide a starting point showing what you tried and describing how it doesn't work. It is much less likely that someone will just write the filter for you. Best, Cory On Sat, Aug 5, 2017 at 1:19 PM, Aron Helser wrote: > Sergey, > A good way to start writing something in Python is to use the 'start > trace' in the Tools menu in ParaView. If you can perform the operation you > want with the GUI in ParaView, this will show equivalent Python commands to > perform those operations. > Regards, > Aron > > On Sat, Aug 5, 2017 at 4:24 AM, ?????? ???????? via ParaView < > paraview at paraview.org> wrote: > >> Hello! >> >> We have the following 3D object: >> >> I want to left cylinder in the center of the object and delete another >> part of the object. The result of such operation is cylinder. >> >> Help me please write a programmable filter (in Python) to perform this >> modification in the object. >> >> >> >> >> >> Best regards, Sergey >> >> >> >> ------------------------------ >> >> ------------------------------ >> >> ------------------------------ >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 143984 bytes Desc: not available URL: From cory.quammen at kitware.com Mon Aug 7 09:27:28 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 7 Aug 2017 09:27:28 -0400 Subject: [Paraview] Dynamic colouring of the geometry in the animation of warped eigenmodes In-Reply-To: <16ba2ed8-3177-4fa6-a879-375c150e5e36@welho.net> References: <16ba2ed8-3177-4fa6-a879-375c150e5e36@welho.net> Message-ID: On Sun, Aug 6, 2017 at 1:30 PM, Juha Kortelainen wrote: > Hi all, > > I?m using the warp filter to visualise the computed eigenmodes of a > structure (computed using a FEM code). Animating the eigenmodes works fine > with the WarpByVector filter using the ScalarFactor as the animation > variable. In addition to animating the deformation of the structure, I would > like to apply colouring of the deformation vector field on the geometry so > that the colour would change dynamically according to the magnitude of > deformation during the animation. This can be done with the Salome > platform?s ParaViS modile (a modified version of ParaView), which has an > additional ScaleVector filter to do the colouring trick. Can this dynamic > colouring be done with standard ParaView and if so, how is it done? Yes, with some work. Take a look at this blog post for the general idea: https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ Basically, you can create XML plugins based on the Programmable Filter that feature some properties, such as a scale factor. The scale factor property should be exposed in the animation controls. Within your Programmable Filter script, you can perform the scaling of the vector with that scale factor property value. There are many examples of Python scripts for the Programmable Filter in Section 13.3 the ParaView Guide to get you started. HTH, Cory > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From andy.bauer at kitware.com Mon Aug 7 09:41:00 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 7 Aug 2017 09:41:00 -0400 Subject: [Paraview] Paraview Catalyst offscreen rendering In-Reply-To: References: Message-ID: Hi, I'd recommend trying to run pvserver or pvbatch in parallel and see if you get the same error. My guess is that it's a connection or firewall issue. On Thu, Aug 3, 2017 at 7:46 AM, Luk?? Kresta wrote: > Thank you. With new build from support I got new error: ERROR: In > /apps/easybuild/build/ParaView/5.4.0/intel-2017a- > mpi-OSPRay-TEST/ParaView-v5.4.0/ParaViewCore/ClientServerCore/Core/ > vtkTCPNetworkAccessManager.cxx, line 413 > vtkTCPNetworkAccessManager (0x6edc60): > Should I try to rebuild ParaView or now it is problem with firewall or > something like that? > > 2017-07-27 20:13 GMT+02:00 Andy Bauer : > >> I think what you're missing is -DVTK_USE_X=OFF and probably >> -DVTK_USE_OFFSCREEN=ON. If that doesn't work, please send your >> CMakeCache.txt from your build directory. >> >> On Thu, Jul 27, 2017 at 5:48 AM, Luk?? Kresta >> wrote: >> >>> it was build with easybuild with these parametrs: >>> >>> cmake /apps/easybuild/build/ParaView/5.4.0/intel-2017a-mpi-OSPRay/ParaView-v5.4.0/ >>> >>> -DCMAKE_INSTALL_PREFIX=/apps/all/ParaView/5.4.0-intel-2017a-mpi-OSPRay >>> >>> -DCMAKE_C_COMPILER='mpiicc' -DCMAKE_Fortran_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' >>> >>> -DCMAKE_CXX_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' -DCMAKE_CXX_COMPILER='mpiicpc' >>> >>> DCMAKE_Fortran_COMPILER='mpiifort' -DCMAKE_C_FLAGS='-O2 -xHost -ftz -fp-speculation=safe -fp-model source -fPIC' >>> >>> -DCMAKE_VERBOSE_MAKEFILE=ON -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DVTK_OPENGL_HAS_OSMESA=ON >>> >>> -DPARAVIEW_USE_MPI=ON -DOPENGL_INCLUDE_DIR=$EBROOTMESA/include -DOPENGL_gl_LIBRARY=$EBROOTMESA/lib/libGL.so >>> >>> -DOSMESA_INCLUDE_DIR=$EBROOTMESA/include -DOSMESA_LIBRARY=$EBROOTMESA/lib/libOSMesa.so >>> >>> -DOPENGL_glu_LIBRARY=$EBROOTLIBGLU/lib/libGLU.so -DVTK_USE_SYSTEM_HDF5=ON -DPARAVIEW_ENABLE_PYTHON=ON -DBUILD_SHARED_LIBS=ON >>> >>> -DVTK_RENDERING_BACKEND=OpenGL2 -DPARAVIEW_USE_OSPRAY=ON -DOSPRAY_INSTALL_DIR=$EBROOT >>> OSPRAY -DPARAVIEW_QT_VERSION=5 -DBUILD_TESTING=OFF >>> >>> >>> I hope, it will help solve my problem. If you need, i can send you complete log. >>> >>> >>> 2017-07-26 17:37 GMT+02:00 Andy Bauer : >>> >>>> Hi, >>>> >>>> It sounds like you didn't properly build with OSMesa. If you share your >>>> CMakeCache.txt from your ParaView build I can see if I can track down the >>>> problem. >>>> >>>> Best, >>>> Andy >>>> >>>> On Wed, Jul 26, 2017 at 11:20 AM, Luk?? Kresta >>>> wrote: >>>> >>>>> Thank you, but I have ParaView build with OSMesa without X. If I run >>>>> program with Catalyst(genereted script from ParaView, with render views) on >>>>> cluster with mpi, ussually one render view will show, but on anothers >>>>> process it crash with this error: ERROR: In .../ParaView-v5.4.0/VTK/Render >>>>> ing/OpenGL2/vtkOpenGLRenderWindow.cxx, line 819 >>>>> vtkXOpenGLRenderWindow (0x3f7cbf0): GLEW could not be initialized. I >>>>> have the same error with pvserver with or without --use-offscreen-rendering >>>>> or without pvserver. >>>>> >>>>> If i run Catalyst with script only for live visualization then the >>>>> program go without problem but i dont get pictures which i want. Is there >>>>> some posibility how fix the error or how to get pictures(with offscreen >>>>> rendering)? >>>>> >>>>> 2017-07-14 16:24 GMT+02:00 Andy Bauer : >>>>> >>>>>> Hi, >>>>>> >>>>>> If you're not memory constrained I suggest just doing a full ParaView >>>>>> build with OSMesa and X11 disabled. There are quite a few discussions on >>>>>> the PV mailing list on how to do that. >>>>>> >>>>>> If you're memory constrained then I would suggest building with all >>>>>> of the Catalyst editions enabled and see if that works for you. >>>>>> >>>>>> Best, >>>>>> Andy >>>>>> >>>>>> On Fri, Jul 14, 2017 at 3:31 AM, Luk?? Kresta >>>>> > wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I would like to ask, which Paraview Catalyst (python) script >>>>>>> use(with render view or live visualization). If i want save images with >>>>>>> offscreen rendering on HPC. On cluster is no gpu. And how to properly use >>>>>>> it? >>>>>>> >>>>>>> Thank you for your help. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Aug 7 12:46:51 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 7 Aug 2017 16:46:51 +0000 Subject: [Paraview] Dynamic colouring of the geometry in the animation of warped eigenmodes Message-ID: <767f8684bc6b48d4a182e36a2ec821b4@ES08AMSNLNT.srn.sandia.gov> Juha, As Cory said you can create a plugin to replicate this behavior, but I believe you can also get similar behavior through a collection of filters. Although this is a bit cumbersome, you can try the following steps: 1. Before applying the WarpByVector filter, add the Calculator filter to your data. Set the "Result Array Name" to "OriginalCoords" and the expression to simply "coords". This will capture the point coordinates before warping. 2. Apply WarpByVector to this calculator filter as you did before to the FEM data. 3. Apply another Calculator filter to the output of WarpByVector. This time, set the "Result Array Name" to "ActualDisplacement" and the expression to "coords-OriginalCoords". This will capture the actual displacement applied after the scale factor is used. 4. Color your data by the "ActualDispalcement" field. 5. Set up your animation of the "ScaleFactor" for the WarpByVector filter as you did before. You should now see "dynamic" colors based on the magnitude of the actual displacement. -Ken -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Cory Quammen Sent: Monday, August 7, 2017 7:27 AM To: Juha Kortelainen Cc: ParaView Subject: [EXTERNAL] Re: [Paraview] Dynamic colouring of the geometry in the animation of warped eigenmodes On Sun, Aug 6, 2017 at 1:30 PM, Juha Kortelainen wrote: > Hi all, > > I?m using the warp filter to visualise the computed eigenmodes of a > structure (computed using a FEM code). Animating the eigenmodes works > fine with the WarpByVector filter using the ScalarFactor as the > animation variable. In addition to animating the deformation of the > structure, I would like to apply colouring of the deformation vector > field on the geometry so that the colour would change dynamically > according to the magnitude of deformation during the animation. This > can be done with the Salome platform?s ParaViS modile (a modified > version of ParaView), which has an additional ScaleVector filter to do > the colouring trick. Can this dynamic colouring be done with standard ParaView and if so, how is it done? Yes, with some work. Take a look at this blog post for the general idea: https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ Basically, you can create XML plugins based on the Programmable Filter that feature some properties, such as a scale factor. The scale factor property should be exposed in the animation controls. Within your Programmable Filter script, you can perform the scaling of the vector with that scale factor property value. There are many examples of Python scripts for the Programmable Filter in Section 13.3 the ParaView Guide to get you started. HTH, Cory > > _______________________________________________ > 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 >J > 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 amylaunspach at gmail.com Mon Aug 7 14:55:33 2017 From: amylaunspach at gmail.com (Amelia Launspach) Date: Mon, 7 Aug 2017 13:55:33 -0500 Subject: [Paraview] ParaView newbie with a (hopefully) simple question Message-ID: Hello everyone, I was assigned a small project on ParaView and I need help getting started. I need to find a way to loop through N number of source files in the Pipeline Browser and return the count for number N and group them together using the group dataset filter. Each time I upload the data it will be a different number of files that look something like this: [image: Inline image 1] Right now there are N=22 files but the N will differ each time. So I want to create a script/or programmable filter that will loop through every file in the pipeline browser, add it to a group dataset, and lastly print the number N. How would I begin to do this? Can this be done with a simple script that I can just copy and paste each time in the shell? Would it be easier to build a programmable filter? Any help would be appreciated ! Thanks, Amy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-08-07 at 1.25.06 PM.png Type: image/png Size: 130460 bytes Desc: not available URL: From u.utku.turuncoglu at be.itu.edu.tr Mon Aug 7 15:01:18 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Mon, 7 Aug 2017 22:01:18 +0300 (EEST) Subject: [Paraview] ParaView newbie with a (hopefully) simple question In-Reply-To: References: Message-ID: <58961.160.75.140.193.1502132478.squirrel@webmail.be.itu.edu.tr> Hi, You can use trace feature (under Tools -> Start Trace) of ParaView to generate desired Python script with little bit modification. For example, I generated a Python script to open single pieces of multi-piece dataset and add loop to script to automatically open them, from paraview.simple import * import glob, os paraview.simple._DisableFirstRenderCameraReset() os.chdir("/Users/turuncu/Desktop/a") for file in glob.glob("atmos_CROSSpoint*.vtk"): # create a new 'Legacy VTK Reader' ocean_CROSSpoint9600vtk = LegacyVTKReader(FileNames=[file]) ... ... ... So, with same logic you could create a script that group two file and modify the Python script to make it automatic for any number of files. I hope it helps, Regards, --ufuk > Hello everyone, > > I was assigned a small project on ParaView and I need help getting > started. > > I need to find a way to loop through N number of source files in the > Pipeline Browser and return the count for number N and group them together > using the group dataset filter. > > Each time I upload the data it will be a different number of files that > look something like this: > [image: Inline image 1] > Right now there are N=22 files but the N will differ each time. So I want > to create a script/or programmable filter that will loop through every > file > in the pipeline browser, add it to a group dataset, and lastly print the > number N. > > How would I begin to do this? Can this be done with a simple script that I > can just copy and paste each time in the shell? Would it be easier to > build > a programmable filter? > > Any help would be appreciated ! > > Thanks, > Amy > _______________________________________________ > 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 shawn.waldon at kitware.com Mon Aug 7 15:08:31 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Mon, 7 Aug 2017 15:08:31 -0400 Subject: [Paraview] ParaView newbie with a (hopefully) simple question In-Reply-To: References: Message-ID: Hi Amy, The easiest way would probably be this: ParaView should automatically recognize the sequence of numbered files and give you an option to load "mbdout_r000102_s000001_e..vtm" in the file dialog. This will load the data as a time series with one data file per step. Then you can apply the "Group Time Steps" filter which reads all the time steps into a multiblock dataset (the equivalent of running Group Dataset on them). Of course if your dataset has a time dimension too, you will have trouble reading that since you are already using time for something else... I see Ufuk has replied since I started typing this and his python scripting approach may be superior if your dataset has time steps already. HTH, Shawn On Mon, Aug 7, 2017 at 2:55 PM, Amelia Launspach wrote: > Hello everyone, > > I was assigned a small project on ParaView and I need help getting started. > > I need to find a way to loop through N number of source files in the > Pipeline Browser and return the count for number N and group them together > using the group dataset filter. > > Each time I upload the data it will be a different number of files that > look something like this: > [image: Inline image 1] > Right now there are N=22 files but the N will differ each time. So I want > to create a script/or programmable filter that will loop through every file > in the pipeline browser, add it to a group dataset, and lastly print the > number N. > > How would I begin to do this? Can this be done with a simple script that I > can just copy and paste each time in the shell? Would it be easier to build > a programmable filter? > > Any help would be appreciated ! > > Thanks, > Amy > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-08-07 at 1.25.06 PM.png Type: image/png Size: 130460 bytes Desc: not available URL: From shawn.waldon at kitware.com Mon Aug 7 15:36:25 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Mon, 7 Aug 2017 15:36:25 -0400 Subject: [Paraview] ParaView newbie with a (hopefully) simple question In-Reply-To: References: Message-ID: Hi Amy, I think a Python scripting approach is probably the best solution then. When replying to a thread on a mailing list, make sure you hit reply all so that the mailing list stays in the conversation. I have added the ParaView users list back to the cc. Shawn On Mon, Aug 7, 2017 at 3:21 PM, Amelia Launspach wrote: > It does already have a time dimension which I eventually was going to > change from 'VTK Color Block' to 'time' after I had grouped all of the data > together. So until then, I am trying to think of a solution to > automatically group all the data together upon loading.. > > Thank you for your input! This is my first time using the mailing list and > I am pleasantly surprised by how quick people respond :) > > On Mon, Aug 7, 2017 at 2:08 PM, Shawn Waldon > wrote: > >> Hi Amy, >> >> The easiest way would probably be this: >> >> ParaView should automatically recognize the sequence of numbered files >> and give you an option to load "mbdout_r000102_s000001_e..vtm" in the >> file dialog. This will load the data as a time series with one data file >> per step. Then you can apply the "Group Time Steps" filter which reads all >> the time steps into a multiblock dataset (the equivalent of running Group >> Dataset on them). Of course if your dataset has a time dimension too, you >> will have trouble reading that since you are already using time for >> something else... >> >> I see Ufuk has replied since I started typing this and his python >> scripting approach may be superior if your dataset has time steps already. >> >> HTH, >> Shawn >> >> On Mon, Aug 7, 2017 at 2:55 PM, Amelia Launspach >> wrote: >> >>> Hello everyone, >>> >>> I was assigned a small project on ParaView and I need help getting >>> started. >>> >>> I need to find a way to loop through N number of source files in the >>> Pipeline Browser and return the count for number N and group them together >>> using the group dataset filter. >>> >>> Each time I upload the data it will be a different number of files that >>> look something like this: >>> [image: Inline image 1] >>> Right now there are N=22 files but the N will differ each time. So I >>> want to create a script/or programmable filter that will loop through every >>> file in the pipeline browser, add it to a group dataset, and lastly print >>> the number N. >>> >>> How would I begin to do this? Can this be done with a simple script that >>> I can just copy and paste each time in the shell? Would it be easier to >>> build a programmable filter? >>> >>> Any help would be appreciated ! >>> >>> Thanks, >>> Amy >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-08-07 at 1.25.06 PM.png Type: image/png Size: 130460 bytes Desc: not available URL: From amylaunspach at gmail.com Mon Aug 7 16:24:03 2017 From: amylaunspach at gmail.com (Amelia Launspach) Date: Mon, 7 Aug 2017 15:24:03 -0500 Subject: [Paraview] ParaView newbie with a (hopefully) simple question In-Reply-To: References: Message-ID: Would there be anyway to automatically group together all the sources without looping? Something like group = GroupDatasets(Input= GetSources()) even though I know GetSources() won't work, but something similar to call all the data at the same time? On Mon, Aug 7, 2017 at 2:36 PM, Shawn Waldon wrote: > Hi Amy, > > I think a Python scripting approach is probably the best solution then. > > When replying to a thread on a mailing list, make sure you hit reply all > so that the mailing list stays in the conversation. I have added the > ParaView users list back to the cc. > > Shawn > > On Mon, Aug 7, 2017 at 3:21 PM, Amelia Launspach > wrote: > >> It does already have a time dimension which I eventually was going to >> change from 'VTK Color Block' to 'time' after I had grouped all of the data >> together. So until then, I am trying to think of a solution to >> automatically group all the data together upon loading.. >> >> Thank you for your input! This is my first time using the mailing list >> and I am pleasantly surprised by how quick people respond :) >> >> On Mon, Aug 7, 2017 at 2:08 PM, Shawn Waldon >> wrote: >> >>> Hi Amy, >>> >>> The easiest way would probably be this: >>> >>> ParaView should automatically recognize the sequence of numbered files >>> and give you an option to load "mbdout_r000102_s000001_e..vtm" in the >>> file dialog. This will load the data as a time series with one data file >>> per step. Then you can apply the "Group Time Steps" filter which reads all >>> the time steps into a multiblock dataset (the equivalent of running Group >>> Dataset on them). Of course if your dataset has a time dimension too, you >>> will have trouble reading that since you are already using time for >>> something else... >>> >>> I see Ufuk has replied since I started typing this and his python >>> scripting approach may be superior if your dataset has time steps already. >>> >>> HTH, >>> Shawn >>> >>> On Mon, Aug 7, 2017 at 2:55 PM, Amelia Launspach >> > wrote: >>> >>>> Hello everyone, >>>> >>>> I was assigned a small project on ParaView and I need help getting >>>> started. >>>> >>>> I need to find a way to loop through N number of source files in the >>>> Pipeline Browser and return the count for number N and group them together >>>> using the group dataset filter. >>>> >>>> Each time I upload the data it will be a different number of files that >>>> look something like this: >>>> [image: Inline image 1] >>>> Right now there are N=22 files but the N will differ each time. So I >>>> want to create a script/or programmable filter that will loop through every >>>> file in the pipeline browser, add it to a group dataset, and lastly print >>>> the number N. >>>> >>>> How would I begin to do this? Can this be done with a simple script >>>> that I can just copy and paste each time in the shell? Would it be easier >>>> to build a programmable filter? >>>> >>>> Any help would be appreciated ! >>>> >>>> Thanks, >>>> Amy >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-08-07 at 1.25.06 PM.png Type: image/png Size: 130460 bytes Desc: not available URL: From shayan.nikoohemat at gmail.com Tue Aug 8 07:08:39 2017 From: shayan.nikoohemat at gmail.com (Shayan Nikoohemat) Date: Tue, 8 Aug 2017 13:08:39 +0200 Subject: [Paraview] Get value of a vtkintarray object by the filed name Message-ID: I have a Paraview programmable filter written in python, that I am running on a table of points to assign RGB colors as UnsignedCharArray. I'm just stuck in one part of the code to get the value of R, G, B fields in the range. Here is the table example: [image: Inline image 1] ids = self.GetInput() ods = self.GetOutput() ocolors = vtk.vtkUnsignedCharArray() ocolors.SetName("colors") ocolors.SetNumberOfComponents(3) ocolors.SetNumberOfTuples(ids.GetNumberOfPoints()) inArray = ids.GetPointData().GetArray(0)for x in range(0, ids.GetNumberOfPoints()): rF = inArray.GetValue(x) # here I need something like GetValue(x, "R") gF = inArray.GetValue(x) # here I need something like GetValue(x, "G") bF = inArray.GetValue(x) # here I need something like GetValue(x, "B") ocolors.SetTuple3(x, rF,gF,bF) ods.GetPointData().AddArray(ocolors) Can anyone help me to fix this. The code source is from an old post from 2012. Thanks. Shayan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 11808 bytes Desc: not available URL: From dave.demarle at kitware.com Tue Aug 8 07:46:17 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 8 Aug 2017 07:46:17 -0400 Subject: [Paraview] Get value of a vtkintarray object by the filed name In-Reply-To: References: Message-ID: Try: inRArray = ids.GetPointData().GetArray("R") inGArray = ids.GetPointData().GetArray("G") inBArray = ids.GetPointData().GetArray("B") for x in range(0, ids.GetNumberOfPoints()): rF = inRArray.GetValue(x) gF = inGArray.GetValue(x) bF = inBArray.GetValue(x) David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Aug 8, 2017 at 7:08 AM, Shayan Nikoohemat < shayan.nikoohemat at gmail.com> wrote: > I have a Paraview programmable filter written in python, that I am > running on a table of points to assign RGB colors as UnsignedCharArray. > I'm just stuck in one part of the code to get the value of R, G, B fields > in the range. Here is the table example: > > [image: Inline image 1] > > ids = self.GetInput() > ods = self.GetOutput() > > ocolors = vtk.vtkUnsignedCharArray() > ocolors.SetName("colors") > ocolors.SetNumberOfComponents(3) > ocolors.SetNumberOfTuples(ids.GetNumberOfPoints()) > > inArray = ids.GetPointData().GetArray(0)for x in range(0, ids.GetNumberOfPoints()): > rF = inArray.GetValue(x) # here I need something like GetValue(x, "R") > gF = inArray.GetValue(x) # here I need something like GetValue(x, "G") > bF = inArray.GetValue(x) # here I need something like GetValue(x, "B") > > ocolors.SetTuple3(x, rF,gF,bF) > > ods.GetPointData().AddArray(ocolors) > > Can anyone help me to fix this. > > The code source is from an old post from 2012. > > Thanks. > > Shayan > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 11808 bytes Desc: not available URL: From shayan.nikoohemat at gmail.com Tue Aug 8 08:11:58 2017 From: shayan.nikoohemat at gmail.com (Shayan Nikoohemat) Date: Tue, 8 Aug 2017 14:11:58 +0200 Subject: [Paraview] Get value of a vtkintarray object by the filed name In-Reply-To: References: Message-ID: Hi David, Thanks for the reply, it works now, but I can't see the original RGB colors in renderview. In color map editor, I changed the settings to RGB but still the color scale is scaled based on color pallet. Is there any other settings that I missed? Thanks. On Tue, Aug 8, 2017 at 1:46 PM, David E DeMarle wrote: > Try: > > inRArray = ids.GetPointData().GetArray("R") > inGArray = ids.GetPointData().GetArray("G") > inBArray = ids.GetPointData().GetArray("B") for x in range(0, ids.GetNumberOfPoints()): > rF = inRArray.GetValue(x) > gF = inGArray.GetValue(x) > bF = inBArray.GetValue(x) > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Tue, Aug 8, 2017 at 7:08 AM, Shayan Nikoohemat < > shayan.nikoohemat at gmail.com> wrote: > >> I have a Paraview programmable filter written in python, that I am >> running on a table of points to assign RGB colors as UnsignedCharArray. >> I'm just stuck in one part of the code to get the value of R, G, B fields >> in the range. Here is the table example: >> >> [image: Inline image 1] >> >> ids = self.GetInput() >> ods = self.GetOutput() >> >> ocolors = vtk.vtkUnsignedCharArray() >> ocolors.SetName("colors") >> ocolors.SetNumberOfComponents(3) >> ocolors.SetNumberOfTuples(ids.GetNumberOfPoints()) >> >> inArray = ids.GetPointData().GetArray(0)for x in range(0, ids.GetNumberOfPoints()): >> rF = inArray.GetValue(x) # here I need something like GetValue(x, "R") >> gF = inArray.GetValue(x) # here I need something like GetValue(x, "G") >> bF = inArray.GetValue(x) # here I need something like GetValue(x, "B") >> >> ocolors.SetTuple3(x, rF,gF,bF) >> >> ods.GetPointData().AddArray(ocolors) >> >> Can anyone help me to fix this. >> >> The code source is from an old post from 2012. >> >> Thanks. >> >> Shayan >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 11808 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Aug 8 10:14:44 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 8 Aug 2017 10:14:44 -0400 Subject: [Paraview] ParaView newbie with a (hopefully) simple question In-Reply-To: References: Message-ID: > > Would there be anyway to automatically group together all the sources > without looping? > This should work: * GroupDatasets(Input=GetSources().values())* Utkarsh -------------- next part -------------- An HTML attachment was scrubbed... URL: From lionel.wilhelm at epfl.ch Tue Aug 8 10:29:01 2017 From: lionel.wilhelm at epfl.ch (Wilhelm Lionel) Date: Tue, 8 Aug 2017 14:29:01 +0000 Subject: [Paraview] Screenshot resolution and 2D actors size In-Reply-To: <1502201225431.60834@epfl.ch> References: <1502201225431.60834@epfl.ch> Message-ID: <1502202542032.8036@epfl.ch> Dear Paraview community, I created a full layout with 5 different views and would like to save a screenshot. The paraview GUI looks exactly like the image I want to save so I just use File -> Save Screenshot and keep the default resolution. The settings and the generated image are attached as "settings_test1" and "test1" (everything works fine). If I change the resolution of one pixel in one of the dimensions (width for example), the resulting image shows huge scalar bars. Here are also attached the screenshot settings and the resulting image ( as "settings_test2" and "test2" ). I have to mention that the small numbers on the views are in fact 3D Text objects. The entire visualization is produced by a Python script that I launch in the following way : Tools -> Python Shell -> Run Script. In order to avoid resolution problems, I also tried to run the script with pvbatch and at the end save the screenshot with the following settings : SaveScreenshot(OutputImageName,layout, SaveAllViews=1, ImageResolution=UsrImageRes, FontScaling="Scale fonts proportionally", SeparatorWidth=1, SeparatorColor=(1,1,1), ImageQuality=100 ) These settings are the same as the ones presented in the "settings_test*" images. The result attached as "test3.png". Is this a bug or this behaviour should be expected ? Does anybody has an idea ? Are the problems with pvbatch and the GUI related or not ? I'm using Paraview 5.4.0 with MPI enabled when I use the GUI. Kindly, Lionel Wilhelm -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: settings_test1.png Type: image/png Size: 54032 bytes Desc: settings_test1.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: settings_test2.png Type: image/png Size: 54031 bytes Desc: settings_test2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test1.png Type: image/png Size: 205745 bytes Desc: test1.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test2.png Type: image/png Size: 215301 bytes Desc: test2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test3.png Type: image/png Size: 43501 bytes Desc: test3.png URL: From cory.quammen at kitware.com Tue Aug 8 10:44:33 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 8 Aug 2017 10:44:33 -0400 Subject: [Paraview] Screenshot resolution and 2D actors size In-Reply-To: <1502202542032.8036@epfl.ch> References: <1502201225431.60834@epfl.ch> <1502202542032.8036@epfl.ch> Message-ID: Hi Lionel, This is a bug [1] that will be fixed in ParaView 5.4.1, coming out in the next week or so. In fact, it is fixed in the latest 5.4.1 release candidate, which you can get from www.paraview.org/download. HTH, Cory [1] https://gitlab.kitware.com/paraview/paraview/issues/17603 On Tue, Aug 8, 2017 at 10:29 AM, Wilhelm Lionel wrote: > Dear Paraview community, > > > I created a full layout with 5 different views and would like to save a > screenshot. The paraview GUI looks exactly like the image I want to save so > I just use File -> Save Screenshot and keep the default resolution. The > settings and the generated image are attached as "settings_test1" and > "test1" (everything works fine). > > > If I change the resolution of one pixel in one of the dimensions (width for > example), the resulting image shows huge scalar bars. Here are also attached > the screenshot settings and the resulting image ( as "settings_test2" and > "test2" ). I have to mention that the small numbers on the views are in fact > 3D Text objects. > > > The entire visualization is produced by a Python script that I launch in the > following way : Tools -> Python Shell -> Run Script. In order to avoid > resolution problems, I also tried to run the script with pvbatch and at the > end save the screenshot with the following settings : > > > SaveScreenshot(OutputImageName,layout, SaveAllViews=1, > ImageResolution=UsrImageRes, > FontScaling="Scale fonts proportionally", > SeparatorWidth=1, > SeparatorColor=(1,1,1), > ImageQuality=100 > ) > > > These settings are the same as the ones presented in the "settings_test*" > images. The result attached as "test3.png". > > > Is this a bug or this behaviour should be expected ? Does anybody has an > idea ? Are the problems with pvbatch and the GUI related or not ? > > > I'm using Paraview 5.4.0 with MPI enabled when I use the GUI. > > > Kindly, > > > Lionel Wilhelm > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From josejmcriollo at gmail.com Tue Aug 8 10:51:06 2017 From: josejmcriollo at gmail.com (Jose Javier Munoz Criollo) Date: Tue, 8 Aug 2017 15:51:06 +0100 Subject: [Paraview] how to uninstall paraview Message-ID: Hi I'm facing a problem in Fedora 26, it seems like my Paraview GUI (5.4) is very very slow, compared with previous versions. I usually do the installation from the Fedora repositories. Now I'm trying to built from source to see if I can fix this problem. However, after the first try it didn't work. It built correctly but the problem persists. I would like to uninstall it and try with an older version. Typically I would use Fedora package manager to remove Paraview but in this case I'm not sure how to properly uninstall it. Any help would be highly appreciated. Regards From juha_kortelainen at welho.net Tue Aug 8 12:32:02 2017 From: juha_kortelainen at welho.net (Juha Kortelainen) Date: Tue, 8 Aug 2017 19:32:02 +0300 Subject: [Paraview] Dynamic colouring of the geometry in the animation, of warped eigenmodes Message-ID: <57f2a291-f998-9659-d82f-a701ef8d2f0e@welho.net> Hello all, Thank you, Cory and Ken, for your answers. The trick with the Calculator and WarpByVector filters was what I was originally looking for as a quick solution, but when I tried some examples with the Programmable filter, I found it a very useful way to implement filters for relatively simple and light data processing. Though, I still need to study more about the details to make my Programmable filter to really work for my case. - Juha - ------------------------------------------------------------------------ Juha, As Cory said you can create a plugin to replicate this behavior, but I believe you can also get similar behavior through a collection of filters. Although this is a bit cumbersome, you can try the following steps: 1. Before applying the WarpByVector filter, add the Calculator filter to your data. Set the "Result Array Name" to "OriginalCoords" and the expression to simply "coords". This will capture the point coordinates before warping. 2. Apply WarpByVector to this calculator filter as you did before to the FEM data. 3. Apply another Calculator filter to the output of WarpByVector. This time, set the "Result Array Name" to "ActualDisplacement" and the expression to "coords-OriginalCoords". This will capture the actual displacement applied after the scale factor is used. 4. Color your data by the "ActualDispalcement" field. 5. Set up your animation of the "ScaleFactor" for the WarpByVector filter as you did before. You should now see "dynamic" colors based on the magnitude of the actual displacement. -Ken -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org ] On Behalf Of Cory Quammen Sent: Monday, August 7, 2017 7:27 AM To: Juha Kortelainen > Cc: ParaView > Subject: [EXTERNAL] Re: [Paraview] Dynamic colouring of the geometry in the animation of warped eigenmodes On Sun, Aug 6, 2017 at 1:30 PM, Juha Kortelainen > wrote: >/Hi all, />//>/I?m using the warp filter to visualise the computed eigenmodes of a />/structure (computed using a FEM code). Animating the eigenmodes works />/fine with the WarpByVector filter using the ScalarFactor as the />/animation variable. In addition to animating the deformation of the />/structure, I would like to apply colouring of the deformation vector />/field on the geometry so that the colour would change dynamically />/according to the magnitude of deformation during the animation. This />/can be done with the Salome platform?s ParaViS modile (a modified />/version of ParaView), which has an additional ScaleVector filter to do />/the colouring trick. Can this dynamic colouring be done with standard ParaView and if so, how is it done? / Yes, with some work. Take a look at this blog post for the general idea:https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ Basically, you can create XML plugins based on the Programmable Filter that feature some properties, such as a scale factor. The scale factor property should be exposed in the animation controls. Within your Programmable Filter script, you can perform the scaling of the vector with that scale factor property value. There are many examples of Python scripts for the Programmable Filter in Section 13.3 the ParaView Guide to get you started. HTH, Cory >//>/_______________________________________________ />/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 />/J />/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 bywww.kitware.com Visit other Kitware open-source projects athttp://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 amylaunspach at gmail.com Tue Aug 8 12:39:13 2017 From: amylaunspach at gmail.com (Amelia Launspach) Date: Tue, 8 Aug 2017 11:39:13 -0500 Subject: [Paraview] Hiding all pipeline objects Message-ID: Hi everyone, I'm trying to hide all pipeline objects on my view. My paraview.simple does not have a "HideAll" so I'm not sure how to do this. The following methods have not worked for me: def HideAll(view=None): """Hide all pipeline sources in the given view. If view is not specified, active view is used.""" if not view: view = active_objects.view controller = servermanager.ParaViewPipelineController() controller.HideAll(view) paraview.simple.HideAll() Does anyone know how I could accomplish this? Seems simple enough but nothing is working? Thanks, Amy -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyndyb at email.arizona.edu Tue Aug 8 12:43:03 2017 From: cyndyb at email.arizona.edu (Hart, Cynthia Joyce - (cyndyb)) Date: Tue, 8 Aug 2017 16:43:03 +0000 Subject: [Paraview] troubles with netCDF reader ? In-Reply-To: References: Message-ID: Hello, To make a long story short, this solution you used below, does not work well for the weather forecasting group here on my campus that I am working with. Is there any possibility of obtaining the source code of the Paraview netCDF reader? If I could edit that source code to accept the non- CF compliant WRF outputs, I could make use of Paraview in an automated script to create animations for our forecasters much, much more readily than manipulating netCDF file headers. The data I?d sent to you was but a very small subset of the hundreds of netCDF files we?d need to change, every time we do a model run, and this is a process we?d like to actually automate daily. I am unable to force the output to be compliant as it is created. Can you help? Sincerely, Cynthia Hart From: Dan Lipsa Date: Friday, June 23, 2017 at 10:57 AM To: Aashish Chaudhary Cc: "Hart, Cynthia Joyce - (cyndyb)" , "paraview at paraview.org" Subject: Re: [Paraview] troubles with netCDF reader ? Cynthia, It seems that the files you send us are not CF compliant. The problem is that the Time dimension does not have a unit. Here are some quotes from the CF Conventions document: - The use of coordinate variables is required for all dimensions that correspond to one dimensional space or time coordinates. - Variables representing time must always explicitly include the units attribute; there is no default value So, to fix one of your files, I did: 1. ncdump ARAD4_test2.ncdf > ARAD4_test2_CF.txt 2. I added a new variable Time with the unit specified to the txt file. float Time(Time) ; Time:units = "minutes since 2016-07-29 12:00:00" ; 3. I generated a new nc file: ncgen ARAD4_test2_CF.txt -o ARAD4_test2_CF.nc This new file is read correctly by ParaView. Best, Dan On Fri, Jun 16, 2017 at 6:31 PM, Aashish Chaudhary > wrote: Dear Cynthia, Is there any chance that you can send me a sample dataset? - Aashish On Fri, Jun 16, 2017 at 6:15 PM Hart, Cynthia Joyce - (cyndyb) > wrote: Folks ? I am struggling with using the netCDF reader, with a bunch of timeseries of WRF data output (weather prediction modeling). I am a visualizer, NOT a meteorologist, and so, my full understanding of the model?s output is shaky at best. The researcher I am trying to assist is currently on vacation, and I?m trying to animate the output of his WRF model. So! I have been viewing some of the output using the built in reader in Paraview (the ?generic and cf? reader) and it works for some variables, not for others. I am using NCO tools to extract some of the variables of interest into their own CDF file, to try and isolate the problem Paraview has, reading some variables.. but that doesn?t help. I am particularly trying to read a variable for radar data, ?REFL_10CM?. Here is the relevant bit of the file header from ncdump, below: netcdf ARAD4_test2 { dimensions: Time = UNLIMITED ; // (1 currently) south_north = 393 ; west_east = 639 ; bottom_top = 37 ; variables: float REFD_MAX(Time, south_north, west_east) ; REFD_MAX:FieldType = 104 ; REFD_MAX:MemoryOrder = "XY " ; REFD_MAX:description = "MAX DERIVED RADAR REFL" ; REFD_MAX:units = "dbZ" ; REFD_MAX:stagger = "" ; REFD_MAX:coordinates = "XLONG XLAT XTIME" ; float REFL_10CM(Time, bottom_top, south_north, west_east) ; REFL_10CM:FieldType = 104 ; REFL_10CM:MemoryOrder = "XYZ" ; REFL_10CM:description = "Radar reflectivity (lamda = 10 cm)" ; REFL_10CM:units = "dBZ" ; REFL_10CM:stagger = "" ; REFL_10CM:coordinates = "XLONG XLAT XTIME" ; float XLAT(Time, south_north, west_east) ; XLAT:FieldType = 104 ; XLAT:MemoryOrder = "XY " ; XLAT:description = "LATITUDE, SOUTH IS NEGATIVE" ; XLAT:units = "degree_north" ; XLAT:stagger = "" ; XLAT:coordinates = "XLONG XLAT" ; float XLONG(Time, south_north, west_east) ; XLONG:FieldType = 104 ; XLONG:MemoryOrder = "XY " ; XLONG:description = "LONGITUDE, WEST IS NEGATIVE" ; XLONG:units = "degree_east" ; XLONG:stagger = "" ; XLONG:coordinates = "XLONG XLAT" ; float XTIME(Time) ; XTIME:FieldType = 104 ; XTIME:MemoryOrder = "0 " ; XTIME:description = "minutes since 2016-07-29 12:00:00" ; XTIME:units = "minutes since 2016-07-29 12:00:00" ; XTIME:stagger = "" ; Paraview complains that it cannot read a variable with more than three dimensions without time. But there appears to ?be? time (I?m very unclear what ?UNLIMITED? time , as seen in the header, refers to in this context). Is there any way I can work around this? Most frustrating. I can actually read this variable into QGIS, but I?d rather use the strengths of Paraview to visualize this data. Thanks in advance. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 8 13:03:09 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 8 Aug 2017 13:03:09 -0400 Subject: [Paraview] Hiding all pipeline objects In-Reply-To: References: Message-ID: What version of ParaView are you using? `simple.HideAll` has been supported since 5.2. On Tue, Aug 8, 2017 at 12:39 PM, Amelia Launspach wrote: > Hi everyone, > > I'm trying to hide all pipeline objects on my view. My paraview.simple > does not have a "HideAll" so I'm not sure how to do this. The following > methods have not worked for me: > > def HideAll(view=None): > > """Hide all pipeline sources in the given view. > > If view is not specified, active view is used.""" > > if not view: > > view = active_objects.view > > controller = servermanager.ParaViewPipelineController() > > controller.HideAll(view) > > > paraview.simple.HideAll() > > > > Does anyone know how I could accomplish this? > Seems simple enough but nothing is working? > > Thanks, > Amy > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amylaunspach at gmail.com Tue Aug 8 13:05:59 2017 From: amylaunspach at gmail.com (Amelia Launspach) Date: Tue, 8 Aug 2017 12:05:59 -0500 Subject: [Paraview] Hiding all pipeline objects In-Reply-To: References: Message-ID: Using paraview 5.1.2, thats a bummer On Tue, Aug 8, 2017 at 12:03 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > What version of ParaView are you using? `simple.HideAll` has been > supported since 5.2. > > On Tue, Aug 8, 2017 at 12:39 PM, Amelia Launspach > wrote: > >> Hi everyone, >> >> I'm trying to hide all pipeline objects on my view. My paraview.simple >> does not have a "HideAll" so I'm not sure how to do this. The following >> methods have not worked for me: >> >> def HideAll(view=None): >> >> """Hide all pipeline sources in the given view. >> >> If view is not specified, active view is used.""" >> >> if not view: >> >> view = active_objects.view >> >> controller = servermanager.ParaViewPipelineController() >> >> controller.HideAll(view) >> >> >> paraview.simple.HideAll() >> >> >> >> Does anyone know how I could accomplish this? >> Seems simple enough but nothing is working? >> >> Thanks, >> Amy >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Aug 8 13:16:53 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 8 Aug 2017 13:16:53 -0400 Subject: [Paraview] Hiding all pipeline objects In-Reply-To: References: Message-ID: With 5.1.2, try this: >>> view = GetActiveView() >>> sources = GetSources().values() >>> for aSource in sources: ... Hide(aSource, view) Utkarsh On Tue, Aug 8, 2017 at 1:05 PM, Amelia Launspach wrote: > Using paraview 5.1.2, thats a bummer > > On Tue, Aug 8, 2017 at 12:03 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> What version of ParaView are you using? `simple.HideAll` has been >> supported since 5.2. >> >> On Tue, Aug 8, 2017 at 12:39 PM, Amelia Launspach > > wrote: >> >>> Hi everyone, >>> >>> I'm trying to hide all pipeline objects on my view. My paraview.simple >>> does not have a "HideAll" so I'm not sure how to do this. The following >>> methods have not worked for me: >>> >>> def HideAll(view=None): >>> >>> """Hide all pipeline sources in the given view. >>> >>> If view is not specified, active view is used.""" >>> >>> if not view: >>> >>> view = active_objects.view >>> >>> controller = servermanager.ParaViewPipelineController() >>> >>> controller.HideAll(view) >>> >>> >>> paraview.simple.HideAll() >>> >>> >>> >>> Does anyone know how I could accomplish this? >>> Seems simple enough but nothing is working? >>> >>> Thanks, >>> Amy >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 8 13:32:05 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 8 Aug 2017 13:32:05 -0400 Subject: [Paraview] Bug in PLOT3D meta reader In-Reply-To: References: Message-ID: Yoshimi's fix has been merged into VTK and will be in ParaView 5.5 due out in November. https://gitlab.kitware.com/vtk/vtk/merge_requests/3090/diffs Thank you for the report, Eric, and for the fix, Yoshimi. Cory On Wed, Aug 2, 2017 at 12:28 AM, kenichiro yoshimi wrote: > Hello Eric, > > If the number of blocks in dataset decreases over time steps then > vtkMultiBlockPLOT3DReader seems to fail to count it. For your > information, I tried commenting out the line 822 in > ParaView-v5.4.0/VTK/IO/Parallel/vtkMultiBlockPLOT3DReader.cxx and this > worked with your data. > ----- > if ( numGrid > (int)this->Internal->Dimensions.size() ) > { > this->Internal->Dimensions.resize(numGrid); > } > > => > > //if ( numGrid > (int)this->Internal->Dimensions.size() ) > { > this->Internal->Dimensions.resize(numGrid); > } > ----- > > Thanks, > yoshimi > > 2017-08-02 2:16 GMT+09:00 Eric Lynch : >> I believe there is a bug in the PLOT3D metafile reader. I've attached two >> PLOT3D meshes and a metafile. Version 5.4.1 appears to read the metafile >> successfully. After reading it, I can see the outline of the two blocks in >> the first mesh file. If I advance to the next time step, I can see the >> outline of the three blocks in the second mesh. If I then go back to the >> previous time step, I get an error message saying: >> >> >> >> ERROR: In >> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/IO/Parallel/vtkMultiBlockPLOT3DReader.cxx, >> line 1397 vtkMPIMultiBlockPLOT3DReader (0x6b53260): Encountered premature >> end-of-file while reading the geometry file (or the file is corrupt). >> >> >> >> ERROR: In >> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, >> line 784 vtkCompositeDataPipeline (0x6946da0): Algorithm >> vtkMPIMultiBlockPLOT3DReader(0x6b53260) returned failure for request: >> vtkInformation (0x68935b0) >> >> Debug: Off >> >> Modified Time: 982828 >> >> Reference Count: 1 >> >> Registered Events: (none) >> >> Request: REQUEST_DATA >> >> ALGORITHM_AFTER_FORWARD: 1 >> >> FROM_OUTPUT_PORT: 0 >> >> FORWARD_DIRECTION: 0 >> >> >> >> To my knowledge, the last version without this bug was 4.3.1. >> >> >> >> Thanks, >> >> Eric >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. From lionel.wilhelm at epfl.ch Tue Aug 8 14:35:55 2017 From: lionel.wilhelm at epfl.ch (Wilhelm Lionel) Date: Tue, 8 Aug 2017 18:35:55 +0000 Subject: [Paraview] Screenshot resolution and 2D actors size In-Reply-To: References: <1502201225431.60834@epfl.ch> <1502202542032.8036@epfl.ch>, Message-ID: Hi Cory, Thanks a lot for your fast response. I will give a try with the new release by tomorrow. Regarding the pvbatch issue, do you have any hint? Kindly, Lionel ________________________________________ De : Cory Quammen [cory.quammen at kitware.com] Envoy? : mardi 8 ao?t 2017 16:44 ? : Wilhelm Lionel Cc : paraview at paraview.org Objet : Re: [Paraview] Screenshot resolution and 2D actors size Hi Lionel, This is a bug [1] that will be fixed in ParaView 5.4.1, coming out in the next week or so. In fact, it is fixed in the latest 5.4.1 release candidate, which you can get from www.paraview.org/download. HTH, Cory [1] https://gitlab.kitware.com/paraview/paraview/issues/17603 On Tue, Aug 8, 2017 at 10:29 AM, Wilhelm Lionel wrote: > Dear Paraview community, > > > I created a full layout with 5 different views and would like to save a > screenshot. The paraview GUI looks exactly like the image I want to save so > I just use File -> Save Screenshot and keep the default resolution. The > settings and the generated image are attached as "settings_test1" and > "test1" (everything works fine). > > > If I change the resolution of one pixel in one of the dimensions (width for > example), the resulting image shows huge scalar bars. Here are also attached > the screenshot settings and the resulting image ( as "settings_test2" and > "test2" ). I have to mention that the small numbers on the views are in fact > 3D Text objects. > > > The entire visualization is produced by a Python script that I launch in the > following way : Tools -> Python Shell -> Run Script. In order to avoid > resolution problems, I also tried to run the script with pvbatch and at the > end save the screenshot with the following settings : > > > SaveScreenshot(OutputImageName,layout, SaveAllViews=1, > ImageResolution=UsrImageRes, > FontScaling="Scale fonts proportionally", > SeparatorWidth=1, > SeparatorColor=(1,1,1), > ImageQuality=100 > ) > > > These settings are the same as the ones presented in the "settings_test*" > images. The result attached as "test3.png". > > > Is this a bug or this behaviour should be expected ? Does anybody has an > idea ? Are the problems with pvbatch and the GUI related or not ? > > > I'm using Paraview 5.4.0 with MPI enabled when I use the GUI. > > > Kindly, > > > Lionel Wilhelm > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Tue Aug 8 14:44:16 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 8 Aug 2017 14:44:16 -0400 Subject: [Paraview] Screenshot resolution and 2D actors size In-Reply-To: References: <1502201225431.60834@epfl.ch> <1502202542032.8036@epfl.ch> Message-ID: > Regarding the pvbatch issue, do you have any hint? That is odd. I'm not sure what is going on exactly. Have you tried running your script with pvpython? Thanks, Cory > Kindly, > > Lionel > ________________________________________ > De : Cory Quammen [cory.quammen at kitware.com] > Envoy? : mardi 8 ao?t 2017 16:44 > ? : Wilhelm Lionel > Cc : paraview at paraview.org > Objet : Re: [Paraview] Screenshot resolution and 2D actors size > > Hi Lionel, > > This is a bug [1] that will be fixed in ParaView 5.4.1, coming out in > the next week or so. In fact, it is fixed in the latest 5.4.1 release > candidate, which you can get from www.paraview.org/download. > > HTH, > Cory > > [1] https://gitlab.kitware.com/paraview/paraview/issues/17603 > > On Tue, Aug 8, 2017 at 10:29 AM, Wilhelm Lionel wrote: >> Dear Paraview community, >> >> >> I created a full layout with 5 different views and would like to save a >> screenshot. The paraview GUI looks exactly like the image I want to save so >> I just use File -> Save Screenshot and keep the default resolution. The >> settings and the generated image are attached as "settings_test1" and >> "test1" (everything works fine). >> >> >> If I change the resolution of one pixel in one of the dimensions (width for >> example), the resulting image shows huge scalar bars. Here are also attached >> the screenshot settings and the resulting image ( as "settings_test2" and >> "test2" ). I have to mention that the small numbers on the views are in fact >> 3D Text objects. >> >> >> The entire visualization is produced by a Python script that I launch in the >> following way : Tools -> Python Shell -> Run Script. In order to avoid >> resolution problems, I also tried to run the script with pvbatch and at the >> end save the screenshot with the following settings : >> >> >> SaveScreenshot(OutputImageName,layout, SaveAllViews=1, >> ImageResolution=UsrImageRes, >> FontScaling="Scale fonts proportionally", >> SeparatorWidth=1, >> SeparatorColor=(1,1,1), >> ImageQuality=100 >> ) >> >> >> These settings are the same as the ones presented in the "settings_test*" >> images. The result attached as "test3.png". >> >> >> Is this a bug or this behaviour should be expected ? Does anybody has an >> idea ? Are the problems with pvbatch and the GUI related or not ? >> >> >> I'm using Paraview 5.4.0 with MPI enabled when I use the GUI. >> >> >> Kindly, >> >> >> Lionel Wilhelm >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From gregory.zaccaro at caboma.com Tue Aug 8 14:45:07 2017 From: gregory.zaccaro at caboma.com (Gregory Zaccaro) Date: Tue, 8 Aug 2017 18:45:07 +0000 Subject: [Paraview] Relation between magnitude and camera view angle in SaveScreenshot Message-ID: Hi Paraviewers, I have a simple question regarding the screenshot saving feature within Paraview. I wrote a python script that I run with pvbatch which basically : 1) Load a polydata 2) Create a render view 3) Set up the camera (position, focal point, view angle) 4) Take a screenshot with SaveScreenshot(file_name, renderView1, quality=100, magnification=magnification) There is a correlation between the magnification and the allowed View Angle values, but I can't figure out what it is. The scale changes a lot between 150 deg and 170 deg of View Angle if the magnification =1. When magnification is superior to 1 (ex. 2), the scales doesn't change much between 150 and 170 deg of View Angle. Why ? What did I miss to understand the relation between these two parameters ? Gregory Zaccaro -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.stormtrooper at gmail.com Tue Aug 8 16:25:11 2017 From: andrew.stormtrooper at gmail.com (Andrew Nicholson) Date: Tue, 8 Aug 2017 21:25:11 +0100 Subject: [Paraview] Paraview source and its associated qt version Message-ID: Is there anywhere that highlights what version of qt should be used for building from source? Current version of qt being 5.9 from its website. Is paraview on this version yet or an older version. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 8 16:34:32 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 8 Aug 2017 16:34:32 -0400 Subject: [Paraview] Paraview source and its associated qt version In-Reply-To: References: Message-ID: Andrew, The officially supported version of Qt is 5.9, but you could use down to Qt 5.6 if you wanted. Best, Cory On Tue, Aug 8, 2017 at 4:25 PM, Andrew Nicholson wrote: > Is there anywhere that highlights what version of qt should be used for > building from source? Current version of qt being 5.9 from its website. Is > paraview on this version yet or an older version. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From dan.lipsa at kitware.com Tue Aug 8 16:40:45 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 8 Aug 2017 16:40:45 -0400 Subject: [Paraview] troubles with netCDF reader ? In-Reply-To: References: Message-ID: Hi Cynthia, It is possible to change the reader. You'll need to compile ParaView from source. The class you need to change is vtkNetCDFCFReader. Probably you'll need an extra parameter to the reader that would be the time unit. The time unit read from the file should overides this parameter. You could also submit your changes back to VTK (most readers in ParaView are actually part of VTK). This seems like something other people might need. Dan On Tue, Aug 8, 2017 at 12:43 PM, Hart, Cynthia Joyce - (cyndyb) < cyndyb at email.arizona.edu> wrote: > Hello, > > > > To make a long story short, this solution you used below, does not work > well for the weather forecasting group here on my campus that I am working > with. Is there any possibility of obtaining the source code of the > Paraview netCDF reader? If I could edit that source code to accept the > non- CF compliant WRF outputs, I could make use of Paraview in an automated > script to create animations for our forecasters much, much more readily > than manipulating netCDF file headers. The data I?d sent to you was but a > very small subset of the hundreds of netCDF files we?d need to change, > every time we do a model run, and this is a process we?d like to actually > automate daily. I am unable to force the output to be compliant as it is > created. Can you help? > > > > Sincerely, > > > > Cynthia Hart > > > > > > *From: *Dan Lipsa > *Date: *Friday, June 23, 2017 at 10:57 AM > *To: *Aashish Chaudhary > *Cc: *"Hart, Cynthia Joyce - (cyndyb)" , " > paraview at paraview.org" > *Subject: *Re: [Paraview] troubles with netCDF reader ? > > > > Cynthia, > > It seems that the files you send us are not CF compliant. > > The problem is that the Time dimension does not have a unit. > > > > > > Here are some quotes from the CF Conventions document: > > - The use of coordinate variables is required for all dimensions that > correspond to one dimensional space or time coordinates. > > - Variables representing time must always explicitly include the units > attribute; there is no default value > > > > So, to fix one of your files, I did: > > > > 1. ncdump ARAD4_test2.ncdf > ARAD4_test2_CF.txt > > > > 2. I added a new variable Time with the unit specified to the txt file. > > > > float Time(Time) ; > > Time:units = "minutes since 2016-07-29 12:00:00" ; > > > > 3. > > I generated a new nc file: > > ncgen ARAD4_test2_CF.txt -o ARAD4_test2_CF.nc > > > > This new file is read correctly by ParaView. > > > > Best, > > Dan > > > > > > > > On Fri, Jun 16, 2017 at 6:31 PM, Aashish Chaudhary < > aashish.chaudhary at kitware.com> wrote: > > Dear Cynthia, > > > > Is there any chance that you can send me a sample dataset? > > > > - Aashish > > > > On Fri, Jun 16, 2017 at 6:15 PM Hart, Cynthia Joyce - (cyndyb) < > cyndyb at email.arizona.edu> wrote: > > Folks ? > > > > I am struggling with using the netCDF reader, with a bunch of timeseries > of WRF data output (weather prediction modeling). I am a visualizer, NOT a > meteorologist, and so, my full understanding of the model?s output is shaky > at best. The researcher I am trying to assist is currently on vacation, > and I?m trying to animate the output of his WRF model. > > > > So! I have been viewing some of the output using the built in reader in > Paraview (the ?generic and cf? reader) and it works for some variables, not > for others. I am using NCO tools to extract some of the variables of > interest into their own CDF file, to try and isolate the problem Paraview > has, reading some variables.. but that doesn?t help. I am particularly > trying to read a variable for radar data, ?REFL_10CM?. Here is the > relevant bit of the file header from ncdump, below: > > > > netcdf ARAD4_test2 { > > dimensions: > > Time = UNLIMITED ; // (1 currently) > > south_north = 393 ; > > west_east = 639 ; > > bottom_top = 37 ; > > variables: > > float REFD_MAX(Time, south_north, west_east) ; > > REFD_MAX:FieldType = 104 ; > > REFD_MAX:MemoryOrder = "XY " ; > > REFD_MAX:description = "MAX DERIVED RADAR > REFL" ; > > REFD_MAX:units = "dbZ" ; > > REFD_MAX:stagger = "" ; > > REFD_MAX:coordinates = "XLONG XLAT XTIME" > ; > > float REFL_10CM(Time, bottom_top, south_north, west_east) ; > > REFL_10CM:FieldType = 104 ; > > REFL_10CM:MemoryOrder = "XYZ" ; > > REFL_10CM:description = "Radar > reflectivity (lamda = 10 cm)" ; > > REFL_10CM:units = "dBZ" ; > > REFL_10CM:stagger = "" ; > > REFL_10CM:coordinates = "XLONG XLAT > XTIME" ; > > float XLAT(Time, south_north, west_east) ; > > XLAT:FieldType = 104 ; > > XLAT:MemoryOrder = "XY " ; > > XLAT:description = "LATITUDE, SOUTH IS > NEGATIVE" ; > > XLAT:units = "degree_north" ; > > XLAT:stagger = "" ; > > XLAT:coordinates = "XLONG XLAT" ; > > float XLONG(Time, south_north, west_east) ; > > XLONG:FieldType = 104 ; > > XLONG:MemoryOrder = "XY " ; > > XLONG:description = "LONGITUDE, WEST IS > NEGATIVE" ; > > XLONG:units = "degree_east" ; > > XLONG:stagger = "" ; > > XLONG:coordinates = "XLONG XLAT" ; > > float XTIME(Time) ; > > XTIME:FieldType = 104 ; > > XTIME:MemoryOrder = "0 " ; > > XTIME:description = "minutes since > 2016-07-29 12:00:00" ; > > XTIME:units = "minutes since 2016-07-29 > 12:00:00" ; > > XTIME:stagger = "" ; > > > > Paraview complains that it cannot read a variable with more than three > dimensions without time. But there appears to ?be? time (I?m very unclear > what ?UNLIMITED? time , as seen in the header, refers to in this context). > Is there any way I can work around this? Most frustrating. I can > actually read this variable into QGIS, but I?d rather use the strengths of > Paraview to visualize this data. > > > > Thanks in advance. > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Tue Aug 8 16:51:05 2017 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 08 Aug 2017 20:51:05 +0000 Subject: [Paraview] troubles with netCDF reader ? In-Reply-To: References: Message-ID: Hi Cynthia, If you could modify the vtkNetCDFCFReader ( https://github.com/Kitware/VTK/blob/master/IO/NetCDF/vtkNetCDFCFReader.cxx) to work with WRF formats, that would be an awesome addition. I know few folks that can use this work. Unfortunately we do not have any direct funding to accomplish this but we will be more than happy to guide or help a little if needed. Let us know and we can discuss more offline. Thanks, On Tue, Aug 8, 2017 at 4:40 PM Dan Lipsa wrote: > Hi Cynthia, > It is possible to change the reader. You'll need to compile ParaView from > source. The class you need to change is vtkNetCDFCFReader. > Probably you'll need an extra parameter to the reader that would be the > time unit. The time unit read from the file should overides this parameter. > > You could also submit your changes back to VTK (most readers in ParaView > are actually part of VTK). This seems like something other people might > need. > > Dan > > > > > On Tue, Aug 8, 2017 at 12:43 PM, Hart, Cynthia Joyce - (cyndyb) < > cyndyb at email.arizona.edu> wrote: > >> Hello, >> >> >> >> To make a long story short, this solution you used below, does not work >> well for the weather forecasting group here on my campus that I am working >> with. Is there any possibility of obtaining the source code of the >> Paraview netCDF reader? If I could edit that source code to accept the >> non- CF compliant WRF outputs, I could make use of Paraview in an automated >> script to create animations for our forecasters much, much more readily >> than manipulating netCDF file headers. The data I?d sent to you was but a >> very small subset of the hundreds of netCDF files we?d need to change, >> every time we do a model run, and this is a process we?d like to actually >> automate daily. I am unable to force the output to be compliant as it is >> created. Can you help? >> >> >> >> Sincerely, >> >> >> >> Cynthia Hart >> >> >> >> >> >> *From: *Dan Lipsa >> *Date: *Friday, June 23, 2017 at 10:57 AM >> *To: *Aashish Chaudhary >> *Cc: *"Hart, Cynthia Joyce - (cyndyb)" , " >> paraview at paraview.org" >> *Subject: *Re: [Paraview] troubles with netCDF reader ? >> >> >> >> Cynthia, >> >> It seems that the files you send us are not CF compliant. >> >> The problem is that the Time dimension does not have a unit. >> >> >> >> >> >> Here are some quotes from the CF Conventions document: >> >> - The use of coordinate variables is required for all dimensions that >> correspond to one dimensional space or time coordinates. >> >> - Variables representing time must always explicitly include the units >> attribute; there is no default value >> >> >> >> So, to fix one of your files, I did: >> >> >> >> 1. ncdump ARAD4_test2.ncdf > ARAD4_test2_CF.txt >> >> >> >> 2. I added a new variable Time with the unit specified to the txt file. >> >> >> >> float Time(Time) ; >> >> Time:units = "minutes since 2016-07-29 12:00:00" ; >> >> >> >> 3. >> >> I generated a new nc file: >> >> ncgen ARAD4_test2_CF.txt -o ARAD4_test2_CF.nc >> >> >> >> This new file is read correctly by ParaView. >> >> >> >> Best, >> >> Dan >> >> >> >> >> >> >> >> On Fri, Jun 16, 2017 at 6:31 PM, Aashish Chaudhary < >> aashish.chaudhary at kitware.com> wrote: >> >> Dear Cynthia, >> >> >> >> Is there any chance that you can send me a sample dataset? >> >> >> >> - Aashish >> >> >> >> On Fri, Jun 16, 2017 at 6:15 PM Hart, Cynthia Joyce - (cyndyb) < >> cyndyb at email.arizona.edu> wrote: >> >> Folks ? >> >> >> >> I am struggling with using the netCDF reader, with a bunch of timeseries >> of WRF data output (weather prediction modeling). I am a visualizer, NOT a >> meteorologist, and so, my full understanding of the model?s output is shaky >> at best. The researcher I am trying to assist is currently on vacation, >> and I?m trying to animate the output of his WRF model. >> >> >> >> So! I have been viewing some of the output using the built in reader in >> Paraview (the ?generic and cf? reader) and it works for some variables, not >> for others. I am using NCO tools to extract some of the variables of >> interest into their own CDF file, to try and isolate the problem Paraview >> has, reading some variables.. but that doesn?t help. I am particularly >> trying to read a variable for radar data, ?REFL_10CM?. Here is the >> relevant bit of the file header from ncdump, below: >> >> >> >> netcdf ARAD4_test2 { >> >> dimensions: >> >> Time = UNLIMITED ; // (1 currently) >> >> south_north = 393 ; >> >> west_east = 639 ; >> >> bottom_top = 37 ; >> >> variables: >> >> float REFD_MAX(Time, south_north, west_east) ; >> >> REFD_MAX:FieldType = 104 ; >> >> REFD_MAX:MemoryOrder = "XY " ; >> >> REFD_MAX:description = "MAX DERIVED RADAR >> REFL" ; >> >> REFD_MAX:units = "dbZ" ; >> >> REFD_MAX:stagger = "" ; >> >> REFD_MAX:coordinates = "XLONG XLAT XTIME" >> ; >> >> float REFL_10CM(Time, bottom_top, south_north, west_east) >> ; >> >> REFL_10CM:FieldType = 104 ; >> >> REFL_10CM:MemoryOrder = "XYZ" ; >> >> REFL_10CM:description = "Radar >> reflectivity (lamda = 10 cm)" ; >> >> REFL_10CM:units = "dBZ" ; >> >> REFL_10CM:stagger = "" ; >> >> REFL_10CM:coordinates = "XLONG XLAT >> XTIME" ; >> >> float XLAT(Time, south_north, west_east) ; >> >> XLAT:FieldType = 104 ; >> >> XLAT:MemoryOrder = "XY " ; >> >> XLAT:description = "LATITUDE, SOUTH IS >> NEGATIVE" ; >> >> XLAT:units = "degree_north" ; >> >> XLAT:stagger = "" ; >> >> XLAT:coordinates = "XLONG XLAT" ; >> >> float XLONG(Time, south_north, west_east) ; >> >> XLONG:FieldType = 104 ; >> >> XLONG:MemoryOrder = "XY " ; >> >> XLONG:description = "LONGITUDE, WEST IS >> NEGATIVE" ; >> >> XLONG:units = "degree_east" ; >> >> XLONG:stagger = "" ; >> >> XLONG:coordinates = "XLONG XLAT" ; >> >> float XTIME(Time) ; >> >> XTIME:FieldType = 104 ; >> >> XTIME:MemoryOrder = "0 " ; >> >> XTIME:description = "minutes since >> 2016-07-29 12:00:00" ; >> >> XTIME:units = "minutes since 2016-07-29 >> 12:00:00" ; >> >> XTIME:stagger = "" ; >> >> >> >> Paraview complains that it cannot read a variable with more than three >> dimensions without time. But there appears to ?be? time (I?m very unclear >> what ?UNLIMITED? time , as seen in the header, refers to in this context). >> Is there any way I can work around this? Most frustrating. I can >> actually read this variable into QGIS, but I?d rather use the strengths of >> Paraview to visualize this data. >> >> >> >> Thanks in advance. >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Tue Aug 8 17:09:30 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 8 Aug 2017 17:09:30 -0400 Subject: [Paraview] paraview 5.4.1 rc3, mac os 10.11.6, volume rendering broken Message-ID: Hi all, Volume rendering seems to be broken on my laptop. The first version of ParaView this works correctly on is ParaView 5.2.0. (it is broken on 5.4.0 and 5.3.0) Here is the info about my graphics card. Thanks, Dan *AMD Radeon R9 M370X:* Chipset Model: AMD Radeon R9 M370X Type: GPU Bus: PCIe PCIe Lane Width: x8 VRAM (Total): 2048 MB Vendor: ATI (0x1002) Device ID: 0x6821 Revision ID: 0x0083 ROM Revision: 113-C5670E-777 gMux Version: 4.0.20 [3.2.8] EFI Driver Version: 01.00.777 Displays: *Color LCD:* Display Type: Retina LCD Resolution: 2880 x 1800 Retina Retina: Yes Pixel Depth: 32-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Built-In: Yes -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paraview-5.4.1-rc3-volume-rendering.png Type: image/png Size: 334396 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: paraview-5.2.0-volume-rendering.png Type: image/png Size: 355672 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Aug 8 17:17:32 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 8 Aug 2017 17:17:32 -0400 Subject: [Paraview] paraview 5.4.1 rc3, mac os 10.11.6, volume rendering broken In-Reply-To: References: Message-ID: Dan, This is a known issue [1] with the Projected Tetrahedra volume rendering algorithm on Mac. Cory [1] https://gitlab.kitware.com/paraview/paraview/issues/17303 On Tue, Aug 8, 2017 at 5:09 PM, Dan Lipsa wrote: > Hi all, > Volume rendering seems to be broken on my laptop. > The first version of ParaView this works correctly on is ParaView 5.2.0. > (it is broken on 5.4.0 and 5.3.0) > > Here is the info about my graphics card. > Thanks, > Dan > > > > > AMD Radeon R9 M370X: > > > Chipset Model: AMD Radeon R9 M370X > > Type: GPU > > Bus: PCIe > > PCIe Lane Width: x8 > > VRAM (Total): 2048 MB > > Vendor: ATI (0x1002) > > Device ID: 0x6821 > > Revision ID: 0x0083 > > ROM Revision: 113-C5670E-777 > > gMux Version: 4.0.20 [3.2.8] > > EFI Driver Version: 01.00.777 > > Displays: > > Color LCD: > > Display Type: Retina LCD > > Resolution: 2880 x 1800 Retina > > Retina: Yes > > Pixel Depth: 32-Bit Color (ARGB8888) > > Main Display: Yes > > Mirror: Off > > Online: Yes > > Built-In: Yes > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From dan.lipsa at kitware.com Tue Aug 8 17:42:25 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 8 Aug 2017 17:42:25 -0400 Subject: [Paraview] paraview 5.4.1 rc3, mac os 10.11.6, volume rendering broken In-Reply-To: References: Message-ID: I see. Thanks Cory. Dan On Tue, Aug 8, 2017 at 5:17 PM, Cory Quammen wrote: > Dan, > > This is a known issue [1] with the Projected Tetrahedra volume > rendering algorithm on Mac. > > Cory > > [1] https://gitlab.kitware.com/paraview/paraview/issues/17303 > > On Tue, Aug 8, 2017 at 5:09 PM, Dan Lipsa wrote: > > Hi all, > > Volume rendering seems to be broken on my laptop. > > The first version of ParaView this works correctly on is ParaView 5.2.0. > > (it is broken on 5.4.0 and 5.3.0) > > > > Here is the info about my graphics card. > > Thanks, > > Dan > > > > > > > > > > AMD Radeon R9 M370X: > > > > > > Chipset Model: AMD Radeon R9 M370X > > > > Type: GPU > > > > Bus: PCIe > > > > PCIe Lane Width: x8 > > > > VRAM (Total): 2048 MB > > > > Vendor: ATI (0x1002) > > > > Device ID: 0x6821 > > > > Revision ID: 0x0083 > > > > ROM Revision: 113-C5670E-777 > > > > gMux Version: 4.0.20 [3.2.8] > > > > EFI Driver Version: 01.00.777 > > > > Displays: > > > > Color LCD: > > > > Display Type: Retina LCD > > > > Resolution: 2880 x 1800 Retina > > > > Retina: Yes > > > > Pixel Depth: 32-Bit Color (ARGB8888) > > > > Main Display: Yes > > > > Mirror: Off > > > > Online: Yes > > > > Built-In: Yes > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lionel.wilhelm at epfl.ch Wed Aug 9 03:10:33 2017 From: lionel.wilhelm at epfl.ch (Wilhelm Lionel) Date: Wed, 9 Aug 2017 07:10:33 +0000 Subject: [Paraview] Screenshot resolution and 2D actors size In-Reply-To: References: <1502201225431.60834@epfl.ch> <1502202542032.8036@epfl.ch> , Message-ID: <1502262633199.69285@epfl.ch> Yes, it gives exactly the same output. I would be happy to send you my python script but I'm unfortunatly not allowed to do this for confidentiality reasons. I will see if I can reproduce the same behaviour with another dataset/script that I could share. Thanks a lot ! Lionel ________________________________________ De : Cory Quammen Envoy? : mardi 8 ao?t 2017 20:44 ? : Wilhelm Lionel Cc : Paraview at paraview.org Objet : Re: [Paraview] Screenshot resolution and 2D actors size > Regarding the pvbatch issue, do you have any hint? That is odd. I'm not sure what is going on exactly. Have you tried running your script with pvpython? Thanks, Cory > Kindly, > > Lionel > ________________________________________ > De : Cory Quammen [cory.quammen at kitware.com] > Envoy? : mardi 8 ao?t 2017 16:44 > ? : Wilhelm Lionel > Cc : paraview at paraview.org > Objet : Re: [Paraview] Screenshot resolution and 2D actors size > > Hi Lionel, > > This is a bug [1] that will be fixed in ParaView 5.4.1, coming out in > the next week or so. In fact, it is fixed in the latest 5.4.1 release > candidate, which you can get from www.paraview.org/download. > > HTH, > Cory > > [1] https://gitlab.kitware.com/paraview/paraview/issues/17603 > > On Tue, Aug 8, 2017 at 10:29 AM, Wilhelm Lionel wrote: >> Dear Paraview community, >> >> >> I created a full layout with 5 different views and would like to save a >> screenshot. The paraview GUI looks exactly like the image I want to save so >> I just use File -> Save Screenshot and keep the default resolution. The >> settings and the generated image are attached as "settings_test1" and >> "test1" (everything works fine). >> >> >> If I change the resolution of one pixel in one of the dimensions (width for >> example), the resulting image shows huge scalar bars. Here are also attached >> the screenshot settings and the resulting image ( as "settings_test2" and >> "test2" ). I have to mention that the small numbers on the views are in fact >> 3D Text objects. >> >> >> The entire visualization is produced by a Python script that I launch in the >> following way : Tools -> Python Shell -> Run Script. In order to avoid >> resolution problems, I also tried to run the script with pvbatch and at the >> end save the screenshot with the following settings : >> >> >> SaveScreenshot(OutputImageName,layout, SaveAllViews=1, >> ImageResolution=UsrImageRes, >> FontScaling="Scale fonts proportionally", >> SeparatorWidth=1, >> SeparatorColor=(1,1,1), >> ImageQuality=100 >> ) >> >> >> These settings are the same as the ones presented in the "settings_test*" >> images. The result attached as "test3.png". >> >> >> Is this a bug or this behaviour should be expected ? Does anybody has an >> idea ? Are the problems with pvbatch and the GUI related or not ? >> >> >> I'm using Paraview 5.4.0 with MPI enabled when I use the GUI. >> >> >> Kindly, >> >> >> Lionel Wilhelm >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From yvan.fournier at free.fr Wed Aug 9 06:29:40 2017 From: yvan.fournier at free.fr (yvan.fournier at free.fr) Date: Wed, 9 Aug 2017 12:29:40 +0200 (CEST) Subject: [Paraview] Question about plugins with Catalyst and Python scripts In-Reply-To: <425190736.204659731.1502273123678.JavaMail.root@zimbra10-e2> Message-ID: <1311768724.204732553.1502274580737.JavaMail.root@zimbra10-e2> Hello, We have been using Catalyst (with Python coprocessing scripts) in our code for quite a while now, and am trying to see how to make thing more user-friendly. One of the main issues we have is that if plugins are loaded in ParaView when using the Coprocessing Generator plugin, extra lines regarding those plugins may appear in the script, even when not dreclty used. For example, when the PointSprite plugins is enabled in PV 5.1, it adds opacity transfer function informations. This particular example might not be relevant to PV 5.4 with integrated PointGaussian, but other plugins may add similar entries, whether used or not in a particular view. This causes issues using Catalyst, as those plugins are not enabled in Catalyst (even using a full ParaView install with OSMesa as Catalyst, not editions, often too incomplete). One solution is to remove the "offending" lines (i.e. run once, check lines reported in error logs, removec those, run again, ...) which while not complicated, tends to scare users and requires multiple additional iterations to setup a visualization. A better solution would be to allow loading of plugins from the Python script (especially as I expect it would allow using plugins such as SurfaceLIC from within Catalyst), but I can't find any documentation for this. I seem to remember some people from Kitware mentioning this was possible in a live discussion I had, but have no additional details. Is there a way to tell ParaView/Catalyst to load a particular plugin from within a Python script ? IF yes, what's the syntax ? Best regards, Yvan From Llion.Evans at ukaea.uk Wed Aug 9 08:32:53 2017 From: Llion.Evans at ukaea.uk (Evans, Llion) Date: Wed, 9 Aug 2017 12:32:53 +0000 Subject: [Paraview] ParaviewWeb on EC2 Message-ID: Hi Seb/Claude, Hopefully this should be an easy answer. I?ve been trying to get Visualizer up and running on aws. I used the ami mentioned below (ami-34f3f65e) and can load the page in a browser which brings up the 'ParaViewWeb' logo and a spinning cog. After a short while I get an error message 'Session did not start before timeout expired. Check session logs.' Other than installing a local browser I've not changed much of anything on the AMI. What am I doing wrong? I assume it's something simple that I'm missing, like do I need to drop in a dataset somewhere before it'll even load the page? Kind regards, Llion From sebastien.jourdain at kitware.com Wed Aug 9 09:48:22 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 9 Aug 2017 09:48:22 -0400 Subject: [Paraview] ParaviewWeb on EC2 In-Reply-To: References: Message-ID: Did you look at the logs on the server to see if you could have some hints on what could be the issue? On Wed, Aug 9, 2017 at 8:32 AM, Evans, Llion wrote: > Hi Seb/Claude, > > Hopefully this should be an easy answer. > > I?ve been trying to get Visualizer up and running on aws. I used the ami > mentioned below (ami-34f3f65e) and can load the page in a browser which > brings up the 'ParaViewWeb' logo and a spinning cog. After a short while I > get an error message 'Session did not start before timeout expired. Check > session logs.' > > Other than installing a local browser I've not changed much of anything on > the AMI. What am I doing wrong? I assume it's something simple that I'm > missing, like do I need to drop in a dataset somewhere before it'll even > load the page? > > Kind regards, > Llion > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Aug 9 09:52:03 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 9 Aug 2017 09:52:03 -0400 Subject: [Paraview] Paraview source and its associated qt version In-Reply-To: References: Message-ID: On Wed, Aug 9, 2017 at 5:34 AM, Andrew Nicholson wrote: > Cory, > > Thanks for the info. Is there anywhere I can find this out when I download > the source? At the point of download? We don't list required versions on the downloads page I'm afraid. We do list some of the dependent library versions in the official binaries on this page: https://www.paraview.org/Wiki/ParaView/Binaries Qt version requirements are available in the source, though. See Documentation/dev/build.md. CMake will also tell you which version of Qt it finds when you configure the ParaView build, and which Qt version is officially recommended. Cory > Thanks > Andrew > > > On Tuesday, 8 August 2017, Cory Quammen wrote: >> >> Andrew, >> >> The officially supported version of Qt is 5.9, but you could use down >> to Qt 5.6 if you wanted. >> >> Best, >> Cory >> >> On Tue, Aug 8, 2017 at 4:25 PM, Andrew Nicholson >> wrote: >> > Is there anywhere that highlights what version of qt should be used for >> > building from source? Current version of qt being 5.9 from its website. >> > Is >> > paraview on this version yet or an older version. >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Search the list archives at: http://markmail.org/search/?q=ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From Llion.Evans at ukaea.uk Wed Aug 9 10:10:10 2017 From: Llion.Evans at ukaea.uk (Evans, Llion) Date: Wed, 9 Aug 2017 14:10:10 +0000 Subject: [Paraview] ParaviewWeb on EC2 In-Reply-To: References: Message-ID: I found the error below (there was a new entry for each time I refreshed the page on the browser). ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash-linux-shared-release_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 333 vtkXOpenGLRenderWindow (0x64982b0): bad X server connection. DISPLAY=:0.0. Aborting. I assume that this is due to my choice of machine (i.e. using the aws free tier which doesn?t have a gpu). Llion From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: 09 August 2017 14:48 To: Evans, Llion Cc: paraview at paraview.org Subject: Re: [Paraview] ParaviewWeb on EC2 Did you look at the logs on the server to see if you could have some hints on what could be the issue? On Wed, Aug 9, 2017 at 8:32 AM, Evans, Llion > wrote: Hi Seb/Claude, Hopefully this should be an easy answer. I?ve been trying to get Visualizer up and running on aws. I used the ami mentioned below (ami-34f3f65e) and can load the page in a browser which brings up the 'ParaViewWeb' logo and a spinning cog. After a short while I get an error message 'Session did not start before timeout expired. Check session logs.' Other than installing a local browser I've not changed much of anything on the AMI. What am I doing wrong? I assume it's something simple that I'm missing, like do I need to drop in a dataset somewhere before it'll even load the page? Kind regards, Llion _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From shayan.nikoohemat at gmail.com Wed Aug 9 10:44:31 2017 From: shayan.nikoohemat at gmail.com (Shayan Nikoohemat) Date: Wed, 9 Aug 2017 16:44:31 +0200 Subject: [Paraview] Fwd: add dataset names as a field to the groupdataset In-Reply-To: References: Message-ID: Is it possible automatically assign block numbers in a group data set to a new field and replace them with each data set name? For example I have data sets of points: wall1, wall2 , ceiling, floor and then I make a group dataset: groupDatasets1 = GroupDatasets(Input=[wall_1, floor_1, ceiling_1, wall_2]) Then I have below spread sheet: [image: Inline image 1] Then I need to make a new field e.g. "groups" (better through a programmable filter) and for each group I add the name of the dataset. The expected result table would looks like this: BlockNumber, Point ID, vtkPointId, Points, Label, Label2, Groups 1, 0, 36617, ..., ..., ... , ..., .............................................. wall_1 1, 1 , 420914, ..., ..., ... , ..., .............................................. wall_1 1, 2, 444161, ..., ..., ... , ..., .............................................. wall_1 2, 0, 27932, ..., ..., ... , ..., ... .......................................... ceiling 2, 1 , 296452, ..., ..., ... , ..., ... ......................................... ceiling 2, 2, 315135, ..., ..., ... , ..., ... ........................................ ceiling 3, 0, 36617, ..., ..., ... , ..., ... ......................................... wall_2 3, 1 , 420914, ..., ..., ... , ..., ... ......................................... wall_2 So my question has two parts: 1. How do we automatically group datasets in the pipeline browser? 2. While grouping, how to add a field as an attribute that contains the datasets names. Then I can save this spreadsheet for later use. Thanks for any help. Shayan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 44509 bytes Desc: not available URL: From sebastien.jourdain at kitware.com Wed Aug 9 12:07:23 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 9 Aug 2017 12:07:23 -0400 Subject: [Paraview] ParaviewWeb on EC2 In-Reply-To: References: Message-ID: Yes, you need a g2 On Wed, Aug 9, 2017 at 10:10 AM, Evans, Llion wrote: > I found the error below (there was a new entry for each time I refreshed > the page on the browser). > > > > ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash- > linux-shared-release_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, > line 333 > > vtkXOpenGLRenderWindow (0x64982b0): bad X server connection. DISPLAY=:0.0. > Aborting. > > > > I assume that this is due to my choice of machine (i.e. using the aws free > tier which doesn?t have a gpu). > > > > Llion > > > > *From:* Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] > *Sent:* 09 August 2017 14:48 > *To:* Evans, Llion > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] ParaviewWeb on EC2 > > > > Did you look at the logs on the server to see if you could have some hints > on what could be the issue? > > > > On Wed, Aug 9, 2017 at 8:32 AM, Evans, Llion wrote: > > Hi Seb/Claude, > > Hopefully this should be an easy answer. > > I?ve been trying to get Visualizer up and running on aws. I used the ami > mentioned below (ami-34f3f65e) and can load the page in a browser which > brings up the 'ParaViewWeb' logo and a spinning cog. After a short while I > get an error message 'Session did not start before timeout expired. Check > session logs.' > > Other than installing a local browser I've not changed much of anything on > the AMI. What am I doing wrong? I assume it's something simple that I'm > missing, like do I need to drop in a dataset somewhere before it'll even > load the page? > > Kind regards, > Llion > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Llion.Evans at ukaea.uk Wed Aug 9 12:19:43 2017 From: Llion.Evans at ukaea.uk (Evans, Llion) Date: Wed, 9 Aug 2017 16:19:43 +0000 Subject: [Paraview] ParaviewWeb on EC2 In-Reply-To: References: Message-ID: Ok, thanks. I guess to get it to work on the free tier I?d need to rebuild with mesa. I?d rather not go down that path as I?m not knowledgeable enough. That means I need to go back to trying to install on my local machine, but I was having difficulty getting Visualizer to start properly on Ubuntu 16. I notice you mentioned a compatibility issue with 16. Will this work on a VM? If so, I could try copying some of the file structure from the AMI to a fresh Ubuntu 14 VM install? Llion From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: 09 August 2017 17:07 To: Evans, Llion Cc: paraview at paraview.org Subject: Re: [Paraview] ParaviewWeb on EC2 Yes, you need a g2 On Wed, Aug 9, 2017 at 10:10 AM, Evans, Llion > wrote: I found the error below (there was a new entry for each time I refreshed the page on the browser). ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash-linux-shared-release_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 333 vtkXOpenGLRenderWindow (0x64982b0): bad X server connection. DISPLAY=:0.0. Aborting. I assume that this is due to my choice of machine (i.e. using the aws free tier which doesn?t have a gpu). Llion From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] Sent: 09 August 2017 14:48 To: Evans, Llion Cc: paraview at paraview.org Subject: Re: [Paraview] ParaviewWeb on EC2 Did you look at the logs on the server to see if you could have some hints on what could be the issue? On Wed, Aug 9, 2017 at 8:32 AM, Evans, Llion > wrote: Hi Seb/Claude, Hopefully this should be an easy answer. I?ve been trying to get Visualizer up and running on aws. I used the ami mentioned below (ami-34f3f65e) and can load the page in a browser which brings up the 'ParaViewWeb' logo and a spinning cog. After a short while I get an error message 'Session did not start before timeout expired. Check session logs.' Other than installing a local browser I've not changed much of anything on the AMI. What am I doing wrong? I assume it's something simple that I'm missing, like do I need to drop in a dataset somewhere before it'll even load the page? Kind regards, Llion _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Aug 9 12:42:41 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 9 Aug 2017 12:42:41 -0400 Subject: [Paraview] ParaviewWeb on EC2 In-Reply-To: References: Message-ID: If you just want to run it on your desktop, just download a ParaView binary and you will be all set. The only thing with Ubuntu 16, is that the documentation explaining how to make services and configure apache might be slightly off. Also the ansible provisioning script won't work, but everything can be done by hand without too much issue. Seb On Wed, Aug 9, 2017 at 12:19 PM, Evans, Llion wrote: > Ok, thanks. I guess to get it to work on the free tier I?d need to rebuild > with mesa. I?d rather not go down that path as I?m not knowledgeable enough. > > > > That means I need to go back to trying to install on my local machine, but > I was having difficulty getting Visualizer to start properly on Ubuntu 16. > > > > I notice you mentioned a compatibility issue with 16. Will this work on a > VM? If so, I could try copying some of the file structure from the AMI to a > fresh Ubuntu 14 VM install? > > > > Llion > > > > *From:* Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] > *Sent:* 09 August 2017 17:07 > > *To:* Evans, Llion > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] ParaviewWeb on EC2 > > > > Yes, you need a g2 > > > > On Wed, Aug 9, 2017 at 10:10 AM, Evans, Llion > wrote: > > I found the error below (there was a new entry for each time I refreshed > the page on the browser). > > > > ERROR: In /home/kitware/Dashboards/buildbot/paraview-debian4dash- > linux-shared-release_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, > line 333 > > vtkXOpenGLRenderWindow (0x64982b0): bad X server connection. DISPLAY=:0.0. > Aborting. > > > > I assume that this is due to my choice of machine (i.e. using the aws free > tier which doesn?t have a gpu). > > > > Llion > > > > *From:* Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] > *Sent:* 09 August 2017 14:48 > *To:* Evans, Llion > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] ParaviewWeb on EC2 > > > > Did you look at the logs on the server to see if you could have some hints > on what could be the issue? > > > > On Wed, Aug 9, 2017 at 8:32 AM, Evans, Llion wrote: > > Hi Seb/Claude, > > Hopefully this should be an easy answer. > > I?ve been trying to get Visualizer up and running on aws. I used the ami > mentioned below (ami-34f3f65e) and can load the page in a browser which > brings up the 'ParaViewWeb' logo and a spinning cog. After a short while I > get an error message 'Session did not start before timeout expired. Check > session logs.' > > Other than installing a local browser I've not changed much of anything on > the AMI. What am I doing wrong? I assume it's something simple that I'm > missing, like do I need to drop in a dataset somewhere before it'll even > load the page? > > Kind regards, > Llion > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.borduas at caboma.com Wed Aug 9 12:52:34 2017 From: jonathan.borduas at caboma.com (Jonathan Borduas) Date: Wed, 9 Aug 2017 16:52:34 +0000 Subject: [Paraview] Rendering/Screenshot with "deep color" (REPOST) Message-ID: Dear Paraviewers, As seen in the attached image, we can see the transitions between the different grays that occur with a 24bits-per-pixel screenshot export of ParaView. While most image editing software and printer support 32bits-per-pixel such as Ms Paint and Photoshop. Most GPU manufacturers call that "deep color". Some display already have 30bpp/10bpc. Is there a setting available to configure the image bit depth (Bit Per Pixel, Bit Per Channel) in ParaView ? If no, is there any short time plans to integrate the control over the bit depth ? Best regards, Jonathan Borduas -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test2.tif Type: image/tiff Size: 62684 bytes Desc: test2.tif URL: From utkarsh.ayachit at kitware.com Wed Aug 9 14:32:46 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 9 Aug 2017 14:32:46 -0400 Subject: [Paraview] [vtkusers] SafeDownCast does not work properly In-Reply-To: <003c01d3113b$074918d0$15db4a70$@gmx.de> References: <001801d31127$33395b30$99ac1190$@gmx.de> <003c01d3113b$074918d0$15db4a70$@gmx.de> Message-ID: Maximilian, That's not a reasonable expectation. Mesh **isa** vtkPolyData, and not vice-versa. Look at docs for dynamic_cast in C++. In spirit, SafeDownCast is essentially the same thing. Utkarsh On Wed, Aug 9, 2017 at 2:12 PM, Maximilian Weiherer < weiherer.maximilian at gmx.de> wrote: > Hi Utkarsh, > > > > thanks for your reply. I created the custom mesh class in order to add > some new functionality (e.g. a method to check whether a mesh intersects > another mesh). The vtkPolyData object which should be casted is the output > of a vtkSTLReader, i.e. > > Mesh* mesh = Mesh::SafeDownCast(reader->GetOutput()); // mesh always > equals NULL > > Best regards > > Maximilian > > > > *Von:* Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > *Gesendet:* Mittwoch, 9. August 2017 17:53 > *An:* Maximilian Weiherer > *Cc:* vtk > *Betreff:* Re: [vtkusers] SafeDownCast does not work properly > > > > Maximilian, > > > > I am confused why any arbitrary vtkPolyData object would be castable to > "Mesh". It will only return non-null, if it's is indeed created as a Mesh. > Is it? Where's the "" coming from? > > > > Utkarsh > > > > On Wed, Aug 9, 2017 at 11:50 AM, Maximilian Weiherer < > weiherer.maximilian at gmx.de> wrote: > > Hi all, > > > > I defined my own mesh class (named *Mesh*) by inheriting from > vtkPolyData. Now I am struggling with the SafeDownCast method in order to > cast a vtkPolyData object into a *Mesh* object. Whenever I am applying a > SafeDownCast to a vtkPolyData object, NULL is returned. > > > > The *Mesh* class looks as follows: > > > > class Mesh : public vtkPolyData > > { > > public: > > static Mesh* New(); > > vtkTypeMacro(Mesh, vtkPolyData); > > void PrintSelf(ostream& os, vtkIndent indent); > > > > protected: > > Mesh(); > > ~Mesh(); > > private: > > Mesh(const Mesh&); // Not implemented. > > void operator=(const Mesh&); // Not implemented. > > }; > > > > ?and this is the cast that does not work properly: > > > > Mesh* mesh = Mesh::SafeDownCast(); // mesh always > equals NULL > > > > Any help would be appreciated. Thanks! > > > > Best regards > > Maximilian > > > > [image: Das Bild wurde vom Absender entfernt.] > > > Virenfrei. www.avast.com > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the VTK FAQ at: > http://www.vtk.org/Wiki/VTK_FAQ > > Search the list archives at: http://markmail.org/search/?q=vtkusers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtkusers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 350 bytes Desc: not available URL: From leonardopessanha74 at gmail.com Wed Aug 9 18:24:40 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Wed, 9 Aug 2017 19:24:40 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: Hi! I did the changes. The only thing I am not sure it's the right paths in the imports of ${ROOT}/src/index.js import CompositeComponent from '..'; > import BGColorComponent from '../../BackgroundColor'; > > Should I change this paths? I did try import CompositeComponent from '/home/user/MyWebProject/node_modules/paraviewweb/src'; import BGColorComponent from '/home/user/MyWebProject/node_modules/paraviewweb/src/Component/Native/BackgroundColor'; and import CompositeComponent from '/home/user/MyWebProject/node_modules/paraviewweb/src/Component'; import BGColorComponent from '/home/user/MyWebProject/node_modules/paraviewweb/src/Component/Native/BackgroundColor'; and import CompositeComponent from '/home/user/MyWebProject/node_modules/paraviewweb/src/Component/Native'; import BGColorComponent from '/home/user/MyWebProject/node_modules/paraviewweb/src/Component/Native/BackgroundColor'; With the last 2 sucessfully building but with JS errors in Firefox TypeError: _Component2.default is not a constructor[Learn More] > and TypeError: _Native2.default is not a constructor > and the first one not building and giving me a lot of Module not found: Error: Can't resolve > Thanks in advance! Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > If I get to it, I'll do what I've done with vtk.js to support both. > > See: https://github.com/Kitware/vtk-js/blob/master/ > Utilities/config/dependency.js > > On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha > wrote: > >> Thank you, Sebastien. I will give a try! >> >> Do you believe it's best to rollback webpack to 1.x or to change the >> webpack.config.js in order to fit webpack 2.x API? >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> Based on the path given in the setup guide, you should copy the example >>> you want to reproduce inside ${ROOT}/src/* where the main example file >>> should be named index.js. >>> >>> Then you should be able to build your example using the npm command: >>> "npm run build". >>> >>> Maybe the vtk.js explanation might be easier to follow ( >>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_dependency.html), >>> but the concept is exactly the same. >>> As it is picking the example available here https://kitware.github.io >>> /vtk-js/examples/Cone.html | https://github.com/Kitware/v >>> tk-js/tree/master/Examples/WebGL/Cone >>> and making a standalone application from it. >>> >>> Just be aware that vtk.js is using webpack2 which is not the case for >>> ParaViewWeb. >>> >>> Hope that helps, >>> >>> Seb >>> >>> >>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>> leonardopessanha74 at gmail.com> wrote: >>> >>>> Hi! >>>> >>>> I would like to know the steps in order to run simple example like the >>>> following one: >>>> >>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>> >>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>> with the main things. >>>> I have little to no background in web development. >>>> >>>> What I managed to do so far was to create my own project and add >>>> paraviewweb to it like its described in https://kitware.github.io/para >>>> viewweb/docs/setup.html . >>>> >>>> I don't know what to do next but I believe that a great start would be >>>> to know where to put the source code in the example and how to run it. >>>> >>>> Thanks in advance, >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>> >>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>> leonardopessanha74 at gmail.com> wrote: >>> >>>> Hi! >>>> >>>> I would like to know the steps in order to run simple example like the >>>> following one: >>>> >>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>> >>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>> with the main things. >>>> I have little to no background in web development. >>>> >>>> What I managed to do so far was to create my own project and add >>>> paraviewweb to it like its described in https://kitware.github.io/para >>>> viewweb/docs/setup.html . >>>> >>>> I don't know what to do next but I believe that a great start would be >>>> to know where to put the source code in the example and how to run it. >>>> >>>> Thanks in advance, >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Aug 9 18:38:58 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 9 Aug 2017 18:38:58 -0400 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: The import should start with 'paraviewweb' then you provide the full path from there like: import BGColorComponent from 'paraviewweb/src/Component/Native/ BackgroundColor'; On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha wrote: > Hi! I did the changes. The only thing I am not sure it's the right paths > in the imports of ${ROOT}/src/index.js > > import CompositeComponent from '..'; >> import BGColorComponent from '../../BackgroundColor'; >> >> > Should I change this paths? > > I did try > > import CompositeComponent from '/home/user/MyWebProject/node_ > modules/paraviewweb/src'; > import BGColorComponent from '/home/user/MyWebProject/node_ > modules/paraviewweb/src/Component/Native/BackgroundColor'; > > and > > import CompositeComponent from '/home/user/MyWebProject/node_ > modules/paraviewweb/src/Component'; > import BGColorComponent from '/home/user/MyWebProject/node_ > modules/paraviewweb/src/Component/Native/BackgroundColor'; > > and > > import CompositeComponent from '/home/user/MyWebProject/node_ > modules/paraviewweb/src/Component/Native'; > import BGColorComponent from '/home/user/MyWebProject/node_ > modules/paraviewweb/src/Component/Native/BackgroundColor'; > > With the last 2 sucessfully building but with JS errors in Firefox > > TypeError: _Component2.default is not a constructor[Learn More] >> > > and > > TypeError: _Native2.default is not a constructor >> > > and the first one not building and giving me a lot of > > Module not found: Error: Can't resolve >> > > > Thanks in advance! > > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain com>: > >> If I get to it, I'll do what I've done with vtk.js to support both. >> >> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >> /config/dependency.js >> >> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> Thank you, Sebastien. I will give a try! >>> >>> Do you believe it's best to rollback webpack to 1.x or to change the >>> webpack.config.js in order to fit webpack 2.x API? >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> Based on the path given in the setup guide, you should copy the example >>>> you want to reproduce inside ${ROOT}/src/* where the main example file >>>> should be named index.js. >>>> >>>> Then you should be able to build your example using the npm command: >>>> "npm run build". >>>> >>>> Maybe the vtk.js explanation might be easier to follow ( >>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_dependency.html), >>>> but the concept is exactly the same. >>>> As it is picking the example available here https://kitware.github.io >>>> /vtk-js/examples/Cone.html | https://github.com/Kitware/v >>>> tk-js/tree/master/Examples/WebGL/Cone >>>> and making a standalone application from it. >>>> >>>> Just be aware that vtk.js is using webpack2 which is not the case for >>>> ParaViewWeb. >>>> >>>> Hope that helps, >>>> >>>> Seb >>>> >>>> >>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>> leonardopessanha74 at gmail.com> wrote: >>>> >>>>> Hi! >>>>> >>>>> I would like to know the steps in order to run simple example like the >>>>> following one: >>>>> >>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>> >>>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>>> with the main things. >>>>> I have little to no background in web development. >>>>> >>>>> What I managed to do so far was to create my own project and add >>>>> paraviewweb to it like its described in https://kitware.github.io/para >>>>> viewweb/docs/setup.html . >>>>> >>>>> I don't know what to do next but I believe that a great start would be >>>>> to know where to put the source code in the example and how to run it. >>>>> >>>>> Thanks in advance, >>>>> >>>>> Leonardo Pessanha >>>>> Laboratory of Computational Methods in Engineering >>>>> Federal University of Rio de Janeiro - COPPE >>>>> Rio de Janeiro, RJ, Brasil >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> >>>> >>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>> leonardopessanha74 at gmail.com> wrote: >>>> >>>>> Hi! >>>>> >>>>> I would like to know the steps in order to run simple example like the >>>>> following one: >>>>> >>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>> >>>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>>> with the main things. >>>>> I have little to no background in web development. >>>>> >>>>> What I managed to do so far was to create my own project and add >>>>> paraviewweb to it like its described in https://kitware.github.io/para >>>>> viewweb/docs/setup.html . >>>>> >>>>> I don't know what to do next but I believe that a great start would be >>>>> to know where to put the source code in the example and how to run it. >>>>> >>>>> Thanks in advance, >>>>> >>>>> Leonardo Pessanha >>>>> Laboratory of Computational Methods in Engineering >>>>> Federal University of Rio de Janeiro - COPPE >>>>> Rio de Janeiro, RJ, Brasil >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Wed Aug 9 18:58:47 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Wed, 9 Aug 2017 19:58:47 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: So I am not sure of the first path yet. Is it 'paraviewweb/src/' or 'paraviewweb/src/Component'? I have the exactly same result using full path or starting with 'paraviewweb' Using: import CompositeComponent from 'paraviewweb/src/'; > import BGColorComponent from > 'paraviewweb/src/Component/Native/BackgroundColor'; > Outputs a lot of: Module not found: Error: Can't resolve > So I did a 'npm list x' with x being the modules it couldn't resolve(axios, hammerjs and etc) and none of then was installed. root at PC:~/MyWebProject# npm list hammerjs > projeto1 at 0.0.1 /home/gabriel/MyWebProject > ??? (empty) > > root at PC:~/MyWebProject# npm list axios > projeto1 at 0.0.1 /home/gabriel/MyWebProject > ??? (empty) > Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite --save-dev* failed installing the dependencies correctly? Best regards, Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > The import should start with 'paraviewweb' then you provide the full path > from there like: > > import BGColorComponent from 'paraviewweb/src/Component/Native/ > BackgroundColor'; > > On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha > wrote: > >> Hi! I did the changes. The only thing I am not sure it's the right paths >> in the imports of ${ROOT}/src/index.js >> >> import CompositeComponent from '..'; >>> import BGColorComponent from '../../BackgroundColor'; >>> >>> >> Should I change this paths? >> >> I did try >> >> import CompositeComponent from '/home/user/MyWebProject/node_ >> modules/paraviewweb/src'; >> import BGColorComponent from '/home/user/MyWebProject/node_ >> modules/paraviewweb/src/Component/Native/BackgroundColor'; >> >> and >> >> import CompositeComponent from '/home/user/MyWebProject/node_ >> modules/paraviewweb/src/Component'; >> import BGColorComponent from '/home/user/MyWebProject/node_ >> modules/paraviewweb/src/Component/Native/BackgroundColor'; >> >> and >> >> import CompositeComponent from '/home/user/MyWebProject/node_ >> modules/paraviewweb/src/Component/Native'; >> import BGColorComponent from '/home/user/MyWebProject/node_ >> modules/paraviewweb/src/Component/Native/BackgroundColor'; >> >> With the last 2 sucessfully building but with JS errors in Firefox >> >> TypeError: _Component2.default is not a constructor[Learn More] >>> >> >> and >> >> TypeError: _Native2.default is not a constructor >>> >> >> and the first one not building and giving me a lot of >> >> Module not found: Error: Can't resolve >>> >> >> >> Thanks in advance! >> >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> If I get to it, I'll do what I've done with vtk.js to support both. >>> >>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>> /config/dependency.js >>> >>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>> leonardopessanha74 at gmail.com> wrote: >>> >>>> Thank you, Sebastien. I will give a try! >>>> >>>> Do you believe it's best to rollback webpack to 1.x or to change the >>>> webpack.config.js in order to fit webpack 2.x API? >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> Based on the path given in the setup guide, you should copy the >>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>> file should be named index.js. >>>>> >>>>> Then you should be able to build your example using the npm command: >>>>> "npm run build". >>>>> >>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_dependency.html), >>>>> but the concept is exactly the same. >>>>> As it is picking the example available here https://kitware.github.io >>>>> /vtk-js/examples/Cone.html | https://github.com/Kitware/v >>>>> tk-js/tree/master/Examples/WebGL/Cone >>>>> and making a standalone application from it. >>>>> >>>>> Just be aware that vtk.js is using webpack2 which is not the case for >>>>> ParaViewWeb. >>>>> >>>>> Hope that helps, >>>>> >>>>> Seb >>>>> >>>>> >>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>> leonardopessanha74 at gmail.com> wrote: >>>>> >>>>>> Hi! >>>>>> >>>>>> I would like to know the steps in order to run simple example like >>>>>> the following one: >>>>>> >>>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>>> >>>>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>>>> with the main things. >>>>>> I have little to no background in web development. >>>>>> >>>>>> What I managed to do so far was to create my own project and add >>>>>> paraviewweb to it like its described in >>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>> >>>>>> I don't know what to do next but I believe that a great start would >>>>>> be to know where to put the source code in the example and how to run it. >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> Leonardo Pessanha >>>>>> Laboratory of Computational Methods in Engineering >>>>>> Federal University of Rio de Janeiro - COPPE >>>>>> Rio de Janeiro, RJ, Brasil >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>> leonardopessanha74 at gmail.com> wrote: >>>>> >>>>>> Hi! >>>>>> >>>>>> I would like to know the steps in order to run simple example like >>>>>> the following one: >>>>>> >>>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>>> >>>>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>>>> with the main things. >>>>>> I have little to no background in web development. >>>>>> >>>>>> What I managed to do so far was to create my own project and add >>>>>> paraviewweb to it like its described in >>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>> >>>>>> I don't know what to do next but I believe that a great start would >>>>>> be to know where to put the source code in the example and how to run it. >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> Leonardo Pessanha >>>>>> Laboratory of Computational Methods in Engineering >>>>>> Federal University of Rio de Janeiro - COPPE >>>>>> Rio de Janeiro, RJ, Brasil >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Wed Aug 9 19:37:24 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Wed, 9 Aug 2017 20:37:24 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: So, I was able to build using 'paraviewweb/src/' and installing forcibly mout, axios and hammerjs packages. Now there's other js errors that I am going after like /plotly.js\ and global reference ones ! It's definitely not a simple task to build an example of paraviewweb as a standalone app. Definitely will come back with updates. Best regards, Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-08-09 19:58 GMT-03:00 L?o Pessanha : > So I am not sure of the first path yet. Is it 'paraviewweb/src/' or > 'paraviewweb/src/Component'? > > I have the exactly same result using full path or starting with > 'paraviewweb' > > Using: > > import CompositeComponent from 'paraviewweb/src/'; >> import BGColorComponent from 'paraviewweb/src/Component/ >> Native/BackgroundColor'; >> > > Outputs a lot of: > > Module not found: Error: Can't resolve >> > > So I did a 'npm list x' with x being the modules it couldn't > resolve(axios, hammerjs and etc) and none of then was installed. > > root at PC:~/MyWebProject# npm list hammerjs >> projeto1 at 0.0.1 /home/gabriel/MyWebProject >> ??? (empty) >> >> root at PC:~/MyWebProject# npm list axios >> projeto1 at 0.0.1 /home/gabriel/MyWebProject >> ??? (empty) >> > > > Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite > --save-dev* failed installing the dependencies correctly? > > Best regards, > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain com>: > >> The import should start with 'paraviewweb' then you provide the full path >> from there like: >> >> import BGColorComponent from 'paraviewweb/src/Component/Native/ >> BackgroundColor'; >> >> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> Hi! I did the changes. The only thing I am not sure it's the right paths >>> in the imports of ${ROOT}/src/index.js >>> >>> import CompositeComponent from '..'; >>>> import BGColorComponent from '../../BackgroundColor'; >>>> >>>> >>> Should I change this paths? >>> >>> I did try >>> >>> import CompositeComponent from '/home/user/MyWebProject/node_ >>> modules/paraviewweb/src'; >>> import BGColorComponent from '/home/user/MyWebProject/node_ >>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>> >>> and >>> >>> import CompositeComponent from '/home/user/MyWebProject/node_ >>> modules/paraviewweb/src/Component'; >>> import BGColorComponent from '/home/user/MyWebProject/node_ >>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>> >>> and >>> >>> import CompositeComponent from '/home/user/MyWebProject/node_ >>> modules/paraviewweb/src/Component/Native'; >>> import BGColorComponent from '/home/user/MyWebProject/node_ >>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>> >>> With the last 2 sucessfully building but with JS errors in Firefox >>> >>> TypeError: _Component2.default is not a constructor[Learn More] >>>> >>> >>> and >>> >>> TypeError: _Native2.default is not a constructor >>>> >>> >>> and the first one not building and giving me a lot of >>> >>> Module not found: Error: Can't resolve >>>> >>> >>> >>> Thanks in advance! >>> >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> If I get to it, I'll do what I've done with vtk.js to support both. >>>> >>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>> /config/dependency.js >>>> >>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>> leonardopessanha74 at gmail.com> wrote: >>>> >>>>> Thank you, Sebastien. I will give a try! >>>>> >>>>> Do you believe it's best to rollback webpack to 1.x or to change the >>>>> webpack.config.js in order to fit webpack 2.x API? >>>>> >>>>> Leonardo Pessanha >>>>> Laboratory of Computational Methods in Engineering >>>>> Federal University of Rio de Janeiro - COPPE >>>>> Rio de Janeiro, RJ, Brasil >>>>> >>>>> >>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> Based on the path given in the setup guide, you should copy the >>>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>>> file should be named index.js. >>>>>> >>>>>> Then you should be able to build your example using the npm command: >>>>>> "npm run build". >>>>>> >>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>> ndency.html), but the concept is exactly the same. >>>>>> As it is picking the example available here https://kitware.github.io >>>>>> /vtk-js/examples/Cone.html | https://github.com/Kitware/v >>>>>> tk-js/tree/master/Examples/WebGL/Cone >>>>>> and making a standalone application from it. >>>>>> >>>>>> Just be aware that vtk.js is using webpack2 which is not the case for >>>>>> ParaViewWeb. >>>>>> >>>>>> Hope that helps, >>>>>> >>>>>> Seb >>>>>> >>>>>> >>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>> >>>>>>> Hi! >>>>>>> >>>>>>> I would like to know the steps in order to run simple example like >>>>>>> the following one: >>>>>>> >>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>>>> >>>>>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>>>>> with the main things. >>>>>>> I have little to no background in web development. >>>>>>> >>>>>>> What I managed to do so far was to create my own project and add >>>>>>> paraviewweb to it like its described in >>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>> >>>>>>> I don't know what to do next but I believe that a great start would >>>>>>> be to know where to put the source code in the example and how to run it. >>>>>>> >>>>>>> Thanks in advance, >>>>>>> >>>>>>> Leonardo Pessanha >>>>>>> Laboratory of Computational Methods in Engineering >>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>> >>>>>>> Hi! >>>>>>> >>>>>>> I would like to know the steps in order to run simple example like >>>>>>> the following one: >>>>>>> >>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>>>> >>>>>>> It doesn't need to be a really elaborated tutorial, but a simple one >>>>>>> with the main things. >>>>>>> I have little to no background in web development. >>>>>>> >>>>>>> What I managed to do so far was to create my own project and add >>>>>>> paraviewweb to it like its described in >>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>> >>>>>>> I don't know what to do next but I believe that a great start would >>>>>>> be to know where to put the source code in the example and how to run it. >>>>>>> >>>>>>> Thanks in advance, >>>>>>> >>>>>>> Leonardo Pessanha >>>>>>> Laboratory of Computational Methods in Engineering >>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Thu Aug 10 10:35:02 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 10 Aug 2017 10:35:02 -0400 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: With ParaViewWeb, we force the user to pick the version of the dependencies they wants to install instead of forcing them. Regarding your import path they are still wrong. from paraviewweb/src/Component/Native/Composite/example/index.js when you import '..' that resolve to paraviewweb/src/Component/Native/Composite which means your imports should be: import CompositeComponent from 'paraviewweb/src/Component/Native/Composite '; import BGColorComponent from 'paraviewweb/src/Component/ Native/BackgroundColor'; On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha wrote: > So, I was able to build using 'paraviewweb/src/' and installing forcibly > mout, axios and hammerjs packages. > > Now there's other js errors that I am going after like /plotly.js\ and > global reference ones ! > > It's definitely not a simple task to build an example of paraviewweb as a > standalone app. > > Definitely will come back with updates. > > Best regards, > > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > 2017-08-09 19:58 GMT-03:00 L?o Pessanha : > >> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or >> 'paraviewweb/src/Component'? >> >> I have the exactly same result using full path or starting with >> 'paraviewweb' >> >> Using: >> >> import CompositeComponent from 'paraviewweb/src/'; >>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>> ive/BackgroundColor'; >>> >> >> Outputs a lot of: >> >> Module not found: Error: Can't resolve >>> >> >> So I did a 'npm list x' with x being the modules it couldn't >> resolve(axios, hammerjs and etc) and none of then was installed. >> >> root at PC:~/MyWebProject# npm list hammerjs >>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>> ??? (empty) >>> >>> root at PC:~/MyWebProject# npm list axios >>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>> ??? (empty) >>> >> >> >> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >> --save-dev* failed installing the dependencies correctly? >> >> Best regards, >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> The import should start with 'paraviewweb' then you provide the full >>> path from there like: >>> >>> import BGColorComponent from 'paraviewweb/src/Component/Native/ >>> BackgroundColor'; >>> >>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>> leonardopessanha74 at gmail.com> wrote: >>> >>>> Hi! I did the changes. The only thing I am not sure it's the right >>>> paths in the imports of ${ROOT}/src/index.js >>>> >>>> import CompositeComponent from '..'; >>>>> import BGColorComponent from '../../BackgroundColor'; >>>>> >>>>> >>>> Should I change this paths? >>>> >>>> I did try >>>> >>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>> modules/paraviewweb/src'; >>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>> >>>> and >>>> >>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>> modules/paraviewweb/src/Component'; >>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>> >>>> and >>>> >>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>> modules/paraviewweb/src/Component/Native'; >>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>> >>>> With the last 2 sucessfully building but with JS errors in Firefox >>>> >>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>> >>>> >>>> and >>>> >>>> TypeError: _Native2.default is not a constructor >>>>> >>>> >>>> and the first one not building and giving me a lot of >>>> >>>> Module not found: Error: Can't resolve >>>>> >>>> >>>> >>>> Thanks in advance! >>>> >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> If I get to it, I'll do what I've done with vtk.js to support both. >>>>> >>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>> /config/dependency.js >>>>> >>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>> leonardopessanha74 at gmail.com> wrote: >>>>> >>>>>> Thank you, Sebastien. I will give a try! >>>>>> >>>>>> Do you believe it's best to rollback webpack to 1.x or to change the >>>>>> webpack.config.js in order to fit webpack 2.x API? >>>>>> >>>>>> Leonardo Pessanha >>>>>> Laboratory of Computational Methods in Engineering >>>>>> Federal University of Rio de Janeiro - COPPE >>>>>> Rio de Janeiro, RJ, Brasil >>>>>> >>>>>> >>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> Based on the path given in the setup guide, you should copy the >>>>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>>>> file should be named index.js. >>>>>>> >>>>>>> Then you should be able to build your example using the npm command: >>>>>>> "npm run build". >>>>>>> >>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>> ndency.html), but the concept is exactly the same. >>>>>>> As it is picking the example available here >>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/WebGL/Cone >>>>>>> and making a standalone application from it. >>>>>>> >>>>>>> Just be aware that vtk.js is using webpack2 which is not the case >>>>>>> for ParaViewWeb. >>>>>>> >>>>>>> Hope that helps, >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> >>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>> >>>>>>>> Hi! >>>>>>>> >>>>>>>> I would like to know the steps in order to run simple example like >>>>>>>> the following one: >>>>>>>> >>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>>>>> >>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>> one with the main things. >>>>>>>> I have little to no background in web development. >>>>>>>> >>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>> paraviewweb to it like its described in >>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>> >>>>>>>> I don't know what to do next but I believe that a great start would >>>>>>>> be to know where to put the source code in the example and how to run it. >>>>>>>> >>>>>>>> Thanks in advance, >>>>>>>> >>>>>>>> Leonardo Pessanha >>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>> >>>>>>>> Hi! >>>>>>>> >>>>>>>> I would like to know the steps in order to run simple example like >>>>>>>> the following one: >>>>>>>> >>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/index.html >>>>>>>> >>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>> one with the main things. >>>>>>>> I have little to no background in web development. >>>>>>>> >>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>> paraviewweb to it like its described in >>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>> >>>>>>>> I don't know what to do next but I believe that a great start would >>>>>>>> be to know where to put the source code in the example and how to run it. >>>>>>>> >>>>>>>> Thanks in advance, >>>>>>>> >>>>>>>> Leonardo Pessanha >>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbahameish at gmail.com Thu Aug 10 17:56:52 2017 From: mbahameish at gmail.com (Mariam) Date: Thu, 10 Aug 2017 22:56:52 +0100 Subject: [Paraview] [Issue] Connecting multiple pvpython scripts simultaneously Message-ID: <0BAFE274-EA46-4ED7-B575-23BC2E6D9434@gmail.com> Hi, I am using the collaboration module in pvpython to connect 30 clients to pvserver. However, when a certain number of clients are connected (13 or 14), the system crashes and it is not able to accept more clients. I receive the following error in the server side: vtkPVAlgorithmPortsInformation: Could not downcast vtkAlgorithm. The setup that I would like to achieve is: - PVServer - running in parallel (with MPI) - ParaView GUI - establishes a connection and load the model/ create a source - 30 pvpython clients connected to the server in the collaboration mode (sharing the same session of ParaView GUI) but each with different camera configuration. I tried to control the time of establishing the connection of each client, then I was able to increase the number of connected clients to 20 (max). Could anyone provide any tips or guidance? Or is this technically not doable? Today, I came across this article: https://blog.kitware.com/beat-the-heat-by-freezing-python-in-paraview/ Could that be a possible contribution to the issue of launching multiple pvpython scripts? Let me know if you require any further details. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuhao at shuhaowu.com Fri Aug 11 15:16:22 2017 From: shuhao at shuhaowu.com (Shuhao Wu) Date: Fri, 11 Aug 2017 15:16:22 -0400 Subject: [Paraview] Paraview pipeline error in python Message-ID: <5874b6c1-4693-25fa-c3ad-116a26f08805@shuhaowu.com> Hello, Is there a way to get errors that occurred while updating a pipeline in Python? I noticed that if I missed the option of GradientOfUnstructuredDataSet.ScalarArray, paraview will emit an error to STDOUT when I call UpdatePipeline. However, my python code continues to execute and then end up with the wrong data. Is there a way to get the error and quit when I call UpdatePipeline? Thanks, Shuhao From cory.quammen at kitware.com Fri Aug 11 16:52:02 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 11 Aug 2017 16:52:02 -0400 Subject: [Paraview] ParaView 5.4.1-RC4 available for download Message-ID: On behalf of the ParaView development team, I am pleased to announce that ParaView 5.4.1-RC4 is available for download. Binaries and source code are available from www.paraview.org/download The 5.4.1-RC4 bug fix release candidate sports a couple of improvements since 5.4.1-RC3: * Added lower limit to how small the GUI font size can be. * Addressed issue affecting layouts when loading a state file from the Python console. Please report any problems you find with this release candidate on the mailing list or on the bug tracker at https://gitlab.kitware.com/paraview/paraview/issues Note: RC4 is expected to be the last release candidate in the 5.4.1 release cycle. Thanks! -- Cory Quammen Staff R&D Engineer Kitware, Inc. From u.utku.turuncoglu at be.itu.edu.tr Sun Aug 13 14:44:41 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Sun, 13 Aug 2017 21:44:41 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf Message-ID: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> Hi, I am trying to install a code with support ParaView, Catalyst (version 5.3) to a new system. In this case, the code crash (seg. fault) at the beginning without giving any valuable hint about the problem. If I run the code under gdb I am getting following error messages, ---Type to continue, or q to quit--- Program received signal SIGSEGV, Segmentation fault. 0x00007fffce45aee7 in _GLOBAL__sub_I_wire_format_lite.cc () from /home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/libprotobuf.so It seems that the error triggered by paraview, protobuf component. I used both Intel and gcc compiler and both of them has same error. I also try to set VTK_USE_SYSTEM_PROTOBUF = ON but in this case I am getting bunch of error related with protobuf library. I also tried to compile my own protobuf library but ParaView complains about the version and I think that ParaView is compatible with version 2.5 but I installed 3.0. It is weird but I could able to run CFullExample without any problem. At this point I need your suggestion. Is there anybody faced similar problem? Do you think that upgrading 5.4 will help? Best Regards, --ufuk From Mariana.Danielova at eli-beams.eu Mon Aug 14 08:34:26 2017 From: Mariana.Danielova at eli-beams.eu (=?iso-8859-1?Q?Danielov=E1_Mariana?=) Date: Mon, 14 Aug 2017 12:34:26 +0000 Subject: [Paraview] vtk-js adding axes grid and labels Message-ID: <9018292187681C4F9B1F3FCE979149F735AEA32C@braun.eli-beams.eu> Hello all, I am using vtk-js for visualization of .vtk datasets. I would like to add axes grid and some labels to my project. Is it possible? I haven't found anything in the documentation here https://kitware.github.io/vtk-js/api/. Is this the correct place to ask questions about vtk-js? Thank you Best regards Mariana Danielova -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Aug 14 09:20:51 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 14 Aug 2017 09:20:51 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> Message-ID: <20170814132051.GB2910@megas.kitware.com> On Sun, Aug 13, 2017 at 21:44:41 +0300, u.utku.turuncoglu at be.itu.edu.tr wrote: > I am trying to install a code with support ParaView, Catalyst (version > 5.3) to a new system. In this case, the code crash (seg. fault) at the > beginning without giving any valuable hint about the problem. If I run the > code under gdb I am getting following error messages, > > ---Type to continue, or q to quit--- > Program received signal SIGSEGV, Segmentation fault. > 0x00007fffce45aee7 in _GLOBAL__sub_I_wire_format_lite.cc () > from > /home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/libprotobuf.so > > It seems that the error triggered by paraview, protobuf component. I used > both Intel and gcc compiler and both of them has same error. I also try to > set VTK_USE_SYSTEM_PROTOBUF = ON but in this case I am getting bunch of > error related with protobuf library. I also tried to compile my own Care to paste these? > protobuf library but ParaView complains about the version and I think that > ParaView is compatible with version 2.5 but I installed 3.0. It is weird > but I could able to run CFullExample without any problem. At this point I > need your suggestion. Is there anybody faced similar problem? Do you think > that upgrading 5.4 will help? Are you on Ubuntu? What version? Did you compile this ParaView yourself? --Ben From u.utku.turuncoglu at be.itu.edu.tr Mon Aug 14 09:49:55 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Mon, 14 Aug 2017 16:49:55 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <20170814132051.GB2910@megas.kitware.com> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> Message-ID: <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> Hi Ben, Thanks for your help. The server is Scientific Linux release 7.3 (Nitrogen) and yes i install PV from source using NVIDIA EGL libraries. In this case, I set USE_X OFF and also QT_GUI OFF. I tried both Intel (2017) and gcc and result is same. I also installed PV 5.4.1RC4 and still same. It is very annoying, the same setup is working in an other system which has Centos and Intel 2014. Regards, --ufuk > On Sun, Aug 13, 2017 at 21:44:41 +0300, u.utku.turuncoglu at be.itu.edu.tr > wrote: >> I am trying to install a code with support ParaView, Catalyst (version >> 5.3) to a new system. In this case, the code crash (seg. fault) at the >> beginning without giving any valuable hint about the problem. If I run >> the >> code under gdb I am getting following error messages, >> >> ---Type to continue, or q to quit--- >> Program received signal SIGSEGV, Segmentation fault. >> 0x00007fffce45aee7 in _GLOBAL__sub_I_wire_format_lite.cc () >> from >> /home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/libprotobuf.so >> >> It seems that the error triggered by paraview, protobuf component. I >> used >> both Intel and gcc compiler and both of them has same error. I also try >> to >> set VTK_USE_SYSTEM_PROTOBUF = ON but in this case I am getting bunch of >> error related with protobuf library. I also tried to compile my own > > Care to paste these? > >> protobuf library but ParaView complains about the version and I think >> that >> ParaView is compatible with version 2.5 but I installed 3.0. It is weird >> but I could able to run CFullExample without any problem. At this point >> I >> need your suggestion. Is there anybody faced similar problem? Do you >> think >> that upgrading 5.4 will help? > > Are you on Ubuntu? What version? Did you compile this ParaView yourself? > > --Ben > From louise.davies at stfc.ac.uk Mon Aug 14 09:46:31 2017 From: louise.davies at stfc.ac.uk (louise.davies at stfc.ac.uk) Date: Mon, 14 Aug 2017 13:46:31 +0000 Subject: [Paraview] ParaViewWeb/Visualizer file upload server Message-ID: Hello, I was reading the docs for ParaViewWeb and Visualizer and I see they both mention a file upload server. Specifically, this section (https://kitware.github.io/paraviewweb/docs/python_launcher.html#Optional-Upload-Server) gives basic details of how it works. My question is that I can't seem to see any evidence that this is working. My launcher config code specifies an "upload_dir" in the "configuration" section as detailed in the example launcher config file in the example but trying to send a post request to the URL specified ("/upload" rather than "/visualizer" which I use to access the Visualizer app) just results in an Apache "request URL not found" error. Am I interpreting the documentation incorrectly? Additionally, what is the functionality of the file upload server/what are its limitations? Could it allow for a user to upload a file and then modify that file in the Visualizer app? Or am I better off implementing my own file upload server? Thanks in advance, Louise -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Aug 14 10:30:29 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 14 Aug 2017 10:30:29 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> Message-ID: <20170814143029.GA21270@megas.kitware.com> On Mon, Aug 14, 2017 at 16:49:55 +0300, u.utku.turuncoglu at be.itu.edu.tr wrote: > Thanks for your help. The server is Scientific Linux release 7.3 > (Nitrogen) and yes i install PV from source using NVIDIA EGL libraries. In > this case, I set USE_X OFF and also QT_GUI OFF. I tried both Intel (2017) > and gcc and result is same. I also installed PV 5.4.1RC4 and still same. > It is very annoying, the same setup is working in an other system which > has Centos and Intel 2014. Hmm. Using an external Protobuf should work as long as it's new enough. I also remember making it work with 3.0, but maybe that broke again? What errors are you getting when trying to use an external protobuf? --Ben From sebastien.jourdain at kitware.com Mon Aug 14 10:31:29 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Mon, 14 Aug 2017 08:31:29 -0600 Subject: [Paraview] vtk-js adding axes grid and labels In-Reply-To: <9018292187681C4F9B1F3FCE979149F735AEA32C@braun.eli-beams.eu> References: <9018292187681C4F9B1F3FCE979149F735AEA32C@braun.eli-beams.eu> Message-ID: Hi Mariana, Questions about vtk.js can be done on the issue tracker of vtk.js as well. Regarding the axis grid, vtk.js does not provide such filter/representation yet. Unfortunately we don't have a time frame of when that will be available. On the other hand, if you feel like it, you can contribute it to the repository or we offer support contract which could then be used to tackle the pieces that you would like to see in vtk.js sooner. Thanks, Seb On Mon, Aug 14, 2017 at 6:34 AM, Danielov? Mariana < Mariana.Danielova at eli-beams.eu> wrote: > Hello all, > > > > I am using vtk-js for visualization of .vtk datasets. I would like to add > axes grid and some labels to my project. Is it possible? I haven?t found > anything in the documentation here https://kitware.github.io/vtk-js/api/. > > Is this the correct place to ask questions about vtk-js? > > > > Thank you > > > > Best regards > > > > Mariana Danielova > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Mon Aug 14 10:47:42 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Mon, 14 Aug 2017 08:47:42 -0600 Subject: [Paraview] ParaViewWeb/Visualizer file upload server In-Reply-To: References: Message-ID: Hi Louise, The upload part can be managed by the launcher or the actual ParaViewWeb server (the later require additional args at startup). That part was meant to be a proof of concept so we could create a form and let the user upload the dataset that he wanted to visualize with Visualizer either before or while Visualizer was running. If you are using Apache, that means you will also have to forward /upload to the launcher like you did with /paraview. On the other hand creating your own endpoint for uploading file, should not be too difficult either. Here is the relevant part of the code that will register /upload if the configuration provide such thing: https://github.com/Kitware/VTK/blob/v7.1.1/Web/Python/vtk/web/launcher.py#L622-L627 Seb On Mon, Aug 14, 2017 at 7:46 AM, wrote: > Hello, > > > > I was reading the docs for ParaViewWeb and Visualizer and I see they both > mention a file upload server. Specifically, this section ( > https://kitware.github.io/paraviewweb/docs/python_ > launcher.html#Optional-Upload-Server) gives basic details of how it works. > > > > My question is that I can?t seem to see any evidence that this is working. > My launcher config code specifies an ?upload_dir? in the ?configuration? > section as detailed in the example launcher config file in the example but > trying to send a post request to the URL specified (?/upload? rather than > ?/visualizer? which I use to access the Visualizer app) just results in an > Apache ?request URL not found? error. > > > > Am I interpreting the documentation incorrectly? Additionally, what is the > functionality of the file upload server/what are its limitations? Could it > allow for a user to upload a file and then modify that file in the > Visualizer app? Or am I better off implementing my own file upload server? > > > > Thanks in advance, > > Louise > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick.oleary at kitware.com Mon Aug 14 13:38:47 2017 From: patrick.oleary at kitware.com (Patrick O'Leary) Date: Mon, 14 Aug 2017 11:38:47 -0600 Subject: [Paraview] ISAV 2017 paper deadline extension: 29 Aug 2017, 3rd Annual Workshop on In Situ Infrastructures for Enabling Extreme-Scale Analysis and Visualization (ISAV 2017) Message-ID: (Apologies if you receive multiple copies of this notice, it is being cross posted to several different lists) Update: paper submission due date extended to 29 Aug 2017 23:59 AoE ISAV 2017: In Situ Infrastructures for Enabling Extreme-Scale Analysis and Visualization In cooperation with SIGHPC and held in conjunction with SC17: The International Conference on High Performance Computing, Networking, Storage and Analysis, Denver, Colorado, U.S.A. ISAV 2017 - http://vis.lbl.gov/Events/ISAV-2017/ Full-day 9:00 AM - 5:30 PM Sunday November 12th, 2017 Workshop Theme The considerable interest in the HPC community regarding in situ analysis and visualization is due to several factors. First is an I/O cost savings, where data is analyzed/visualized while being generated, without first storing to a file system. Second is the potential for increased accuracy, where fine temporal sampling of transient analysis might expose some complex behavior missed in coarse temporal sampling. Third is the ability to use all available resources, CPUs and accelerators, in the computation of analysis products. The workshop brings together researchers, developers and practitioners from industry, academia, and government laboratories developing, applying, and deploying in situ methods in extreme-scale, high performance computing. The goal is to present research findings, lessons learned, and insights related to developing and applying in situ methods and infrastructure across a range of science and engineering applications in HPC environments; to discuss topics like opportunities presented by new architectures, existing infrastructure needs, requirements, and gaps, and experiences to foster and enable in situ analysis and visualization; to serve as a ?center of gravity? for researchers, practitioners, and users/consumers of in situ methods and infrastructure in the HPC space. Participation/Call for Papers and Oral Presentations We invite two types of submissions to ISAV 2017: (1) short, 4-page papers that present research results, that identify opportunities or challenges, and that present case studies/best practices for in situ methods/infrastructure in the areas of data management, analysis and visualization; (2) lightning presentation submission, consisting of a 1- or 2-page submission, for a brief oral presentation at the workshop. Short papers will appear in the workshop proceedings and will be invited to give an oral presentation of 15 to 20 minutes; lightning round submissions that are invited to present at the workshop will have author names and titles included as part of the proceedings. Submissions of both types are welcome that fall within one or more areas of interest, as follows: Areas of interest for ISAV, include, but are not limited to: In situ infrastructures * Current Systems: production quality, research prototypes * Opportunities * Gaps System resources, hardware, and emerging architectures * Enabling Hardware * Hardware and architectures that provide opportunities for in situ processing, such as burst buffers, staging computations on I/O nodes, sharing cores within a node for both simulation and in situ processing Methods/algorithms/applications/Case studies * Best practices * Analysis: feature detection, statistical methods, temporal methods, geometric methods * Visualization: information visualization, scientific visualization, time-varying methods * Data reduction/compression * Examples/case studies of solving a specific science challenge with in situ methods/infrastructure. Simulation * Integration:data modeling, software-engineering * Resilience: error detection, fault recovery * Workflows for supporting complex in situ processing pipelines Requirements * Preserve important elements * Significantly reduce the data size * Flexibility for post-processing exploration Review Process All submissions will undergo a peer-review process consisting of three reviews by experts in the field, and evaluated according to relevance to the workshop theme, technical soundness, creativity, originality, and impactfulness of method/results. Lightning round submissions will be evaluated primarily for relevance to the workshop. Submission Process Authors are invited to submit papers of at most 4 pages in PDF format, excluding references, and lightning presentations of at most 2 pages in PDF format, excluding references. Papers must be submitted in PDF format (readable by Adobe Acrobat Reader 5.0 and higher) and formatted for 8.5" x 11" (U.S. Letter). Submissions are required in the ACM format ( http://www.acm.org/sigs/publications/proceedings-templates) using the sample-sigconf template and submitted via EasyChair ( https://easychair.org/conferences/?conf=isav17). No changes to the margins, spacing, or font sizes as specified by the style file are allowed. Papers must be self-contained and provide the technical substance required for the program committee to evaluate their contributions. Submitted papers must be original work that has not appeared in and is not under consideration for another conference or a journal. See the ACM Prior Publication Policy for more details (http://www.acm.org/publicatio ns/policies/). Papers can be submitted at https://easychair.org/conferen ces/?conf=isav17. Publication in proceedings, presentation at the workshop All paper submissions that receive favorable reviews will be included as part of the workshop proceedings, which will be published through SIGHPC along with other SC17 workshop proceedings in the ACM Digital Library and IEEE Xplore. Lightning round submissions will not be included as part of the proceedings. Subject to the constraints of workshop length, some subset of the accepted publications will be invited to give a brief oral presentation at the workshop. The exact number of such presentations and their length will be determined after the review process has been completed. Timeline/Important Dates 29 August 2017 Paper submission deadline 22 September 2017 Author notification 06 October 2017 Camera ready copy due 15 October 2017 Final program posted to ISAV web page 12 November 2017 ISAV 2017 workshop at SC17 -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Mon Aug 14 13:45:41 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Mon, 14 Aug 2017 20:45:41 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <20170814143029.GA21270@megas.kitware.com> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> Message-ID: <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> Hi Ben, Again thanks for your help. I tried to use protobuf 3.3.0 with PV 5.4.0rc4 but i am getting following error CMake Warning at /usr/local/software/spack/develop-290617/spack/opt/spack/linux-rhel7-x86_64/gcc-5.4.0/cmake-3.8.1-hvzxbkmal ie677klawvpwyipv7giycyh/share/cmake-3.8/Modules/FindProtobuf.cmake:387 (message): Protobuf compiler version doesn't match library version 3.3.0 Call Stack (most recent call first): VTK/CMake/vtkModuleMacros.cmake:888 (find_package) ThirdParty/protobuf/CMakeLists.txt:40 (vtk_module_third_party) I have also version 2.5 in the system but I am getting lots of error (see attached log.txt) related with undefined references. --ufuk > On Mon, Aug 14, 2017 at 16:49:55 +0300, u.utku.turuncoglu at be.itu.edu.tr > wrote: >> Thanks for your help. The server is Scientific Linux release 7.3 >> (Nitrogen) and yes i install PV from source using NVIDIA EGL libraries. >> In >> this case, I set USE_X OFF and also QT_GUI OFF. I tried both Intel >> (2017) >> and gcc and result is same. I also installed PV 5.4.1RC4 and still same. >> It is very annoying, the same setup is working in an other system which >> has Centos and Intel 2014. > > Hmm. Using an external Protobuf should work as long as it's new enough. > I also remember making it work with 3.0, but maybe that broke again? > What errors are you getting when trying to use an external protobuf? > > --Ben > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: log.txt URL: From u.utku.turuncoglu at be.itu.edu.tr Mon Aug 14 14:37:55 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Mon, 14 Aug 2017 21:37:55 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> Message-ID: <60178.78.182.67.99.1502735875.squirrel@webmail.be.itu.edu.tr> It is my fault, I forgot to change coupe of variable in PV config, it seems that PV is compiling with 3.3.0. I'll try to run the code when it is installed. It seems that 2.5 is not usable with PV and old. Anyway, I'll let you know about the result. --ufuk > Hi Ben, > > Again thanks for your help. I tried to use protobuf 3.3.0 with PV 5.4.0rc4 > but i am getting following error > > CMake Warning at > /usr/local/software/spack/develop-290617/spack/opt/spack/linux-rhel7-x86_64/gcc-5.4.0/cmake-3.8.1-hvzxbkmal > ie677klawvpwyipv7giycyh/share/cmake-3.8/Modules/FindProtobuf.cmake:387 > (message): > Protobuf compiler version doesn't match library version 3.3.0 > Call Stack (most recent call first): > VTK/CMake/vtkModuleMacros.cmake:888 (find_package) > ThirdParty/protobuf/CMakeLists.txt:40 (vtk_module_third_party) > > I have also version 2.5 in the system but I am getting lots of error (see > attached log.txt) related with undefined references. > > --ufuk > >> On Mon, Aug 14, 2017 at 16:49:55 +0300, u.utku.turuncoglu at be.itu.edu.tr >> wrote: >>> Thanks for your help. The server is Scientific Linux release 7.3 >>> (Nitrogen) and yes i install PV from source using NVIDIA EGL libraries. >>> In >>> this case, I set USE_X OFF and also QT_GUI OFF. I tried both Intel >>> (2017) >>> and gcc and result is same. I also installed PV 5.4.1RC4 and still >>> same. >>> It is very annoying, the same setup is working in an other system which >>> has Centos and Intel 2014. >> >> Hmm. Using an external Protobuf should work as long as it's new enough. >> I also remember making it work with 3.0, but maybe that broke again? >> What errors are you getting when trying to use an external protobuf? >> >> --Ben >> From ben.boeckel at kitware.com Mon Aug 14 14:50:09 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 14 Aug 2017 14:50:09 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> Message-ID: <20170814185009.GA21197@rotor.kitware.com> On Mon, Aug 14, 2017 at 20:45:41 +0300, u.utku.turuncoglu at be.itu.edu.tr wrote: > Again thanks for your help. I tried to use protobuf 3.3.0 with PV 5.4.0rc4 > but i am getting following error > > CMake Warning at > /usr/local/software/spack/develop-290617/spack/opt/spack/linux-rhel7-x86_64/gcc-5.4.0/cmake-3.8.1-hvzxbkmal > ie677klawvpwyipv7giycyh/share/cmake-3.8/Modules/FindProtobuf.cmake:387 > (message): > Protobuf compiler version doesn't match library version 3.3.0 > Call Stack (most recent call first): > VTK/CMake/vtkModuleMacros.cmake:888 (find_package) > ThirdParty/protobuf/CMakeLists.txt:40 (vtk_module_third_party) > > I have also version 2.5 in the system but I am getting lots of error (see > attached log.txt) related with undefined references. It looks like it's finding the compiler for 2.5 with the 3.3 library. Set them both so that they match first. --Ben From ganplankr at hotmail.com Mon Aug 14 16:58:58 2017 From: ganplankr at hotmail.com (=?gb2312?B?tq0gyua1zw==?=) Date: Mon, 14 Aug 2017 20:58:58 +0000 Subject: [Paraview] Help: How to get multi screenshots in one picture from Paraview Message-ID: Dear all, I am currently using paraview to analyse my .vtk data. I want to get some screenshots for my presentation. I have tried version 4.1 and 5.2 and I could save one screenshot per time. Does anyone know how can I get multi screenshots in one picture with paraview itself? I do not want to use python as I have no experience with it. I would appreciate your reply and help. Many thanks Shudi Dong -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Mon Aug 14 17:12:50 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Mon, 14 Aug 2017 18:12:50 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: Hi! Thank you for the help! Because of it I was able to build and start the example correctly. Now I am trying different examples such as MultiLayoutViewer https://kitware.github.io/paraviewweb/examples/MultiLayoutViewer.html . I am still a little doubtful about my imports but I believe import MultiLayoutViewer from '..'; > should be import MultiLayoutViewer from > 'paraviewweb/src/React/Viewers/MultiLayoutViewer' Right? I couldn't find the package *tonic-arctic-sample-data *that holds the content needed in MultiLayoutViewer, MultiLayoutRenderer and Probe3DViewer examples in trough npm. Do you know how to do proceed? Thanks in advance. Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-08-10 11:35 GMT-03:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > With ParaViewWeb, we force the user to pick the version of the > dependencies they wants to install instead of forcing them. > > Regarding your import path they are still wrong. > > from paraviewweb/src/Component/Native/Composite/example/index.js > > when you import '..' that resolve to paraviewweb/src/Component/ > Native/Composite > > which means your imports should be: > > import CompositeComponent from 'paraviewweb/src/Component/ > Native/Composite'; > import BGColorComponent from 'paraviewweb/src/Component/Nat > ive/BackgroundColor'; > > On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha > wrote: > >> So, I was able to build using 'paraviewweb/src/' and installing forcibly >> mout, axios and hammerjs packages. >> >> Now there's other js errors that I am going after like /plotly.js\ and >> global reference ones ! >> >> It's definitely not a simple task to build an example of paraviewweb as a >> standalone app. >> >> Definitely will come back with updates. >> >> Best regards, >> >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> 2017-08-09 19:58 GMT-03:00 L?o Pessanha : >> >>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or >>> 'paraviewweb/src/Component'? >>> >>> I have the exactly same result using full path or starting with >>> 'paraviewweb' >>> >>> Using: >>> >>> import CompositeComponent from 'paraviewweb/src/'; >>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>> ive/BackgroundColor'; >>>> >>> >>> Outputs a lot of: >>> >>> Module not found: Error: Can't resolve >>>> >>> >>> So I did a 'npm list x' with x being the modules it couldn't >>> resolve(axios, hammerjs and etc) and none of then was installed. >>> >>> root at PC:~/MyWebProject# npm list hammerjs >>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>> ??? (empty) >>>> >>>> root at PC:~/MyWebProject# npm list axios >>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>> ??? (empty) >>>> >>> >>> >>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >>> --save-dev* failed installing the dependencies correctly? >>> >>> Best regards, >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> The import should start with 'paraviewweb' then you provide the full >>>> path from there like: >>>> >>>> import BGColorComponent from 'paraviewweb/src/Component/Native/ >>>> BackgroundColor'; >>>> >>>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>>> leonardopessanha74 at gmail.com> wrote: >>>> >>>>> Hi! I did the changes. The only thing I am not sure it's the right >>>>> paths in the imports of ${ROOT}/src/index.js >>>>> >>>>> import CompositeComponent from '..'; >>>>>> import BGColorComponent from '../../BackgroundColor'; >>>>>> >>>>>> >>>>> Should I change this paths? >>>>> >>>>> I did try >>>>> >>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>> modules/paraviewweb/src'; >>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>> >>>>> and >>>>> >>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>> modules/paraviewweb/src/Component'; >>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>> >>>>> and >>>>> >>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>> modules/paraviewweb/src/Component/Native'; >>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>> >>>>> With the last 2 sucessfully building but with JS errors in Firefox >>>>> >>>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>>> >>>>> >>>>> and >>>>> >>>>> TypeError: _Native2.default is not a constructor >>>>>> >>>>> >>>>> and the first one not building and giving me a lot of >>>>> >>>>> Module not found: Error: Can't resolve >>>>>> >>>>> >>>>> >>>>> Thanks in advance! >>>>> >>>>> >>>>> Leonardo Pessanha >>>>> Laboratory of Computational Methods in Engineering >>>>> Federal University of Rio de Janeiro - COPPE >>>>> Rio de Janeiro, RJ, Brasil >>>>> >>>>> >>>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> If I get to it, I'll do what I've done with vtk.js to support both. >>>>>> >>>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>>> /config/dependency.js >>>>>> >>>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>> >>>>>>> Thank you, Sebastien. I will give a try! >>>>>>> >>>>>>> Do you believe it's best to rollback webpack to 1.x or to change the >>>>>>> webpack.config.js in order to fit webpack 2.x API? >>>>>>> >>>>>>> Leonardo Pessanha >>>>>>> Laboratory of Computational Methods in Engineering >>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>> >>>>>>> >>>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com>: >>>>>>> >>>>>>>> Based on the path given in the setup guide, you should copy the >>>>>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>>>>> file should be named index.js. >>>>>>>> >>>>>>>> Then you should be able to build your example using the npm >>>>>>>> command: "npm run build". >>>>>>>> >>>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>>> ndency.html), but the concept is exactly the same. >>>>>>>> As it is picking the example available here >>>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/WebGL/Cone >>>>>>>> and making a standalone application from it. >>>>>>>> >>>>>>>> Just be aware that vtk.js is using webpack2 which is not the case >>>>>>>> for ParaViewWeb. >>>>>>>> >>>>>>>> Hope that helps, >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi! >>>>>>>>> >>>>>>>>> I would like to know the steps in order to run simple example like >>>>>>>>> the following one: >>>>>>>>> >>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>> ex.html >>>>>>>>> >>>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>>> one with the main things. >>>>>>>>> I have little to no background in web development. >>>>>>>>> >>>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>>> paraviewweb to it like its described in >>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>> >>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>> it. >>>>>>>>> >>>>>>>>> Thanks in advance, >>>>>>>>> >>>>>>>>> Leonardo Pessanha >>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi! >>>>>>>>> >>>>>>>>> I would like to know the steps in order to run simple example like >>>>>>>>> the following one: >>>>>>>>> >>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>> ex.html >>>>>>>>> >>>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>>> one with the main things. >>>>>>>>> I have little to no background in web development. >>>>>>>>> >>>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>>> paraviewweb to it like its described in >>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>> >>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>> it. >>>>>>>>> >>>>>>>>> Thanks in advance, >>>>>>>>> >>>>>>>>> Leonardo Pessanha >>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>>>> ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Mon Aug 14 17:38:23 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Mon, 14 Aug 2017 15:38:23 -0600 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: I think your import is correct. Regarding the sample data, this is the way you can download it via npm (when doing "npm install") => https://github.com/Kitware/paraviewweb/blob/master/package.json#L48 On Mon, Aug 14, 2017 at 3:12 PM, L?o Pessanha wrote: > Hi! Thank you for the help! Because of it I was able to build and start > the example correctly. Now I am trying different examples such as > MultiLayoutViewer https://kitware.github.io/paraviewweb/examples/ > MultiLayoutViewer.html . > I am still a little doubtful about my imports but I believe > > import MultiLayoutViewer from '..'; >> > should be > > import MultiLayoutViewer from 'paraviewweb/src/React/ >> Viewers/MultiLayoutViewer' > > > Right? > > I couldn't find the package *tonic-arctic-sample-data *that holds the > content needed in MultiLayoutViewer, MultiLayoutRenderer and Probe3DViewer > examples in trough npm. > > Do you know how to do proceed? > > Thanks in advance. > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > 2017-08-10 11:35 GMT-03:00 Sebastien Jourdain com>: > >> With ParaViewWeb, we force the user to pick the version of the >> dependencies they wants to install instead of forcing them. >> >> Regarding your import path they are still wrong. >> >> from paraviewweb/src/Component/Native/Composite/example/index.js >> >> when you import '..' that resolve to paraviewweb/src/Component/Nati >> ve/Composite >> >> which means your imports should be: >> >> import CompositeComponent from 'paraviewweb/src/Component/Nat >> ive/Composite'; >> import BGColorComponent from 'paraviewweb/src/Component/Nat >> ive/BackgroundColor'; >> >> On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> So, I was able to build using 'paraviewweb/src/' and installing forcibly >>> mout, axios and hammerjs packages. >>> >>> Now there's other js errors that I am going after like /plotly.js\ and >>> global reference ones ! >>> >>> It's definitely not a simple task to build an example of paraviewweb as >>> a standalone app. >>> >>> Definitely will come back with updates. >>> >>> Best regards, >>> >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> 2017-08-09 19:58 GMT-03:00 L?o Pessanha : >>> >>>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or >>>> 'paraviewweb/src/Component'? >>>> >>>> I have the exactly same result using full path or starting with >>>> 'paraviewweb' >>>> >>>> Using: >>>> >>>> import CompositeComponent from 'paraviewweb/src/'; >>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>> ive/BackgroundColor'; >>>>> >>>> >>>> Outputs a lot of: >>>> >>>> Module not found: Error: Can't resolve >>>>> >>>> >>>> So I did a 'npm list x' with x being the modules it couldn't >>>> resolve(axios, hammerjs and etc) and none of then was installed. >>>> >>>> root at PC:~/MyWebProject# npm list hammerjs >>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>> ??? (empty) >>>>> >>>>> root at PC:~/MyWebProject# npm list axios >>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>> ??? (empty) >>>>> >>>> >>>> >>>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >>>> --save-dev* failed installing the dependencies correctly? >>>> >>>> Best regards, >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> The import should start with 'paraviewweb' then you provide the full >>>>> path from there like: >>>>> >>>>> import BGColorComponent from 'paraviewweb/src/Component/Native/ >>>>> BackgroundColor'; >>>>> >>>>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>>>> leonardopessanha74 at gmail.com> wrote: >>>>> >>>>>> Hi! I did the changes. The only thing I am not sure it's the right >>>>>> paths in the imports of ${ROOT}/src/index.js >>>>>> >>>>>> import CompositeComponent from '..'; >>>>>>> import BGColorComponent from '../../BackgroundColor'; >>>>>>> >>>>>>> >>>>>> Should I change this paths? >>>>>> >>>>>> I did try >>>>>> >>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>> modules/paraviewweb/src'; >>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>> >>>>>> and >>>>>> >>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>> modules/paraviewweb/src/Component'; >>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>> >>>>>> and >>>>>> >>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>> modules/paraviewweb/src/Component/Native'; >>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>> >>>>>> With the last 2 sucessfully building but with JS errors in Firefox >>>>>> >>>>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>>>> >>>>>> >>>>>> and >>>>>> >>>>>> TypeError: _Native2.default is not a constructor >>>>>>> >>>>>> >>>>>> and the first one not building and giving me a lot of >>>>>> >>>>>> Module not found: Error: Can't resolve >>>>>>> >>>>>> >>>>>> >>>>>> Thanks in advance! >>>>>> >>>>>> >>>>>> Leonardo Pessanha >>>>>> Laboratory of Computational Methods in Engineering >>>>>> Federal University of Rio de Janeiro - COPPE >>>>>> Rio de Janeiro, RJ, Brasil >>>>>> >>>>>> >>>>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> If I get to it, I'll do what I've done with vtk.js to support both. >>>>>>> >>>>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>>>> /config/dependency.js >>>>>>> >>>>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>> >>>>>>>> Thank you, Sebastien. I will give a try! >>>>>>>> >>>>>>>> Do you believe it's best to rollback webpack to 1.x or to change >>>>>>>> the webpack.config.js in order to fit webpack 2.x API? >>>>>>>> >>>>>>>> Leonardo Pessanha >>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>> >>>>>>>> >>>>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>> >>>>>>>>> Based on the path given in the setup guide, you should copy the >>>>>>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>>>>>> file should be named index.js. >>>>>>>>> >>>>>>>>> Then you should be able to build your example using the npm >>>>>>>>> command: "npm run build". >>>>>>>>> >>>>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>>>> ndency.html), but the concept is exactly the same. >>>>>>>>> As it is picking the example available here >>>>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/WebGL/Cone >>>>>>>>> and making a standalone application from it. >>>>>>>>> >>>>>>>>> Just be aware that vtk.js is using webpack2 which is not the case >>>>>>>>> for ParaViewWeb. >>>>>>>>> >>>>>>>>> Hope that helps, >>>>>>>>> >>>>>>>>> Seb >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi! >>>>>>>>>> >>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>> like the following one: >>>>>>>>>> >>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>> ex.html >>>>>>>>>> >>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>>>> one with the main things. >>>>>>>>>> I have little to no background in web development. >>>>>>>>>> >>>>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>>>> paraviewweb to it like its described in >>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>> >>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>> it. >>>>>>>>>> >>>>>>>>>> Thanks in advance, >>>>>>>>>> >>>>>>>>>> Leonardo Pessanha >>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi! >>>>>>>>>> >>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>> like the following one: >>>>>>>>>> >>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>> ex.html >>>>>>>>>> >>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>>>> one with the main things. >>>>>>>>>> I have little to no background in web development. >>>>>>>>>> >>>>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>>>> paraviewweb to it like its described in >>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>> >>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>> it. >>>>>>>>>> >>>>>>>>>> Thanks in advance, >>>>>>>>>> >>>>>>>>>> Leonardo Pessanha >>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Powered by www.kitware.com >>>>>>>>>> >>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>> >>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>> >>>>>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>>>>> ParaView >>>>>>>>>> >>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Aug 14 22:46:54 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 14 Aug 2017 22:46:54 -0400 Subject: [Paraview] Help: How to get multi screenshots in one picture from Paraview In-Reply-To: References: Message-ID: Shudi, Can you elaborate a little? I am not sure I understand what you want to take multiple screenshots of. Utkarsh On Mon, Aug 14, 2017 at 4:58 PM, ? ?? wrote: > Dear all, > > > I am currently using paraview to analyse my .vtk data. I want to get some > screenshots for my presentation. I have tried version 4.1 and 5.2 and I > could save one screenshot per time. Does anyone know how can I get multi > screenshots in one picture with paraview itself? I do not want to use > python as I have no experience with it. I would appreciate your reply and > help. > > > Many thanks > > Shudi Dong > > > _______________________________________________ > 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 u.utku.turuncoglu at be.itu.edu.tr Tue Aug 15 10:59:47 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Tue, 15 Aug 2017 17:59:47 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <20170814185009.GA21197@rotor.kitware.com> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> Message-ID: <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> Hi, I solved the problem and i am able to run the simulation code with Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer version of protobuf library (3.3.0) and compiling the model code with this version of PV (using gcc). Now, the problem is that the code gives following warnings and do nothing with standard allinputsgridwriter.py script. Do you think that it is related with protobuf library. The same setup is working without any problem in an other system using Intel compiler. Traceback (most recent call last): File "", line 2, in Traceback (most recent call last): Traceback (most recent call last): File "", line 2, in File "", line 2, in Traceback (most recent call last): File "", line 2, in Traceback (most recent call last): File "", line 2, in Traceback (most recent call last): File "", line 2, in Traceback (most recent call last): File "", line 2, in Traceback (most recent call last): File "", line 2, in File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "allinputsgridwriter.py", line 97, in DoCoProcessing File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers self.CreatePipeline(datadescription) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers File "allinputsgridwriter.py", line 50, in CreatePipeline self.CreatePipeline(datadescription) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers File "allinputsgridwriter.py", line 50, in CreatePipeline File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers self.CreatePipeline(datadescription) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers self.CreatePipeline(datadescription) File "allinputsgridwriter.py", line 23, in _CreatePipeline File "allinputsgridwriter.py", line 50, in CreatePipeline File "allinputsgridwriter.py", line 50, in CreatePipeline self.CreatePipeline(datadescription) self.CreatePipeline(datadescription) File "allinputsgridwriter.py", line 50, in CreatePipeline File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers File "allinputsgridwriter.py", line 50, in CreatePipeline File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers self.CreatePipeline(datadescription) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers self.CreatePipeline(datadescription) File "allinputsgridwriter.py", line 50, in CreatePipeline self.CreatePipeline(datadescription) File "allinputsgridwriter.py", line 50, in CreatePipeline File "allinputsgridwriter.py", line 50, in CreatePipeline File "allinputsgridwriter.py", line 23, in _CreatePipeline File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 160, in UpdateProducers File "allinputsgridwriter.py", line 23, in _CreatePipeline for name in namedinputs: File "allinputsgridwriter.py", line 26, in Pipeline self.CreatePipeline(datadescription) File "allinputsgridwriter.py", line 23, in _CreatePipeline File "allinputsgridwriter.py", line 50, in CreatePipeline File "allinputsgridwriter.py", line 23, in _CreatePipeline File "allinputsgridwriter.py", line 23, in _CreatePipeline File "allinputsgridwriter.py", line 23, in _CreatePipeline File "allinputsgridwriter.py", line 23, in _CreatePipeline File "allinputsgridwriter.py", line 23, in _CreatePipeline File "allinputsgridwriter.py", line 23, in _CreatePipeline for name in namedinputs: for name in namedinputs: grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) File "allinputsgridwriter.py", line 26, in Pipeline File "allinputsgridwriter.py", line 26, in Pipeline File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer for name in namedinputs: for name in namedinputs: File "allinputsgridwriter.py", line 26, in Pipeline File "allinputsgridwriter.py", line 26, in Pipeline if grid.IsA("vtkImageData") == True or \ for name in namedinputs: AttributeError: 'NoneType' object has no attribute 'IsA' File "allinputsgridwriter.py", line 26, in Pipeline for name in namedinputs: for name in namedinputs: for name in namedinputs: File "allinputsgridwriter.py", line 26, in Pipeline File "allinputsgridwriter.py", line 26, in Pipeline File "allinputsgridwriter.py", line 26, in Pipeline grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) for name in namedinputs: File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer File "allinputsgridwriter.py", line 26, in Pipeline grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) if grid.IsA("vtkImageData") == True or \ grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer AttributeError: 'NoneType' object has no attribute 'IsA' File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) if grid.IsA("vtkImageData") == True or \ File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer AttributeError: 'NoneType' object has no attribute 'IsA' File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer if grid.IsA("vtkImageData") == True or \ if grid.IsA("vtkImageData") == True or \ AttributeError: 'NoneType' object has no attribute 'IsA' grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) if grid.IsA("vtkImageData") == True or \ if grid.IsA("vtkImageData") == True or \ AttributeError: 'NoneType' object has no attribute 'IsA' AttributeError: 'NoneType' object has no attribute 'IsA' if grid.IsA("vtkImageData") == True or \ AttributeError: 'NoneType' object has no attribute 'IsA' File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer if grid.IsA("vtkImageData") == True or \ AttributeError: 'NoneType' object has no attribute 'IsA' [PERFLOG] :: COPROC 2 0.01404021SEC. Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 Time Step: 2 [ 720.00] ATM-TO-COP: redist mask [CROSS] to mask [CROSS] ATM-TO-COP: redist topo [CROSS] to topo [CROSS] AttributeError: 'NoneType' object has no attribute 'IsA' grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer if grid.IsA("vtkImageData") == True or \ > On Mon, Aug 14, 2017 at 20:45:41 +0300, u.utku.turuncoglu at be.itu.edu.tr > wrote: >> Again thanks for your help. I tried to use protobuf 3.3.0 with PV >> 5.4.0rc4 >> but i am getting following error >> >> CMake Warning at >> /usr/local/software/spack/develop-290617/spack/opt/spack/linux-rhel7-x86_64/gcc-5.4.0/cmake-3.8.1-hvzxbkmal >> ie677klawvpwyipv7giycyh/share/cmake-3.8/Modules/FindProtobuf.cmake:387 >> (message): >> Protobuf compiler version doesn't match library version 3.3.0 >> Call Stack (most recent call first): >> VTK/CMake/vtkModuleMacros.cmake:888 (find_package) >> ThirdParty/protobuf/CMakeLists.txt:40 (vtk_module_third_party) >> >> I have also version 2.5 in the system but I am getting lots of error >> (see >> attached log.txt) related with undefined references. > > It looks like it's finding the compiler for 2.5 with the 3.3 library. > Set them both so that they match first. > > --Ben > From ben.boeckel at kitware.com Tue Aug 15 12:40:04 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 15 Aug 2017 12:40:04 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> Message-ID: <20170815164004.GA17070@rotor.kitware.com> On Tue, Aug 15, 2017 at 17:59:47 +0300, u.utku.turuncoglu at be.itu.edu.tr wrote: > I solved the problem and i am able to run the simulation code with > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer version > of protobuf library (3.3.0) and compiling the model code with this version > of PV (using gcc). > > Now, the problem is that the code gives following warnings and do nothing > with standard allinputsgridwriter.py script. Do you think that it is > related with protobuf library. The same setup is working without any > problem in an other system using Intel compiler. It'd be better to try with one MPI process rather than?I count 10 to get the error? Not sure what's up though, Andy? > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > if grid.IsA("vtkImageData") == True or \ > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > AttributeError: 'NoneType' object has no attribute 'IsA' > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > if grid.IsA("vtkImageData") == True or \ > if grid.IsA("vtkImageData") == True or \ > AttributeError: 'NoneType' object has no attribute 'IsA' > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > if grid.IsA("vtkImageData") == True or \ > if grid.IsA("vtkImageData") == True or \ > AttributeError: 'NoneType' object has no attribute 'IsA' > AttributeError: 'NoneType' object has no attribute 'IsA' > if grid.IsA("vtkImageData") == True or \ > AttributeError: 'NoneType' object has no attribute 'IsA' > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > if grid.IsA("vtkImageData") == True or \ > AttributeError: 'NoneType' object has no attribute 'IsA' > [PERFLOG] :: COPROC 2 0.01404021SEC. > Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 Time > Step: 2 [ 720.00] > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] > AttributeError: 'NoneType' object has no attribute 'IsA' > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > if grid.IsA("vtkImageData") == True or \ --Ben From andy.bauer at kitware.com Tue Aug 15 14:13:05 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 15 Aug 2017 14:13:05 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <20170815164004.GA17070@rotor.kitware.com> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> Message-ID: Hi Ufuk, For the allinputsgridwriter.py you currently need to manually add in the inputs yourself (i.e. replace the "namedinputs = ['input']" line with the name of your inputs. That has caught me in the past as well so I decided to fix that. Attached is my new version of that script where it doesn't require you to specify the input names in case you want to try this new one instead. If you do, please let us know if that solves your problem or not. Best, Andy On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel wrote: > On Tue, Aug 15, 2017 at 17:59:47 +0300, u.utku.turuncoglu at be.itu.edu.tr > wrote: > > I solved the problem and i am able to run the simulation code with > > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer > version > > of protobuf library (3.3.0) and compiling the model code with this > version > > of PV (using gcc). > > > > Now, the problem is that the code gives following warnings and do nothing > > with standard allinputsgridwriter.py script. Do you think that it is > > related with protobuf library. The same setup is working without any > > problem in an other system using Intel compiler. > > It'd be better to try with one MPI process rather than?I count 10 to get > the error? Not sure what's up though, Andy? > > > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > /lib/site-packages/paraview/coprocessing.py", > > line 305, in CreateProducer > > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > > if grid.IsA("vtkImageData") == True or \ > > File > > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > /lib/site-packages/paraview/coprocessing.py", > > line 305, in CreateProducer > > AttributeError: 'NoneType' object has no attribute 'IsA' > > File > > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > /lib/site-packages/paraview/coprocessing.py", > > line 305, in CreateProducer > > if grid.IsA("vtkImageData") == True or \ > > if grid.IsA("vtkImageData") == True or \ > > AttributeError: 'NoneType' object has no attribute 'IsA' > > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > > File > > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > /lib/site-packages/paraview/coprocessing.py", > > line 305, in CreateProducer > > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > > if grid.IsA("vtkImageData") == True or \ > > if grid.IsA("vtkImageData") == True or \ > > AttributeError: 'NoneType' object has no attribute 'IsA' > > AttributeError: 'NoneType' object has no attribute 'IsA' > > if grid.IsA("vtkImageData") == True or \ > > AttributeError: 'NoneType' object has no attribute 'IsA' > > File > > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > /lib/site-packages/paraview/coprocessing.py", > > line 305, in CreateProducer > > if grid.IsA("vtkImageData") == True or \ > > AttributeError: 'NoneType' object has no attribute 'IsA' > > [PERFLOG] :: COPROC 2 0.01404021SEC. > > Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 Time > > Step: 2 [ 720.00] > > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] > > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] > > AttributeError: 'NoneType' object has no attribute 'IsA' > > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > > File > > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > /lib/site-packages/paraview/coprocessing.py", > > line 305, in CreateProducer > > if grid.IsA("vtkImageData") == True or \ > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: allinputsgridwriter.py Type: text/x-python Size: 4226 bytes Desc: not available URL: From u.utku.turuncoglu at be.itu.edu.tr Tue Aug 15 14:27:07 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Tue, 15 Aug 2017 21:27:07 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> Message-ID: <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> Hi Andy, Thanks for your help and the script. Actually, I was adding input names to the script by hand. Anyway, I tested your script and it gives similar error as follows, File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer if grid.IsA("vtkImageData") == True or \ AttributeError: 'NoneType' object has no attribute 'IsA' grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer if grid.IsA("vtkImageData") == True or \ AttributeError: 'NoneType' object has no attribute 'IsA' grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) File "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py", line 305, in CreateProducer if grid.IsA("vtkImageData") == True or \ AttributeError: 'NoneType' object has no attribute 'IsA' I'll tested whole environment once again with Intel compiler to see it helps or not. Let me know if you have any other idea. Regards, --ufuk > Hi Ufuk, > > For the allinputsgridwriter.py you currently need to manually add in the > inputs yourself (i.e. replace the "namedinputs = ['input']" line with the > name of your inputs. That has caught me in the past as well so I decided > to > fix that. Attached is my new version of that script where it doesn't > require you to specify the input names in case you want to try this new > one > instead. If you do, please let us know if that solves your problem or not. > > Best, > Andy > > > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel > wrote: > >> On Tue, Aug 15, 2017 at 17:59:47 +0300, u.utku.turuncoglu at be.itu.edu.tr >> wrote: >> > I solved the problem and i am able to run the simulation code with >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer >> version >> > of protobuf library (3.3.0) and compiling the model code with this >> version >> > of PV (using gcc). >> > >> > Now, the problem is that the code gives following warnings and do >> nothing >> > with standard allinputsgridwriter.py script. Do you think that it is >> > related with protobuf library. The same setup is working without any >> > problem in an other system using Intel compiler. >> >> It'd be better to try with one MPI process rather than???I count 10 to >> get >> the error? Not sure what's up though, Andy? >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> /lib/site-packages/paraview/coprocessing.py", >> > line 305, in CreateProducer >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> > if grid.IsA("vtkImageData") == True or \ >> > File >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> /lib/site-packages/paraview/coprocessing.py", >> > line 305, in CreateProducer >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> > File >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> /lib/site-packages/paraview/coprocessing.py", >> > line 305, in CreateProducer >> > if grid.IsA("vtkImageData") == True or \ >> > if grid.IsA("vtkImageData") == True or \ >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> > File >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> /lib/site-packages/paraview/coprocessing.py", >> > line 305, in CreateProducer >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> > if grid.IsA("vtkImageData") == True or \ >> > if grid.IsA("vtkImageData") == True or \ >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> > if grid.IsA("vtkImageData") == True or \ >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> > File >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> /lib/site-packages/paraview/coprocessing.py", >> > line 305, in CreateProducer >> > if grid.IsA("vtkImageData") == True or \ >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> > [PERFLOG] :: COPROC 2 0.01404021SEC. >> > Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 >> Time >> > Step: 2 [ 720.00] >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> > File >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> /lib/site-packages/paraview/coprocessing.py", >> > line 305, in CreateProducer >> > if grid.IsA("vtkImageData") == True or \ >> >> --Ben >> > From andy.bauer at kitware.com Tue Aug 15 14:45:33 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 15 Aug 2017 14:45:33 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> Message-ID: Hi Ufuk, It looks like the script line that is not working properly is: grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) grid is set to None here for your build. Trying something simpler, in pvpython can you try the following and let us know if it works: ============= from paraview.simple import * a = Wavelet() a.UpdatePipeline() b = a.GetClientSideObject() c = b.GetOutputDataObject(0) print c ============= It should give output like the following if it works: vtkImageData (0x4586a00) Debug: Off Modified Time: 204809 Reference Count: 2 Registered Events: (none) Information: 0x4586450 Data Released: False Global Release Data: Off UpdateTime: 204810 Field Data: Debug: Off Modified Time: 204775 Reference Count: 1 Registered Events: (none) Number Of Arrays: 0 Number Of Components: 0 Number Of Tuples: 0 Number Of Points: 9261 Number Of Cells: 8000 Cell Data: Debug: Off Modified Time: 204783 Reference Count: 1 Registered Events: Registered Observers: vtkObserver (0x4586550) Event: 33 EventName: ModifiedEvent Command: 0x45864a0 Priority: 0 Tag: 1 Number Of Arrays: 0 Number Of Components: 0 Number Of Tuples: 0 Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) Scalars: (none) Vectors: (none) Normals: (none) TCoords: (none) Tensors: (none) GlobalIds: (none) PedigreeIds: (none) EdgeFlag: (none) Point Data: Debug: Off Modified Time: 204809 Reference Count: 1 Registered Events: Registered Observers: vtkObserver (0x45864f0) Event: 33 EventName: ModifiedEvent Command: 0x45864a0 Priority: 0 Tag: 1 Number Of Arrays: 1 Array 0 name = RTData Number Of Components: 1 Number Of Tuples: 9261 Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) Scalars: Debug: Off Modified Time: 204809 Reference Count: 2 Registered Events: (none) Name: RTData Data type: float Size: 9261 MaxId: 9260 NumberOfComponents: 1 Information: 0 Name: RTData Number Of Components: 1 Number Of Tuples: 9261 Size: 9261 MaxId: 9260 LookupTable: (none) Vectors: (none) Normals: (none) TCoords: (none) Tensors: (none) GlobalIds: (none) PedigreeIds: (none) EdgeFlag: (none) Bounds: Xmin,Xmax: (-10, 10) Ymin,Ymax: (-10, 10) Zmin,Zmax: (-10, 10) Compute Time: 204875 Spacing: (1, 1, 1) Origin: (0, 0, 0) Dimensions: (21, 21, 21) Increments: (0, 0, 0) Extent: (-10, 10, -10, 10, -10, 10) On Tue, Aug 15, 2017 at 2:27 PM, wrote: > Hi Andy, > > Thanks for your help and the script. Actually, I was adding input names to > the script by hand. Anyway, I tested your script and it gives similar > error as follows, > > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > if grid.IsA("vtkImageData") == True or \ > AttributeError: 'NoneType' object has no attribute 'IsA' > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > if grid.IsA("vtkImageData") == True or \ > AttributeError: 'NoneType' object has no attribute 'IsA' > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > File > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > egl/lib/site-packages/paraview/coprocessing.py", > line 305, in CreateProducer > if grid.IsA("vtkImageData") == True or \ > AttributeError: 'NoneType' object has no attribute 'IsA' > > I'll tested whole environment once again with Intel compiler to see it > helps or not. Let me know if you have any other idea. > > Regards, > > --ufuk > > > > Hi Ufuk, > > > > For the allinputsgridwriter.py you currently need to manually add in the > > inputs yourself (i.e. replace the "namedinputs = ['input']" line with the > > name of your inputs. That has caught me in the past as well so I decided > > to > > fix that. Attached is my new version of that script where it doesn't > > require you to specify the input names in case you want to try this new > > one > > instead. If you do, please let us know if that solves your problem or > not. > > > > Best, > > Andy > > > > > > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel > > wrote: > > > >> On Tue, Aug 15, 2017 at 17:59:47 +0300, u.utku.turuncoglu at be.itu.edu.tr > >> wrote: > >> > I solved the problem and i am able to run the simulation code with > >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer > >> version > >> > of protobuf library (3.3.0) and compiling the model code with this > >> version > >> > of PV (using gcc). > >> > > >> > Now, the problem is that the code gives following warnings and do > >> nothing > >> > with standard allinputsgridwriter.py script. Do you think that it is > >> > related with protobuf library. The same setup is working without any > >> > problem in an other system using Intel compiler. > >> > >> It'd be better to try with one MPI process rather than???I count 10 to > >> get > >> the error? Not sure what's up though, Andy? > >> > >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> /lib/site-packages/paraview/coprocessing.py", > >> > line 305, in CreateProducer > >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> > if grid.IsA("vtkImageData") == True or \ > >> > File > >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> /lib/site-packages/paraview/coprocessing.py", > >> > line 305, in CreateProducer > >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> > File > >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> /lib/site-packages/paraview/coprocessing.py", > >> > line 305, in CreateProducer > >> > if grid.IsA("vtkImageData") == True or \ > >> > if grid.IsA("vtkImageData") == True or \ > >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> > File > >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> /lib/site-packages/paraview/coprocessing.py", > >> > line 305, in CreateProducer > >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> > if grid.IsA("vtkImageData") == True or \ > >> > if grid.IsA("vtkImageData") == True or \ > >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> > if grid.IsA("vtkImageData") == True or \ > >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> > File > >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> /lib/site-packages/paraview/coprocessing.py", > >> > line 305, in CreateProducer > >> > if grid.IsA("vtkImageData") == True or \ > >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> > [PERFLOG] :: COPROC 2 0.01404021SEC. > >> > Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 > >> Time > >> > Step: 2 [ 720.00] > >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] > >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] > >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> > File > >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> /lib/site-packages/paraview/coprocessing.py", > >> > line 305, in CreateProducer > >> > if grid.IsA("vtkImageData") == True or \ > >> > >> --Ben > >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Tue Aug 15 14:49:56 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Tue, 15 Aug 2017 21:49:56 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> Message-ID: <64381.5.254.103.147.1502822996.squirrel@webmail.be.itu.edu.tr> Hi, Yes. It works and produces same output. --ufuk > Hi Ufuk, > > It looks like the script line that is not working properly is: > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > > grid is set to None here for your build. Trying something simpler, in > pvpython can you try the following and let us know if it works: > ============= > from paraview.simple import * > a = Wavelet() > a.UpdatePipeline() > b = a.GetClientSideObject() > c = b.GetOutputDataObject(0) > print c > ============= > > > > It should give output like the following if it works: > vtkImageData (0x4586a00) > Debug: Off > Modified Time: 204809 > Reference Count: 2 > Registered Events: (none) > Information: 0x4586450 > Data Released: False > Global Release Data: Off > UpdateTime: 204810 > Field Data: > Debug: Off > Modified Time: 204775 > Reference Count: 1 > Registered Events: (none) > Number Of Arrays: 0 > Number Of Components: 0 > Number Of Tuples: 0 > Number Of Points: 9261 > Number Of Cells: 8000 > Cell Data: > Debug: Off > Modified Time: 204783 > Reference Count: 1 > Registered Events: > Registered Observers: > vtkObserver (0x4586550) > Event: 33 > EventName: ModifiedEvent > Command: 0x45864a0 > Priority: 0 > Tag: 1 > Number Of Arrays: 0 > Number Of Components: 0 > Number Of Tuples: 0 > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > Scalars: (none) > Vectors: (none) > Normals: (none) > TCoords: (none) > Tensors: (none) > GlobalIds: (none) > PedigreeIds: (none) > EdgeFlag: (none) > Point Data: > Debug: Off > Modified Time: 204809 > Reference Count: 1 > Registered Events: > Registered Observers: > vtkObserver (0x45864f0) > Event: 33 > EventName: ModifiedEvent > Command: 0x45864a0 > Priority: 0 > Tag: 1 > Number Of Arrays: 1 > Array 0 name = RTData > Number Of Components: 1 > Number Of Tuples: 9261 > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > Scalars: > Debug: Off > Modified Time: 204809 > Reference Count: 2 > Registered Events: (none) > Name: RTData > Data type: float > Size: 9261 > MaxId: 9260 > NumberOfComponents: 1 > Information: 0 > Name: RTData > Number Of Components: 1 > Number Of Tuples: 9261 > Size: 9261 > MaxId: 9260 > LookupTable: (none) > Vectors: (none) > Normals: (none) > TCoords: (none) > Tensors: (none) > GlobalIds: (none) > PedigreeIds: (none) > EdgeFlag: (none) > Bounds: > Xmin,Xmax: (-10, 10) > Ymin,Ymax: (-10, 10) > Zmin,Zmax: (-10, 10) > Compute Time: 204875 > Spacing: (1, 1, 1) > Origin: (0, 0, 0) > Dimensions: (21, 21, 21) > Increments: (0, 0, 0) > Extent: (-10, 10, -10, 10, -10, 10) > > > > On Tue, Aug 15, 2017 at 2:27 PM, wrote: > >> Hi Andy, >> >> Thanks for your help and the script. Actually, I was adding input names >> to >> the script by hand. Anyway, I tested your script and it gives similar >> error as follows, >> >> File >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> egl/lib/site-packages/paraview/coprocessing.py", >> line 305, in CreateProducer >> if grid.IsA("vtkImageData") == True or \ >> AttributeError: 'NoneType' object has no attribute 'IsA' >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> File >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> egl/lib/site-packages/paraview/coprocessing.py", >> line 305, in CreateProducer >> if grid.IsA("vtkImageData") == True or \ >> AttributeError: 'NoneType' object has no attribute 'IsA' >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> File >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> egl/lib/site-packages/paraview/coprocessing.py", >> line 305, in CreateProducer >> if grid.IsA("vtkImageData") == True or \ >> AttributeError: 'NoneType' object has no attribute 'IsA' >> >> I'll tested whole environment once again with Intel compiler to see it >> helps or not. Let me know if you have any other idea. >> >> Regards, >> >> --ufuk >> >> >> > Hi Ufuk, >> > >> > For the allinputsgridwriter.py you currently need to manually add in >> the >> > inputs yourself (i.e. replace the "namedinputs = ['input']" line with >> the >> > name of your inputs. That has caught me in the past as well so I >> decided >> > to >> > fix that. Attached is my new version of that script where it doesn't >> > require you to specify the input names in case you want to try this >> new >> > one >> > instead. If you do, please let us know if that solves your problem or >> not. >> > >> > Best, >> > Andy >> > >> > >> > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel >> >> > wrote: >> > >> >> On Tue, Aug 15, 2017 at 17:59:47 +0300, >> u.utku.turuncoglu at be.itu.edu.tr >> >> wrote: >> >> > I solved the problem and i am able to run the simulation code with >> >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer >> >> version >> >> > of protobuf library (3.3.0) and compiling the model code with this >> >> version >> >> > of PV (using gcc). >> >> > >> >> > Now, the problem is that the code gives following warnings and do >> >> nothing >> >> > with standard allinputsgridwriter.py script. Do you think that it >> is >> >> > related with protobuf library. The same setup is working without >> any >> >> > problem in an other system using Intel compiler. >> >> >> >> It'd be better to try with one MPI process rather than???????I count >> 10 to >> >> get >> >> the error? Not sure what's up though, Andy? >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> /lib/site-packages/paraview/coprocessing.py", >> >> > line 305, in CreateProducer >> >> > grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> > grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> > if grid.IsA("vtkImageData") == True or \ >> >> > File >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> /lib/site-packages/paraview/coprocessing.py", >> >> > line 305, in CreateProducer >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> > File >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> /lib/site-packages/paraview/coprocessing.py", >> >> > line 305, in CreateProducer >> >> > if grid.IsA("vtkImageData") == True or \ >> >> > if grid.IsA("vtkImageData") == True or \ >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> > grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> > File >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> /lib/site-packages/paraview/coprocessing.py", >> >> > line 305, in CreateProducer >> >> > grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> > if grid.IsA("vtkImageData") == True or \ >> >> > if grid.IsA("vtkImageData") == True or \ >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> > if grid.IsA("vtkImageData") == True or \ >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> > File >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> /lib/site-packages/paraview/coprocessing.py", >> >> > line 305, in CreateProducer >> >> > if grid.IsA("vtkImageData") == True or \ >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> > [PERFLOG] :: COPROC 2 0.01404021SEC. >> >> > Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 >> >> Time >> >> > Step: 2 [ 720.00] >> >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] >> >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> > grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> > File >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> /lib/site-packages/paraview/coprocessing.py", >> >> > line 305, in CreateProducer >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> --Ben >> >> >> > >> >> > From andy.bauer at kitware.com Tue Aug 15 15:05:54 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 15 Aug 2017 15:05:54 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <64381.5.254.103.147.1502822996.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> <64381.5.254.103.147.1502822996.squirrel@webmail.be.itu.edu.tr> Message-ID: Hmm, how about making that Python code into a file and running it with both: mpirun -np 4 pvbatch mpirun -np 4 pvbatch -sym Just to verify, the allinputsgridwriter.py didn't work with any of the Catalyst examples (e.g. CFullExample), correct? I think this is going to be some issue where we continually bisect the problem space so I appreciate your patience on this. Best, Andy On Tue, Aug 15, 2017 at 2:49 PM, wrote: > Hi, > > Yes. It works and produces same output. > > --ufuk > > > Hi Ufuk, > > > > It looks like the script line that is not working properly is: > > grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > > > > grid is set to None here for your build. Trying something simpler, in > > pvpython can you try the following and let us know if it works: > > ============= > > from paraview.simple import * > > a = Wavelet() > > a.UpdatePipeline() > > b = a.GetClientSideObject() > > c = b.GetOutputDataObject(0) > > print c > > ============= > > > > > > > > It should give output like the following if it works: > > vtkImageData (0x4586a00) > > Debug: Off > > Modified Time: 204809 > > Reference Count: 2 > > Registered Events: (none) > > Information: 0x4586450 > > Data Released: False > > Global Release Data: Off > > UpdateTime: 204810 > > Field Data: > > Debug: Off > > Modified Time: 204775 > > Reference Count: 1 > > Registered Events: (none) > > Number Of Arrays: 0 > > Number Of Components: 0 > > Number Of Tuples: 0 > > Number Of Points: 9261 > > Number Of Cells: 8000 > > Cell Data: > > Debug: Off > > Modified Time: 204783 > > Reference Count: 1 > > Registered Events: > > Registered Observers: > > vtkObserver (0x4586550) > > Event: 33 > > EventName: ModifiedEvent > > Command: 0x45864a0 > > Priority: 0 > > Tag: 1 > > Number Of Arrays: 0 > > Number Of Components: 0 > > Number Of Tuples: 0 > > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > > Scalars: (none) > > Vectors: (none) > > Normals: (none) > > TCoords: (none) > > Tensors: (none) > > GlobalIds: (none) > > PedigreeIds: (none) > > EdgeFlag: (none) > > Point Data: > > Debug: Off > > Modified Time: 204809 > > Reference Count: 1 > > Registered Events: > > Registered Observers: > > vtkObserver (0x45864f0) > > Event: 33 > > EventName: ModifiedEvent > > Command: 0x45864a0 > > Priority: 0 > > Tag: 1 > > Number Of Arrays: 1 > > Array 0 name = RTData > > Number Of Components: 1 > > Number Of Tuples: 9261 > > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > > Scalars: > > Debug: Off > > Modified Time: 204809 > > Reference Count: 2 > > Registered Events: (none) > > Name: RTData > > Data type: float > > Size: 9261 > > MaxId: 9260 > > NumberOfComponents: 1 > > Information: 0 > > Name: RTData > > Number Of Components: 1 > > Number Of Tuples: 9261 > > Size: 9261 > > MaxId: 9260 > > LookupTable: (none) > > Vectors: (none) > > Normals: (none) > > TCoords: (none) > > Tensors: (none) > > GlobalIds: (none) > > PedigreeIds: (none) > > EdgeFlag: (none) > > Bounds: > > Xmin,Xmax: (-10, 10) > > Ymin,Ymax: (-10, 10) > > Zmin,Zmax: (-10, 10) > > Compute Time: 204875 > > Spacing: (1, 1, 1) > > Origin: (0, 0, 0) > > Dimensions: (21, 21, 21) > > Increments: (0, 0, 0) > > Extent: (-10, 10, -10, 10, -10, 10) > > > > > > > > On Tue, Aug 15, 2017 at 2:27 PM, > wrote: > > > >> Hi Andy, > >> > >> Thanks for your help and the script. Actually, I was adding input names > >> to > >> the script by hand. Anyway, I tested your script and it gives similar > >> error as follows, > >> > >> File > >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> egl/lib/site-packages/paraview/coprocessing.py", > >> line 305, in CreateProducer > >> if grid.IsA("vtkImageData") == True or \ > >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> File > >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> egl/lib/site-packages/paraview/coprocessing.py", > >> line 305, in CreateProducer > >> if grid.IsA("vtkImageData") == True or \ > >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> File > >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> egl/lib/site-packages/paraview/coprocessing.py", > >> line 305, in CreateProducer > >> if grid.IsA("vtkImageData") == True or \ > >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> > >> I'll tested whole environment once again with Intel compiler to see it > >> helps or not. Let me know if you have any other idea. > >> > >> Regards, > >> > >> --ufuk > >> > >> > >> > Hi Ufuk, > >> > > >> > For the allinputsgridwriter.py you currently need to manually add in > >> the > >> > inputs yourself (i.e. replace the "namedinputs = ['input']" line with > >> the > >> > name of your inputs. That has caught me in the past as well so I > >> decided > >> > to > >> > fix that. Attached is my new version of that script where it doesn't > >> > require you to specify the input names in case you want to try this > >> new > >> > one > >> > instead. If you do, please let us know if that solves your problem or > >> not. > >> > > >> > Best, > >> > Andy > >> > > >> > > >> > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel > >> > >> > wrote: > >> > > >> >> On Tue, Aug 15, 2017 at 17:59:47 +0300, > >> u.utku.turuncoglu at be.itu.edu.tr > >> >> wrote: > >> >> > I solved the problem and i am able to run the simulation code with > >> >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer > >> >> version > >> >> > of protobuf library (3.3.0) and compiling the model code with this > >> >> version > >> >> > of PV (using gcc). > >> >> > > >> >> > Now, the problem is that the code gives following warnings and do > >> >> nothing > >> >> > with standard allinputsgridwriter.py script. Do you think that it > >> is > >> >> > related with protobuf library. The same setup is working without > >> any > >> >> > problem in an other system using Intel compiler. > >> >> > >> >> It'd be better to try with one MPI process rather than???????I count > >> 10 to > >> >> get > >> >> the error? Not sure what's up though, Andy? > >> >> > >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> > line 305, in CreateProducer > >> >> > grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> > grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > File > >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> > line 305, in CreateProducer > >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > File > >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> > line 305, in CreateProducer > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> > File > >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> > line 305, in CreateProducer > >> >> > grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > File > >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> > line 305, in CreateProducer > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > [PERFLOG] :: COPROC 2 0.01404021SEC. > >> >> > Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 > >> >> Time > >> >> > Step: 2 [ 720.00] > >> >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] > >> >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] > >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> > File > >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> > line 305, in CreateProducer > >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> > >> >> --Ben > >> >> > >> > > >> > >> > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Tue Aug 15 15:30:28 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Tue, 15 Aug 2017 22:30:28 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> <64381.5.254.103.147.1502822996.squirrel@webmail.be.itu.edu.tr> Message-ID: <65507.5.254.103.147.1502825428.squirrel@webmail.be.itu.edu.tr> Without support of you and also Ben, i could not even reach to this point. Thanks again. At least, code runs now. I think that this is big improvement. Anyway, both command is working as expected, > mpirun -np 4 pvbatch > mpirun -np 4 pvbatch -sym I also tested allinputsgridwriter_new.py with CFullExample (and also Fortran90FullExample) and it works without any problem. As I mentioned before, CFullExample was also working before upgrading protobuf (still, i don't know why). So, it is not a good way to find the source of the problem. --ufuk > Hmm, how about making that Python code into a file and running it with > both: > mpirun -np 4 pvbatch > mpirun -np 4 pvbatch -sym > > Just to verify, the allinputsgridwriter.py didn't work with any of the > Catalyst examples (e.g. CFullExample), correct? > > I think this is going to be some issue where we continually bisect the > problem space so I appreciate your patience on this. > > Best, > Andy > > On Tue, Aug 15, 2017 at 2:49 PM, wrote: > >> Hi, >> >> Yes. It works and produces same output. >> >> --ufuk >> >> > Hi Ufuk, >> > >> > It looks like the script line that is not working properly is: >> > grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> > >> > grid is set to None here for your build. Trying something simpler, in >> > pvpython can you try the following and let us know if it works: >> > ============= >> > from paraview.simple import * >> > a = Wavelet() >> > a.UpdatePipeline() >> > b = a.GetClientSideObject() >> > c = b.GetOutputDataObject(0) >> > print c >> > ============= >> > >> > >> > >> > It should give output like the following if it works: >> > vtkImageData (0x4586a00) >> > Debug: Off >> > Modified Time: 204809 >> > Reference Count: 2 >> > Registered Events: (none) >> > Information: 0x4586450 >> > Data Released: False >> > Global Release Data: Off >> > UpdateTime: 204810 >> > Field Data: >> > Debug: Off >> > Modified Time: 204775 >> > Reference Count: 1 >> > Registered Events: (none) >> > Number Of Arrays: 0 >> > Number Of Components: 0 >> > Number Of Tuples: 0 >> > Number Of Points: 9261 >> > Number Of Cells: 8000 >> > Cell Data: >> > Debug: Off >> > Modified Time: 204783 >> > Reference Count: 1 >> > Registered Events: >> > Registered Observers: >> > vtkObserver (0x4586550) >> > Event: 33 >> > EventName: ModifiedEvent >> > Command: 0x45864a0 >> > Priority: 0 >> > Tag: 1 >> > Number Of Arrays: 0 >> > Number Of Components: 0 >> > Number Of Tuples: 0 >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) >> > Scalars: (none) >> > Vectors: (none) >> > Normals: (none) >> > TCoords: (none) >> > Tensors: (none) >> > GlobalIds: (none) >> > PedigreeIds: (none) >> > EdgeFlag: (none) >> > Point Data: >> > Debug: Off >> > Modified Time: 204809 >> > Reference Count: 1 >> > Registered Events: >> > Registered Observers: >> > vtkObserver (0x45864f0) >> > Event: 33 >> > EventName: ModifiedEvent >> > Command: 0x45864a0 >> > Priority: 0 >> > Tag: 1 >> > Number Of Arrays: 1 >> > Array 0 name = RTData >> > Number Of Components: 1 >> > Number Of Tuples: 9261 >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) >> > Scalars: >> > Debug: Off >> > Modified Time: 204809 >> > Reference Count: 2 >> > Registered Events: (none) >> > Name: RTData >> > Data type: float >> > Size: 9261 >> > MaxId: 9260 >> > NumberOfComponents: 1 >> > Information: 0 >> > Name: RTData >> > Number Of Components: 1 >> > Number Of Tuples: 9261 >> > Size: 9261 >> > MaxId: 9260 >> > LookupTable: (none) >> > Vectors: (none) >> > Normals: (none) >> > TCoords: (none) >> > Tensors: (none) >> > GlobalIds: (none) >> > PedigreeIds: (none) >> > EdgeFlag: (none) >> > Bounds: >> > Xmin,Xmax: (-10, 10) >> > Ymin,Ymax: (-10, 10) >> > Zmin,Zmax: (-10, 10) >> > Compute Time: 204875 >> > Spacing: (1, 1, 1) >> > Origin: (0, 0, 0) >> > Dimensions: (21, 21, 21) >> > Increments: (0, 0, 0) >> > Extent: (-10, 10, -10, 10, -10, 10) >> > >> > >> > >> > On Tue, Aug 15, 2017 at 2:27 PM, >> wrote: >> > >> >> Hi Andy, >> >> >> >> Thanks for your help and the script. Actually, I was adding input >> names >> >> to >> >> the script by hand. Anyway, I tested your script and it gives similar >> >> error as follows, >> >> >> >> File >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> >> egl/lib/site-packages/paraview/coprocessing.py", >> >> line 305, in CreateProducer >> >> if grid.IsA("vtkImageData") == True or \ >> >> AttributeError: 'NoneType' object has no attribute 'IsA' >> >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> File >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> >> egl/lib/site-packages/paraview/coprocessing.py", >> >> line 305, in CreateProducer >> >> if grid.IsA("vtkImageData") == True or \ >> >> AttributeError: 'NoneType' object has no attribute 'IsA' >> >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> File >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> >> egl/lib/site-packages/paraview/coprocessing.py", >> >> line 305, in CreateProducer >> >> if grid.IsA("vtkImageData") == True or \ >> >> AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> I'll tested whole environment once again with Intel compiler to see >> it >> >> helps or not. Let me know if you have any other idea. >> >> >> >> Regards, >> >> >> >> --ufuk >> >> >> >> >> >> > Hi Ufuk, >> >> > >> >> > For the allinputsgridwriter.py you currently need to manually add >> in >> >> the >> >> > inputs yourself (i.e. replace the "namedinputs = ['input']" line >> with >> >> the >> >> > name of your inputs. That has caught me in the past as well so I >> >> decided >> >> > to >> >> > fix that. Attached is my new version of that script where it >> doesn't >> >> > require you to specify the input names in case you want to try this >> >> new >> >> > one >> >> > instead. If you do, please let us know if that solves your problem >> or >> >> not. >> >> > >> >> > Best, >> >> > Andy >> >> > >> >> > >> >> > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel >> >> >> >> > wrote: >> >> > >> >> >> On Tue, Aug 15, 2017 at 17:59:47 +0300, >> >> u.utku.turuncoglu at be.itu.edu.tr >> >> >> wrote: >> >> >> > I solved the problem and i am able to run the simulation code >> with >> >> >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with >> newer >> >> >> version >> >> >> > of protobuf library (3.3.0) and compiling the model code with >> this >> >> >> version >> >> >> > of PV (using gcc). >> >> >> > >> >> >> > Now, the problem is that the code gives following warnings and >> do >> >> >> nothing >> >> >> > with standard allinputsgridwriter.py script. Do you think that >> it >> >> is >> >> >> > related with protobuf library. The same setup is working without >> >> any >> >> >> > problem in an other system using Intel compiler. >> >> >> >> >> >> It'd be better to try with one MPI process rather >> than???????????????I count >> >> 10 to >> >> >> get >> >> >> the error? Not sure what's up though, Andy? >> >> >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> > line 305, in CreateProducer >> >> >> > grid = >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> > grid = >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> > File >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> > line 305, in CreateProducer >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> > File >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> > line 305, in CreateProducer >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> > grid = >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> > File >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> > line 305, in CreateProducer >> >> >> > grid = >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> > File >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> > line 305, in CreateProducer >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> > [PERFLOG] :: COPROC 2 0.01404021SEC. >> >> >> > Running COP Component: 2005-08-27T00:12:00 --> >> 2005-08-27T00:18:00 >> >> >> Time >> >> >> > Step: 2 [ 720.00] >> >> >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] >> >> >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> > grid = >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> > File >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> > line 305, in CreateProducer >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> >> >> --Ben >> >> >> >> >> > >> >> >> >> >> > >> >> >> > From andy.bauer at kitware.com Tue Aug 15 15:41:55 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 15 Aug 2017 15:41:55 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <65507.5.254.103.147.1502825428.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> <64381.5.254.103.147.1502822996.squirrel@webmail.be.itu.edu.tr> <65507.5.254.103.147.1502825428.squirrel@webmail.be.itu.edu.tr> Message-ID: Hmm, can you check that you've set the vtkCPInputDataDescription grid through the SetGrid() method? You can add in something like "print("input is ", datadescription.GetInputDescriptionByName().GetGrid())" a couple of places in your Python script to see if there is actually a grid added there for that input. Best, Andy On Tue, Aug 15, 2017 at 3:30 PM, wrote: > Without support of you and also Ben, i could not even reach to this point. > Thanks again. At least, code runs now. I think that this is big > improvement. > > Anyway, both command is working as expected, > > > mpirun -np 4 pvbatch > > mpirun -np 4 pvbatch -sym > > I also tested allinputsgridwriter_new.py with CFullExample (and also > Fortran90FullExample) and it works without any problem. As I mentioned > before, CFullExample was also working before upgrading protobuf (still, i > don't know why). So, it is not a good way to find the source of the > problem. > > --ufuk > > > > Hmm, how about making that Python code into a file and running it with > > both: > > mpirun -np 4 pvbatch > > mpirun -np 4 pvbatch -sym > > > > Just to verify, the allinputsgridwriter.py didn't work with any of the > > Catalyst examples (e.g. CFullExample), correct? > > > > I think this is going to be some issue where we continually bisect the > > problem space so I appreciate your patience on this. > > > > Best, > > Andy > > > > On Tue, Aug 15, 2017 at 2:49 PM, > wrote: > > > >> Hi, > >> > >> Yes. It works and produces same output. > >> > >> --ufuk > >> > >> > Hi Ufuk, > >> > > >> > It looks like the script line that is not working properly is: > >> > grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> > > >> > grid is set to None here for your build. Trying something simpler, in > >> > pvpython can you try the following and let us know if it works: > >> > ============= > >> > from paraview.simple import * > >> > a = Wavelet() > >> > a.UpdatePipeline() > >> > b = a.GetClientSideObject() > >> > c = b.GetOutputDataObject(0) > >> > print c > >> > ============= > >> > > >> > > >> > > >> > It should give output like the following if it works: > >> > vtkImageData (0x4586a00) > >> > Debug: Off > >> > Modified Time: 204809 > >> > Reference Count: 2 > >> > Registered Events: (none) > >> > Information: 0x4586450 > >> > Data Released: False > >> > Global Release Data: Off > >> > UpdateTime: 204810 > >> > Field Data: > >> > Debug: Off > >> > Modified Time: 204775 > >> > Reference Count: 1 > >> > Registered Events: (none) > >> > Number Of Arrays: 0 > >> > Number Of Components: 0 > >> > Number Of Tuples: 0 > >> > Number Of Points: 9261 > >> > Number Of Cells: 8000 > >> > Cell Data: > >> > Debug: Off > >> > Modified Time: 204783 > >> > Reference Count: 1 > >> > Registered Events: > >> > Registered Observers: > >> > vtkObserver (0x4586550) > >> > Event: 33 > >> > EventName: ModifiedEvent > >> > Command: 0x45864a0 > >> > Priority: 0 > >> > Tag: 1 > >> > Number Of Arrays: 0 > >> > Number Of Components: 0 > >> > Number Of Tuples: 0 > >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > >> > Scalars: (none) > >> > Vectors: (none) > >> > Normals: (none) > >> > TCoords: (none) > >> > Tensors: (none) > >> > GlobalIds: (none) > >> > PedigreeIds: (none) > >> > EdgeFlag: (none) > >> > Point Data: > >> > Debug: Off > >> > Modified Time: 204809 > >> > Reference Count: 1 > >> > Registered Events: > >> > Registered Observers: > >> > vtkObserver (0x45864f0) > >> > Event: 33 > >> > EventName: ModifiedEvent > >> > Command: 0x45864a0 > >> > Priority: 0 > >> > Tag: 1 > >> > Number Of Arrays: 1 > >> > Array 0 name = RTData > >> > Number Of Components: 1 > >> > Number Of Tuples: 9261 > >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > >> > Scalars: > >> > Debug: Off > >> > Modified Time: 204809 > >> > Reference Count: 2 > >> > Registered Events: (none) > >> > Name: RTData > >> > Data type: float > >> > Size: 9261 > >> > MaxId: 9260 > >> > NumberOfComponents: 1 > >> > Information: 0 > >> > Name: RTData > >> > Number Of Components: 1 > >> > Number Of Tuples: 9261 > >> > Size: 9261 > >> > MaxId: 9260 > >> > LookupTable: (none) > >> > Vectors: (none) > >> > Normals: (none) > >> > TCoords: (none) > >> > Tensors: (none) > >> > GlobalIds: (none) > >> > PedigreeIds: (none) > >> > EdgeFlag: (none) > >> > Bounds: > >> > Xmin,Xmax: (-10, 10) > >> > Ymin,Ymax: (-10, 10) > >> > Zmin,Zmax: (-10, 10) > >> > Compute Time: 204875 > >> > Spacing: (1, 1, 1) > >> > Origin: (0, 0, 0) > >> > Dimensions: (21, 21, 21) > >> > Increments: (0, 0, 0) > >> > Extent: (-10, 10, -10, 10, -10, 10) > >> > > >> > > >> > > >> > On Tue, Aug 15, 2017 at 2:27 PM, > >> wrote: > >> > > >> >> Hi Andy, > >> >> > >> >> Thanks for your help and the script. Actually, I was adding input > >> names > >> >> to > >> >> the script by hand. Anyway, I tested your script and it gives similar > >> >> error as follows, > >> >> > >> >> File > >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> >> egl/lib/site-packages/paraview/coprocessing.py", > >> >> line 305, in CreateProducer > >> >> if grid.IsA("vtkImageData") == True or \ > >> >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> File > >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> >> egl/lib/site-packages/paraview/coprocessing.py", > >> >> line 305, in CreateProducer > >> >> if grid.IsA("vtkImageData") == True or \ > >> >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> File > >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> >> egl/lib/site-packages/paraview/coprocessing.py", > >> >> line 305, in CreateProducer > >> >> if grid.IsA("vtkImageData") == True or \ > >> >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> > >> >> I'll tested whole environment once again with Intel compiler to see > >> it > >> >> helps or not. Let me know if you have any other idea. > >> >> > >> >> Regards, > >> >> > >> >> --ufuk > >> >> > >> >> > >> >> > Hi Ufuk, > >> >> > > >> >> > For the allinputsgridwriter.py you currently need to manually add > >> in > >> >> the > >> >> > inputs yourself (i.e. replace the "namedinputs = ['input']" line > >> with > >> >> the > >> >> > name of your inputs. That has caught me in the past as well so I > >> >> decided > >> >> > to > >> >> > fix that. Attached is my new version of that script where it > >> doesn't > >> >> > require you to specify the input names in case you want to try this > >> >> new > >> >> > one > >> >> > instead. If you do, please let us know if that solves your problem > >> or > >> >> not. > >> >> > > >> >> > Best, > >> >> > Andy > >> >> > > >> >> > > >> >> > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel > >> >> > >> >> > wrote: > >> >> > > >> >> >> On Tue, Aug 15, 2017 at 17:59:47 +0300, > >> >> u.utku.turuncoglu at be.itu.edu.tr > >> >> >> wrote: > >> >> >> > I solved the problem and i am able to run the simulation code > >> with > >> >> >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with > >> newer > >> >> >> version > >> >> >> > of protobuf library (3.3.0) and compiling the model code with > >> this > >> >> >> version > >> >> >> > of PV (using gcc). > >> >> >> > > >> >> >> > Now, the problem is that the code gives following warnings and > >> do > >> >> >> nothing > >> >> >> > with standard allinputsgridwriter.py script. Do you think that > >> it > >> >> is > >> >> >> > related with protobuf library. The same setup is working without > >> >> any > >> >> >> > problem in an other system using Intel compiler. > >> >> >> > >> >> >> It'd be better to try with one MPI process rather > >> than???????????????I count > >> >> 10 to > >> >> >> get > >> >> >> the error? Not sure what's up though, Andy? > >> >> >> > >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> > line 305, in CreateProducer > >> >> >> > grid = > >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> > grid = > >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > File > >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> > line 305, in CreateProducer > >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > File > >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> > line 305, in CreateProducer > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > grid = > >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> > File > >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> > line 305, in CreateProducer > >> >> >> > grid = > >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > File > >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> > line 305, in CreateProducer > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > [PERFLOG] :: COPROC 2 0.01404021SEC. > >> >> >> > Running COP Component: 2005-08-27T00:12:00 --> > >> 2005-08-27T00:18:00 > >> >> >> Time > >> >> >> > Step: 2 [ 720.00] > >> >> >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] > >> >> >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] > >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > grid = > >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> > File > >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> > line 305, in CreateProducer > >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> > >> >> >> --Ben > >> >> >> > >> >> > > >> >> > >> >> > >> > > >> > >> > >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Wed Aug 16 05:04:49 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 16 Aug 2017 11:04:49 +0200 Subject: [Paraview] Question about plugins with Catalyst and Python scripts In-Reply-To: <1311768724.204732553.1502274580737.JavaMail.root@zimbra10-e2> References: <425190736.204659731.1502273123678.JavaMail.root@zimbra10-e2> <1311768724.204732553.1502274580737.JavaMail.root@zimbra10-e2> Message-ID: Hi Yvan I understand your catalyst issue but I do not see any other solutions. Regarding loading a plugin from python, it actually is quite simple : >>> from paraview.simple import * >>> LoadPlugin("path/to/lib.so") Best regards, Mathieu Westphal On Wed, Aug 9, 2017 at 12:29 PM, wrote: > Hello, > > We have been using Catalyst (with Python coprocessing scripts) in our code > for quite a while now, and am trying to see how to make thing more > user-friendly. > > One of the main issues we have is that if plugins are loaded in ParaView > when using the Coprocessing Generator plugin, extra lines regarding those > plugins may appear in the script, even when not dreclty used. For example, > when the PointSprite plugins is enabled in PV 5.1, it adds opacity transfer > function informations. This particular example might not be relevant to PV > 5.4 with integrated PointGaussian, but other plugins may add similar > entries, whether used or not in a particular view. > > This causes issues using Catalyst, as those plugins are not enabled in > Catalyst (even using a full ParaView install with OSMesa as Catalyst, not > editions, often too incomplete). > > One solution is to remove the "offending" lines (i.e. run once, check > lines reported in error logs, removec those, run again, ...) which while > not complicated, tends to scare users and requires multiple additional > iterations to setup a visualization. > > A better solution would be to allow loading of plugins from the Python > script (especially as I expect it would allow using plugins such as > SurfaceLIC from within Catalyst), but I can't find any documentation for > this. I seem to remember some people from Kitware mentioning this was > possible in a live discussion I had, but have no additional details. > > Is there a way to tell ParaView/Catalyst to load a particular plugin from > within a Python script ? IF yes, what's the syntax ? > > Best regards, > > Yvan > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From u.utku.turuncoglu at be.itu.edu.tr Wed Aug 16 11:09:08 2017 From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr) Date: Wed, 16 Aug 2017 18:09:08 +0300 (EEST) Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> <64381.5.254.103.147.1502822996.squirrel@webmail.be.itu.edu.tr> <65507.5.254.103.147.1502825428.squirrel@webmail.be.itu.edu.tr> Message-ID: <53982.78.182.67.99.1502896148.squirrel@webmail.be.itu.edu.tr> Hi, I add print statement to python script and it shows that three input port is ok but one of them is empty. The new allinputsgridwriter.py that has automatic detection of input port fail in this case but if I use old one with manual configuration of the ports (there is no definition of empty port in this case) work fine. Anyway, the issue seems solved with external installation of protobuf library and I tested both gcc and intel compilers. It could be the version issue of the internal protobuf library in PV. So, you may consider to update it. Thanks to both of you for your help. Regards, --ufuk > Hmm, can you check that you've set the vtkCPInputDataDescription grid > through the SetGrid() method? You can add in something like "print("input > is ", datadescription.GetInputDescriptionByName().GetGrid())" a > couple of places in your Python script to see if there is actually a grid > added there for that input. > > Best, > Andy > > On Tue, Aug 15, 2017 at 3:30 PM, wrote: > >> Without support of you and also Ben, i could not even reach to this >> point. >> Thanks again. At least, code runs now. I think that this is big >> improvement. >> >> Anyway, both command is working as expected, >> >> > mpirun -np 4 pvbatch >> > mpirun -np 4 pvbatch -sym >> >> I also tested allinputsgridwriter_new.py with CFullExample (and also >> Fortran90FullExample) and it works without any problem. As I mentioned >> before, CFullExample was also working before upgrading protobuf (still, >> i >> don't know why). So, it is not a good way to find the source of the >> problem. >> >> --ufuk >> >> >> > Hmm, how about making that Python code into a file and running it with >> > both: >> > mpirun -np 4 pvbatch >> > mpirun -np 4 pvbatch -sym >> > >> > Just to verify, the allinputsgridwriter.py didn't work with any of the >> > Catalyst examples (e.g. CFullExample), correct? >> > >> > I think this is going to be some issue where we continually bisect the >> > problem space so I appreciate your patience on this. >> > >> > Best, >> > Andy >> > >> > On Tue, Aug 15, 2017 at 2:49 PM, >> wrote: >> > >> >> Hi, >> >> >> >> Yes. It works and produces same output. >> >> >> >> --ufuk >> >> >> >> > Hi Ufuk, >> >> > >> >> > It looks like the script line that is not working properly is: >> >> > grid = >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> > >> >> > grid is set to None here for your build. Trying something simpler, >> in >> >> > pvpython can you try the following and let us know if it works: >> >> > ============= >> >> > from paraview.simple import * >> >> > a = Wavelet() >> >> > a.UpdatePipeline() >> >> > b = a.GetClientSideObject() >> >> > c = b.GetOutputDataObject(0) >> >> > print c >> >> > ============= >> >> > >> >> > >> >> > >> >> > It should give output like the following if it works: >> >> > vtkImageData (0x4586a00) >> >> > Debug: Off >> >> > Modified Time: 204809 >> >> > Reference Count: 2 >> >> > Registered Events: (none) >> >> > Information: 0x4586450 >> >> > Data Released: False >> >> > Global Release Data: Off >> >> > UpdateTime: 204810 >> >> > Field Data: >> >> > Debug: Off >> >> > Modified Time: 204775 >> >> > Reference Count: 1 >> >> > Registered Events: (none) >> >> > Number Of Arrays: 0 >> >> > Number Of Components: 0 >> >> > Number Of Tuples: 0 >> >> > Number Of Points: 9261 >> >> > Number Of Cells: 8000 >> >> > Cell Data: >> >> > Debug: Off >> >> > Modified Time: 204783 >> >> > Reference Count: 1 >> >> > Registered Events: >> >> > Registered Observers: >> >> > vtkObserver (0x4586550) >> >> > Event: 33 >> >> > EventName: ModifiedEvent >> >> > Command: 0x45864a0 >> >> > Priority: 0 >> >> > Tag: 1 >> >> > Number Of Arrays: 0 >> >> > Number Of Components: 0 >> >> > Number Of Tuples: 0 >> >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) >> >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) >> >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) >> >> > Scalars: (none) >> >> > Vectors: (none) >> >> > Normals: (none) >> >> > TCoords: (none) >> >> > Tensors: (none) >> >> > GlobalIds: (none) >> >> > PedigreeIds: (none) >> >> > EdgeFlag: (none) >> >> > Point Data: >> >> > Debug: Off >> >> > Modified Time: 204809 >> >> > Reference Count: 1 >> >> > Registered Events: >> >> > Registered Observers: >> >> > vtkObserver (0x45864f0) >> >> > Event: 33 >> >> > EventName: ModifiedEvent >> >> > Command: 0x45864a0 >> >> > Priority: 0 >> >> > Tag: 1 >> >> > Number Of Arrays: 1 >> >> > Array 0 name = RTData >> >> > Number Of Components: 1 >> >> > Number Of Tuples: 9261 >> >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) >> >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) >> >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) >> >> > Scalars: >> >> > Debug: Off >> >> > Modified Time: 204809 >> >> > Reference Count: 2 >> >> > Registered Events: (none) >> >> > Name: RTData >> >> > Data type: float >> >> > Size: 9261 >> >> > MaxId: 9260 >> >> > NumberOfComponents: 1 >> >> > Information: 0 >> >> > Name: RTData >> >> > Number Of Components: 1 >> >> > Number Of Tuples: 9261 >> >> > Size: 9261 >> >> > MaxId: 9260 >> >> > LookupTable: (none) >> >> > Vectors: (none) >> >> > Normals: (none) >> >> > TCoords: (none) >> >> > Tensors: (none) >> >> > GlobalIds: (none) >> >> > PedigreeIds: (none) >> >> > EdgeFlag: (none) >> >> > Bounds: >> >> > Xmin,Xmax: (-10, 10) >> >> > Ymin,Ymax: (-10, 10) >> >> > Zmin,Zmax: (-10, 10) >> >> > Compute Time: 204875 >> >> > Spacing: (1, 1, 1) >> >> > Origin: (0, 0, 0) >> >> > Dimensions: (21, 21, 21) >> >> > Increments: (0, 0, 0) >> >> > Extent: (-10, 10, -10, 10, -10, 10) >> >> > >> >> > >> >> > >> >> > On Tue, Aug 15, 2017 at 2:27 PM, >> >> wrote: >> >> > >> >> >> Hi Andy, >> >> >> >> >> >> Thanks for your help and the script. Actually, I was adding input >> >> names >> >> >> to >> >> >> the script by hand. Anyway, I tested your script and it gives >> similar >> >> >> error as follows, >> >> >> >> >> >> File >> >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> >> >> egl/lib/site-packages/paraview/coprocessing.py", >> >> >> line 305, in CreateProducer >> >> >> if grid.IsA("vtkImageData") == True or \ >> >> >> AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> File >> >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> >> >> egl/lib/site-packages/paraview/coprocessing.py", >> >> >> line 305, in CreateProducer >> >> >> if grid.IsA("vtkImageData") == True or \ >> >> >> AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> grid = >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> File >> >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ >> >> >> egl/lib/site-packages/paraview/coprocessing.py", >> >> >> line 305, in CreateProducer >> >> >> if grid.IsA("vtkImageData") == True or \ >> >> >> AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> >> >> I'll tested whole environment once again with Intel compiler to >> see >> >> it >> >> >> helps or not. Let me know if you have any other idea. >> >> >> >> >> >> Regards, >> >> >> >> >> >> --ufuk >> >> >> >> >> >> >> >> >> > Hi Ufuk, >> >> >> > >> >> >> > For the allinputsgridwriter.py you currently need to manually >> add >> >> in >> >> >> the >> >> >> > inputs yourself (i.e. replace the "namedinputs = ['input']" line >> >> with >> >> >> the >> >> >> > name of your inputs. That has caught me in the past as well so I >> >> >> decided >> >> >> > to >> >> >> > fix that. Attached is my new version of that script where it >> >> doesn't >> >> >> > require you to specify the input names in case you want to try >> this >> >> >> new >> >> >> > one >> >> >> > instead. If you do, please let us know if that solves your >> problem >> >> or >> >> >> not. >> >> >> > >> >> >> > Best, >> >> >> > Andy >> >> >> > >> >> >> > >> >> >> > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel >> >> >> >> >> >> > wrote: >> >> >> > >> >> >> >> On Tue, Aug 15, 2017 at 17:59:47 +0300, >> >> >> u.utku.turuncoglu at be.itu.edu.tr >> >> >> >> wrote: >> >> >> >> > I solved the problem and i am able to run the simulation code >> >> with >> >> >> >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with >> >> newer >> >> >> >> version >> >> >> >> > of protobuf library (3.3.0) and compiling the model code with >> >> this >> >> >> >> version >> >> >> >> > of PV (using gcc). >> >> >> >> > >> >> >> >> > Now, the problem is that the code gives following warnings >> and >> >> do >> >> >> >> nothing >> >> >> >> > with standard allinputsgridwriter.py script. Do you think >> that >> >> it >> >> >> is >> >> >> >> > related with protobuf library. The same setup is working >> without >> >> >> any >> >> >> >> > problem in an other system using Intel compiler. >> >> >> >> >> >> >> >> It'd be better to try with one MPI process rather >> >> than????????????????????????????????I count >> >> >> 10 to >> >> >> >> get >> >> >> >> the error? Not sure what's up though, Andy? >> >> >> >> >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> >> > line 305, in CreateProducer >> >> >> >> > grid = >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> >> > grid = >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> > File >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> >> > line 305, in CreateProducer >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> > File >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> >> > line 305, in CreateProducer >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> > grid = >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> >> > File >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> >> > line 305, in CreateProducer >> >> >> >> > grid = >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> > File >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> >> > line 305, in CreateProducer >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> > [PERFLOG] :: COPROC 2 0.01404021SEC. >> >> >> >> > Running COP Component: 2005-08-27T00:12:00 --> >> >> 2005-08-27T00:18:00 >> >> >> >> Time >> >> >> >> > Step: 2 [ 720.00] >> >> >> >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] >> >> >> >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' >> >> >> >> > grid = >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) >> >> >> >> > File >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl >> >> >> >> /lib/site-packages/paraview/coprocessing.py", >> >> >> >> > line 305, in CreateProducer >> >> >> >> > if grid.IsA("vtkImageData") == True or \ >> >> >> >> >> >> >> >> --Ben >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> > >> >> > From mbahameish at gmail.com Wed Aug 16 14:34:03 2017 From: mbahameish at gmail.com (Mariam) Date: Wed, 16 Aug 2017 19:34:03 +0100 Subject: [Paraview] [Issue] IceT on a Display Wall Message-ID: <8826AA53-08EE-4721-AFA3-5730ED5BB03E@gmail.com> Hi, I am trying to configure IceT on our display wall. I followed all the instructions on paraview website & mail list. However, when the client connects to the head node server, the window displayed for few seconds then pvserver crashes with the following error: [0-1] terminated [2] process exited without calling finalize [3] terminated ---- error analysis ----- [2] on Node1 pvserver ended prematurely and may have crashed. exit code 0xc0000005 I checked the event viewer logs, and this is the error message: Faulting application name: pvserver.exe, version: 0.0.0.0, time stamp: 0x59365720 Faulting module name: vtkPVClientServerCoreRendering-pv5.4.dll, version: 0.0.0.0, time stamp: 0x593652a6 Exception code: 0xc0000005 Fault offset: 0x000000000005e86b Faulting process id: 0x8c4 Faulting application start time: 0x01d316ac26879696 Faulting application path: path\to\paraview\bin\pvserver.exe Faulting module path: path\to\paraview \bin\vtkPVClientServerCoreRendering-pv5.4.dll The display wall consists of 32 nodes where each driving two screens; Operating System: Windows 10, ParaView Version: 5.4. As a beginning, I was trying one 1 node and 2 nodes. PVX File; for 1 node: ??????????????? ??????????????? ????????????? ??????????????? ?? ?? Command: mpiexec -np 4 pvserver tiles.pvx PVX file for two nodes: ??????????????? ???? ??????????????? ???? ?? ?? Command: mpiexec ?hosts 2 Node1 2 Node2 2 pvserver ?tx=2 ?ty=1 tiles.pvx Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Aug 16 15:03:00 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 16 Aug 2017 15:03:00 -0400 Subject: [Paraview] Segmentation fault in protobuf In-Reply-To: <53982.78.182.67.99.1502896148.squirrel@webmail.be.itu.edu.tr> References: <54037.78.182.67.99.1502649881.squirrel@webmail.be.itu.edu.tr> <20170814132051.GB2910@megas.kitware.com> <57762.78.182.67.99.1502718595.squirrel@webmail.be.itu.edu.tr> <20170814143029.GA21270@megas.kitware.com> <59870.78.182.67.99.1502732741.squirrel@webmail.be.itu.edu.tr> <20170814185009.GA21197@rotor.kitware.com> <62482.78.182.67.99.1502809187.squirrel@webmail.be.itu.edu.tr> <20170815164004.GA17070@rotor.kitware.com> <63652.78.182.67.99.1502821627.squirrel@webmail.be.itu.edu.tr> <64381.5.254.103.147.1502822996.squirrel@webmail.be.itu.edu.tr> <65507.5.254.103.147.1502825428.squirrel@webmail.be.itu.edu.tr> <53982.78.182.67.99.1502896148.squirrel@webmail.be.itu.edu.tr> Message-ID: Hi Ufuk, Glad to hear that things are working for you and thanks for reporting back. Cheers, Andy On Wed, Aug 16, 2017 at 11:09 AM, wrote: > Hi, > > I add print statement to python script and it shows that three input port > is ok but one of them is empty. The new allinputsgridwriter.py that has > automatic detection of input port fail in this case but if I use old one > with manual configuration of the ports (there is no definition of empty > port in this case) work fine. Anyway, the issue seems solved with external > installation of protobuf library and I tested both gcc and intel > compilers. It could be the version issue of the internal protobuf library > in PV. So, you may consider to update it. Thanks to both of you for your > help. > > Regards, > > --ufuk > > > Hmm, can you check that you've set the vtkCPInputDataDescription grid > > through the SetGrid() method? You can add in something like "print("input > > is ", datadescription.GetInputDescriptionByName().GetGrid())" a > > couple of places in your Python script to see if there is actually a grid > > added there for that input. > > > > Best, > > Andy > > > > On Tue, Aug 15, 2017 at 3:30 PM, > wrote: > > > >> Without support of you and also Ben, i could not even reach to this > >> point. > >> Thanks again. At least, code runs now. I think that this is big > >> improvement. > >> > >> Anyway, both command is working as expected, > >> > >> > mpirun -np 4 pvbatch > >> > mpirun -np 4 pvbatch -sym > >> > >> I also tested allinputsgridwriter_new.py with CFullExample (and also > >> Fortran90FullExample) and it works without any problem. As I mentioned > >> before, CFullExample was also working before upgrading protobuf (still, > >> i > >> don't know why). So, it is not a good way to find the source of the > >> problem. > >> > >> --ufuk > >> > >> > >> > Hmm, how about making that Python code into a file and running it with > >> > both: > >> > mpirun -np 4 pvbatch > >> > mpirun -np 4 pvbatch -sym > >> > > >> > Just to verify, the allinputsgridwriter.py didn't work with any of the > >> > Catalyst examples (e.g. CFullExample), correct? > >> > > >> > I think this is going to be some issue where we continually bisect the > >> > problem space so I appreciate your patience on this. > >> > > >> > Best, > >> > Andy > >> > > >> > On Tue, Aug 15, 2017 at 2:49 PM, > >> wrote: > >> > > >> >> Hi, > >> >> > >> >> Yes. It works and produces same output. > >> >> > >> >> --ufuk > >> >> > >> >> > Hi Ufuk, > >> >> > > >> >> > It looks like the script line that is not working properly is: > >> >> > grid = > >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> > > >> >> > grid is set to None here for your build. Trying something simpler, > >> in > >> >> > pvpython can you try the following and let us know if it works: > >> >> > ============= > >> >> > from paraview.simple import * > >> >> > a = Wavelet() > >> >> > a.UpdatePipeline() > >> >> > b = a.GetClientSideObject() > >> >> > c = b.GetOutputDataObject(0) > >> >> > print c > >> >> > ============= > >> >> > > >> >> > > >> >> > > >> >> > It should give output like the following if it works: > >> >> > vtkImageData (0x4586a00) > >> >> > Debug: Off > >> >> > Modified Time: 204809 > >> >> > Reference Count: 2 > >> >> > Registered Events: (none) > >> >> > Information: 0x4586450 > >> >> > Data Released: False > >> >> > Global Release Data: Off > >> >> > UpdateTime: 204810 > >> >> > Field Data: > >> >> > Debug: Off > >> >> > Modified Time: 204775 > >> >> > Reference Count: 1 > >> >> > Registered Events: (none) > >> >> > Number Of Arrays: 0 > >> >> > Number Of Components: 0 > >> >> > Number Of Tuples: 0 > >> >> > Number Of Points: 9261 > >> >> > Number Of Cells: 8000 > >> >> > Cell Data: > >> >> > Debug: Off > >> >> > Modified Time: 204783 > >> >> > Reference Count: 1 > >> >> > Registered Events: > >> >> > Registered Observers: > >> >> > vtkObserver (0x4586550) > >> >> > Event: 33 > >> >> > EventName: ModifiedEvent > >> >> > Command: 0x45864a0 > >> >> > Priority: 0 > >> >> > Tag: 1 > >> >> > Number Of Arrays: 0 > >> >> > Number Of Components: 0 > >> >> > Number Of Tuples: 0 > >> >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > >> >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > >> >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > >> >> > Scalars: (none) > >> >> > Vectors: (none) > >> >> > Normals: (none) > >> >> > TCoords: (none) > >> >> > Tensors: (none) > >> >> > GlobalIds: (none) > >> >> > PedigreeIds: (none) > >> >> > EdgeFlag: (none) > >> >> > Point Data: > >> >> > Debug: Off > >> >> > Modified Time: 204809 > >> >> > Reference Count: 1 > >> >> > Registered Events: > >> >> > Registered Observers: > >> >> > vtkObserver (0x45864f0) > >> >> > Event: 33 > >> >> > EventName: ModifiedEvent > >> >> > Command: 0x45864a0 > >> >> > Priority: 0 > >> >> > Tag: 1 > >> >> > Number Of Arrays: 1 > >> >> > Array 0 name = RTData > >> >> > Number Of Components: 1 > >> >> > Number Of Tuples: 9261 > >> >> > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > >> >> > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > >> >> > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > >> >> > Scalars: > >> >> > Debug: Off > >> >> > Modified Time: 204809 > >> >> > Reference Count: 2 > >> >> > Registered Events: (none) > >> >> > Name: RTData > >> >> > Data type: float > >> >> > Size: 9261 > >> >> > MaxId: 9260 > >> >> > NumberOfComponents: 1 > >> >> > Information: 0 > >> >> > Name: RTData > >> >> > Number Of Components: 1 > >> >> > Number Of Tuples: 9261 > >> >> > Size: 9261 > >> >> > MaxId: 9260 > >> >> > LookupTable: (none) > >> >> > Vectors: (none) > >> >> > Normals: (none) > >> >> > TCoords: (none) > >> >> > Tensors: (none) > >> >> > GlobalIds: (none) > >> >> > PedigreeIds: (none) > >> >> > EdgeFlag: (none) > >> >> > Bounds: > >> >> > Xmin,Xmax: (-10, 10) > >> >> > Ymin,Ymax: (-10, 10) > >> >> > Zmin,Zmax: (-10, 10) > >> >> > Compute Time: 204875 > >> >> > Spacing: (1, 1, 1) > >> >> > Origin: (0, 0, 0) > >> >> > Dimensions: (21, 21, 21) > >> >> > Increments: (0, 0, 0) > >> >> > Extent: (-10, 10, -10, 10, -10, 10) > >> >> > > >> >> > > >> >> > > >> >> > On Tue, Aug 15, 2017 at 2:27 PM, > >> >> wrote: > >> >> > > >> >> >> Hi Andy, > >> >> >> > >> >> >> Thanks for your help and the script. Actually, I was adding input > >> >> names > >> >> >> to > >> >> >> the script by hand. Anyway, I tested your script and it gives > >> similar > >> >> >> error as follows, > >> >> >> > >> >> >> File > >> >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> >> >> egl/lib/site-packages/paraview/coprocessing.py", > >> >> >> line 305, in CreateProducer > >> >> >> if grid.IsA("vtkImageData") == True or \ > >> >> >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> File > >> >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> >> >> egl/lib/site-packages/paraview/coprocessing.py", > >> >> >> line 305, in CreateProducer > >> >> >> if grid.IsA("vtkImageData") == True or \ > >> >> >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> grid = > >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> File > >> >> >> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/ > >> >> >> egl/lib/site-packages/paraview/coprocessing.py", > >> >> >> line 305, in CreateProducer > >> >> >> if grid.IsA("vtkImageData") == True or \ > >> >> >> AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> > >> >> >> I'll tested whole environment once again with Intel compiler to > >> see > >> >> it > >> >> >> helps or not. Let me know if you have any other idea. > >> >> >> > >> >> >> Regards, > >> >> >> > >> >> >> --ufuk > >> >> >> > >> >> >> > >> >> >> > Hi Ufuk, > >> >> >> > > >> >> >> > For the allinputsgridwriter.py you currently need to manually > >> add > >> >> in > >> >> >> the > >> >> >> > inputs yourself (i.e. replace the "namedinputs = ['input']" line > >> >> with > >> >> >> the > >> >> >> > name of your inputs. That has caught me in the past as well so I > >> >> >> decided > >> >> >> > to > >> >> >> > fix that. Attached is my new version of that script where it > >> >> doesn't > >> >> >> > require you to specify the input names in case you want to try > >> this > >> >> >> new > >> >> >> > one > >> >> >> > instead. If you do, please let us know if that solves your > >> problem > >> >> or > >> >> >> not. > >> >> >> > > >> >> >> > Best, > >> >> >> > Andy > >> >> >> > > >> >> >> > > >> >> >> > On Tue, Aug 15, 2017 at 12:40 PM, Ben Boeckel > >> >> >> > >> >> >> > wrote: > >> >> >> > > >> >> >> >> On Tue, Aug 15, 2017 at 17:59:47 +0300, > >> >> >> u.utku.turuncoglu at be.itu.edu.tr > >> >> >> >> wrote: > >> >> >> >> > I solved the problem and i am able to run the simulation code > >> >> with > >> >> >> >> > Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with > >> >> newer > >> >> >> >> version > >> >> >> >> > of protobuf library (3.3.0) and compiling the model code with > >> >> this > >> >> >> >> version > >> >> >> >> > of PV (using gcc). > >> >> >> >> > > >> >> >> >> > Now, the problem is that the code gives following warnings > >> and > >> >> do > >> >> >> >> nothing > >> >> >> >> > with standard allinputsgridwriter.py script. Do you think > >> that > >> >> it > >> >> >> is > >> >> >> >> > related with protobuf library. The same setup is working > >> without > >> >> >> any > >> >> >> >> > problem in an other system using Intel compiler. > >> >> >> >> > >> >> >> >> It'd be better to try with one MPI process rather > >> >> than????????????????????????????????I count > >> >> >> 10 to > >> >> >> >> get > >> >> >> >> the error? Not sure what's up though, Andy? > >> >> >> >> > >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> >> > line 305, in CreateProducer > >> >> >> >> > grid = > >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> >> > grid = > >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > File > >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> >> > line 305, in CreateProducer > >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> >> > File > >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> >> > line 305, in CreateProducer > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> >> > grid = > >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> >> > File > >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> >> > line 305, in CreateProducer > >> >> >> >> > grid = > >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> >> > File > >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> >> > line 305, in CreateProducer > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> >> > [PERFLOG] :: COPROC 2 0.01404021SEC. > >> >> >> >> > Running COP Component: 2005-08-27T00:12:00 --> > >> >> 2005-08-27T00:18:00 > >> >> >> >> Time > >> >> >> >> > Step: 2 [ 720.00] > >> >> >> >> > ATM-TO-COP: redist mask [CROSS] to mask [CROSS] > >> >> >> >> > ATM-TO-COP: redist topo [CROSS] to topo [CROSS] > >> >> >> >> > AttributeError: 'NoneType' object has no attribute 'IsA' > >> >> >> >> > grid = > >> >> >> adaptorinput.GetClientSideObject().GetOutputDataObject(0) > >> >> >> >> > File > >> >> >> >> > "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl > >> >> >> >> /lib/site-packages/paraview/coprocessing.py", > >> >> >> >> > line 305, in CreateProducer > >> >> >> >> > if grid.IsA("vtkImageData") == True or \ > >> >> >> >> > >> >> >> >> --Ben > >> >> >> >> > >> >> >> > > >> >> >> > >> >> >> > >> >> > > >> >> > >> >> > >> >> > >> > > >> > >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 16 22:29:26 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 16 Aug 2017 22:29:26 -0400 Subject: [Paraview] =?utf-8?b?562U5aSNOiAgSGVscDogSG93IHRvIGdldCBtdWx0aSBz?= =?utf-8?q?creenshots_in_one_picture_from_Paraview?= In-Reply-To: References: Message-ID: Shudi, Is this what you're looking for: https://www.paraview.org/Wiki/Parameter_Study If so, you may want to look at Chapter 12 in the ParaView Users Guide[1]. It covers in the comparative views in more up-to-date details. Utkarsh [1] https://www.paraview.org/paraview-guide/ On Tue, Aug 15, 2017 at 7:10 PM, ? ?? wrote: > Hi Utkarsh, > > > Good evening. > > I am running a series of numerical data (.vtk file) in Paraview, which is > about 90s long. What I want are several screenshots from different time > period and conbine them into one picture with Paraview. For example, I want > the screenshots of 12s, 13s, 14s and 15s, and output these four screenshots > into one picture. I heard Paraview itself coiuld help me to do it but I > cannot find how. > > > I am not sure it this explaination makes sense? Do you have anyidea about > how to obtain this kind of screenshots? > > > Best regards > > Shudi Dong. > > > > ________________________________ > ???: Utkarsh Ayachit > ????: 2017?8?15? 2:46 > ???: ? ?? > ??: paraview at paraview.org > ??: Re: [Paraview] Help: How to get multi screenshots in one picture from > Paraview > > Shudi, > > Can you elaborate a little? I am not sure I understand what you want > to take multiple screenshots of. > > Utkarsh > > On Mon, Aug 14, 2017 at 4:58 PM, ? ?? wrote: >> Dear all, >> >> >> I am currently using paraview to analyse my .vtk data. I want to get some >> screenshots for my presentation. I have tried version 4.1 and 5.2 and I >> could save one screenshot per time. Does anyone know how can I get multi >> screenshots in one picture with paraview itself? I do not want to use >> python as I have no experience with it. I would appreciate your reply and >> help. >> >> >> Many thanks >> >> Shudi Dong >> >> >> _______________________________________________ >> 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 > ParaView - KitwarePublic > paraview.org > ParaView is an open-source, multi-platform application designed to visualize > data sets of varying sizes from small to very large. The goals of the > ParaView project ... > >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > ParaView Info Page - Kitware > public.kitware.com > To see the collection of prior postings to the list, visit the ParaView > Archives. Using ParaView: To post a message to all the list members, send > ... > >> From dave.demarle at kitware.com Thu Aug 17 09:35:02 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 17 Aug 2017 09:35:02 -0400 Subject: [Paraview] Is anyone using the Extra Headlight in ParaView? Message-ID: By default, Paraview illuminates the scene with a vtkLightKit . You can however add an extra headlight. I am about to add a more general capability which lets you add any number and any kind of light, including the headlight. When I do that, the semi-hardcoded extra headlight becomes redundant. I would like to remove it to streamline both the code and the UI. Are there any objections to me doing that? David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 17 09:57:16 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 17 Aug 2017 09:57:16 -0400 Subject: [Paraview] =?utf-8?b?562U5aSNOiDnrZTlpI06ICBIZWxwOiBIb3cgdG8gZ2V0?= =?utf-8?q?_multi_screenshots_in_one_picture_from_Paraview?= In-Reply-To: References: Message-ID: Shudi, (please cc the paraview mailing list in your communication so others can participate in the conversation as well) Comparative View is still the easiest way to get a pretty similar viz. On Thu, Aug 17, 2017 at 7:03 AM, ? ?? wrote: > Hi Utkarsh, > > > I have had a quick look of the user guide. Yes, what I want is a similar > thing with what you sent me but not same. I will have a try with the > Chapter 12. > > A sample screen shots has been attached in this email, which is exactly > what I want to get. Do you know how to get that screenshots with Paraview > itself? > > > > > Many thanks, > > Shudi Dong. > > ------------------------------ > *???:* Utkarsh Ayachit > *????:* 2017?8?17? 2:29 > *???:* ? ??; ParaView > *??:* Re: ??: [Paraview] Help: How to get multi screenshots in one > picture from Paraview > > Shudi, > > Is this what you're looking for: > https://www.paraview.org/Wiki/Parameter_Study > > Parameter Study - KitwarePublic - ParaView > > www.paraview.org > Parameter study refers to creating visualizations in grid with one or more > parameters changing across each view in the grid so that users can visually > compare the ... > > > If so, you may want to look at Chapter 12 in the ParaView Users > Guide[1]. It covers in the comparative views in more up-to-date > details. > > Utkarsh > > [1] https://www.paraview.org/paraview-guide/ > The ParaView Guide | ParaView > www.paraview.org > Get the ParaView Guide! The ParaView Guide is the official user?s manual > and reference guide for ParaView. There are several ways of obtaining the > latest version of ... > > > On Tue, Aug 15, 2017 at 7:10 PM, ? ?? wrote: > > Hi Utkarsh, > > > > > > Good evening. > > > > I am running a series of numerical data (.vtk file) in Paraview, which is > > about 90s long. What I want are several screenshots from different time > > period and conbine them into one picture with Paraview. For example, I > want > > the screenshots of 12s, 13s, 14s and 15s, and output these four > screenshots > > into one picture. I heard Paraview itself coiuld help me to do it but I > > cannot find how. > > > > > > I am not sure it this explaination makes sense? Do you have anyidea about > > how to obtain this kind of screenshots? > > > > > > Best regards > > > > Shudi Dong. > > > > > > > > ________________________________ > > ???: Utkarsh Ayachit > > ????: 2017?8?15? 2:46 > > ???: ? ?? > > ??: paraview at paraview.org > > ??: Re: [Paraview] Help: How to get multi screenshots in one picture from > > Paraview > > > > Shudi, > > > > Can you elaborate a little? I am not sure I understand what you want > > to take multiple screenshots of. > > > > Utkarsh > > > > On Mon, Aug 14, 2017 at 4:58 PM, ? ?? wrote: > >> Dear all, > >> > >> > >> I am currently using paraview to analyse my .vtk data. I want to get > some > >> screenshots for my presentation. I have tried version 4.1 and 5.2 and I > >> could save one screenshot per time. Does anyone know how can I get multi > >> screenshots in one picture with paraview itself? I do not want to use > >> python as I have no experience with it. I would appreciate your reply > and > >> help. > >> > >> > >> Many thanks > >> > >> Shudi Dong > >> > >> > >> _______________________________________________ > >> 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 > ParaView - KitwarePublic > paraview.org > ParaView is an open-source, multi-platform application designed to > visualize data sets of varying sizes from small to very large. The goals of > the ParaView project ... > > > ParaView - KitwarePublic > > paraview.org > > ParaView is an open-source, multi-platform application designed to > visualize > > data sets of varying sizes from small to very large. The goals of the > > ParaView project ... > > > >> > >> Search the list archives at: http://markmail.org/search/?q=ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > ParaView Info Page - Kitware > > public.kitware.com > To see the collection of prior postings to the list, visit the ParaView > Archives. Using ParaView: To post a message to all the list members, send > ... > > > ParaView Info Page - Kitware > > public.kitware.com > > To see the collection of prior postings to the list, visit the ParaView > > Archives. Using ParaView: To post a message to all the list members, send > > ... > > > >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SPH screenshots1.png Type: image/png Size: 256607 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ParaView 5.4.1-RC4 64-bit_351.png Type: image/png Size: 139967 bytes Desc: not available URL: From ganplankr at hotmail.com Thu Aug 17 12:35:34 2017 From: ganplankr at hotmail.com (=?gb2312?B?tq0gyua1zw==?=) Date: Thu, 17 Aug 2017 16:35:34 +0000 Subject: [Paraview] =?gb2312?b?tPC4tDogtPC4tDogtPC4tDogIEhlbHA6IEhvdyB0?= =?gb2312?b?byBnZXQgbXVsdGkgc2NyZWVuc2hvdHMgaW4gb25lIHBpY3R1cmUgZnJvbSBQ?= =?gb2312?b?YXJhdmlldw==?= In-Reply-To: References: , Message-ID: Hi Utkarsh Sorry, I forgot to reply to all. Thank you, your picture look great! I will try to follow the user guide. Best wishes, Shudi Dong. ________________________________ ???: Utkarsh Ayachit ????: 2017?8?17? 13:57 ???: ? ??; ParaView ??: Re: ??: ??: [Paraview] Help: How to get multi screenshots in one picture from Paraview Shudi, (please cc the paraview mailing list in your communication so others can participate in the conversation as well) Comparative View is still the easiest way to get a pretty similar viz. On Thu, Aug 17, 2017 at 7:03 AM, ? ?? > wrote: Hi Utkarsh, I have had a quick look of the user guide. Yes, what I want is a similar thing with what you sent me but not same. I will have a try with the Chapter 12. A sample screen shots has been attached in this email, which is exactly what I want to get. Do you know how to get that screenshots with Paraview itself? [cid:b68a98b6-f0f2-41da-961e-b04560d40e91] Many thanks, Shudi Dong. ________________________________ ???: Utkarsh Ayachit > ????: 2017?8?17? 2:29 ???: ? ??; ParaView ??: Re: ??: [Paraview] Help: How to get multi screenshots in one picture from Paraview Shudi, Is this what you're looking for: https://www.paraview.org/Wiki/Parameter_Study [https://www.paraview.org/Wiki/images/5/5e/ParaViewComparativeView.jpg] Parameter Study - KitwarePublic - ParaView www.paraview.org Parameter study refers to creating visualizations in grid with one or more parameters changing across each view in the grid so that users can visually compare the ... If so, you may want to look at Chapter 12 in the ParaView Users Guide[1]. It covers in the comparative views in more up-to-date details. Utkarsh [1] https://www.paraview.org/paraview-guide/ The ParaView Guide | ParaView www.paraview.org Get the ParaView Guide! The ParaView Guide is the official user?s manual and reference guide for ParaView. There are several ways of obtaining the latest version of ... On Tue, Aug 15, 2017 at 7:10 PM, ? ?? > wrote: > Hi Utkarsh, > > > Good evening. > > I am running a series of numerical data (.vtk file) in Paraview, which is > about 90s long. What I want are several screenshots from different time > period and conbine them into one picture with Paraview. For example, I want > the screenshots of 12s, 13s, 14s and 15s, and output these four screenshots > into one picture. I heard Paraview itself coiuld help me to do it but I > cannot find how. > > > I am not sure it this explaination makes sense? Do you have anyidea about > how to obtain this kind of screenshots? > > > Best regards > > Shudi Dong. > > > > ________________________________ > ???: Utkarsh Ayachit > > ????: 2017?8?15? 2:46 > ???: ? ?? > ??: paraview at paraview.org > ??: Re: [Paraview] Help: How to get multi screenshots in one picture from > Paraview > > Shudi, > > Can you elaborate a little? I am not sure I understand what you want > to take multiple screenshots of. > > Utkarsh > > On Mon, Aug 14, 2017 at 4:58 PM, ? ?? > wrote: >> Dear all, >> >> >> I am currently using paraview to analyse my .vtk data. I want to get some >> screenshots for my presentation. I have tried version 4.1 and 5.2 and I >> could save one screenshot per time. Does anyone know how can I get multi >> screenshots in one picture with paraview itself? I do not want to use >> python as I have no experience with it. I would appreciate your reply and >> help. >> >> >> Many thanks >> >> Shudi Dong >> >> >> _______________________________________________ >> 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 ParaView - KitwarePublic paraview.org ParaView is an open-source, multi-platform application designed to visualize data sets of varying sizes from small to very large. The goals of the ParaView project ... > ParaView - KitwarePublic > paraview.org > ParaView is an open-source, multi-platform application designed to visualize > data sets of varying sizes from small to very large. The goals of the > ParaView project ... > >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview ParaView Info Page - Kitware public.kitware.com To see the collection of prior postings to the list, visit the ParaView Archives. Using ParaView: To post a message to all the list members, send ... > ParaView Info Page - Kitware > public.kitware.com > To see the collection of prior postings to the list, visit the ParaView > Archives. Using ParaView: To post a message to all the list members, send > ... > >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SPH screenshots1.png Type: image/png Size: 256607 bytes Desc: SPH screenshots1.png URL: From wascott at sandia.gov Thu Aug 17 13:16:15 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 17 Aug 2017 17:16:15 +0000 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: References: Message-ID: No objection here. Only thought I have is that the lights may be setup by default slightly differently for 2d and 3d. We may want a ?headlight? for 2d. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: Thursday, August 17, 2017 7:35 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in ParaView? By default, Paraview illuminates the scene with a vtkLightKit. You can however add an extra headlight. I am about to add a more general capability which lets you add any number and any kind of light, including the headlight. When I do that, the semi-hardcoded extra headlight becomes redundant. I would like to remove it to streamline both the code and the UI. Are there any objections to me doing that? David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From timothy.dunn at colorado.edu Thu Aug 17 13:34:03 2017 From: timothy.dunn at colorado.edu (Timothy Dwight Dunn) Date: Thu, 17 Aug 2017 11:34:03 -0600 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: References: Message-ID: Actually I was just talking about this in a Paraview tutorial I gave this morning at a conference. I would prefer to kill the hard coded light allowing the ability to add in general lights that the user can design and setup. In addition to save a conf out for the setup to be used as a default. I normally set things up in Paraview export what I need pop them in a CG app so that I can light them with so much more control but this is often difficult at best to impossible as the norm due to complexity of the scene. If we could get more and better light control, especially with Osprey then I'd be a very happy camper. Just to make really difficult make sure the lights interact with objects/layers as desired by the user, including volumeterics. This is a common thing to do in CG apps. Light objects A,B,C with light rig1, object D,E with light rig2 and object F with light rig3 .... The easiest way to do this is to have a panel for each light, or for paraview the gui controls with a check box list for each available layer which can activate/deactivate each light per layer. OK this makes sense in my head but I don't think I'm explaining it well do to conference exhaustion. If desired I can do a mock up gui layout image of what I'm trying to describe. Tim Dunn Scientific\Data Visualization & Visual Analytics for; CIRES - Earth Lab-Analytics Hub CU Research Computing (CURC) Center for Research Data and Digital Scholarship (CRDDS) tdunn at colorado.edu On Thu, Aug 17, 2017 at 11:16 AM, Scott, W Alan wrote: > No objection here. Only thought I have is that the lights may be setup by > default slightly differently for 2d and 3d. We may want a ?headlight? for > 2d. > > > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *David > E DeMarle > *Sent:* Thursday, August 17, 2017 7:35 AM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in > ParaView? > > > > By default, Paraview illuminates the scene with a vtkLightKit > . You can however > add an extra headlight. I am about to add a more general capability which > lets you add any number and any kind of light, including the headlight. > When I do that, the semi-hardcoded extra headlight becomes redundant. I > would like to remove it to streamline both the code and the UI. > > Are there any objections to me doing that? > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Aug 17 13:37:23 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 17 Aug 2017 13:37:23 -0400 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: References: Message-ID: Yes please do provide a mockup when you get a chance. I think I see your idea but a picture is worth a million lines of code. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Aug 17, 2017 at 1:34 PM, Timothy Dwight Dunn < timothy.dunn at colorado.edu> wrote: > Actually I was just talking about this in a Paraview tutorial I gave this > morning at a conference. I would prefer to kill the hard coded light > allowing the ability to add in general lights that the user can design and > setup. In addition to save a conf out for the setup to be used as a > default. I normally set things up in Paraview export what I need pop them > in a CG app so that I can light them with so much more control but this is > often difficult at best to impossible as the norm due to complexity of the > scene. If we could get more and better light control, especially with > Osprey then I'd be a very happy camper. > > Just to make really difficult make sure the lights interact with > objects/layers as desired by the user, including volumeterics. This is a > common thing to do in CG apps. Light objects A,B,C with light rig1, object > D,E with light rig2 and object F with light rig3 .... The easiest way to do > this is to have a panel for each light, or for paraview the gui controls > with a check box list for each available layer which can > activate/deactivate each light per layer. OK this makes sense in my head > but I don't think I'm explaining it well do to conference exhaustion. If > desired I can do a mock up gui layout image of what I'm trying to describe. > > > Tim Dunn > Scientific\Data Visualization & Visual Analytics for; > CIRES - Earth Lab-Analytics Hub > CU Research Computing (CURC) > Center for Research Data and Digital Scholarship (CRDDS) > tdunn at colorado.edu > > On Thu, Aug 17, 2017 at 11:16 AM, Scott, W Alan > wrote: > >> No objection here. Only thought I have is that the lights may be setup >> by default slightly differently for 2d and 3d. We may want a ?headlight? >> for 2d. >> >> >> >> >> >> Alan >> >> >> >> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *David >> E DeMarle >> *Sent:* Thursday, August 17, 2017 7:35 AM >> *To:* paraview at paraview.org >> *Subject:* [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in >> ParaView? >> >> >> >> By default, Paraview illuminates the scene with a vtkLightKit >> . You can however >> add an extra headlight. I am about to add a more general capability which >> lets you add any number and any kind of light, including the headlight. >> When I do that, the semi-hardcoded extra headlight becomes redundant. I >> would like to remove it to streamline both the code and the UI. >> >> Are there any objections to me doing that? >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 <(518)%20881-4909> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Aug 17 13:40:04 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 17 Aug 2017 17:40:04 +0000 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: References: Message-ID: <55a66aed0a3d42da98ce2923ed6e2154@ES01AMSNLNT.srn.sandia.gov> I believe this is the bug Dave is working on: https://gitlab.kitware.com/paraview/paraview/issues/13963. Dave ? am I correct? Alan From: Timothy Dwight Dunn [mailto:timothy.dunn at colorado.edu] Sent: Thursday, August 17, 2017 11:34 AM To: Scott, W Alan Cc: DeMarle, David E. (External Contacts) ; paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? Actually I was just talking about this in a Paraview tutorial I gave this morning at a conference. I would prefer to kill the hard coded light allowing the ability to add in general lights that the user can design and setup. In addition to save a conf out for the setup to be used as a default. I normally set things up in Paraview export what I need pop them in a CG app so that I can light them with so much more control but this is often difficult at best to impossible as the norm due to complexity of the scene. If we could get more and better light control, especially with Osprey then I'd be a very happy camper. Just to make really difficult make sure the lights interact with objects/layers as desired by the user, including volumeterics. This is a common thing to do in CG apps. Light objects A,B,C with light rig1, object D,E with light rig2 and object F with light rig3 .... The easiest way to do this is to have a panel for each light, or for paraview the gui controls with a check box list for each available layer which can activate/deactivate each light per layer. OK this makes sense in my head but I don't think I'm explaining it well do to conference exhaustion. If desired I can do a mock up gui layout image of what I'm trying to describe. Tim Dunn Scientific\Data Visualization & Visual Analytics for; CIRES - Earth Lab-Analytics Hub CU Research Computing (CURC) Center for Research Data and Digital Scholarship (CRDDS) tdunn at colorado.edu On Thu, Aug 17, 2017 at 11:16 AM, Scott, W Alan > wrote: No objection here. Only thought I have is that the lights may be setup by default slightly differently for 2d and 3d. We may want a ?headlight? for 2d. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: Thursday, August 17, 2017 7:35 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in ParaView? By default, Paraview illuminates the scene with a vtkLightKit. You can however add an extra headlight. I am about to add a more general capability which lets you add any number and any kind of light, including the headlight. When I do that, the semi-hardcoded extra headlight becomes redundant. I would like to remove it to streamline both the code and the UI. Are there any objections to me doing that? David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Aug 17 13:42:18 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 17 Aug 2017 13:42:18 -0400 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: <55a66aed0a3d42da98ce2923ed6e2154@ES01AMSNLNT.srn.sandia.gov> References: <55a66aed0a3d42da98ce2923ed6e2154@ES01AMSNLNT.srn.sandia.gov> Message-ID: I wasn't aware of that bug. Thanks Alan we will try steer towards that as well. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Aug 17, 2017 at 1:40 PM, Scott, W Alan wrote: > I believe this is the bug Dave is working on: https://gitlab.kitware.com/ > paraview/paraview/issues/13963. Dave ? am I correct? > > > > Alan > > > > *From:* Timothy Dwight Dunn [mailto:timothy.dunn at colorado.edu] > *Sent:* Thursday, August 17, 2017 11:34 AM > *To:* Scott, W Alan > *Cc:* DeMarle, David E. (External Contacts) ; > paraview at paraview.org > *Subject:* Re: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight > in ParaView? > > > > Actually I was just talking about this in a Paraview tutorial I gave this > morning at a conference. I would prefer to kill the hard coded light > allowing the ability to add in general lights that the user can design and > setup. In addition to save a conf out for the setup to be used as a > default. I normally set things up in Paraview export what I need pop them > in a CG app so that I can light them with so much more control but this is > often difficult at best to impossible as the norm due to complexity of the > scene. If we could get more and better light control, especially with > Osprey then I'd be a very happy camper. > > > Just to make really difficult make sure the lights interact with > objects/layers as desired by the user, including volumeterics. This is a > common thing to do in CG apps. Light objects A,B,C with light rig1, object > D,E with light rig2 and object F with light rig3 .... The easiest way to do > this is to have a panel for each light, or for paraview the gui controls > with a check box list for each available layer which can > activate/deactivate each light per layer. OK this makes sense in my head > but I don't think I'm explaining it well do to conference exhaustion. If > desired I can do a mock up gui layout image of what I'm trying to describe. > > > Tim Dunn > Scientific\Data Visualization & Visual Analytics for; > CIRES - Earth Lab-Analytics Hub > CU Research Computing (CURC) > > Center for Research Data and Digital Scholarship (CRDDS) > > tdunn at colorado.edu > > > > On Thu, Aug 17, 2017 at 11:16 AM, Scott, W Alan > wrote: > > No objection here. Only thought I have is that the lights may be setup by > default slightly differently for 2d and 3d. We may want a ?headlight? for > 2d. > > > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *David > E DeMarle > *Sent:* Thursday, August 17, 2017 7:35 AM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in > ParaView? > > > > By default, Paraview illuminates the scene with a vtkLightKit > . You can however > add an extra headlight. I am about to add a more general capability which > lets you add any number and any kind of light, including the headlight. > When I do that, the semi-hardcoded extra headlight becomes redundant. I > would like to remove it to streamline both the code and the UI. > > Are there any objections to me doing that? > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Aug 17 13:51:14 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 17 Aug 2017 17:51:14 +0000 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: References: Message-ID: <80417c1b6b5642609b73e7a06c141901@ES08AMSNLNT.srn.sandia.gov> The use case Alan brings up is captured in bug 17236: https://gitlab.kitware.com/paraview/paraview/issues/17236. Until that bug is fixed, I would argue strenuously against disabling the headlight. The implementation of the bug fix may or may not require the headlight to stick around (depending on how it is implemented). I don?t personally have any other use case for the headlight, but it is a convenient way to get a bright light shining directly on the view. It?s valuable to quickly illuminate an object where the shading has made the colors murky. Is there a compelling reason to get rid of it? It?s tucked away in an innocuous corner of the GUI. -Ken From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, August 17, 2017 11:16 AM To: DeMarle, David E. (External Contacts) ; paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? No objection here. Only thought I have is that the lights may be setup by default slightly differently for 2d and 3d. We may want a ?headlight? for 2d. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of David E DeMarle Sent: Thursday, August 17, 2017 7:35 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in ParaView? By default, Paraview illuminates the scene with a vtkLightKit. You can however add an extra headlight. I am about to add a more general capability which lets you add any number and any kind of light, including the headlight. When I do that, the semi-hardcoded extra headlight becomes redundant. I would like to remove it to streamline both the code and the UI. Are there any objections to me doing that? David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Aug 17 13:56:03 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 17 Aug 2017 13:56:03 -0400 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: <80417c1b6b5642609b73e7a06c141901@ES08AMSNLNT.srn.sandia.gov> References: <80417c1b6b5642609b73e7a06c141901@ES08AMSNLNT.srn.sandia.gov> Message-ID: The only reason to "get rid of it" is because something new is coming that is a superset of its functionality. From a user perspective it would be instead of "turn on the extra headlight" it would be "add light and select headlight as its type". Afterward they would behave exactly the same. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Aug 17, 2017 at 1:51 PM, Moreland, Kenneth wrote: > The use case Alan brings up is captured in bug 17236: > https://gitlab.kitware.com/paraview/paraview/issues/17236. Until that bug > is fixed, I would argue strenuously against disabling the headlight. The > implementation of the bug fix may or may not require the headlight to stick > around (depending on how it is implemented). > > > > I don?t personally have any other use case for the headlight, but it is a > convenient way to get a bright light shining directly on the view. It?s > valuable to quickly illuminate an object where the shading has made the > colors murky. Is there a compelling reason to get rid of it? It?s tucked > away in an innocuous corner of the GUI. > > > > -Ken > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Scott, > W Alan > *Sent:* Thursday, August 17, 2017 11:16 AM > *To:* DeMarle, David E. (External Contacts) ; > paraview at paraview.org > *Subject:* Re: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight > in ParaView? > > > > No objection here. Only thought I have is that the lights may be setup by > default slightly differently for 2d and 3d. We may want a ?headlight? for > 2d. > > > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org > ] *On Behalf Of *David E DeMarle > *Sent:* Thursday, August 17, 2017 7:35 AM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in > ParaView? > > > > By default, Paraview illuminates the scene with a vtkLightKit > . You can however > add an extra headlight. I am about to add a more general capability which > lets you add any number and any kind of light, including the headlight. > When I do that, the semi-hardcoded extra headlight becomes redundant. I > would like to remove it to streamline both the code and the UI. > > Are there any objections to me doing that? > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From timothy.dunn at colorado.edu Thu Aug 17 21:18:28 2017 From: timothy.dunn at colorado.edu (Timothy Dwight Dunn) Date: Thu, 17 Aug 2017 19:18:28 -0600 Subject: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView? In-Reply-To: References: <80417c1b6b5642609b73e7a06c141901@ES08AMSNLNT.srn.sandia.gov> Message-ID: Just got home and have a ton of Emails to respond to and then gone till Tuesday (Wyoming bound for the eclipse). I'll draft up what I'm thing early next week. Tim Dunn Scientific\Data Visualization & Visual Analytics for; CIRES - Earth Lab-Analytics Hub CU Research Computing (CURC) Center for Research Data and Digital Scholarship (CRDDS) tdunn at colorado.edu On Thu, Aug 17, 2017 at 11:56 AM, David E DeMarle wrote: > The only reason to "get rid of it" is because something new is coming that > is a superset of its functionality. From a user perspective it would be > instead of "turn on the extra headlight" it would be "add light and select > headlight as its type". Afterward they would behave exactly the same. > > > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > On Thu, Aug 17, 2017 at 1:51 PM, Moreland, Kenneth > wrote: > >> The use case Alan brings up is captured in bug 17236: >> https://gitlab.kitware.com/paraview/paraview/issues/17236. Until that >> bug is fixed, I would argue strenuously against disabling the headlight. >> The implementation of the bug fix may or may not require the headlight to >> stick around (depending on how it is implemented). >> >> >> >> I don?t personally have any other use case for the headlight, but it is a >> convenient way to get a bright light shining directly on the view. It?s >> valuable to quickly illuminate an object where the shading has made the >> colors murky. Is there a compelling reason to get rid of it? It?s tucked >> away in an innocuous corner of the GUI. >> >> >> >> -Ken >> >> >> >> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Scott, >> W Alan >> *Sent:* Thursday, August 17, 2017 11:16 AM >> *To:* DeMarle, David E. (External Contacts) ; >> paraview at paraview.org >> *Subject:* Re: [Paraview] [EXTERNAL] Is anyone using the Extra Headlight >> in ParaView? >> >> >> >> No objection here. Only thought I have is that the lights may be setup >> by default slightly differently for 2d and 3d. We may want a ?headlight? >> for 2d. >> >> >> >> >> >> Alan >> >> >> >> *From:* ParaView [mailto:paraview-bounces at paraview.org >> ] *On Behalf Of *David E DeMarle >> *Sent:* Thursday, August 17, 2017 7:35 AM >> *To:* paraview at paraview.org >> *Subject:* [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in >> ParaView? >> >> >> >> By default, Paraview illuminates the scene with a vtkLightKit >> . You can however >> add an extra headlight. I am about to add a more general capability which >> lets you add any number and any kind of light, including the headlight. >> When I do that, the semi-hardcoded extra headlight becomes redundant. I >> would like to remove it to streamline both the code and the UI. >> >> Are there any objections to me doing that? >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 <(518)%20881-4909> >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hongchao.wang2013 at gmail.com Thu Aug 17 23:36:40 2017 From: hongchao.wang2013 at gmail.com (HongchaoWang) Date: Fri, 18 Aug 2017 11:36:40 +0800 Subject: [Paraview] Interpolation error in paraview Message-ID: <006801d317d3$368572d0$a3905870$@gmail.com> I'm just wondering what interpolation scheme is used for data manipulation in Paraview? I'm using Paraview 5.2.0. I want to measure the velocity very close to a wall surface so that I can obtain the wall shear stress. However, I found the velocity measured using Paraview is different from the results I have obtained using the postprocessing tool in OpenFoam. Compared with the analytical solution which is already known in my case, Paraview result is worse and is 10% smaller than the analytical solution while the OpenFoam result agrees with the analytical solution very well. With finer mesh, the difference between the Paraview and OpenFoam results becomes smaller, so I believe the difference is due to the interpolation error. Anyone who has experience on this problem? Is there any advanced interpolation scheme that I can use in Paraview? Many thanks, Wilson -------------- next part -------------- An HTML attachment was scrubbed... URL: From hongchao.wang2013 at gmail.com Sat Aug 19 02:13:28 2017 From: hongchao.wang2013 at gmail.com (HongchaoWang) Date: Sat, 19 Aug 2017 14:13:28 +0800 Subject: [Paraview] Interpolation error in paraview Message-ID: <011f01d318b2$489e8530$d9db8f90$@gmail.com> Hi, Besides the question below, is the filter "point interpolation" is used for more advanced interpolation scheme? Can I use this filter to obtain more accurate interpolation result? Anyone who could explain this filter to me? I just couldn't find any tutorial on this filter. Many thanks, Wilson From: HongchaoWang [mailto:hongchao.wang2013 at gmail.com] Sent: Friday, 18 August 2017 11:37 AM To: 'paraview at paraview.org' Subject: Interpolation error in paraview I'm just wondering what interpolation scheme is used for data manipulation in Paraview? I'm using Paraview 5.2.0. I want to measure the velocity very close to a wall surface so that I can obtain the wall shear stress. However, I found the velocity measured using Paraview is different from the results I have obtained using the postprocessing tool in OpenFoam. Compared with the analytical solution which is already known in my case, Paraview result is worse and is 10% smaller than the analytical solution while the OpenFoam result agrees with the analytical solution very well. With finer mesh, the difference between the Paraview and OpenFoam results becomes smaller, so I believe the difference is due to the interpolation error. Anyone who has experience on this problem? Is there any advanced interpolation scheme that I can use in Paraview? Many thanks, Wilson -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Aug 21 11:04:16 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 21 Aug 2017 11:04:16 -0400 Subject: [Paraview] ParaView 5.4.1 is now available for download Message-ID: The ParaView development team is pleased to announce that ParaView 5.4.1 is available for download. Binaries and source code are available from www.paraview.org/download Note that the ParaView Download page has been updated with an improved layout that makes downloading ParaView easier. The ParaView 5.4.1 bug fix release addresses a number of problems in 5.4.0, including: * The black render window observed on some systems when FXAA was enabled or an object's opacity was less than 1 has been fixed. * Field output for cells with non-straight edges has been corrected. * Derivatives for quadratic triangles are now computed correctly. * A bug that occurred when generating a Catalyst script with no images output has been fixed. * A problem with writing animations as AVIs was fixed. * Logic in the CGNS reader was updated to correctly read all solution nodes for each centering type when FlowSolutionPointers are missing. * Fixed crash in CGNS reader when moving forward in time. * Fixed problem with long-running animations not advancing past a certain number of time steps. * Resolved issue where changing one file path in the state file loader "Choose File Names" dialog also changed the file paths of other files with the same type. * Addressed problem with enumerated property dependencies in ParaViewWeb. * Added ability to change the font size in the ParaView user interface. * Fixed BoxLib3D file reader. * State files now properly support files with relative paths. * Removed inappropriate scalar bar scaling when saving large screen shots. * A bug in the color mapping that in some cases incorrectly mapped some data values to the above-range color was fixed. * OSPRay can now be compiled in Cray programming environments and for the first time has support for Intel Skylake processors. * Added lower limit to how small the GUI font size can be. * Addressed issue affecting layouts when loading a state file from the Python console. Thanks! -- Cory Quammen Staff R&D Engineer Kitware, Inc. From martin34148 at gmail.com Tue Aug 22 05:36:50 2017 From: martin34148 at gmail.com (M P) Date: Tue, 22 Aug 2017 11:36:50 +0200 Subject: [Paraview] Point Dataset Interpolator - EllipsoidalGaussianKernel Message-ID: Hello all, I am trying to setup this filter to sample a point volume dataset along a defined spline curve. The ideal "kernel" for my purpose would be a short cylinder with some relatively big radius and constant weight in the whole volume of the cylinder (the axis of this cylinder should follow the direction vector of the spline). From all the kernels available for this filter the "EllipsoidalGaussianKernel" seems to be the most suitable. But I have a problem understanding what some of the parameters exactly mean. ------ "Use Normals": Specify whether vector values should be used to affect the shape of the Gaussian distribution. ?: What Normals vector values are meant here? Is it the normal to the spline or some vector from dataset? And how is then the kernel oriented if this option is not used? ------ "Use Scalars" ?: Similar question, what scalar is meant here and how is the weighting done? But I guess this is not important for my use case ------ "Sharpness": Specify the sharpness (i.e., falloff) of the Gaussian. By default Sharpness=2. As the sharpness increases the effects of distant points are reduced. ?: I would like all the dataset points have the same weight - so I guess I need maximum sharpness (like 20) - but this parameter help comment indicate that it works the opposite way - higher value means lower weight of distant points ------ "Eccentricity": Specify the eccentricity of the ellipsoidal Gaussian. A value=1.0 produces a spherical distribution. Values less than 1 produce a needle like distribution (in the direction of the normal); values greater than 1 produce a pancake like distribution (orthogonal to the normal. ?: Here I am confused by the word "normal", should I understand that it actually means direction vector? ------ Is there some paper or book where this parameters are exactly explained, or could someone point me to a source code where this is implemented (and hopefully it would be possible to understand from there)? Best regards, Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillermo180395 at gmail.com Tue Aug 22 06:04:14 2017 From: guillermo180395 at gmail.com (=?UTF-8?Q?Guillermo_Su=C3=A1rez?=) Date: Tue, 22 Aug 2017 09:04:14 -0100 Subject: [Paraview] paraview.simple Message-ID: Dear all, Yesterday I installed paraview v5.3 using the binaries from the website on my Linux (ubuntu) OS. The steps followed are (they my influence on the final result): 1. Download the binaries from http://www.paraview.org. For me this results in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz 2. Extract and copy them: tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz sudo emacs ~/.bashrc 3. then insert the following line, save & close export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ Then I created a symbolic link: sudo ln -s /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview /usr/bin/paraview sudo ln -s /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ /usr/lib/paraview-5.3 Before installing paraview from the binaries files I was using the version from Ubuntu repositories (paraview version 5.0 [I think]). Also I was using a python script which uses paraview to take some snapshoots and it worked really well. The problem is that now, when I want to use this python script, it reports this message: "from paraview.simple import * ImportError: No module named paraview.simple" I have made some searches on the Internet and I found a web page about this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup I have copied and pasted those sentences on my .bashrc file, restarted the computer but it still does not work. Could you please help me? Best regards, Guillermo S. -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin34148 at gmail.com Tue Aug 22 08:28:04 2017 From: martin34148 at gmail.com (M P) Date: Tue, 22 Aug 2017 14:28:04 +0200 Subject: [Paraview] Point Dataset Interpolator - EllipsoidalGaussianKernel In-Reply-To: References: Message-ID: ... reading it again, the "Sharpness" parameter is clear - for my purpose of uniform weights it should be as low as possible. But some exact equation would still be useful. On Tue, Aug 22, 2017 at 11:36 AM, M P wrote: > Hello all, > > I am trying to setup this filter to sample a point volume dataset along a > defined spline curve. The ideal "kernel" for my purpose would be a short > cylinder with some relatively big radius and constant weight in the whole > volume of the cylinder (the axis of this cylinder should follow the > direction vector of the spline). From all the kernels available for this > filter the "EllipsoidalGaussianKernel" seems to be the most suitable. But I > have a problem understanding what some of the parameters exactly mean. > > ------ > "Use Normals": Specify whether vector values should be used to affect the > shape of the Gaussian distribution. > > ?: What Normals vector values are meant here? Is it the normal to the > spline or some vector from dataset? And how is then the kernel oriented if > this option is not used? > ------ > "Use Scalars" > > ?: Similar question, what scalar is meant here and how is the weighting > done? But I guess this is not important for my use case > ------ > "Sharpness": Specify the sharpness (i.e., falloff) of the Gaussian. By > default Sharpness=2. As the sharpness increases the effects of distant > points are reduced. > > ?: I would like all the dataset points have the same weight - so I guess I > need maximum sharpness (like 20) - but this parameter help comment indicate > that it works the opposite way - higher value means lower weight of distant > points > ------ > "Eccentricity": Specify the eccentricity of the ellipsoidal Gaussian. A > value=1.0 produces a spherical distribution. Values less than 1 produce a > needle like distribution (in the direction of the normal); values greater > than 1 produce a pancake like distribution (orthogonal to the normal. > > ?: Here I am confused by the word "normal", should I understand that it > actually means direction vector? > ------ > > Is there some paper or book where this parameters are exactly explained, > or could someone point me to a source code where this is implemented (and > hopefully it would be possible to understand from there)? > > Best regards, > > Martin > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 22 09:31:32 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 22 Aug 2017 09:31:32 -0400 Subject: [Paraview] paraview.simple In-Reply-To: References: Message-ID: Hi Guillermo, I think the content in that wiki page is outdated. Try setting PYTHONPATH to the following in your .bashrc export PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5- OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages See if that works and let us know, Cory On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez wrote: > Dear all, > > Yesterday I installed paraview v5.3 using the binaries from the website on > my Linux (ubuntu) OS. The steps followed are (they my influence on the > final result): > > 1. Download the binaries from http://www.paraview.org. For me this > results in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > 2. Extract and copy them: > > tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > sudo emacs ~/.bashrc > > 3. then insert the following line, save & close > > export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/ > bin/ > > > Then I created a symbolic link: > > sudo ln -s /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview > /usr/bin/paraview > > sudo ln -s /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ > /usr/lib/paraview-5.3 > > Before installing paraview from the binaries files I was using the version > from Ubuntu repositories (paraview version 5.0 [I think]). Also I was using > a python script which uses paraview to take some snapshoots and it worked > really well. The problem is that now, when I want to use this python > script, it reports this message: > > "from paraview.simple import * > ImportError: No module named paraview.simple" > > I have made some searches on the Internet and I found a web page about > this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup > I have copied and pasted those sentences on my .bashrc file, restarted the > computer but it still does not work. > > Could you please help me? > > Best regards, > > Guillermo S. > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 22 10:24:15 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 22 Aug 2017 10:24:15 -0400 Subject: [Paraview] paraview.simple In-Reply-To: References: Message-ID: Guillermo, Please CC the mailing list so others can participate and learn from the discussion. That looks like progress. Now try adding to your .bashrc: export PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 HTH, Cory On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez wrote: > Hi Cory, > > Thank you very much for your fast response. Unfortunately it didn't work (I > just copied and pasted into the .bashrc the sentence you gave to me). > However, the new error message is: > > Error: Could not import vtkCommonComputationalGeometry > Traceback (most recent call last): > File "./", line XX, in > from paraview.simple import * > File > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", > line 43, in > from paraview import servermanager > File > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", > line 53, in > from paraview import vtk > File > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", > line 7, in > from paraview.vtk.vtkCommonCore import * > File > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", > line 9, in > from vtkCommonCorePython import * > ImportError: No module named vtkCommonCorePython > > I have searched around the Internet and I found a thread that I though it > could help: > http://public.kitware.com/pipermail/paraview/2014-February/030506.html > > The idea is to use this: > > setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} > > setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: your-install > /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk > > I copied and pasted this on my .bashrc file substituting the corresponding > names, but it didn't work. :( > > Any idea? > > Really grateful, > > Guillermo S. > > > > > 2017-08-22 12:31 GMT-01:00 Cory Quammen : >> >> Hi Guillermo, >> >> I think the content in that wiki page is outdated. >> >> Try setting PYTHONPATH to the following in your .bashrc >> >> export >> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages >> >> See if that works and let us know, >> Cory >> >> On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez >> wrote: >>> >>> Dear all, >>> >>> Yesterday I installed paraview v5.3 using the binaries from the website >>> on my Linux (ubuntu) OS. The steps followed are (they my influence on the >>> final result): >>> >>> Download the binaries from http://www.paraview.org. For me this results >>> in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>> Extract and copy them: >>> >>> tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>> sudo emacs ~/.bashrc >>> >>> then insert the following line, save & close >>> >>> export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ >>> >>> Then I created a symbolic link: >>> >>> sudo ln -s >>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview >>> /usr/bin/paraview >>> >>> sudo ln -s >>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ >>> /usr/lib/paraview-5.3 >>> >>> Before installing paraview from the binaries files I was using the >>> version from Ubuntu repositories (paraview version 5.0 [I think]). Also I >>> was using a python script which uses paraview to take some snapshoots and it >>> worked really well. The problem is that now, when I want to use this python >>> script, it reports this message: >>> >>> "from paraview.simple import * >>> ImportError: No module named paraview.simple" >>> >>> I have made some searches on the Internet and I found a web page about >>> this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup >>> I have copied and pasted those sentences on my .bashrc file, restarted >>> the computer but it still does not work. >>> >>> Could you please help me? >>> >>> Best regards, >>> >>> Guillermo S. >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From guillermo180395 at gmail.com Tue Aug 22 13:37:18 2017 From: guillermo180395 at gmail.com (Guillermo) Date: Tue, 22 Aug 2017 16:37:18 -0100 Subject: [Paraview] paraview.simple In-Reply-To: References: Message-ID: <8a4bea5a-2f8a-1874-5281-cd0b856a98da@gmail.com> Hi Cory, I just copied and pasted that sentence on my .bashrc but it doesn't work. Also I have tried typing .../paraview-5.3.0 but neither works. Thanks, Guillermo On 22/08/17 13:24, Cory Quammen wrote: > Guillermo, > > Please CC the mailing list so others can participate and learn from > the discussion. > > That looks like progress. Now try adding to your .bashrc: > > export PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 > > HTH, > Cory > > On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez > wrote: >> Hi Cory, >> >> Thank you very much for your fast response. Unfortunately it didn't work (I >> just copied and pasted into the .bashrc the sentence you gave to me). >> However, the new error message is: >> >> Error: Could not import vtkCommonComputationalGeometry >> Traceback (most recent call last): >> File "./", line XX, in >> from paraview.simple import * >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", >> line 43, in >> from paraview import servermanager >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", >> line 53, in >> from paraview import vtk >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", >> line 7, in >> from paraview.vtk.vtkCommonCore import * >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", >> line 9, in >> from vtkCommonCorePython import * >> ImportError: No module named vtkCommonCorePython >> >> I have searched around the Internet and I found a thread that I though it >> could help: >> http://public.kitware.com/pipermail/paraview/2014-February/030506.html >> >> The idea is to use this: >> >> setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} >> >> setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: your-install >> /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk >> >> I copied and pasted this on my .bashrc file substituting the corresponding >> names, but it didn't work. :( >> >> Any idea? >> >> Really grateful, >> >> Guillermo S. >> >> >> >> >> 2017-08-22 12:31 GMT-01:00 Cory Quammen : >>> Hi Guillermo, >>> >>> I think the content in that wiki page is outdated. >>> >>> Try setting PYTHONPATH to the following in your .bashrc >>> >>> export >>> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages >>> >>> See if that works and let us know, >>> Cory >>> >>> On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez >>> wrote: >>>> Dear all, >>>> >>>> Yesterday I installed paraview v5.3 using the binaries from the website >>>> on my Linux (ubuntu) OS. The steps followed are (they my influence on the >>>> final result): >>>> >>>> Download the binaries from http://www.paraview.org. For me this results >>>> in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>> Extract and copy them: >>>> >>>> tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>> sudo emacs ~/.bashrc >>>> >>>> then insert the following line, save & close >>>> >>>> export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ >>>> >>>> Then I created a symbolic link: >>>> >>>> sudo ln -s >>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview >>>> /usr/bin/paraview >>>> >>>> sudo ln -s >>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ >>>> /usr/lib/paraview-5.3 >>>> >>>> Before installing paraview from the binaries files I was using the >>>> version from Ubuntu repositories (paraview version 5.0 [I think]). Also I >>>> was using a python script which uses paraview to take some snapshoots and it >>>> worked really well. The problem is that now, when I want to use this python >>>> script, it reports this message: >>>> >>>> "from paraview.simple import * >>>> ImportError: No module named paraview.simple" >>>> >>>> I have made some searches on the Internet and I found a web page about >>>> this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup >>>> I have copied and pasted those sentences on my .bashrc file, restarted >>>> the computer but it still does not work. >>>> >>>> Could you please help me? >>>> >>>> Best regards, >>>> >>>> Guillermo S. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >> > > From guillermo180395 at gmail.com Tue Aug 22 13:38:11 2017 From: guillermo180395 at gmail.com (Guillermo) Date: Tue, 22 Aug 2017 16:38:11 -0100 Subject: [Paraview] paraview.simple In-Reply-To: References: Message-ID: I forgot to mention that the error message is the same as before. On 22/08/17 13:24, Cory Quammen wrote: > Guillermo, > > Please CC the mailing list so others can participate and learn from > the discussion. > > That looks like progress. Now try adding to your .bashrc: > > export PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 > > HTH, > Cory > > On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez > wrote: >> Hi Cory, >> >> Thank you very much for your fast response. Unfortunately it didn't work (I >> just copied and pasted into the .bashrc the sentence you gave to me). >> However, the new error message is: >> >> Error: Could not import vtkCommonComputationalGeometry >> Traceback (most recent call last): >> File "./", line XX, in >> from paraview.simple import * >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", >> line 43, in >> from paraview import servermanager >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", >> line 53, in >> from paraview import vtk >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", >> line 7, in >> from paraview.vtk.vtkCommonCore import * >> File >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", >> line 9, in >> from vtkCommonCorePython import * >> ImportError: No module named vtkCommonCorePython >> >> I have searched around the Internet and I found a thread that I though it >> could help: >> http://public.kitware.com/pipermail/paraview/2014-February/030506.html >> >> The idea is to use this: >> >> setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} >> >> setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: your-install >> /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk >> >> I copied and pasted this on my .bashrc file substituting the corresponding >> names, but it didn't work. :( >> >> Any idea? >> >> Really grateful, >> >> Guillermo S. >> >> >> >> >> 2017-08-22 12:31 GMT-01:00 Cory Quammen : >>> Hi Guillermo, >>> >>> I think the content in that wiki page is outdated. >>> >>> Try setting PYTHONPATH to the following in your .bashrc >>> >>> export >>> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages >>> >>> See if that works and let us know, >>> Cory >>> >>> On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez >>> wrote: >>>> Dear all, >>>> >>>> Yesterday I installed paraview v5.3 using the binaries from the website >>>> on my Linux (ubuntu) OS. The steps followed are (they my influence on the >>>> final result): >>>> >>>> Download the binaries from http://www.paraview.org. For me this results >>>> in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>> Extract and copy them: >>>> >>>> tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>> sudo emacs ~/.bashrc >>>> >>>> then insert the following line, save & close >>>> >>>> export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ >>>> >>>> Then I created a symbolic link: >>>> >>>> sudo ln -s >>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview >>>> /usr/bin/paraview >>>> >>>> sudo ln -s >>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ >>>> /usr/lib/paraview-5.3 >>>> >>>> Before installing paraview from the binaries files I was using the >>>> version from Ubuntu repositories (paraview version 5.0 [I think]). Also I >>>> was using a python script which uses paraview to take some snapshoots and it >>>> worked really well. The problem is that now, when I want to use this python >>>> script, it reports this message: >>>> >>>> "from paraview.simple import * >>>> ImportError: No module named paraview.simple" >>>> >>>> I have made some searches on the Internet and I found a web page about >>>> this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup >>>> I have copied and pasted those sentences on my .bashrc file, restarted >>>> the computer but it still does not work. >>>> >>>> Could you please help me? >>>> >>>> Best regards, >>>> >>>> Guillermo S. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >> > > From cory.quammen at kitware.com Tue Aug 22 10:46:16 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 22 Aug 2017 10:46:16 -0400 Subject: [Paraview] paraview.simple In-Reply-To: References: Message-ID: Oops, I failed to change the version number in the line I gave you, but caught that and corrected it, just not quite to the right version number. Try export PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 Basically, you have to set the PYTHONPATH to where the lib*Python.so files are located. Make sure /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 exists and confirm that a file starting with libvtkCommonCorePython27 is there. Stepping back a bit, you wouldn't have to do any of this PYTHONPATH stuff if you just add /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin to your PATH. HTH, Cory On Tue, Aug 22, 2017 at 1:38 PM, Guillermo wrote: > I forgot to mention that the error message is the same as before. > > > On 22/08/17 13:24, Cory Quammen wrote: >> >> Guillermo, >> >> Please CC the mailing list so others can participate and learn from >> the discussion. >> >> That looks like progress. Now try adding to your .bashrc: >> >> export >> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 >> >> HTH, >> Cory >> >> On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez >> wrote: >>> >>> Hi Cory, >>> >>> Thank you very much for your fast response. Unfortunately it didn't work >>> (I >>> just copied and pasted into the .bashrc the sentence you gave to me). >>> However, the new error message is: >>> >>> Error: Could not import vtkCommonComputationalGeometry >>> Traceback (most recent call last): >>> File "./", line XX, in >>> from paraview.simple import * >>> File >>> >>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", >>> line 43, in >>> from paraview import servermanager >>> File >>> >>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", >>> line 53, in >>> from paraview import vtk >>> File >>> >>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", >>> line 7, in >>> from paraview.vtk.vtkCommonCore import * >>> File >>> >>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", >>> line 9, in >>> from vtkCommonCorePython import * >>> ImportError: No module named vtkCommonCorePython >>> >>> I have searched around the Internet and I found a thread that I though it >>> could help: >>> http://public.kitware.com/pipermail/paraview/2014-February/030506.html >>> >>> The idea is to use this: >>> >>> setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} >>> >>> setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: >>> your-install >>> /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk >>> >>> I copied and pasted this on my .bashrc file substituting the >>> corresponding >>> names, but it didn't work. :( >>> >>> Any idea? >>> >>> Really grateful, >>> >>> Guillermo S. >>> >>> >>> >>> >>> 2017-08-22 12:31 GMT-01:00 Cory Quammen : >>>> >>>> Hi Guillermo, >>>> >>>> I think the content in that wiki page is outdated. >>>> >>>> Try setting PYTHONPATH to the following in your .bashrc >>>> >>>> export >>>> >>>> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages >>>> >>>> See if that works and let us know, >>>> Cory >>>> >>>> On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez >>>> wrote: >>>>> >>>>> Dear all, >>>>> >>>>> Yesterday I installed paraview v5.3 using the binaries from the website >>>>> on my Linux (ubuntu) OS. The steps followed are (they my influence on >>>>> the >>>>> final result): >>>>> >>>>> Download the binaries from http://www.paraview.org. For me this results >>>>> in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>>> Extract and copy them: >>>>> >>>>> tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>>> sudo emacs ~/.bashrc >>>>> >>>>> then insert the following line, save & close >>>>> >>>>> export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ >>>>> >>>>> Then I created a symbolic link: >>>>> >>>>> sudo ln -s >>>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview >>>>> /usr/bin/paraview >>>>> >>>>> sudo ln -s >>>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ >>>>> /usr/lib/paraview-5.3 >>>>> >>>>> Before installing paraview from the binaries files I was using the >>>>> version from Ubuntu repositories (paraview version 5.0 [I think]). Also >>>>> I >>>>> was using a python script which uses paraview to take some snapshoots >>>>> and it >>>>> worked really well. The problem is that now, when I want to use this >>>>> python >>>>> script, it reports this message: >>>>> >>>>> "from paraview.simple import * >>>>> ImportError: No module named paraview.simple" >>>>> >>>>> I have made some searches on the Internet and I found a web page about >>>>> this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup >>>>> I have copied and pasted those sentences on my .bashrc file, restarted >>>>> the computer but it still does not work. >>>>> >>>>> Could you please help me? >>>>> >>>>> Best regards, >>>>> >>>>> Guillermo S. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> -- >>>> Cory Quammen >>>> Staff R&D Engineer >>>> Kitware, Inc. >>> >>> >> >> > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From guillermo180395 at gmail.com Tue Aug 22 14:26:27 2017 From: guillermo180395 at gmail.com (Guillermo) Date: Tue, 22 Aug 2017 17:26:27 -0100 Subject: [Paraview] paraview.simple In-Reply-To: References: Message-ID: Hi, I noticed that I do not have the file libvtkCommonCorePython27 nor libvtkCommonCorePython. However, I have the files libvtkCommonColorPython27D-pv5.3.so and libvtkCommonColorPython27D-pv5.3.so.1. I have already tried to execute my script following your instructions but it did not work. This makes me think that I do not properly installed paraview-5.3. So I am going to reinstall it again. I would let you know if that fixes the problem. Thanks, Guillermo S. On 22/08/17 13:46, Cory Quammen wrote: > Oops, I failed to change the version number in the line I gave you, > but caught that and corrected it, just not quite to the right version > number. > > Try > > export PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > > Basically, you have to set the PYTHONPATH to where the lib*Python.so > files are located. Make sure > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > exists and confirm that a file starting with libvtkCommonCorePython27 > is there. > > Stepping back a bit, you wouldn't have to do any of this PYTHONPATH > stuff if you just add > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > > to your PATH. > > HTH, > Cory > > On Tue, Aug 22, 2017 at 1:38 PM, Guillermo wrote: >> I forgot to mention that the error message is the same as before. >> >> >> On 22/08/17 13:24, Cory Quammen wrote: >>> Guillermo, >>> >>> Please CC the mailing list so others can participate and learn from >>> the discussion. >>> >>> That looks like progress. Now try adding to your .bashrc: >>> >>> export >>> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 >>> >>> HTH, >>> Cory >>> >>> On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez >>> wrote: >>>> Hi Cory, >>>> >>>> Thank you very much for your fast response. Unfortunately it didn't work >>>> (I >>>> just copied and pasted into the .bashrc the sentence you gave to me). >>>> However, the new error message is: >>>> >>>> Error: Could not import vtkCommonComputationalGeometry >>>> Traceback (most recent call last): >>>> File "./", line XX, in >>>> from paraview.simple import * >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", >>>> line 43, in >>>> from paraview import servermanager >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", >>>> line 53, in >>>> from paraview import vtk >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", >>>> line 7, in >>>> from paraview.vtk.vtkCommonCore import * >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", >>>> line 9, in >>>> from vtkCommonCorePython import * >>>> ImportError: No module named vtkCommonCorePython >>>> >>>> I have searched around the Internet and I found a thread that I though it >>>> could help: >>>> http://public.kitware.com/pipermail/paraview/2014-February/030506.html >>>> >>>> The idea is to use this: >>>> >>>> setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} >>>> >>>> setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: >>>> your-install >>>> /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk >>>> >>>> I copied and pasted this on my .bashrc file substituting the >>>> corresponding >>>> names, but it didn't work. :( >>>> >>>> Any idea? >>>> >>>> Really grateful, >>>> >>>> Guillermo S. >>>> >>>> >>>> >>>> >>>> 2017-08-22 12:31 GMT-01:00 Cory Quammen : >>>>> Hi Guillermo, >>>>> >>>>> I think the content in that wiki page is outdated. >>>>> >>>>> Try setting PYTHONPATH to the following in your .bashrc >>>>> >>>>> export >>>>> >>>>> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages >>>>> >>>>> See if that works and let us know, >>>>> Cory >>>>> >>>>> On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez >>>>> wrote: >>>>>> Dear all, >>>>>> >>>>>> Yesterday I installed paraview v5.3 using the binaries from the website >>>>>> on my Linux (ubuntu) OS. The steps followed are (they my influence on >>>>>> the >>>>>> final result): >>>>>> >>>>>> Download the binaries from http://www.paraview.org. For me this results >>>>>> in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>>>> Extract and copy them: >>>>>> >>>>>> tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>>>> sudo emacs ~/.bashrc >>>>>> >>>>>> then insert the following line, save & close >>>>>> >>>>>> export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ >>>>>> >>>>>> Then I created a symbolic link: >>>>>> >>>>>> sudo ln -s >>>>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview >>>>>> /usr/bin/paraview >>>>>> >>>>>> sudo ln -s >>>>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ >>>>>> /usr/lib/paraview-5.3 >>>>>> >>>>>> Before installing paraview from the binaries files I was using the >>>>>> version from Ubuntu repositories (paraview version 5.0 [I think]). Also >>>>>> I >>>>>> was using a python script which uses paraview to take some snapshoots >>>>>> and it >>>>>> worked really well. The problem is that now, when I want to use this >>>>>> python >>>>>> script, it reports this message: >>>>>> >>>>>> "from paraview.simple import * >>>>>> ImportError: No module named paraview.simple" >>>>>> >>>>>> I have made some searches on the Internet and I found a web page about >>>>>> this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup >>>>>> I have copied and pasted those sentences on my .bashrc file, restarted >>>>>> the computer but it still does not work. >>>>>> >>>>>> Could you please help me? >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Guillermo S. >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> -- >>>>> Cory Quammen >>>>> Staff R&D Engineer >>>>> Kitware, Inc. >>>> >>> > > From cory.quammen at kitware.com Tue Aug 22 13:07:25 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 22 Aug 2017 13:07:25 -0400 Subject: [Paraview] ParaView superbuild for 5.4.1 tagged Message-ID: Hi folks, ParaView's superbuild git repository has now been tagged with v5.4.1. Thanks, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From leonardopessanha74 at gmail.com Tue Aug 22 13:45:25 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Tue, 22 Aug 2017 14:45:25 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: Thank you, Sebastien. I am able to build the example but the data don't show up yelding in the browser debugger ReferenceError: __BASE_PATH__ is not defined[Learn More] > In the following line of MyWebApp.js dataModel = new _QueryDataModel2.default(_index2.default, __BASE_PATH__ + > '/data/probe/'), > Do you know what path should be resolved by (__BASE_PATH__ + 'data/probe') ? I looked upon the the example webpage and repositories of paraviewweb/vtk.js and in then the resolve is dataModel = new _QueryDataModel2.default(_index2.default, ('/paraviewweb') > + '/data/probe/'), > but this path does not exists after npm install paraviewweb --save > npm install kw-web-suite --save-dev > In the repositories, __BASE_PATH__ shows up in karma.config. Not using and not knowing how to use karma the problem? I tried defining __BASE_PATH__ in var path = require('path'), webpack = require('webpack'), loaders = require('./node_modules/paraviewweb/config/webpack.loaders.js'), plugins = [ new webpack.DefinePlugin( { __BASE_PATH__: ''' a lot of paths '" }), ], but of the lot of paths I tried, none worked. Hope you can help me here! Thanks in advance! Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-08-14 18:38 GMT-03:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > I think your import is correct. > > Regarding the sample data, this is the way you can download it via npm > (when doing "npm install") > => https://github.com/Kitware/paraviewweb/blob/master/package.json#L48 > > On Mon, Aug 14, 2017 at 3:12 PM, L?o Pessanha < > leonardopessanha74 at gmail.com> wrote: > >> Hi! Thank you for the help! Because of it I was able to build and start >> the example correctly. Now I am trying different examples such as >> MultiLayoutViewer https://kitware.github.io/para >> viewweb/examples/MultiLayoutViewer.html . >> I am still a little doubtful about my imports but I believe >> >> import MultiLayoutViewer from '..'; >>> >> should be >> >> import MultiLayoutViewer from 'paraviewweb/src/React/Viewers >>> /MultiLayoutViewer' >> >> >> Right? >> >> I couldn't find the package *tonic-arctic-sample-data *that holds the >> content needed in MultiLayoutViewer, MultiLayoutRenderer and Probe3DViewer >> examples in trough npm. >> >> Do you know how to do proceed? >> >> Thanks in advance. >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> 2017-08-10 11:35 GMT-03:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> With ParaViewWeb, we force the user to pick the version of the >>> dependencies they wants to install instead of forcing them. >>> >>> Regarding your import path they are still wrong. >>> >>> from paraviewweb/src/Component/Native/Composite/example/index.js >>> >>> when you import '..' that resolve to paraviewweb/src/Component/Nati >>> ve/Composite >>> >>> which means your imports should be: >>> >>> import CompositeComponent from 'paraviewweb/src/Component/Nat >>> ive/Composite'; >>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>> ive/BackgroundColor'; >>> >>> On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha < >>> leonardopessanha74 at gmail.com> wrote: >>> >>>> So, I was able to build using 'paraviewweb/src/' and installing >>>> forcibly mout, axios and hammerjs packages. >>>> >>>> Now there's other js errors that I am going after like /plotly.js\ and >>>> global reference ones ! >>>> >>>> It's definitely not a simple task to build an example of paraviewweb as >>>> a standalone app. >>>> >>>> Definitely will come back with updates. >>>> >>>> Best regards, >>>> >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> 2017-08-09 19:58 GMT-03:00 L?o Pessanha : >>>> >>>>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or >>>>> 'paraviewweb/src/Component'? >>>>> >>>>> I have the exactly same result using full path or starting with >>>>> 'paraviewweb' >>>>> >>>>> Using: >>>>> >>>>> import CompositeComponent from 'paraviewweb/src/'; >>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>> ive/BackgroundColor'; >>>>>> >>>>> >>>>> Outputs a lot of: >>>>> >>>>> Module not found: Error: Can't resolve >>>>>> >>>>> >>>>> So I did a 'npm list x' with x being the modules it couldn't >>>>> resolve(axios, hammerjs and etc) and none of then was installed. >>>>> >>>>> root at PC:~/MyWebProject# npm list hammerjs >>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>> ??? (empty) >>>>>> >>>>>> root at PC:~/MyWebProject# npm list axios >>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>> ??? (empty) >>>>>> >>>>> >>>>> >>>>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >>>>> --save-dev* failed installing the dependencies correctly? >>>>> >>>>> Best regards, >>>>> >>>>> Leonardo Pessanha >>>>> Laboratory of Computational Methods in Engineering >>>>> Federal University of Rio de Janeiro - COPPE >>>>> Rio de Janeiro, RJ, Brasil >>>>> >>>>> >>>>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> The import should start with 'paraviewweb' then you provide the full >>>>>> path from there like: >>>>>> >>>>>> import BGColorComponent from 'paraviewweb/src/Component/Native/ >>>>>> BackgroundColor'; >>>>>> >>>>>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>> >>>>>>> Hi! I did the changes. The only thing I am not sure it's the right >>>>>>> paths in the imports of ${ROOT}/src/index.js >>>>>>> >>>>>>> import CompositeComponent from '..'; >>>>>>>> import BGColorComponent from '../../BackgroundColor'; >>>>>>>> >>>>>>>> >>>>>>> Should I change this paths? >>>>>>> >>>>>>> I did try >>>>>>> >>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>> modules/paraviewweb/src'; >>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>> >>>>>>> and >>>>>>> >>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>> modules/paraviewweb/src/Component'; >>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>> >>>>>>> and >>>>>>> >>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>> modules/paraviewweb/src/Component/Native'; >>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>> >>>>>>> With the last 2 sucessfully building but with JS errors in Firefox >>>>>>> >>>>>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>>>>> >>>>>>> >>>>>>> and >>>>>>> >>>>>>> TypeError: _Native2.default is not a constructor >>>>>>>> >>>>>>> >>>>>>> and the first one not building and giving me a lot of >>>>>>> >>>>>>> Module not found: Error: Can't resolve >>>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks in advance! >>>>>>> >>>>>>> >>>>>>> Leonardo Pessanha >>>>>>> Laboratory of Computational Methods in Engineering >>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>> >>>>>>> >>>>>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com>: >>>>>>> >>>>>>>> If I get to it, I'll do what I've done with vtk.js to support both. >>>>>>>> >>>>>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>>>>> /config/dependency.js >>>>>>>> >>>>>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>> >>>>>>>>> Thank you, Sebastien. I will give a try! >>>>>>>>> >>>>>>>>> Do you believe it's best to rollback webpack to 1.x or to change >>>>>>>>> the webpack.config.js in order to fit webpack 2.x API? >>>>>>>>> >>>>>>>>> Leonardo Pessanha >>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>> >>>>>>>>> >>>>>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>> >>>>>>>>>> Based on the path given in the setup guide, you should copy the >>>>>>>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>>>>>>> file should be named index.js. >>>>>>>>>> >>>>>>>>>> Then you should be able to build your example using the npm >>>>>>>>>> command: "npm run build". >>>>>>>>>> >>>>>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>>>>> ndency.html), but the concept is exactly the same. >>>>>>>>>> As it is picking the example available here >>>>>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/WebGL/Cone >>>>>>>>>> and making a standalone application from it. >>>>>>>>>> >>>>>>>>>> Just be aware that vtk.js is using webpack2 which is not the case >>>>>>>>>> for ParaViewWeb. >>>>>>>>>> >>>>>>>>>> Hope that helps, >>>>>>>>>> >>>>>>>>>> Seb >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi! >>>>>>>>>>> >>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>> like the following one: >>>>>>>>>>> >>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>> ex.html >>>>>>>>>>> >>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>>>>> one with the main things. >>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>> >>>>>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>>>>> paraviewweb to it like its described in >>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>> >>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>> it. >>>>>>>>>>> >>>>>>>>>>> Thanks in advance, >>>>>>>>>>> >>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi! >>>>>>>>>>> >>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>> like the following one: >>>>>>>>>>> >>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>> ex.html >>>>>>>>>>> >>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a simple >>>>>>>>>>> one with the main things. >>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>> >>>>>>>>>>> What I managed to do so far was to create my own project and add >>>>>>>>>>> paraviewweb to it like its described in >>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>> >>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>> it. >>>>>>>>>>> >>>>>>>>>>> Thanks in advance, >>>>>>>>>>> >>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>> >>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>> >>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>> >>>>>>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>>>>>> ParaView >>>>>>>>>>> >>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Tue Aug 22 14:01:17 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 22 Aug 2017 12:01:17 -0600 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: __BASE_PATH__ is meant to dynamically define the http endpoint. This should not be a file path... You can remove it from your code and provide a proper endpoint. For us it is used on to allow local and github.io deployment. In your case, you need to copy that data by yourself to the dist/data directory so you can access it via http... Hope that helps, Seb On Tue, Aug 22, 2017 at 11:45 AM, L?o Pessanha wrote: > Thank you, Sebastien. > > I am able to build the example but the data don't show up yelding in the > browser debugger > > ReferenceError: __BASE_PATH__ is not defined[Learn More] >> > > In the following line of MyWebApp.js > > dataModel = new _QueryDataModel2.default(_index2.default, __BASE_PATH__ + >> '/data/probe/'), >> > > Do you know what path should be resolved by (__BASE_PATH__ + 'data/probe') > ? > > I looked upon the the example webpage and repositories of > paraviewweb/vtk.js and in then the resolve is > > dataModel = new _QueryDataModel2.default(_index2.default, >> ('/paraviewweb') + '/data/probe/'), >> > > but this path does not exists after > > npm install paraviewweb --save >> npm install kw-web-suite --save-dev >> > > In the repositories, __BASE_PATH__ shows up in karma.config. Not using and > not knowing how to use karma the problem? > > I tried defining __BASE_PATH__ in > > var path = require('path'), > webpack = require('webpack'), > loaders = require('./node_modules/paraviewweb/config/webpack. > loaders.js'), > plugins = > [ new webpack.DefinePlugin( > { > __BASE_PATH__: ''' a lot of paths '" > }), > ], > > > but of the lot of paths I tried, none worked. > > Hope you can help me here! > Thanks in advance! > > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > 2017-08-14 18:38 GMT-03:00 Sebastien Jourdain com>: > >> I think your import is correct. >> >> Regarding the sample data, this is the way you can download it via npm >> (when doing "npm install") >> => https://github.com/Kitware/paraviewweb/blob/master/package.json#L48 >> >> On Mon, Aug 14, 2017 at 3:12 PM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> Hi! Thank you for the help! Because of it I was able to build and start >>> the example correctly. Now I am trying different examples such as >>> MultiLayoutViewer https://kitware.github.io/para >>> viewweb/examples/MultiLayoutViewer.html . >>> I am still a little doubtful about my imports but I believe >>> >>> import MultiLayoutViewer from '..'; >>>> >>> should be >>> >>> import MultiLayoutViewer from 'paraviewweb/src/React/Viewers >>>> /MultiLayoutViewer' >>> >>> >>> Right? >>> >>> I couldn't find the package *tonic-arctic-sample-data *that holds the >>> content needed in MultiLayoutViewer, MultiLayoutRenderer and Probe3DViewer >>> examples in trough npm. >>> >>> Do you know how to do proceed? >>> >>> Thanks in advance. >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> 2017-08-10 11:35 GMT-03:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> With ParaViewWeb, we force the user to pick the version of the >>>> dependencies they wants to install instead of forcing them. >>>> >>>> Regarding your import path they are still wrong. >>>> >>>> from paraviewweb/src/Component/Native/Composite/example/index.js >>>> >>>> when you import '..' that resolve to paraviewweb/src/Component/Nati >>>> ve/Composite >>>> >>>> which means your imports should be: >>>> >>>> import CompositeComponent from 'paraviewweb/src/Component/Nat >>>> ive/Composite'; >>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>> ive/BackgroundColor'; >>>> >>>> On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha < >>>> leonardopessanha74 at gmail.com> wrote: >>>> >>>>> So, I was able to build using 'paraviewweb/src/' and installing >>>>> forcibly mout, axios and hammerjs packages. >>>>> >>>>> Now there's other js errors that I am going after like /plotly.js\ and >>>>> global reference ones ! >>>>> >>>>> It's definitely not a simple task to build an example of paraviewweb >>>>> as a standalone app. >>>>> >>>>> Definitely will come back with updates. >>>>> >>>>> Best regards, >>>>> >>>>> >>>>> Leonardo Pessanha >>>>> Laboratory of Computational Methods in Engineering >>>>> Federal University of Rio de Janeiro - COPPE >>>>> Rio de Janeiro, RJ, Brasil >>>>> >>>>> >>>>> 2017-08-09 19:58 GMT-03:00 L?o Pessanha >>>>> : >>>>> >>>>>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or >>>>>> 'paraviewweb/src/Component'? >>>>>> >>>>>> I have the exactly same result using full path or starting with >>>>>> 'paraviewweb' >>>>>> >>>>>> Using: >>>>>> >>>>>> import CompositeComponent from 'paraviewweb/src/'; >>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>>> ive/BackgroundColor'; >>>>>>> >>>>>> >>>>>> Outputs a lot of: >>>>>> >>>>>> Module not found: Error: Can't resolve >>>>>>> >>>>>> >>>>>> So I did a 'npm list x' with x being the modules it couldn't >>>>>> resolve(axios, hammerjs and etc) and none of then was installed. >>>>>> >>>>>> root at PC:~/MyWebProject# npm list hammerjs >>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>> ??? (empty) >>>>>>> >>>>>>> root at PC:~/MyWebProject# npm list axios >>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>> ??? (empty) >>>>>>> >>>>>> >>>>>> >>>>>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >>>>>> --save-dev* failed installing the dependencies correctly? >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Leonardo Pessanha >>>>>> Laboratory of Computational Methods in Engineering >>>>>> Federal University of Rio de Janeiro - COPPE >>>>>> Rio de Janeiro, RJ, Brasil >>>>>> >>>>>> >>>>>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> The import should start with 'paraviewweb' then you provide the full >>>>>>> path from there like: >>>>>>> >>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Native/ >>>>>>> BackgroundColor'; >>>>>>> >>>>>>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>> >>>>>>>> Hi! I did the changes. The only thing I am not sure it's the right >>>>>>>> paths in the imports of ${ROOT}/src/index.js >>>>>>>> >>>>>>>> import CompositeComponent from '..'; >>>>>>>>> import BGColorComponent from '../../BackgroundColor'; >>>>>>>>> >>>>>>>>> >>>>>>>> Should I change this paths? >>>>>>>> >>>>>>>> I did try >>>>>>>> >>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>> modules/paraviewweb/src'; >>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>> >>>>>>>> and >>>>>>>> >>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>> modules/paraviewweb/src/Component'; >>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>> >>>>>>>> and >>>>>>>> >>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>> modules/paraviewweb/src/Component/Native'; >>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>> >>>>>>>> With the last 2 sucessfully building but with JS errors in Firefox >>>>>>>> >>>>>>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>>>>>> >>>>>>>> >>>>>>>> and >>>>>>>> >>>>>>>> TypeError: _Native2.default is not a constructor >>>>>>>>> >>>>>>>> >>>>>>>> and the first one not building and giving me a lot of >>>>>>>> >>>>>>>> Module not found: Error: Can't resolve >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thanks in advance! >>>>>>>> >>>>>>>> >>>>>>>> Leonardo Pessanha >>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>> >>>>>>>> >>>>>>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>> >>>>>>>>> If I get to it, I'll do what I've done with vtk.js to support both. >>>>>>>>> >>>>>>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>>>>>> /config/dependency.js >>>>>>>>> >>>>>>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Thank you, Sebastien. I will give a try! >>>>>>>>>> >>>>>>>>>> Do you believe it's best to rollback webpack to 1.x or to change >>>>>>>>>> the webpack.config.js in order to fit webpack 2.x API? >>>>>>>>>> >>>>>>>>>> Leonardo Pessanha >>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>> >>>>>>>>>>> Based on the path given in the setup guide, you should copy the >>>>>>>>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>>>>>>>> file should be named index.js. >>>>>>>>>>> >>>>>>>>>>> Then you should be able to build your example using the npm >>>>>>>>>>> command: "npm run build". >>>>>>>>>>> >>>>>>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>>>>>> ndency.html), but the concept is exactly the same. >>>>>>>>>>> As it is picking the example available here >>>>>>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/Web >>>>>>>>>>> GL/Cone >>>>>>>>>>> and making a standalone application from it. >>>>>>>>>>> >>>>>>>>>>> Just be aware that vtk.js is using webpack2 which is not the >>>>>>>>>>> case for ParaViewWeb. >>>>>>>>>>> >>>>>>>>>>> Hope that helps, >>>>>>>>>>> >>>>>>>>>>> Seb >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi! >>>>>>>>>>>> >>>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>>> like the following one: >>>>>>>>>>>> >>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>> ex.html >>>>>>>>>>>> >>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>> >>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>> >>>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>>> it. >>>>>>>>>>>> >>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>> >>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi! >>>>>>>>>>>> >>>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>>> like the following one: >>>>>>>>>>>> >>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>> ex.html >>>>>>>>>>>> >>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>> >>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>> >>>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>>> it. >>>>>>>>>>>> >>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>> >>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>> >>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>> >>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>>> >>>>>>>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>>>>>>> ParaView >>>>>>>>>>>> >>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Tue Aug 22 14:23:33 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Tue, 22 Aug 2017 15:23:33 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: So, just to be clear in order for me to understand I should copy the content of 'node_modules/tonic-arctic-sample-data/data/probe/' to 'dist/data' and use dataModel = new QueryDataModel(jsonData, 'path/to/dist/data'), > in the src/index.js ? Thanks in advance! Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-08-22 15:01 GMT-03:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > __BASE_PATH__ is meant to dynamically define the http endpoint. This > should not be a file path... > You can remove it from your code and provide a proper endpoint. For us it > is used on to allow local and github.io deployment. > > In your case, you need to copy that data by yourself to the dist/data > directory so you can access it via http... > > Hope that helps, > > Seb > > On Tue, Aug 22, 2017 at 11:45 AM, L?o Pessanha < > leonardopessanha74 at gmail.com> wrote: > >> Thank you, Sebastien. >> >> I am able to build the example but the data don't show up yelding in the >> browser debugger >> >> ReferenceError: __BASE_PATH__ is not defined[Learn More] >>> >> >> In the following line of MyWebApp.js >> >> dataModel = new _QueryDataModel2.default(_index2.default, __BASE_PATH__ >>> + '/data/probe/'), >>> >> >> Do you know what path should be resolved by (__BASE_PATH__ + >> 'data/probe') ? >> >> I looked upon the the example webpage and repositories of >> paraviewweb/vtk.js and in then the resolve is >> >> dataModel = new _QueryDataModel2.default(_index2.default, >>> ('/paraviewweb') + '/data/probe/'), >>> >> >> but this path does not exists after >> >> npm install paraviewweb --save >>> npm install kw-web-suite --save-dev >>> >> >> In the repositories, __BASE_PATH__ shows up in karma.config. Not using >> and not knowing how to use karma the problem? >> >> I tried defining __BASE_PATH__ in >> >> var path = require('path'), >> webpack = require('webpack'), >> loaders = require('./node_modules/paraviewweb/config/webpack.loaders. >> js'), >> plugins = >> [ new webpack.DefinePlugin( >> { >> __BASE_PATH__: ''' a lot of paths '" >> }), >> ], >> >> >> but of the lot of paths I tried, none worked. >> >> Hope you can help me here! >> Thanks in advance! >> >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> 2017-08-14 18:38 GMT-03:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> I think your import is correct. >>> >>> Regarding the sample data, this is the way you can download it via npm >>> (when doing "npm install") >>> => https://github.com/Kitware/paraviewweb/blob/master/package.json#L48 >>> >>> On Mon, Aug 14, 2017 at 3:12 PM, L?o Pessanha < >>> leonardopessanha74 at gmail.com> wrote: >>> >>>> Hi! Thank you for the help! Because of it I was able to build and start >>>> the example correctly. Now I am trying different examples such as >>>> MultiLayoutViewer https://kitware.github.io/para >>>> viewweb/examples/MultiLayoutViewer.html . >>>> I am still a little doubtful about my imports but I believe >>>> >>>> import MultiLayoutViewer from '..'; >>>>> >>>> should be >>>> >>>> import MultiLayoutViewer from 'paraviewweb/src/React/Viewers >>>>> /MultiLayoutViewer' >>>> >>>> >>>> Right? >>>> >>>> I couldn't find the package *tonic-arctic-sample-data *that holds the >>>> content needed in MultiLayoutViewer, MultiLayoutRenderer and Probe3DViewer >>>> examples in trough npm. >>>> >>>> Do you know how to do proceed? >>>> >>>> Thanks in advance. >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> 2017-08-10 11:35 GMT-03:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> With ParaViewWeb, we force the user to pick the version of the >>>>> dependencies they wants to install instead of forcing them. >>>>> >>>>> Regarding your import path they are still wrong. >>>>> >>>>> from paraviewweb/src/Component/Native/Composite/example/index.js >>>>> >>>>> when you import '..' that resolve to paraviewweb/src/Component/Nati >>>>> ve/Composite >>>>> >>>>> which means your imports should be: >>>>> >>>>> import CompositeComponent from 'paraviewweb/src/Component/Nat >>>>> ive/Composite'; >>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>> ive/BackgroundColor'; >>>>> >>>>> On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha < >>>>> leonardopessanha74 at gmail.com> wrote: >>>>> >>>>>> So, I was able to build using 'paraviewweb/src/' and installing >>>>>> forcibly mout, axios and hammerjs packages. >>>>>> >>>>>> Now there's other js errors that I am going after like /plotly.js\ >>>>>> and global reference ones ! >>>>>> >>>>>> It's definitely not a simple task to build an example of paraviewweb >>>>>> as a standalone app. >>>>>> >>>>>> Definitely will come back with updates. >>>>>> >>>>>> Best regards, >>>>>> >>>>>> >>>>>> Leonardo Pessanha >>>>>> Laboratory of Computational Methods in Engineering >>>>>> Federal University of Rio de Janeiro - COPPE >>>>>> Rio de Janeiro, RJ, Brasil >>>>>> >>>>>> >>>>>> 2017-08-09 19:58 GMT-03:00 L?o Pessanha >>>>> >: >>>>>> >>>>>>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or >>>>>>> 'paraviewweb/src/Component'? >>>>>>> >>>>>>> I have the exactly same result using full path or starting with >>>>>>> 'paraviewweb' >>>>>>> >>>>>>> Using: >>>>>>> >>>>>>> import CompositeComponent from 'paraviewweb/src/'; >>>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>>>> ive/BackgroundColor'; >>>>>>>> >>>>>>> >>>>>>> Outputs a lot of: >>>>>>> >>>>>>> Module not found: Error: Can't resolve >>>>>>>> >>>>>>> >>>>>>> So I did a 'npm list x' with x being the modules it couldn't >>>>>>> resolve(axios, hammerjs and etc) and none of then was installed. >>>>>>> >>>>>>> root at PC:~/MyWebProject# npm list hammerjs >>>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>>> ??? (empty) >>>>>>>> >>>>>>>> root at PC:~/MyWebProject# npm list axios >>>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>>> ??? (empty) >>>>>>>> >>>>>>> >>>>>>> >>>>>>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >>>>>>> --save-dev* failed installing the dependencies correctly? >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Leonardo Pessanha >>>>>>> Laboratory of Computational Methods in Engineering >>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>> >>>>>>> >>>>>>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com>: >>>>>>> >>>>>>>> The import should start with 'paraviewweb' then you provide the >>>>>>>> full path from there like: >>>>>>>> >>>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Native/ >>>>>>>> BackgroundColor'; >>>>>>>> >>>>>>>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi! I did the changes. The only thing I am not sure it's the right >>>>>>>>> paths in the imports of ${ROOT}/src/index.js >>>>>>>>> >>>>>>>>> import CompositeComponent from '..'; >>>>>>>>>> import BGColorComponent from '../../BackgroundColor'; >>>>>>>>>> >>>>>>>>>> >>>>>>>>> Should I change this paths? >>>>>>>>> >>>>>>>>> I did try >>>>>>>>> >>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>> modules/paraviewweb/src'; >>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>> >>>>>>>>> and >>>>>>>>> >>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>> modules/paraviewweb/src/Component'; >>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>> >>>>>>>>> and >>>>>>>>> >>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>> modules/paraviewweb/src/Component/Native'; >>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>> >>>>>>>>> With the last 2 sucessfully building but with JS errors in Firefox >>>>>>>>> >>>>>>>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>>>>>>> >>>>>>>>> >>>>>>>>> and >>>>>>>>> >>>>>>>>> TypeError: _Native2.default is not a constructor >>>>>>>>>> >>>>>>>>> >>>>>>>>> and the first one not building and giving me a lot of >>>>>>>>> >>>>>>>>> Module not found: Error: Can't resolve >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks in advance! >>>>>>>>> >>>>>>>>> >>>>>>>>> Leonardo Pessanha >>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>> >>>>>>>>> >>>>>>>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>> >>>>>>>>>> If I get to it, I'll do what I've done with vtk.js to support >>>>>>>>>> both. >>>>>>>>>> >>>>>>>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>>>>>>> /config/dependency.js >>>>>>>>>> >>>>>>>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Thank you, Sebastien. I will give a try! >>>>>>>>>>> >>>>>>>>>>> Do you believe it's best to rollback webpack to 1.x or to change >>>>>>>>>>> the webpack.config.js in order to fit webpack 2.x API? >>>>>>>>>>> >>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>> >>>>>>>>>>>> Based on the path given in the setup guide, you should copy the >>>>>>>>>>>> example you want to reproduce inside ${ROOT}/src/* where the main example >>>>>>>>>>>> file should be named index.js. >>>>>>>>>>>> >>>>>>>>>>>> Then you should be able to build your example using the npm >>>>>>>>>>>> command: "npm run build". >>>>>>>>>>>> >>>>>>>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>>>>>>> ndency.html), but the concept is exactly the same. >>>>>>>>>>>> As it is picking the example available here >>>>>>>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/Web >>>>>>>>>>>> GL/Cone >>>>>>>>>>>> and making a standalone application from it. >>>>>>>>>>>> >>>>>>>>>>>> Just be aware that vtk.js is using webpack2 which is not the >>>>>>>>>>>> case for ParaViewWeb. >>>>>>>>>>>> >>>>>>>>>>>> Hope that helps, >>>>>>>>>>>> >>>>>>>>>>>> Seb >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi! >>>>>>>>>>>>> >>>>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>>>> like the following one: >>>>>>>>>>>>> >>>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>>> ex.html >>>>>>>>>>>>> >>>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>>> >>>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>>> >>>>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>>>> it. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>>> >>>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi! >>>>>>>>>>>>> >>>>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>>>> like the following one: >>>>>>>>>>>>> >>>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>>> ex.html >>>>>>>>>>>>> >>>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>>> >>>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>>> >>>>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>>>> it. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>>> >>>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>> >>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>> >>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>>>> >>>>>>>>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>>>>>>>> ParaView >>>>>>>>>>>>> >>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Tue Aug 22 14:30:07 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 22 Aug 2017 12:30:07 -0600 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: Almost, the missing part is for "dataModel = new QueryDataModel(jsonData, 'path/to/dist/data')" 'path/to/dist/data' should be '/data' since your web server is serving path/to/dist as / On Tue, Aug 22, 2017 at 12:23 PM, L?o Pessanha wrote: > So, just to be clear in order for me to understand > > I should copy the content of 'node_modules/tonic-arctic-sample-data/data/probe/' > to 'dist/data' and use > > dataModel = new QueryDataModel(jsonData, 'path/to/dist/data'), >> > > in the src/index.js ? > > Thanks in advance! > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > 2017-08-22 15:01 GMT-03:00 Sebastien Jourdain com>: > >> __BASE_PATH__ is meant to dynamically define the http endpoint. This >> should not be a file path... >> You can remove it from your code and provide a proper endpoint. For us it >> is used on to allow local and github.io deployment. >> >> In your case, you need to copy that data by yourself to the dist/data >> directory so you can access it via http... >> >> Hope that helps, >> >> Seb >> >> On Tue, Aug 22, 2017 at 11:45 AM, L?o Pessanha < >> leonardopessanha74 at gmail.com> wrote: >> >>> Thank you, Sebastien. >>> >>> I am able to build the example but the data don't show up yelding in the >>> browser debugger >>> >>> ReferenceError: __BASE_PATH__ is not defined[Learn More] >>>> >>> >>> In the following line of MyWebApp.js >>> >>> dataModel = new _QueryDataModel2.default(_index2.default, __BASE_PATH__ >>>> + '/data/probe/'), >>>> >>> >>> Do you know what path should be resolved by (__BASE_PATH__ + >>> 'data/probe') ? >>> >>> I looked upon the the example webpage and repositories of >>> paraviewweb/vtk.js and in then the resolve is >>> >>> dataModel = new _QueryDataModel2.default(_index2.default, >>>> ('/paraviewweb') + '/data/probe/'), >>>> >>> >>> but this path does not exists after >>> >>> npm install paraviewweb --save >>>> npm install kw-web-suite --save-dev >>>> >>> >>> In the repositories, __BASE_PATH__ shows up in karma.config. Not using >>> and not knowing how to use karma the problem? >>> >>> I tried defining __BASE_PATH__ in >>> >>> var path = require('path'), >>> webpack = require('webpack'), >>> loaders = require('./node_modules/paravi >>> ewweb/config/webpack.loaders.js'), >>> plugins = >>> [ new webpack.DefinePlugin( >>> { >>> __BASE_PATH__: ''' a lot of paths '" >>> }), >>> ], >>> >>> >>> but of the lot of paths I tried, none worked. >>> >>> Hope you can help me here! >>> Thanks in advance! >>> >>> >>> Leonardo Pessanha >>> Laboratory of Computational Methods in Engineering >>> Federal University of Rio de Janeiro - COPPE >>> Rio de Janeiro, RJ, Brasil >>> >>> >>> 2017-08-14 18:38 GMT-03:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> I think your import is correct. >>>> >>>> Regarding the sample data, this is the way you can download it via npm >>>> (when doing "npm install") >>>> => https://github.com/Kitware/paraviewweb/blob/master/package.json#L48 >>>> >>>> On Mon, Aug 14, 2017 at 3:12 PM, L?o Pessanha < >>>> leonardopessanha74 at gmail.com> wrote: >>>> >>>>> Hi! Thank you for the help! Because of it I was able to build and >>>>> start the example correctly. Now I am trying different examples such as >>>>> MultiLayoutViewer https://kitware.github.io/para >>>>> viewweb/examples/MultiLayoutViewer.html . >>>>> I am still a little doubtful about my imports but I believe >>>>> >>>>> import MultiLayoutViewer from '..'; >>>>>> >>>>> should be >>>>> >>>>> import MultiLayoutViewer from 'paraviewweb/src/React/Viewers >>>>>> /MultiLayoutViewer' >>>>> >>>>> >>>>> Right? >>>>> >>>>> I couldn't find the package *tonic-arctic-sample-data *that holds the >>>>> content needed in MultiLayoutViewer, MultiLayoutRenderer and Probe3DViewer >>>>> examples in trough npm. >>>>> >>>>> Do you know how to do proceed? >>>>> >>>>> Thanks in advance. >>>>> >>>>> Leonardo Pessanha >>>>> Laboratory of Computational Methods in Engineering >>>>> Federal University of Rio de Janeiro - COPPE >>>>> Rio de Janeiro, RJ, Brasil >>>>> >>>>> >>>>> 2017-08-10 11:35 GMT-03:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> With ParaViewWeb, we force the user to pick the version of the >>>>>> dependencies they wants to install instead of forcing them. >>>>>> >>>>>> Regarding your import path they are still wrong. >>>>>> >>>>>> from paraviewweb/src/Component/Native/Composite/example/index.js >>>>>> >>>>>> when you import '..' that resolve to paraviewweb/src/Component/Nati >>>>>> ve/Composite >>>>>> >>>>>> which means your imports should be: >>>>>> >>>>>> import CompositeComponent from 'paraviewweb/src/Component/Nat >>>>>> ive/Composite'; >>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>> ive/BackgroundColor'; >>>>>> >>>>>> On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha < >>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>> >>>>>>> So, I was able to build using 'paraviewweb/src/' and installing >>>>>>> forcibly mout, axios and hammerjs packages. >>>>>>> >>>>>>> Now there's other js errors that I am going after like /plotly.js\ >>>>>>> and global reference ones ! >>>>>>> >>>>>>> It's definitely not a simple task to build an example of paraviewweb >>>>>>> as a standalone app. >>>>>>> >>>>>>> Definitely will come back with updates. >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> >>>>>>> Leonardo Pessanha >>>>>>> Laboratory of Computational Methods in Engineering >>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>> >>>>>>> >>>>>>> 2017-08-09 19:58 GMT-03:00 L?o Pessanha < >>>>>>> leonardopessanha74 at gmail.com>: >>>>>>> >>>>>>>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' or >>>>>>>> 'paraviewweb/src/Component'? >>>>>>>> >>>>>>>> I have the exactly same result using full path or starting with >>>>>>>> 'paraviewweb' >>>>>>>> >>>>>>>> Using: >>>>>>>> >>>>>>>> import CompositeComponent from 'paraviewweb/src/'; >>>>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>>>>> ive/BackgroundColor'; >>>>>>>>> >>>>>>>> >>>>>>>> Outputs a lot of: >>>>>>>> >>>>>>>> Module not found: Error: Can't resolve >>>>>>>>> >>>>>>>> >>>>>>>> So I did a 'npm list x' with x being the modules it couldn't >>>>>>>> resolve(axios, hammerjs and etc) and none of then was installed. >>>>>>>> >>>>>>>> root at PC:~/MyWebProject# npm list hammerjs >>>>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>>>> ??? (empty) >>>>>>>>> >>>>>>>>> root at PC:~/MyWebProject# npm list axios >>>>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>>>> ??? (empty) >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >>>>>>>> --save-dev* failed installing the dependencies correctly? >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Leonardo Pessanha >>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>> >>>>>>>> >>>>>>>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>> >>>>>>>>> The import should start with 'paraviewweb' then you provide the >>>>>>>>> full path from there like: >>>>>>>>> >>>>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>>>>> ive/BackgroundColor'; >>>>>>>>> >>>>>>>>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi! I did the changes. The only thing I am not sure it's the >>>>>>>>>> right paths in the imports of ${ROOT}/src/index.js >>>>>>>>>> >>>>>>>>>> import CompositeComponent from '..'; >>>>>>>>>>> import BGColorComponent from '../../BackgroundColor'; >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> Should I change this paths? >>>>>>>>>> >>>>>>>>>> I did try >>>>>>>>>> >>>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>>> modules/paraviewweb/src'; >>>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>>> >>>>>>>>>> and >>>>>>>>>> >>>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>>> modules/paraviewweb/src/Component'; >>>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>>> >>>>>>>>>> and >>>>>>>>>> >>>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>>> modules/paraviewweb/src/Component/Native'; >>>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>>> >>>>>>>>>> With the last 2 sucessfully building but with JS errors in Firefox >>>>>>>>>> >>>>>>>>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> and >>>>>>>>>> >>>>>>>>>> TypeError: _Native2.default is not a constructor >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> and the first one not building and giving me a lot of >>>>>>>>>> >>>>>>>>>> Module not found: Error: Can't resolve >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks in advance! >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Leonardo Pessanha >>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>> >>>>>>>>>>> If I get to it, I'll do what I've done with vtk.js to support >>>>>>>>>>> both. >>>>>>>>>>> >>>>>>>>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>>>>>>>> /config/dependency.js >>>>>>>>>>> >>>>>>>>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Thank you, Sebastien. I will give a try! >>>>>>>>>>>> >>>>>>>>>>>> Do you believe it's best to rollback webpack to 1.x or to >>>>>>>>>>>> change the webpack.config.js in order to fit webpack 2.x API? >>>>>>>>>>>> >>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>>> >>>>>>>>>>>>> Based on the path given in the setup guide, you should copy >>>>>>>>>>>>> the example you want to reproduce inside ${ROOT}/src/* where the main >>>>>>>>>>>>> example file should be named index.js. >>>>>>>>>>>>> >>>>>>>>>>>>> Then you should be able to build your example using the npm >>>>>>>>>>>>> command: "npm run build". >>>>>>>>>>>>> >>>>>>>>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>>>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>>>>>>>> ndency.html), but the concept is exactly the same. >>>>>>>>>>>>> As it is picking the example available here >>>>>>>>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>>>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/Web >>>>>>>>>>>>> GL/Cone >>>>>>>>>>>>> and making a standalone application from it. >>>>>>>>>>>>> >>>>>>>>>>>>> Just be aware that vtk.js is using webpack2 which is not the >>>>>>>>>>>>> case for ParaViewWeb. >>>>>>>>>>>>> >>>>>>>>>>>>> Hope that helps, >>>>>>>>>>>>> >>>>>>>>>>>>> Seb >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi! >>>>>>>>>>>>>> >>>>>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>>>>> like the following one: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>>>> ex.html >>>>>>>>>>>>>> >>>>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>>>> >>>>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>>>> >>>>>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>>>>> it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi! >>>>>>>>>>>>>> >>>>>>>>>>>>>> I would like to know the steps in order to run simple example >>>>>>>>>>>>>> like the following one: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>>>> ex.html >>>>>>>>>>>>>> >>>>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>>>> >>>>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>>>> >>>>>>>>>>>>>> I don't know what to do next but I believe that a great start >>>>>>>>>>>>>> would be to know where to put the source code in the example and how to run >>>>>>>>>>>>>> it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>>> >>>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>>>>> >>>>>>>>>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>>>>>>>>> ParaView >>>>>>>>>>>>>> >>>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Tue Aug 22 14:57:53 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Tue, 22 Aug 2017 15:57:53 -0300 Subject: [Paraview] Running a simple example using ParaviewWeb In-Reply-To: References: Message-ID: Thank you, Sebastien! It worked! The correct path should also have a '/' at the end so: dataModel = new QueryDataModel(jsonData, '/data/'), > instead of dataModel = new QueryDataModel(jsonData, '/data'), > Thanks again! Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil 2017-08-22 15:30 GMT-03:00 Sebastien Jourdain < sebastien.jourdain at kitware.com>: > Almost, the missing part is for "dataModel = new QueryDataModel(jsonData, > 'path/to/dist/data')" > > 'path/to/dist/data' should be '/data' since your web server is serving > path/to/dist as / > > On Tue, Aug 22, 2017 at 12:23 PM, L?o Pessanha < > leonardopessanha74 at gmail.com> wrote: > >> So, just to be clear in order for me to understand >> >> I should copy the content of 'node_modules/tonic-arctic-sample-data/data/probe/' >> to 'dist/data' and use >> >> dataModel = new QueryDataModel(jsonData, 'path/to/dist/data'), >>> >> >> in the src/index.js ? >> >> Thanks in advance! >> >> Leonardo Pessanha >> Laboratory of Computational Methods in Engineering >> Federal University of Rio de Janeiro - COPPE >> Rio de Janeiro, RJ, Brasil >> >> >> 2017-08-22 15:01 GMT-03:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> __BASE_PATH__ is meant to dynamically define the http endpoint. This >>> should not be a file path... >>> You can remove it from your code and provide a proper endpoint. For us >>> it is used on to allow local and github.io deployment. >>> >>> In your case, you need to copy that data by yourself to the dist/data >>> directory so you can access it via http... >>> >>> Hope that helps, >>> >>> Seb >>> >>> On Tue, Aug 22, 2017 at 11:45 AM, L?o Pessanha < >>> leonardopessanha74 at gmail.com> wrote: >>> >>>> Thank you, Sebastien. >>>> >>>> I am able to build the example but the data don't show up yelding in >>>> the browser debugger >>>> >>>> ReferenceError: __BASE_PATH__ is not defined[Learn More] >>>>> >>>> >>>> In the following line of MyWebApp.js >>>> >>>> dataModel = new _QueryDataModel2.default(_index2.default, >>>>> __BASE_PATH__ + '/data/probe/'), >>>>> >>>> >>>> Do you know what path should be resolved by (__BASE_PATH__ + >>>> 'data/probe') ? >>>> >>>> I looked upon the the example webpage and repositories of >>>> paraviewweb/vtk.js and in then the resolve is >>>> >>>> dataModel = new _QueryDataModel2.default(_index2.default, >>>>> ('/paraviewweb') + '/data/probe/'), >>>>> >>>> >>>> but this path does not exists after >>>> >>>> npm install paraviewweb --save >>>>> npm install kw-web-suite --save-dev >>>>> >>>> >>>> In the repositories, __BASE_PATH__ shows up in karma.config. Not using >>>> and not knowing how to use karma the problem? >>>> >>>> I tried defining __BASE_PATH__ in >>>> >>>> var path = require('path'), >>>> webpack = require('webpack'), >>>> loaders = require('./node_modules/paravi >>>> ewweb/config/webpack.loaders.js'), >>>> plugins = >>>> [ new webpack.DefinePlugin( >>>> { >>>> __BASE_PATH__: ''' a lot of paths '" >>>> }), >>>> ], >>>> >>>> >>>> but of the lot of paths I tried, none worked. >>>> >>>> Hope you can help me here! >>>> Thanks in advance! >>>> >>>> >>>> Leonardo Pessanha >>>> Laboratory of Computational Methods in Engineering >>>> Federal University of Rio de Janeiro - COPPE >>>> Rio de Janeiro, RJ, Brasil >>>> >>>> >>>> 2017-08-14 18:38 GMT-03:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> I think your import is correct. >>>>> >>>>> Regarding the sample data, this is the way you can download it via npm >>>>> (when doing "npm install") >>>>> => https://github.com/Kitware/paraviewweb/blob/master/package.json#L48 >>>>> >>>>> On Mon, Aug 14, 2017 at 3:12 PM, L?o Pessanha < >>>>> leonardopessanha74 at gmail.com> wrote: >>>>> >>>>>> Hi! Thank you for the help! Because of it I was able to build and >>>>>> start the example correctly. Now I am trying different examples such as >>>>>> MultiLayoutViewer https://kitware.github.io/para >>>>>> viewweb/examples/MultiLayoutViewer.html . >>>>>> I am still a little doubtful about my imports but I believe >>>>>> >>>>>> import MultiLayoutViewer from '..'; >>>>>>> >>>>>> should be >>>>>> >>>>>> import MultiLayoutViewer from 'paraviewweb/src/React/Viewers >>>>>>> /MultiLayoutViewer' >>>>>> >>>>>> >>>>>> Right? >>>>>> >>>>>> I couldn't find the package *tonic-arctic-sample-data *that holds >>>>>> the content needed in MultiLayoutViewer, MultiLayoutRenderer and >>>>>> Probe3DViewer examples in trough npm. >>>>>> >>>>>> Do you know how to do proceed? >>>>>> >>>>>> Thanks in advance. >>>>>> >>>>>> Leonardo Pessanha >>>>>> Laboratory of Computational Methods in Engineering >>>>>> Federal University of Rio de Janeiro - COPPE >>>>>> Rio de Janeiro, RJ, Brasil >>>>>> >>>>>> >>>>>> 2017-08-10 11:35 GMT-03:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> With ParaViewWeb, we force the user to pick the version of the >>>>>>> dependencies they wants to install instead of forcing them. >>>>>>> >>>>>>> Regarding your import path they are still wrong. >>>>>>> >>>>>>> from paraviewweb/src/Component/Native/Composite/example/index.js >>>>>>> >>>>>>> when you import '..' that resolve to paraviewweb/src/Component/Nati >>>>>>> ve/Composite >>>>>>> >>>>>>> which means your imports should be: >>>>>>> >>>>>>> import CompositeComponent from 'paraviewweb/src/Component/Nat >>>>>>> ive/Composite'; >>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>>> ive/BackgroundColor'; >>>>>>> >>>>>>> On Wed, Aug 9, 2017 at 7:37 PM, L?o Pessanha < >>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>> >>>>>>>> So, I was able to build using 'paraviewweb/src/' and installing >>>>>>>> forcibly mout, axios and hammerjs packages. >>>>>>>> >>>>>>>> Now there's other js errors that I am going after like /plotly.js\ >>>>>>>> and global reference ones ! >>>>>>>> >>>>>>>> It's definitely not a simple task to build an example of >>>>>>>> paraviewweb as a standalone app. >>>>>>>> >>>>>>>> Definitely will come back with updates. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> >>>>>>>> Leonardo Pessanha >>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>> >>>>>>>> >>>>>>>> 2017-08-09 19:58 GMT-03:00 L?o Pessanha < >>>>>>>> leonardopessanha74 at gmail.com>: >>>>>>>> >>>>>>>>> So I am not sure of the first path yet. Is it 'paraviewweb/src/' >>>>>>>>> or 'paraviewweb/src/Component'? >>>>>>>>> >>>>>>>>> I have the exactly same result using full path or starting with >>>>>>>>> 'paraviewweb' >>>>>>>>> >>>>>>>>> Using: >>>>>>>>> >>>>>>>>> import CompositeComponent from 'paraviewweb/src/'; >>>>>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>>>>>> ive/BackgroundColor'; >>>>>>>>>> >>>>>>>>> >>>>>>>>> Outputs a lot of: >>>>>>>>> >>>>>>>>> Module not found: Error: Can't resolve >>>>>>>>>> >>>>>>>>> >>>>>>>>> So I did a 'npm list x' with x being the modules it couldn't >>>>>>>>> resolve(axios, hammerjs and etc) and none of then was installed. >>>>>>>>> >>>>>>>>> root at PC:~/MyWebProject# npm list hammerjs >>>>>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>>>>> ??? (empty) >>>>>>>>>> >>>>>>>>>> root at PC:~/MyWebProject# npm list axios >>>>>>>>>> projeto1 at 0.0.1 /home/gabriel/MyWebProject >>>>>>>>>> ??? (empty) >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Do you believe *npm install paraviewweb --save* and npm install *kw-web-suite >>>>>>>>> --save-dev* failed installing the dependencies correctly? >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> >>>>>>>>> Leonardo Pessanha >>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>> >>>>>>>>> >>>>>>>>> 2017-08-09 19:38 GMT-03:00 Sebastien Jourdain < >>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>> >>>>>>>>>> The import should start with 'paraviewweb' then you provide the >>>>>>>>>> full path from there like: >>>>>>>>>> >>>>>>>>>> import BGColorComponent from 'paraviewweb/src/Component/Nat >>>>>>>>>> ive/BackgroundColor'; >>>>>>>>>> >>>>>>>>>> On Wed, Aug 9, 2017 at 6:24 PM, L?o Pessanha < >>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi! I did the changes. The only thing I am not sure it's the >>>>>>>>>>> right paths in the imports of ${ROOT}/src/index.js >>>>>>>>>>> >>>>>>>>>>> import CompositeComponent from '..'; >>>>>>>>>>>> import BGColorComponent from '../../BackgroundColor'; >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> Should I change this paths? >>>>>>>>>>> >>>>>>>>>>> I did try >>>>>>>>>>> >>>>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>>>> modules/paraviewweb/src'; >>>>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>>>> >>>>>>>>>>> and >>>>>>>>>>> >>>>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>>>> modules/paraviewweb/src/Component'; >>>>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>>>> >>>>>>>>>>> and >>>>>>>>>>> >>>>>>>>>>> import CompositeComponent from '/home/user/MyWebProject/node_ >>>>>>>>>>> modules/paraviewweb/src/Component/Native'; >>>>>>>>>>> import BGColorComponent from '/home/user/MyWebProject/node_ >>>>>>>>>>> modules/paraviewweb/src/Component/Native/BackgroundColor'; >>>>>>>>>>> >>>>>>>>>>> With the last 2 sucessfully building but with JS errors in >>>>>>>>>>> Firefox >>>>>>>>>>> >>>>>>>>>>> TypeError: _Component2.default is not a constructor[Learn More] >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> and >>>>>>>>>>> >>>>>>>>>>> TypeError: _Native2.default is not a constructor >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> and the first one not building and giving me a lot of >>>>>>>>>>> >>>>>>>>>>> Module not found: Error: Can't resolve >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks in advance! >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2017-08-03 17:42 GMT-03:00 Sebastien Jourdain < >>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>> >>>>>>>>>>>> If I get to it, I'll do what I've done with vtk.js to support >>>>>>>>>>>> both. >>>>>>>>>>>> >>>>>>>>>>>> See: https://github.com/Kitware/vtk-js/blob/master/Utilities >>>>>>>>>>>> /config/dependency.js >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Aug 3, 2017 at 1:49 PM, L?o Pessanha < >>>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Thank you, Sebastien. I will give a try! >>>>>>>>>>>>> >>>>>>>>>>>>> Do you believe it's best to rollback webpack to 1.x or to >>>>>>>>>>>>> change the webpack.config.js in order to fit webpack 2.x API? >>>>>>>>>>>>> >>>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 2017-07-24 17:21 GMT-03:00 Sebastien Jourdain < >>>>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>>>> >>>>>>>>>>>>>> Based on the path given in the setup guide, you should copy >>>>>>>>>>>>>> the example you want to reproduce inside ${ROOT}/src/* where the main >>>>>>>>>>>>>> example file should be named index.js. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Then you should be able to build your example using the npm >>>>>>>>>>>>>> command: "npm run build". >>>>>>>>>>>>>> >>>>>>>>>>>>>> Maybe the vtk.js explanation might be easier to follow ( >>>>>>>>>>>>>> https://kitware.github.io/vtk-js/docs/intro_vtk_as_es6_depe >>>>>>>>>>>>>> ndency.html), but the concept is exactly the same. >>>>>>>>>>>>>> As it is picking the example available here >>>>>>>>>>>>>> https://kitware.github.io/vtk-js/examples/Cone.html | >>>>>>>>>>>>>> https://github.com/Kitware/vtk-js/tree/master/Examples/Web >>>>>>>>>>>>>> GL/Cone >>>>>>>>>>>>>> and making a standalone application from it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Just be aware that vtk.js is using webpack2 which is not the >>>>>>>>>>>>>> case for ParaViewWeb. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hope that helps, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Seb >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I would like to know the steps in order to run simple >>>>>>>>>>>>>>> example like the following one: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>>>>> ex.html >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I don't know what to do next but I believe that a great >>>>>>>>>>>>>>> start would be to know where to put the source code in the example and how >>>>>>>>>>>>>>> to run it. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Jul 24, 2017 at 1:28 PM, L?o Pessanha < >>>>>>>>>>>>>> leonardopessanha74 at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I would like to know the steps in order to run simple >>>>>>>>>>>>>>> example like the following one: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/examples/Composite/ind >>>>>>>>>>>>>>> ex.html >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It doesn't need to be a really elaborated tutorial, but a >>>>>>>>>>>>>>> simple one with the main things. >>>>>>>>>>>>>>> I have little to no background in web development. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> What I managed to do so far was to create my own project and >>>>>>>>>>>>>>> add paraviewweb to it like its described in >>>>>>>>>>>>>>> https://kitware.github.io/paraviewweb/docs/setup.html . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I don't know what to do next but I believe that a great >>>>>>>>>>>>>>> start would be to know where to put the source code in the example and how >>>>>>>>>>>>>>> to run it. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Leonardo Pessanha >>>>>>>>>>>>>>> Laboratory of Computational Methods in Engineering >>>>>>>>>>>>>>> Federal University of Rio de Janeiro - COPPE >>>>>>>>>>>>>>> Rio de Janeiro, RJ, Brasil >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki >>>>>>>>>>>>>>> at: http://paraview.org/Wiki/ParaView >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Search the list archives at: http://markmail.org/search/?q= >>>>>>>>>>>>>>> ParaView >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kirit_101 at yahoo.com Tue Aug 22 18:06:58 2017 From: kirit_101 at yahoo.com (Niaz M.) Date: Tue, 22 Aug 2017 17:06:58 -0500 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format Message-ID: Hello: I am exporting Fluent simulation results as Ensight gold case. Then importing in paraview. Then I am plotting a slice . I am selecting Representation as Surface (not surface with edge). But I can't get rid of Mesh (or wireframe) . Is there any way I can get rid of wire frame. Thanks in advance [image: Inline image 1] Niaz -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 67453 bytes Desc: not available URL: From antech777 at gmail.com Wed Aug 23 02:02:12 2017 From: antech777 at gmail.com (Andrew) Date: Wed, 23 Aug 2017 09:02:12 +0300 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format In-Reply-To: References: Message-ID: Hello, Niaz. I also noticed the same problem in some cases with export from Fluent. I suspect that Fluent write files incorrectly, as if every cell was a separate domain. It explains why ParaView becomes very slow with such files and why we cannot remove mesh lines from representation. Sorry, cannot suggest something useful, because didn't remember details. Maybe exporting in CGNS or changing export options will help. Or, maybe, providing a sample dataset to ParaView developers will help them to identify the problem and introduce some tweak/workaround in reader. Actually, there are various problems with exporting from Fluent and CFX in neutral formats. Apart from the bug you mentioned, ParaView (4.3, 5.0, 5.2 for Win64) cannot open CGNS files written by CFX 18.0 Solver Manager: there are no variables in list (I tweaked export settings without effect). At the same time, it reads successfully CGNS written by CFX 14.5 Solver Manager. -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin34148 at gmail.com Wed Aug 23 02:18:04 2017 From: martin34148 at gmail.com (M P) Date: Wed, 23 Aug 2017 08:18:04 +0200 Subject: [Paraview] Point Dataset Interpolator - EllipsoidalGaussianKernel In-Reply-To: References: Message-ID: hmm, reading the vtkEllipsoidalGaussianKernel documentation, it seems it is not suitable for my purpose after all. Not possible to achieve constant weight inside the sampling cylinder. Also the use of word "normal" in the documentation confuses me, e.g.: "z is the distance of the current voxel sample point along the local normal N" W(x) = S * exp( -( Sharpness^2 * ((rxy/E)**2 + z**2)/R**2) ) - I would expect that it should be direction of the curve, not normal. When I display Normals on my spline curve it is as expected perpendicular to the curve and that I believe should not be the z coordinate of the kernel. Will make some simple Programmable Filter for that. Best regards, Martin On Tue, Aug 22, 2017 at 11:36 AM, M P wrote: > Hello all, > > I am trying to setup this filter to sample a point volume dataset along a > defined spline curve. The ideal "kernel" for my purpose would be a short > cylinder with some relatively big radius and constant weight in the whole > volume of the cylinder (the axis of this cylinder should follow the > direction vector of the spline). From all the kernels available for this > filter the "EllipsoidalGaussianKernel" seems to be the most suitable. But I > have a problem understanding what some of the parameters exactly mean. > > ------ > "Use Normals": Specify whether vector values should be used to affect the > shape of the Gaussian distribution. > > ?: What Normals vector values are meant here? Is it the normal to the > spline or some vector from dataset? And how is then the kernel oriented if > this option is not used? > ------ > "Use Scalars" > > ?: Similar question, what scalar is meant here and how is the weighting > done? But I guess this is not important for my use case > ------ > "Sharpness": Specify the sharpness (i.e., falloff) of the Gaussian. By > default Sharpness=2. As the sharpness increases the effects of distant > points are reduced. > > ?: I would like all the dataset points have the same weight - so I guess I > need maximum sharpness (like 20) - but this parameter help comment indicate > that it works the opposite way - higher value means lower weight of distant > points > ------ > "Eccentricity": Specify the eccentricity of the ellipsoidal Gaussian. A > value=1.0 produces a spherical distribution. Values less than 1 produce a > needle like distribution (in the direction of the normal); values greater > than 1 produce a pancake like distribution (orthogonal to the normal. > > ?: Here I am confused by the word "normal", should I understand that it > actually means direction vector? > ------ > > Is there some paper or book where this parameters are exactly explained, > or could someone point me to a source code where this is implemented (and > hopefully it would be possible to understand from there)? > > Best regards, > > Martin > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kashifsaeed38 at gmail.com Wed Aug 23 02:57:46 2017 From: kashifsaeed38 at gmail.com (Muhammad Kashif Saeed) Date: Wed, 23 Aug 2017 11:57:46 +0500 Subject: [Paraview] creating subdomain/cells/sections Message-ID: Hi, I am working on mixing of particles in a cylindrical mixer using DEM in open source software liggghts and for post processing, i am using paraview. I want to calculate the non-sampling mixing index for that purpose it requires to divide the cylindrical portion of the domain into a different subdomain (sections/cells) of the known number. and want to find the number of particles in each subdomain/cell/section. Kindly first help me how to divide into different subdomains. my simulation consists of a cylinder in which 4 bladed impeller rotates to mix the two different size particle beds mix together. thanks in advance -- *Muhammad Kashif Saeed* Chemical Engineer Cell: +92-300-7328139 -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillermo180395 at gmail.com Wed Aug 23 07:32:57 2017 From: guillermo180395 at gmail.com (Guillermo) Date: Wed, 23 Aug 2017 10:32:57 -0100 Subject: [Paraview] paraview.simple In-Reply-To: References: Message-ID: <10634343-3815-d21f-b66e-eeaadfcba5b4@gmail.com> Hi Cory, I have made a purge of paraview, reinstalled the 5.3 version, as I indicated on the first email, but the result is the same, it does not work and the message is the same as in the beginning. Also, the libs you indicated to me are not present. Actually, I really need to use this python script and I do not have too much time to spend on it, so I decided to downgrade to 5.0.1 version. In a near future, 1-1.5 month, I will try it again, as I want to upgrade to a newer version. I will let you know if I experiment any issue. Sorry for the inconveniences, Really grateful, Guillermo S. On 22/08/17 13:46, Cory Quammen wrote: > Oops, I failed to change the version number in the line I gave you, > but caught that and corrected it, just not quite to the right version > number. > > Try > > export PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > > Basically, you have to set the PYTHONPATH to where the lib*Python.so > files are located. Make sure > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > exists and confirm that a file starting with libvtkCommonCorePython27 > is there. > > Stepping back a bit, you wouldn't have to do any of this PYTHONPATH > stuff if you just add > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > > to your PATH. > > HTH, > Cory > > On Tue, Aug 22, 2017 at 1:38 PM, Guillermo wrote: >> I forgot to mention that the error message is the same as before. >> >> >> On 22/08/17 13:24, Cory Quammen wrote: >>> Guillermo, >>> >>> Please CC the mailing list so others can participate and learn from >>> the discussion. >>> >>> That looks like progress. Now try adding to your .bashrc: >>> >>> export >>> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 >>> >>> HTH, >>> Cory >>> >>> On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez >>> wrote: >>>> Hi Cory, >>>> >>>> Thank you very much for your fast response. Unfortunately it didn't work >>>> (I >>>> just copied and pasted into the .bashrc the sentence you gave to me). >>>> However, the new error message is: >>>> >>>> Error: Could not import vtkCommonComputationalGeometry >>>> Traceback (most recent call last): >>>> File "./", line XX, in >>>> from paraview.simple import * >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", >>>> line 43, in >>>> from paraview import servermanager >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", >>>> line 53, in >>>> from paraview import vtk >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", >>>> line 7, in >>>> from paraview.vtk.vtkCommonCore import * >>>> File >>>> >>>> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", >>>> line 9, in >>>> from vtkCommonCorePython import * >>>> ImportError: No module named vtkCommonCorePython >>>> >>>> I have searched around the Internet and I found a thread that I though it >>>> could help: >>>> http://public.kitware.com/pipermail/paraview/2014-February/030506.html >>>> >>>> The idea is to use this: >>>> >>>> setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} >>>> >>>> setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: >>>> your-install >>>> /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk >>>> >>>> I copied and pasted this on my .bashrc file substituting the >>>> corresponding >>>> names, but it didn't work. :( >>>> >>>> Any idea? >>>> >>>> Really grateful, >>>> >>>> Guillermo S. >>>> >>>> >>>> >>>> >>>> 2017-08-22 12:31 GMT-01:00 Cory Quammen : >>>>> Hi Guillermo, >>>>> >>>>> I think the content in that wiki page is outdated. >>>>> >>>>> Try setting PYTHONPATH to the following in your .bashrc >>>>> >>>>> export >>>>> >>>>> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages >>>>> >>>>> See if that works and let us know, >>>>> Cory >>>>> >>>>> On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez >>>>> wrote: >>>>>> Dear all, >>>>>> >>>>>> Yesterday I installed paraview v5.3 using the binaries from the website >>>>>> on my Linux (ubuntu) OS. The steps followed are (they my influence on >>>>>> the >>>>>> final result): >>>>>> >>>>>> Download the binaries from http://www.paraview.org. For me this results >>>>>> in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>>>> Extract and copy them: >>>>>> >>>>>> tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >>>>>> sudo emacs ~/.bashrc >>>>>> >>>>>> then insert the following line, save & close >>>>>> >>>>>> export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ >>>>>> >>>>>> Then I created a symbolic link: >>>>>> >>>>>> sudo ln -s >>>>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview >>>>>> /usr/bin/paraview >>>>>> >>>>>> sudo ln -s >>>>>> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ >>>>>> /usr/lib/paraview-5.3 >>>>>> >>>>>> Before installing paraview from the binaries files I was using the >>>>>> version from Ubuntu repositories (paraview version 5.0 [I think]). Also >>>>>> I >>>>>> was using a python script which uses paraview to take some snapshoots >>>>>> and it >>>>>> worked really well. The problem is that now, when I want to use this >>>>>> python >>>>>> script, it reports this message: >>>>>> >>>>>> "from paraview.simple import * >>>>>> ImportError: No module named paraview.simple" >>>>>> >>>>>> I have made some searches on the Internet and I found a web page about >>>>>> this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup >>>>>> I have copied and pasted those sentences on my .bashrc file, restarted >>>>>> the computer but it still does not work. >>>>>> >>>>>> Could you please help me? >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Guillermo S. >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> -- >>>>> Cory Quammen >>>>> Staff R&D Engineer >>>>> Kitware, Inc. >>>> >>> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Aug 23 09:58:11 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 23 Aug 2017 09:58:11 -0400 Subject: [Paraview] paraview.simple In-Reply-To: <10634343-3815-d21f-b66e-eeaadfcba5b4@gmail.com> References: <10634343-3815-d21f-b66e-eeaadfcba5b4@gmail.com> Message-ID: Guillermo, I'm sorry that my suggestions didn't work out. Could you try one last thing? Please run the following commands: cd /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin ./paraview That should work without problem. If it doesn't, we definitely have a problem. Cheers, Cory On Wed, Aug 23, 2017 at 7:32 AM, Guillermo wrote: > Hi Cory, > > I have made a purge of paraview, reinstalled the 5.3 version, as I indicated > on the first email, but the result is the same, it does not work and the > message is the same as in the beginning. Also, the libs you indicated to me > are not present. > > Actually, I really need to use this python script and I do not have too much > time to spend on it, so I decided to downgrade to 5.0.1 version. > > In a near future, 1-1.5 month, I will try it again, as I want to upgrade to > a newer version. I will let you know if I experiment any issue. > > Sorry for the inconveniences, > > Really grateful, > > Guillermo S. > > > On 22/08/17 13:46, Cory Quammen wrote: > > Oops, I failed to change the version number in the line I gave you, > but caught that and corrected it, just not quite to the right version > number. > > Try > > export > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > > Basically, you have to set the PYTHONPATH to where the lib*Python.so > files are located. Make sure > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > exists and confirm that a file starting with libvtkCommonCorePython27 > is there. > > Stepping back a bit, you wouldn't have to do any of this PYTHONPATH > stuff if you just add > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > > to your PATH. > > HTH, > Cory > > On Tue, Aug 22, 2017 at 1:38 PM, Guillermo > wrote: > > I forgot to mention that the error message is the same as before. > > > On 22/08/17 13:24, Cory Quammen wrote: > > Guillermo, > > Please CC the mailing list so others can participate and learn from > the discussion. > > That looks like progress. Now try adding to your .bashrc: > > export > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 > > HTH, > Cory > > On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez > wrote: > > Hi Cory, > > Thank you very much for your fast response. Unfortunately it didn't work > (I > just copied and pasted into the .bashrc the sentence you gave to me). > However, the new error message is: > > Error: Could not import vtkCommonComputationalGeometry > Traceback (most recent call last): > File "./", line XX, in > from paraview.simple import * > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", > line 43, in > from paraview import servermanager > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", > line 53, in > from paraview import vtk > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", > line 7, in > from paraview.vtk.vtkCommonCore import * > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", > line 9, in > from vtkCommonCorePython import * > ImportError: No module named vtkCommonCorePython > > I have searched around the Internet and I found a thread that I though it > could help: > http://public.kitware.com/pipermail/paraview/2014-February/030506.html > > The idea is to use this: > > setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} > > setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: > your-install > /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk > > I copied and pasted this on my .bashrc file substituting the > corresponding > names, but it didn't work. :( > > Any idea? > > Really grateful, > > Guillermo S. > > > > > 2017-08-22 12:31 GMT-01:00 Cory Quammen : > > Hi Guillermo, > > I think the content in that wiki page is outdated. > > Try setting PYTHONPATH to the following in your .bashrc > > export > > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages > > See if that works and let us know, > Cory > > On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez > wrote: > > Dear all, > > Yesterday I installed paraview v5.3 using the binaries from the website > on my Linux (ubuntu) OS. The steps followed are (they my influence on > the > final result): > > Download the binaries from http://www.paraview.org. For me this results > in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > Extract and copy them: > > tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > sudo emacs ~/.bashrc > > then insert the following line, save & close > > export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ > > Then I created a symbolic link: > > sudo ln -s > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview > /usr/bin/paraview > > sudo ln -s > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ > /usr/lib/paraview-5.3 > > Before installing paraview from the binaries files I was using the > version from Ubuntu repositories (paraview version 5.0 [I think]). Also > I > was using a python script which uses paraview to take some snapshoots > and it > worked really well. The problem is that now, when I want to use this > python > script, it reports this message: > > "from paraview.simple import * > ImportError: No module named paraview.simple" > > I have made some searches on the Internet and I found a web page about > this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup > I have copied and pasted those sentences on my .bashrc file, restarted > the computer but it still does not work. > > Could you please help me? > > Best regards, > > Guillermo S. > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From guillermo180395 at gmail.com Wed Aug 23 13:10:04 2017 From: guillermo180395 at gmail.com (Guillermo) Date: Wed, 23 Aug 2017 16:10:04 -0100 Subject: [Paraview] paraview.simple In-Reply-To: References: <10634343-3815-d21f-b66e-eeaadfcba5b4@gmail.com> Message-ID: <27625f87-f17d-3ad2-0666-0ccc91d7cb82@gmail.com> Hi Cory, It works perfectly. I can use paraview 5.3 version without any problem (I can use it as I normally do). The problem results when executing the python script from the Ubuntu's terminal. Thank you very much. ASAP I will try to install the v5.3 and I will let you know if I encounter any problem. Cheers, Guillermo On 23/08/17 12:58, Cory Quammen wrote: > Guillermo, > > I'm sorry that my suggestions didn't work out. > > Could you try one last thing? Please run the following commands: > > cd /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > ./paraview > > That should work without problem. If it doesn't, we definitely have a problem. > > Cheers, > Cory > > On Wed, Aug 23, 2017 at 7:32 AM, Guillermo wrote: >> Hi Cory, >> >> I have made a purge of paraview, reinstalled the 5.3 version, as I indicated >> on the first email, but the result is the same, it does not work and the >> message is the same as in the beginning. Also, the libs you indicated to me >> are not present. >> >> Actually, I really need to use this python script and I do not have too much >> time to spend on it, so I decided to downgrade to 5.0.1 version. >> >> In a near future, 1-1.5 month, I will try it again, as I want to upgrade to >> a newer version. I will let you know if I experiment any issue. >> >> Sorry for the inconveniences, >> >> Really grateful, >> >> Guillermo S. >> >> >> On 22/08/17 13:46, Cory Quammen wrote: >> >> Oops, I failed to change the version number in the line I gave you, >> but caught that and corrected it, just not quite to the right version >> number. >> >> Try >> >> export >> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 >> >> Basically, you have to set the PYTHONPATH to where the lib*Python.so >> files are located. Make sure >> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 >> exists and confirm that a file starting with libvtkCommonCorePython27 >> is there. >> >> Stepping back a bit, you wouldn't have to do any of this PYTHONPATH >> stuff if you just add >> >> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin >> >> to your PATH. >> >> HTH, >> Cory >> >> On Tue, Aug 22, 2017 at 1:38 PM, Guillermo >> wrote: >> >> I forgot to mention that the error message is the same as before. >> >> >> On 22/08/17 13:24, Cory Quammen wrote: >> >> Guillermo, >> >> Please CC the mailing list so others can participate and learn from >> the discussion. >> >> That looks like progress. Now try adding to your .bashrc: >> >> export >> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 >> >> HTH, >> Cory >> >> On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez >> wrote: >> >> Hi Cory, >> >> Thank you very much for your fast response. Unfortunately it didn't work >> (I >> just copied and pasted into the .bashrc the sentence you gave to me). >> However, the new error message is: >> >> Error: Could not import vtkCommonComputationalGeometry >> Traceback (most recent call last): >> File "./", line XX, in >> from paraview.simple import * >> File >> >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", >> line 43, in >> from paraview import servermanager >> File >> >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", >> line 53, in >> from paraview import vtk >> File >> >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", >> line 7, in >> from paraview.vtk.vtkCommonCore import * >> File >> >> "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", >> line 9, in >> from vtkCommonCorePython import * >> ImportError: No module named vtkCommonCorePython >> >> I have searched around the Internet and I found a thread that I though it >> could help: >> http://public.kitware.com/pipermail/paraview/2014-February/030506.html >> >> The idea is to use this: >> >> setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} >> >> setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: >> your-install >> /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk >> >> I copied and pasted this on my .bashrc file substituting the >> corresponding >> names, but it didn't work. :( >> >> Any idea? >> >> Really grateful, >> >> Guillermo S. >> >> >> >> >> 2017-08-22 12:31 GMT-01:00 Cory Quammen : >> >> Hi Guillermo, >> >> I think the content in that wiki page is outdated. >> >> Try setting PYTHONPATH to the following in your .bashrc >> >> export >> >> PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages >> >> See if that works and let us know, >> Cory >> >> On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez >> wrote: >> >> Dear all, >> >> Yesterday I installed paraview v5.3 using the binaries from the website >> on my Linux (ubuntu) OS. The steps followed are (they my influence on >> the >> final result): >> >> Download the binaries from http://www.paraview.org. For me this results >> in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >> Extract and copy them: >> >> tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz >> sudo emacs ~/.bashrc >> >> then insert the following line, save & close >> >> export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ >> >> Then I created a symbolic link: >> >> sudo ln -s >> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview >> /usr/bin/paraview >> >> sudo ln -s >> /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ >> /usr/lib/paraview-5.3 >> >> Before installing paraview from the binaries files I was using the >> version from Ubuntu repositories (paraview version 5.0 [I think]). Also >> I >> was using a python script which uses paraview to take some snapshoots >> and it >> worked really well. The problem is that now, when I want to use this >> python >> script, it reports this message: >> >> "from paraview.simple import * >> ImportError: No module named paraview.simple" >> >> I have made some searches on the Internet and I found a web page about >> this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup >> I have copied and pasted those sentences on my .bashrc file, restarted >> the computer but it still does not work. >> >> Could you please help me? >> >> Best regards, >> >> Guillermo S. >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> >> >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Aug 23 10:15:51 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 23 Aug 2017 10:15:51 -0400 Subject: [Paraview] paraview.simple In-Reply-To: <27625f87-f17d-3ad2-0666-0ccc91d7cb82@gmail.com> References: <10634343-3815-d21f-b66e-eeaadfcba5b4@gmail.com> <27625f87-f17d-3ad2-0666-0ccc91d7cb82@gmail.com> Message-ID: > The problem results when executing the python script from the Ubuntu's > terminal. What command are you using to run the Python script? Thanks, Cory > Thank you very much. > > ASAP I will try to install the v5.3 and I will let you know if I encounter > any problem. > > Cheers, > > Guillermo > > > On 23/08/17 12:58, Cory Quammen wrote: > > Guillermo, > > I'm sorry that my suggestions didn't work out. > > Could you try one last thing? Please run the following commands: > > cd /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > ./paraview > > That should work without problem. If it doesn't, we definitely have a > problem. > > Cheers, > Cory > > On Wed, Aug 23, 2017 at 7:32 AM, Guillermo > wrote: > > Hi Cory, > > I have made a purge of paraview, reinstalled the 5.3 version, as I indicated > on the first email, but the result is the same, it does not work and the > message is the same as in the beginning. Also, the libs you indicated to me > are not present. > > Actually, I really need to use this python script and I do not have too much > time to spend on it, so I decided to downgrade to 5.0.1 version. > > In a near future, 1-1.5 month, I will try it again, as I want to upgrade to > a newer version. I will let you know if I experiment any issue. > > Sorry for the inconveniences, > > Really grateful, > > Guillermo S. > > > On 22/08/17 13:46, Cory Quammen wrote: > > Oops, I failed to change the version number in the line I gave you, > but caught that and corrected it, just not quite to the right version > number. > > Try > > export > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > > Basically, you have to set the PYTHONPATH to where the lib*Python.so > files are located. Make sure > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > exists and confirm that a file starting with libvtkCommonCorePython27 > is there. > > Stepping back a bit, you wouldn't have to do any of this PYTHONPATH > stuff if you just add > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > > to your PATH. > > HTH, > Cory > > On Tue, Aug 22, 2017 at 1:38 PM, Guillermo > wrote: > > I forgot to mention that the error message is the same as before. > > > On 22/08/17 13:24, Cory Quammen wrote: > > Guillermo, > > Please CC the mailing list so others can participate and learn from > the discussion. > > That looks like progress. Now try adding to your .bashrc: > > export > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.4 > > HTH, > Cory > > On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez > wrote: > > Hi Cory, > > Thank you very much for your fast response. Unfortunately it didn't work > (I > just copied and pasted into the .bashrc the sentence you gave to me). > However, the new error message is: > > Error: Could not import vtkCommonComputationalGeometry > Traceback (most recent call last): > File "./", line XX, in > from paraview.simple import * > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/simple.py", > line 43, in > from paraview import servermanager > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/servermanager.py", > line 53, in > from paraview import vtk > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/__init__.py", > line 7, in > from paraview.vtk.vtkCommonCore import * > File > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/vtk/vtkCommonCore.py", > line 9, in > from vtkCommonCorePython import * > ImportError: No module named vtkCommonCorePython > > I have searched around the Internet and I found a thread that I though it > could help: > http://public.kitware.com/pipermail/paraview/2014-February/030506.html > > The idea is to use this: > > setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} > > setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: > your-install > /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk > > I copied and pasted this on my .bashrc file substituting the > corresponding > names, but it didn't work. :( > > Any idea? > > Really grateful, > > Guillermo S. > > > > > 2017-08-22 12:31 GMT-01:00 Cory Quammen : > > Hi Guillermo, > > I think the content in that wiki page is outdated. > > Try setting PYTHONPATH to the following in your .bashrc > > export > > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2.7/site-packages > > See if that works and let us know, > Cory > > On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez > wrote: > > Dear all, > > Yesterday I installed paraview v5.3 using the binaries from the website > on my Linux (ubuntu) OS. The steps followed are (they my influence on > the > final result): > > Download the binaries from http://www.paraview.org. For me this results > in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > Extract and copy them: > > tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > sudo emacs ~/.bashrc > > then insert the following line, save & close > > export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ > > Then I created a symbolic link: > > sudo ln -s > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview > /usr/bin/paraview > > sudo ln -s > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ > /usr/lib/paraview-5.3 > > Before installing paraview from the binaries files I was using the > version from Ubuntu repositories (paraview version 5.0 [I think]). Also > I > was using a python script which uses paraview to take some snapshoots > and it > worked really well. The problem is that now, when I want to use this > python > script, it reports this message: > > "from paraview.simple import * > ImportError: No module named paraview.simple" > > I have made some searches on the Internet and I found a web page about > this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup > I have copied and pasted those sentences on my .bashrc file, restarted > the computer but it still does not work. > > Could you please help me? > > Best regards, > > Guillermo S. > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > > > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From kirit_101 at yahoo.com Wed Aug 23 10:14:38 2017 From: kirit_101 at yahoo.com (Niaz M.) Date: Wed, 23 Aug 2017 09:14:38 -0500 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format Message-ID: Hi Andrew: Thanks for sharing your experience. Yes I have figure it out CGNS works best so far when you want to export from Fluent. But one think I miss the boundary name (or ID) in CGNS. Fluent doesn't write that info when you export as CGNS . It only export fluid domain. I am a newbie in Paraview. If I want to share some sample dataset to developer what will be best way. Niaz -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillermo180395 at gmail.com Wed Aug 23 10:48:02 2017 From: guillermo180395 at gmail.com (=?UTF-8?Q?Guillermo_Su=C3=A1rez?=) Date: Wed, 23 Aug 2017 13:48:02 -0100 Subject: [Paraview] Fwd: paraview.simple In-Reply-To: References: <10634343-3815-d21f-b66e-eeaadfcba5b4@gmail.com> <27625f87-f17d-3ad2-0666-0ccc91d7cb82@gmail.com> Message-ID: ---------- Forwarded message ---------- From: Guillermo Su?rez Date: 2017-08-23 13:33 GMT-01:00 Subject: Re: [Paraview] paraview.simple To: Cory Quammen I usually use: ./ but I also tried with: python3 Guillermo P.S: With the version 5.0.1 installed and working fine (the script works) I have searched the lib you mentioned to me but I do not have it. 2017-08-23 13:15 GMT-01:00 Cory Quammen : > > The problem results when executing the python script from the Ubuntu's > > terminal. > > What command are you using to run the Python script? > > Thanks, > Cory > > > Thank you very much. > > > > ASAP I will try to install the v5.3 and I will let you know if I > encounter > > any problem. > > > > Cheers, > > > > Guillermo > > > > > > On 23/08/17 12:58, Cory Quammen wrote: > > > > Guillermo, > > > > I'm sorry that my suggestions didn't work out. > > > > Could you try one last thing? Please run the following commands: > > > > cd /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > > ./paraview > > > > That should work without problem. If it doesn't, we definitely have a > > problem. > > > > Cheers, > > Cory > > > > On Wed, Aug 23, 2017 at 7:32 AM, Guillermo > > wrote: > > > > Hi Cory, > > > > I have made a purge of paraview, reinstalled the 5.3 version, as I > indicated > > on the first email, but the result is the same, it does not work and the > > message is the same as in the beginning. Also, the libs you indicated to > me > > are not present. > > > > Actually, I really need to use this python script and I do not have too > much > > time to spend on it, so I decided to downgrade to 5.0.1 version. > > > > In a near future, 1-1.5 month, I will try it again, as I want to upgrade > to > > a newer version. I will let you know if I experiment any issue. > > > > Sorry for the inconveniences, > > > > Really grateful, > > > > Guillermo S. > > > > > > On 22/08/17 13:46, Cory Quammen wrote: > > > > Oops, I failed to change the version number in the line I gave you, > > but caught that and corrected it, just not quite to the right version > > number. > > > > Try > > > > export > > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI- > Linux-64bit/lib/paraview-5.3 > > > > Basically, you have to set the PYTHONPATH to where the lib*Python.so > > files are located. Make sure > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3 > > exists and confirm that a file starting with libvtkCommonCorePython27 > > is there. > > > > Stepping back a bit, you wouldn't have to do any of this PYTHONPATH > > stuff if you just add > > > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin > > > > to your PATH. > > > > HTH, > > Cory > > > > On Tue, Aug 22, 2017 at 1:38 PM, Guillermo > > wrote: > > > > I forgot to mention that the error message is the same as before. > > > > > > On 22/08/17 13:24, Cory Quammen wrote: > > > > Guillermo, > > > > Please CC the mailing list so others can participate and learn from > > the discussion. > > > > That looks like progress. Now try adding to your .bashrc: > > > > export > > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI- > Linux-64bit/lib/paraview-5.4 > > > > HTH, > > Cory > > > > On Tue, Aug 22, 2017 at 10:19 AM, Guillermo Su?rez > > wrote: > > > > Hi Cory, > > > > Thank you very much for your fast response. Unfortunately it didn't work > > (I > > just copied and pasted into the .bashrc the sentence you gave to me). > > However, the new error message is: > > > > Error: Could not import vtkCommonComputationalGeometry > > Traceback (most recent call last): > > File "./", line XX, in > > from paraview.simple import * > > File > > > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2 > .7/site-packages/paraview/simple.py", > > line 43, in > > from paraview import servermanager > > File > > > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2 > .7/site-packages/paraview/servermanager.py", > > line 53, in > > from paraview import vtk > > File > > > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2 > .7/site-packages/paraview/vtk/__init__.py", > > line 7, in > > from paraview.vtk.vtkCommonCore import * > > File > > > > "/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/python2 > .7/site-packages/paraview/vtk/vtkCommonCore.py", > > line 9, in > > from vtkCommonCorePython import * > > ImportError: No module named vtkCommonCorePython > > > > I have searched around the Internet and I found a thread that I though it > > could help: > > http://public.kitware.com/pipermail/paraview/2014-February/030506.html > > > > The idea is to use this: > > > > setenv LD_LIBRARY_PATH your-install/lib/paraview-4.1:${LD_LIBRARY_PATH} > > > > setenv PYTHONPATH your-install /lib/paraview-4.1/site-packages: > > your-install > > /lib/paraview-4.1: your-install /lib/paraview-4.1/site-packages/vtk > > > > I copied and pasted this on my .bashrc file substituting the > > corresponding > > names, but it didn't work. :( > > > > Any idea? > > > > Really grateful, > > > > Guillermo S. > > > > > > > > > > 2017-08-22 12:31 GMT-01:00 Cory Quammen : > > > > Hi Guillermo, > > > > I think the content in that wiki page is outdated. > > > > Try setting PYTHONPATH to the following in your .bashrc > > > > export > > > > PYTHONPATH=$PYTHONPATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI- > Linux-64bit/lib/python2.7/site-packages > > > > See if that works and let us know, > > Cory > > > > On Tue, Aug 22, 2017 at 6:04 AM, Guillermo Su?rez > > wrote: > > > > Dear all, > > > > Yesterday I installed paraview v5.3 using the binaries from the website > > on my Linux (ubuntu) OS. The steps followed are (they my influence on > > the > > final result): > > > > Download the binaries from http://www.paraview.org. For me this results > > in: ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > > Extract and copy them: > > > > tar xzvf -C /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit.tar.gz > > sudo emacs ~/.bashrc > > > > then insert the following line, save & close > > > > export PATH=$PATH:/opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/ > > > > Then I created a symbolic link: > > > > sudo ln -s > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/bin/paraview > > /usr/bin/paraview > > > > sudo ln -s > > /opt/ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit/lib/paraview-5.3/ > > /usr/lib/paraview-5.3 > > > > Before installing paraview from the binaries files I was using the > > version from Ubuntu repositories (paraview version 5.0 [I think]). Also > > I > > was using a python script which uses paraview to take some snapshoots > > and it > > worked really well. The problem is that now, when I want to use this > > python > > script, it reports this message: > > > > "from paraview.simple import * > > ImportError: No module named paraview.simple" > > > > I have made some searches on the Internet and I found a web page about > > this problem: https://www.paraview.org/Wiki/ParaView/EnvironmentSetup > > I have copied and pasted those sentences on my .bashrc file, restarted > > the computer but it still does not work. > > > > Could you please help me? > > > > Best regards, > > > > Guillermo S. > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > > Cory Quammen > > Staff R&D Engineer > > Kitware, Inc. > > > > > > > > > > > > > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 23 14:33:07 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 23 Aug 2017 14:33:07 -0400 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format In-Reply-To: References: Message-ID: Can you share a sample dataset? That'll make it easier. Thanks Utkarsh On Tue, Aug 22, 2017 at 6:06 PM, Niaz M. via ParaView wrote: > Hello: > I am exporting Fluent simulation results as Ensight gold case. Then > importing in paraview. Then I am plotting a slice . I am selecting > Representation as Surface (not surface with edge). But I can't get rid of > Mesh (or wireframe) . Is there any way I can get rid of wire frame. > Thanks in advance > > > [image: Inline image 1] > > > Niaz > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 67453 bytes Desc: not available URL: From kirit_101 at yahoo.com Wed Aug 23 16:39:33 2017 From: kirit_101 at yahoo.com (Niaz M.) Date: Wed, 23 Aug 2017 15:39:33 -0500 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format In-Reply-To: References: Message-ID: Thanks Utkarsh: I think I have found the issue. If I select Interior Zone Surfaces while exporting from Fluent I get those wire mesh. if I un-select it, those wire mesh are gone . [image: Inline image 1] Niaz On Wed, Aug 23, 2017 at 1:33 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Can you share a sample dataset? That'll make it easier > > Thanks > Utkarsh > > On Tue, Aug 22, 2017 at 6:06 PM, Niaz M. via ParaView < > paraview at paraview.org> wrote: > >> Hello: >> I am exporting Fluent simulation results as Ensight gold case. Then >> importing in paraview. Then I am plotting a slice . I am selecting >> Representation as Surface (not surface with edge). But I can't get rid of >> Mesh (or wireframe) . Is there any way I can get rid of wire frame. >> Thanks in advance >> >> >> [image: Inline image 1] >> >> >> Niaz >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 45983 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 67453 bytes Desc: not available URL: From super_achie at hotmail.com Wed Aug 23 20:02:31 2017 From: super_achie at hotmail.com (A .) Date: Thu, 24 Aug 2017 00:02:31 +0000 Subject: [Paraview] Can I set textures for Glyph? Message-ID: Hi, For a Sphere filter it is possible to set its texture with TextureMaptoSphere. I was wondering if the same thing could be done for Glyph filters? In particular spherical glyphs. In the Properties menu of Glyph the Texture option is grayed out. Using a TextureMaptoSphere on a Glyph does not give the desired result. I had expected a "TextureMaptoGlyph" filter, but I cannot seem to find something like that. Best, jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From hongchao.wang2013 at gmail.com Thu Aug 24 00:49:48 2017 From: hongchao.wang2013 at gmail.com (HongchaoWang) Date: Thu, 24 Aug 2017 12:49:48 +0800 Subject: [Paraview] How does Paraview calculate the velocity gradient Message-ID: <032e01d31c94$6c099060$441cb120$@gmail.com> Hi, How does Paraview calculate the velocity gradient if I use filter "gradient of unstructured data set"? And what is the difference between using cell data and point data as input? For my case I am simulating an oscillatory flow inside a narrow channel, I would like to obtain the velocity gradient in order to calculate the shear stress across the channel. I applied the filter "gradient of unstructured data set" and use cell data as input. The results are reasonable for most region in the channel except for the velocity gradient in the first near-wall cell. The value is about half the analytical solution. Why is that? Many thanks, Wilson -------------- next part -------------- An HTML attachment was scrubbed... URL: From antech777 at gmail.com Thu Aug 24 02:01:53 2017 From: antech777 at gmail.com (Andrew) Date: Thu, 24 Aug 2017 09:01:53 +0300 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format In-Reply-To: References: Message-ID: Hello. Yes, there is a problem that exported CGNS doesnt consist BCs. So I create slices at appropriate positions limiting their span with Threshold filter by coordiates if needed. Another problem with BCs is that even if you have surfaces there may be very limited variables so you cannot average by mass flow that is absolutely unaccaptable. With slices you have all variables that are difined in fluid domain. More suitable and simple way is using CFD Post but it will consume a license. So I often postprocess "visual features" in ParaView and use CFD Post's Function Calculator for averaging, mass flow calculation on boundaries e.t.c. To my knowledge, there is no such functionality in ParaView (various types of averaging, convenient BC support, convenient multi-variant support, for example, if you need to open 3 separate cases and compute 10 quantities for each case, CFD Post will be one of best choices). But, apart from consuming a license, CFD Post is not so "feature-loaded" as ParaView. There is no Python Shell and only basic tools in CFD Post so use what is more appropriate for particular usecases. The thing that is called post processor in Fluent cannot be described in good words and easily can hang. Don't use it if you can. CFD Post and ParaView compared to this thing in Fluent are unrealistic good! 2017-08-23 17:14 GMT+03:00 Niaz M. via ParaView : > Hi Andrew: > Thanks for sharing your experience. Yes I have figure it out CGNS works > best so far when you want to export from Fluent. But one think I miss the > boundary name (or ID) in CGNS. Fluent doesn't write that info when you > export as CGNS . It only export fluid domain. > > I am a newbie in Paraview. If I want to share some sample dataset to > developer what will be best way. > > Niaz > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bencesomogyi at protonmail.com Thu Aug 24 02:51:12 2017 From: bencesomogyi at protonmail.com (Bence Somogyi) Date: Thu, 24 Aug 2017 02:51:12 -0400 Subject: [Paraview] paraview.exe disappears? Message-ID: Dear All, Using the latest version for Windows ["ParaView-5.4.1-Qt5-OpenGL2-MPI-Windows-64bit.zip "] I face the following problem: When I execute paraview.exe from the bin directory ParaView won't start, and the .exe file will disappear. Has anyone faced the same issue before? BR, Bence Somogyi -------------- next part -------------- An HTML attachment was scrubbed... URL: From bencesomogyi at protonmail.com Thu Aug 24 03:02:39 2017 From: bencesomogyi at protonmail.com (Bence Somogyi) Date: Thu, 24 Aug 2017 03:02:39 -0400 Subject: [Paraview] problems with cylinder slice Message-ID: Dear All, I have found a problem using the cylinder slice. The default axis for the cylinder is the y axis, with this setting the slice works as expected. When the axis is modified (e.g. x axis), the widget is updated correctly, but the slice itself is not. It only works, when "crinkle clip" is enabled. I have found the same behavior with the box slice The version I use is: ParaView-5.4.0-Qt5-OpenGL2-MPI-Windows-64bit BR, Bence Somogyi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Thu Aug 24 03:10:16 2017 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 24 Aug 2017 09:10:16 +0200 Subject: [Paraview] problems with cylinder slice In-Reply-To: References: Message-ID: Hello This is a bug in ParaView 5.4 and has been corrected already in the upcoming version, 5.4.1, soon to be released. Best Regards, Mathieu Westphal On Thu, Aug 24, 2017 at 9:02 AM, Bence Somogyi via ParaView < paraview at paraview.org> wrote: > Dear All, > > I have found a problem using the cylinder slice. The default axis for the > cylinder is the y axis, with this setting the slice works as expected. When > the axis is modified (e.g. x axis), the widget is updated correctly, but > the slice itself is not. It only works, when "crinkle clip" is enabled. > I have found the same behavior with the box slice > > The version I use is: ParaView-5.4.0-Qt5-OpenGL2-MPI-Windows-64bit > > BR, > Bence Somogyi > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antech777 at gmail.com Thu Aug 24 07:20:16 2017 From: antech777 at gmail.com (Andrew) Date: Thu, 24 Aug 2017 14:20:16 +0300 Subject: [Paraview] paraview.exe disappears? In-Reply-To: References: Message-ID: Hello. Looks like you have some antivirus-related problem. 2017-08-24 9:51 GMT+03:00 Bence Somogyi via ParaView : > Dear All, > > Using the latest version for Windows ["ParaView-5.4.1-Qt5-OpenGL2-MPI-Windows-64bit.zip > "] I face the following problem: When I execute paraview.exe from the bin > directory ParaView won't start, and the .exe file will disappear. > Has anyone faced the same issue before? > > BR, > Bence Somogyi > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Aug 24 09:23:23 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 24 Aug 2017 09:23:23 -0400 Subject: [Paraview] problems with cylinder slice In-Reply-To: References: Message-ID: On Thu, Aug 24, 2017 at 3:10 AM, Mathieu Westphal wrote: > Hello > > This is a bug in ParaView 5.4 and has been corrected already in the upcoming > version, 5.4.1, soon to be released. ParaView 5.4.1 has already been released :-) > > Best Regards, > > Mathieu Westphal > > On Thu, Aug 24, 2017 at 9:02 AM, Bence Somogyi via ParaView > wrote: >> >> Dear All, >> >> I have found a problem using the cylinder slice. The default axis for the >> cylinder is the y axis, with this setting the slice works as expected. When >> the axis is modified (e.g. x axis), the widget is updated correctly, but the >> slice itself is not. It only works, when "crinkle clip" is enabled. >> I have found the same behavior with the box slice >> >> The version I use is: ParaView-5.4.0-Qt5-OpenGL2-MPI-Windows-64bit >> >> BR, >> Bence Somogyi >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From A.T.T.McRae at bath.ac.uk Thu Aug 24 14:15:12 2017 From: A.T.T.McRae at bath.ac.uk (Andrew McRae) Date: Thu, 24 Aug 2017 19:15:12 +0100 Subject: [Paraview] solid white surface (with edges) in 3D via UI + large vector graphic pdfs Message-ID: Hi all, I think I am trying to do the same thing as http://public.kitware.com/ pipermail/paraview/2015-July/034441.html from two years ago: show a solid white 3D mesh, with black lines marking the cell edges, on a white background. I finally got what I wanted by following Cory's instructions in that thread, using the Python scripting window. *I can't seem to find a way to do this through the GUI options though... am I missing something?* Using a black wireframe on a white background almost does what I want, but I don't want the back of the mesh showing through the image... (it's a non-uniform mesh of the sphere, so seeing the back cells becomes confusing). vtu file, in case anyone is interested: https://www.dropbox.com/s/y3euop4nzurf9gf/ri-cs_0.vtu?dl=1 *Also, why are the generated vector images so large?* (Export Scene, turn off rasterization) The pdf produced by ParaView for the above vtu (no data, just the mesh, viewed from +Y) is over 2MB for a mesh with 6146 vertices, 6144 cells. At first I thought this was due to shading, but it has persisted even when making the cells fully white. Somehow, outputting as a .eps file (~1MB) and running epspdf on this generates a ~200KB .pdf, which is much more reasonable: https://www.dropbox.com/s/njavup5vwubsq8p/ri-cs.pdf?dl=1 This is all with ParaView 5.0.1. At various times I tried downloading Paraview 5.3-5.4, but there was no improvement in this area (and, IIRC, some regressions, such as glitchy pdfs). Thanks, Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Aug 24 17:26:37 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 24 Aug 2017 21:26:37 +0000 Subject: [Paraview] Windows Surface Book Message-ID: <5d884755ef424aff819a1d9234ac70d5@ES01AMSNLNT.srn.sandia.gov> I have a user that is having issues running ParaView on a Windows Surface Book. Has anyone else seen this? Any advice? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Aug 24 17:43:54 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 24 Aug 2017 17:43:54 -0400 Subject: [Paraview] Rendering/Screenshot with "deep color" (REPOST) In-Reply-To: References: Message-ID: Jonathan, As far as I know, no such a setting is not available in ParaView currently. It's not on our todo list. Feel free to report an issue at `https://gitlab.kitware.com/paraview/paraview/issues` so that it can be tackled in the future. Utkarsh On Wed, Aug 9, 2017 at 12:52 PM, Jonathan Borduas wrote: > Dear Paraviewers, > > As seen in the attached image, we can see the transitions between the > different grays that occur with a 24bits-per-pixel screenshot export of > ParaView. > While most image editing software and printer support 32bits-per-pixel such > as Ms Paint and Photoshop. > > Most GPU manufacturers call that ?deep color?. Some display already have > 30bpp/10bpc. > > > Is there a setting available to configure the image bit depth (Bit Per > Pixel, Bit Per Channel) in ParaView ? > If no, is there any short time plans to integrate the control over the bit > depth ? > > Best regards, > > Jonathan Borduas > > > > > _______________________________________________ > 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 kirit_101 at yahoo.com Fri Aug 25 11:14:23 2017 From: kirit_101 at yahoo.com (Niaz M.) Date: Fri, 25 Aug 2017 10:14:23 -0500 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format Message-ID: Hi Andrew: Thats a smart way to create Boundary. Just wondering if you have some curved boundary, how do you do it ? Niaz -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicholas.richmond at maine.edu Fri Aug 25 12:37:52 2017 From: nicholas.richmond at maine.edu (Nicholas Richmond) Date: Fri, 25 Aug 2017 12:37:52 -0400 Subject: [Paraview] Compiling ParaView for Windows x64 Release Message-ID: Greetings, I've been having some trouble building ParaView 5.4.1 on my system. I'm hoping a Windows-savvy user might be able to lend some insight. ParaView builds just fine under "Debug" mode, but when built as "Release," I get four errors signaling that "The procedure entry point...could not be located in the dynamic link library" for paraview.exe, vtkpqPython-pv5.4.dll, vtkpwWidgets-pv5.4.dll, and vtkpqCore-pv5.4.dll. The debugger shows: Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: 0xC0000139: Entry Point Not Found. Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: 0xC0000139: Entry Point Not Found. Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: 0xC0000139: Entry Point Not Found. Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: 0xC0000139: Entry Point Not Found. The thread 0x4fcc has exited with code -1073741511 (0xc0000139). The thread 0x6c7c has exited with code -1073741511 (0xc0000139). The thread 0x65a0 has exited with code -1073741511 (0xc0000139). The program '[15092] paraview.exe' has exited with code -1073741511 (0xc0000139) 'Entry Point Not Found'. In case it matters, the only thing I'm changing in CMake is the python version (to 3). Any help would be most appreciated. Thanks, Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Fri Aug 25 23:11:56 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Fri, 25 Aug 2017 22:11:56 -0500 Subject: [Paraview] Uncomplete display of large unstructured grid Message-ID: Hello all, With some self-written plugin I am generating rather large "unstructured grids". With a model with something more than 700'000 blocks I realized that on my Lenovo notebook I did not get a complete display of all the blocks, so I made tests with subsets of the data. It turns out that with less than 1000 blocks everything works fine, with 20'000 blocks there are already some "reductions" and finally with the full model even more: see the attached Powerpoint with screenshots (plus details about my system and the Paraview version). My question is now if there is possibly some kind of "graphic card overflow" happening? I could so far not test the software with the same model on another computer. And whatever the reason is: is there something that I can do about it? It is to say that the unstructured grid is a bit "unconventional" by the fact that often adjacent blocks do not have common edges and points, sharing thus only common partial faces. With this one possibility would be that Paraview cannot properly carry out certain optimizations that are relying on the fact that neighbor blocks "normally" (??) share a face, edges and points. However I do not know whether this is an issue or not!? In this case it might be an option to change the entire data set to a set of just cubes that happen to touch each other. Regards, Cornelis -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Uncomplete Display.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 516655 bytes Desc: not available URL: From rccm.kyoshimi at gmail.com Sat Aug 26 04:06:42 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Sat, 26 Aug 2017 17:06:42 +0900 Subject: [Paraview] Compiling ParaView for Windows x64 Release In-Reply-To: References: Message-ID: Hi Nick, You need to put the missing Qt DLLs in the same directory as paraview.exe built as "Release". Note that it seems to be difficult to know the missing DLLs' names since some of them are not displayed directly as warning messages. Probably the following DLLs may be missing: ------ Qt5Core.dll Qt5Gui.dll Qt5Help.dll Qt5Network.dll Qt5Sql.dll Qt5Widgets.dll ... Thanks, yoshimi 2017-08-26 1:37 GMT+09:00 Nicholas Richmond : > Greetings, > > I've been having some trouble building ParaView 5.4.1 on my system. I'm > hoping a Windows-savvy user might be able to lend some insight. ParaView > builds just fine under "Debug" mode, but when built as "Release," I get four > errors signaling that "The procedure entry point...could not be located in > the dynamic link library" for paraview.exe, vtkpqPython-pv5.4.dll, > vtkpwWidgets-pv5.4.dll, and vtkpqCore-pv5.4.dll. > > The debugger shows: > > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > 0xC0000139: Entry Point Not Found. > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > 0xC0000139: Entry Point Not Found. > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > 0xC0000139: Entry Point Not Found. > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > 0xC0000139: Entry Point Not Found. > The thread 0x4fcc has exited with code -1073741511 (0xc0000139). > The thread 0x6c7c has exited with code -1073741511 (0xc0000139). > The thread 0x65a0 has exited with code -1073741511 (0xc0000139). > The program '[15092] paraview.exe' has exited with code -1073741511 > (0xc0000139) 'Entry Point Not Found'. > > In case it matters, the only thing I'm changing in CMake is the python > version (to 3). > > Any help would be most appreciated. > Thanks, > Nick > > _______________________________________________ > 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 ken.martin at kitware.com Sat Aug 26 08:42:26 2017 From: ken.martin at kitware.com (Ken Martin) Date: Sat, 26 Aug 2017 08:42:26 -0400 Subject: [Paraview] Uncomplete display of large unstructured grid In-Reply-To: References: Message-ID: If possible can you try updating the Intel driver for your HD4000 and see if that makes a difference? https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000 On Fri, Aug 25, 2017 at 11:11 PM, Cornelis Bockem?hl < cornelis.bockemuehl at gmail.com> wrote: > Hello all, > > With some self-written plugin I am generating rather large "unstructured > grids". With a model with something more than 700'000 blocks I realized > that on my Lenovo notebook I did not get a complete display of all the > blocks, so I made tests with subsets of the data. It turns out that with > less than 1000 blocks everything works fine, with 20'000 blocks there are > already some "reductions" and finally with the full model even more: see > the attached Powerpoint with screenshots (plus details about my system and > the Paraview version). > > My question is now if there is possibly some kind of "graphic card > overflow" happening? I could so far not test the software with the same > model on another computer. > > And whatever the reason is: is there something that I can do about it? > > It is to say that the unstructured grid is a bit "unconventional" by the > fact that often adjacent blocks do not have common edges and points, > sharing thus only common partial faces. With this one possibility would be > that Paraview cannot properly carry out certain optimizations that are > relying on the fact that neighbor blocks "normally" (??) share a face, > edges and points. However I do not know whether this is an issue or not!? > In this case it might be an option to change the entire data set to a set > of just cubes that happen to touch each other. > > Regards, Cornelis > > -- > Cornelis Bockem?hl > Basel, Schweiz > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Sat Aug 26 17:37:17 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Sat, 26 Aug 2017 23:37:17 +0200 Subject: [Paraview] Uncomplete display of large unstructured grid In-Reply-To: References: Message-ID: Thanks Ken, this solved indeed already the problem! It was actually already my first guess, so I went to the Intel site and installed from there a tool that was supposed to check for potential driver updates - which found nothing! The driver that actually helped came finally from the Lenovo site. Regards, Cornelis Am 26.08.2017 07:42 schrieb "Ken Martin" : > If possible can you try updating the Intel driver for your HD4000 and see > if that makes a difference? > > https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000 > > > > On Fri, Aug 25, 2017 at 11:11 PM, Cornelis Bockem?hl < > cornelis.bockemuehl at gmail.com> wrote: > >> Hello all, >> >> With some self-written plugin I am generating rather large "unstructured >> grids". With a model with something more than 700'000 blocks I realized >> that on my Lenovo notebook I did not get a complete display of all the >> blocks, so I made tests with subsets of the data. It turns out that with >> less than 1000 blocks everything works fine, with 20'000 blocks there are >> already some "reductions" and finally with the full model even more: see >> the attached Powerpoint with screenshots (plus details about my system and >> the Paraview version). >> >> My question is now if there is possibly some kind of "graphic card >> overflow" happening? I could so far not test the software with the same >> model on another computer. >> >> And whatever the reason is: is there something that I can do about it? >> >> It is to say that the unstructured grid is a bit "unconventional" by the >> fact that often adjacent blocks do not have common edges and points, >> sharing thus only common partial faces. With this one possibility would be >> that Paraview cannot properly carry out certain optimizations that are >> relying on the fact that neighbor blocks "normally" (??) share a face, >> edges and points. However I do not know whether this is an issue or not!? >> In this case it might be an option to change the entire data set to a set >> of just cubes that happen to touch each other. >> >> Regards, Cornelis >> >> -- >> Cornelis Bockem?hl >> Basel, Schweiz >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From super_achie at hotmail.com Mon Aug 28 17:41:21 2017 From: super_achie at hotmail.com (A .) Date: Mon, 28 Aug 2017 21:41:21 +0000 Subject: [Paraview] Shortcut for Catalyst server connection Message-ID: Hi all, I was wondering if there is a faster way to open a Catalyst connection with ParaView. Currently I see myself doing the following routine "Catalyst" --> "Connect" --> "OK" --> "OK" --> "Pause Simulation" quite a lot. Is there a way to compress this into a single step? Best, Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Mon Aug 28 19:57:02 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 28 Aug 2017 19:57:02 -0400 Subject: [Paraview] Shortcut for Catalyst server connection In-Reply-To: References: Message-ID: Hi, You may be able to save a Python trace of those actions as a macro. This may require editing the Python trace output though as I'm not if all of those actions would be tracked in a trace. Best, Andy On Mon, Aug 28, 2017 at 5:41 PM, A . wrote: > Hi all, > > > I was wondering if there is a faster way to open a Catalyst connection > with ParaView. Currently I see myself doing the following routine > "Catalyst" --> "Connect" --> "OK" --> "OK" --> "Pause Simulation" quite a > lot. > > > Is there a way to compress this into a single step? > > > Best, > > Jimmy > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antech777 at gmail.com Tue Aug 29 08:40:15 2017 From: antech777 at gmail.com (Andrew) Date: Tue, 29 Aug 2017 15:40:15 +0300 Subject: [Paraview] Removing wire frame from Ensight Gold Case Data format In-Reply-To: References: Message-ID: Hello, Niaz. Sorry for being late. I usually process such features in CFD Post. If there is a long-time task (creating an analytical report) than I do most visual processing in ParaView and some things that a too non-convenient in ParaView I do in CFD Post. Fast processing like checking current simulation state is usually done in CFD Post. Possibly there are special types of curved slices in ParaView, I don't know... What is great in CFD Post that it perfectly understands boundaries including mass fluxes "from the box" for both CFX and Fluent (in ParaView I use a simple Python script to do it, and I need to tweak this script every time variable names change). 2017-08-25 18:14 GMT+03:00 Niaz M. via ParaView : > Hi Andrew: > Thats a smart way to create Boundary. Just wondering if you have some > curved boundary, how do you do it ? > > Niaz > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicholas.richmond at maine.edu Tue Aug 29 10:28:53 2017 From: nicholas.richmond at maine.edu (Nicholas Richmond) Date: Tue, 29 Aug 2017 10:28:53 -0400 Subject: [Paraview] Compiling ParaView for Windows x64 Release In-Reply-To: References: Message-ID: ?Hi Yoshimi, I copied the six DLLs from Qt into the Release directory and it worked! Thank you very much for your help with this. Best wishes, Nick? On Sat, Aug 26, 2017 at 4:06 AM, kenichiro yoshimi wrote: > Hi Nick, > > You need to put the missing Qt DLLs in the same directory as > paraview.exe built as "Release". Note that it seems to be difficult to > know the missing DLLs' names since some of them are not displayed > directly as warning messages. Probably the following DLLs may be > missing: > ------ > Qt5Core.dll > Qt5Gui.dll > Qt5Help.dll > Qt5Network.dll > Qt5Sql.dll > Qt5Widgets.dll > ... > > Thanks, > yoshimi > > 2017-08-26 1:37 GMT+09:00 Nicholas Richmond : > > Greetings, > > > > I've been having some trouble building ParaView 5.4.1 on my system. I'm > > hoping a Windows-savvy user might be able to lend some insight. ParaView > > builds just fine under "Debug" mode, but when built as "Release," I get > four > > errors signaling that "The procedure entry point...could not be located > in > > the dynamic link library" for paraview.exe, vtkpqPython-pv5.4.dll, > > vtkpwWidgets-pv5.4.dll, and vtkpqCore-pv5.4.dll. > > > > The debugger shows: > > > > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > > 0xC0000139: Entry Point Not Found. > > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > > 0xC0000139: Entry Point Not Found. > > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > > 0xC0000139: Entry Point Not Found. > > Exception thrown at 0x00007FFD18054B90 (ntdll.dll) in paraview.exe: > > 0xC0000139: Entry Point Not Found. > > The thread 0x4fcc has exited with code -1073741511 (0xc0000139). > > The thread 0x6c7c has exited with code -1073741511 (0xc0000139). > > The thread 0x65a0 has exited with code -1073741511 (0xc0000139). > > The program '[15092] paraview.exe' has exited with code -1073741511 > > (0xc0000139) 'Entry Point Not Found'. > > > > In case it matters, the only thing I'm changing in CMake is the python > > version (to 3). > > > > Any help would be most appreciated. > > Thanks, > > Nick > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at snumerics.com Tue Aug 29 10:42:03 2017 From: chrisneal at snumerics.com (Christopher Neal) Date: Tue, 29 Aug 2017 10:42:03 -0400 Subject: [Paraview] How does Paraview calculate the velocity gradient In-Reply-To: <032e01d31c94$6c099060$441cb120$@gmail.com> References: <032e01d31c94$6c099060$441cb120$@gmail.com> Message-ID: Hi Wilson, Perhaps this post contains information that may be helpful? http://public.kitware.com/pipermail/paraview/2009-January/010608.html Is the boundary layer in your simulation properly resolved? That steep gradient near the wall could be smeared out if the proper resolution isn't used. -Chris On Thu, Aug 24, 2017 at 12:49 AM, HongchaoWang wrote: > Hi, > > > > How does Paraview calculate the velocity gradient if I use filter ?gradient of unstructured data set?? And what is the difference between using cell data and point data as input? > > > > > > For my case I am simulating an oscillatory flow inside a narrow channel, I would like to obtain the velocity gradient in order to calculate the shear stress across the channel. I applied the filter ?gradient of unstructured data set? and use cell data as input. The results are reasonable for most region in the channel except for the velocity gradient in the first near-wall cell. The value is about half the analytical solution. Why is that? > > > > > > Many thanks, > > Wilson > > > > > _______________________________________________ > 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 > > -- Christopher Neal Research Engineer Streamline Numerics, Inc. https://www.snumerics.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Tue Aug 29 13:20:46 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Tue, 29 Aug 2017 19:20:46 +0200 Subject: [Paraview] Uncomplete display of large unstructured grid In-Reply-To: References: Message-ID: A little after a couple of days: It turns out that while the display is now complete, the program behaves now rather "ticklish" Doing too much of zooming, panning etc with a large model leads to crushes of the graphics driver (the message says explicitly!), the PV prog window becomes completely white and the program does not react any more; has to be killed with the task manager. So better save as the first action after a lengthy calculation, and only then try everytjing else to investigate the result. Regards, Cornelis Am 26.08.2017 23:37 schrieb "Cornelis Bockem?hl" < cornelis.bockemuehl at gmail.com>: > Thanks Ken, this solved indeed already the problem! > > It was actually already my first guess, so I went to the Intel site and > installed from there a tool that was supposed to check for potential driver > updates - which found nothing! > > The driver that actually helped came finally from the Lenovo site. > > Regards, Cornelis > > Am 26.08.2017 07:42 schrieb "Ken Martin" : > >> If possible can you try updating the Intel driver for your HD4000 and see >> if that makes a difference? >> >> https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000 >> >> >> >> On Fri, Aug 25, 2017 at 11:11 PM, Cornelis Bockem?hl < >> cornelis.bockemuehl at gmail.com> wrote: >> >>> Hello all, >>> >>> With some self-written plugin I am generating rather large "unstructured >>> grids". With a model with something more than 700'000 blocks I realized >>> that on my Lenovo notebook I did not get a complete display of all the >>> blocks, so I made tests with subsets of the data. It turns out that with >>> less than 1000 blocks everything works fine, with 20'000 blocks there are >>> already some "reductions" and finally with the full model even more: see >>> the attached Powerpoint with screenshots (plus details about my system and >>> the Paraview version). >>> >>> My question is now if there is possibly some kind of "graphic card >>> overflow" happening? I could so far not test the software with the same >>> model on another computer. >>> >>> And whatever the reason is: is there something that I can do about it? >>> >>> It is to say that the unstructured grid is a bit "unconventional" by the >>> fact that often adjacent blocks do not have common edges and points, >>> sharing thus only common partial faces. With this one possibility would be >>> that Paraview cannot properly carry out certain optimizations that are >>> relying on the fact that neighbor blocks "normally" (??) share a face, >>> edges and points. However I do not know whether this is an issue or not!? >>> In this case it might be an option to change the entire data set to a set >>> of just cubes that happen to touch each other. >>> >>> Regards, Cornelis >>> >>> -- >>> Cornelis Bockem?hl >>> Basel, Schweiz >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> >> -- >> Ken Martin PhD >> Distinguished Engineer >> Kitware Inc. >> 28 Corporate Drive >> Clifton Park NY 12065 >> >> This communication, including all attachments, contains confidential and >> legally privileged information, and it is intended only for the use of the >> addressee. Access to this email by anyone else is unauthorized. If you are >> not the intended recipient, any disclosure, copying, distribution or any >> action taken in reliance on it is prohibited and may be unlawful. If you >> received this communication in error please notify us immediately and >> destroy the original message. Thank you. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikos.beratlis at gmail.com Tue Aug 29 14:07:08 2017 From: nikos.beratlis at gmail.com (Nikolaos Beratlis) Date: Tue, 29 Aug 2017 14:07:08 -0400 Subject: [Paraview] Error reading XDMF file Message-ID: Hi, I have the following XDMF file: ../grid3dc_vxvyvz_VP.h5sp:/X ../grid3dc_vxvyvz_VP.h5sp:/Y ../grid3dc_vxvyvz_VP.h5sp:/Z ../Qcrit.0001.h5sp:/var3d I can read the file into Paraview 5.0 without any problems. When I try to read it with Paraview 4.1 I get the following error message: ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/Xdmf2/vtkXdmfHeavyData.cxx, line 1126 vtkXdmfReader (0x1177e62f0): Failed to read attribute data It seems that Paraview 4.1 reads the grid fine but it can't read the attribute. Any idea what is wrong? Regards, Nikos -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonardopessanha74 at gmail.com Tue Aug 29 15:48:21 2017 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Tue, 29 Aug 2017 16:48:21 -0300 Subject: [Paraview] ParaviewWeb Examples | Python Libraries | Import Error Message-ID: Hi! I am trying to build the example: > https://kitware.github.io/paraviewweb/examples/RemoteRenderer.html > I can't get past the python script that serves ParaView as server The errors I have encountered are: 'No module named wslink found' that I managed to fix installing wslink trough pip with 'pip install wslink' and copying the wslink folder to one of the folders in the path of pvpython Then the following one showed up to me from paraview.web import wslink as pv_wslink > ImportError: cannot import name wslink > At first I tought it was a circular dependencie problem and tried import paraview.web.pv_wslink > But got: File "/home/leo/remoteRenderer/pv_server.py", line 10, in > import paraview.web.pv_wslink > File "/opt/pv52/lib/python2.7/site-packages/paraview/web/pv_wslink.py", > line 6, in > from vtk.web import wslink as vtk_wslink > ImportError: cannot import name wslink > I believe I am missing an important step needed to code with pvpython without problems. Something like a 'build_essentials' package or 'paraview.web'/'vtk.web' ones How can I manage the *sys.path* of pvpython in order for it to find those modules(pv_wslink and vtk_wslink) that are missing? (Installing trough pip adds the modules to python executable and not to the pvpython one) Can someone help me with this? Thanks in advance! Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ, Brasil -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Tue Aug 29 15:54:54 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Tue, 29 Aug 2017 13:54:54 -0600 Subject: [Paraview] ParaviewWeb Examples | Python Libraries | Import Error In-Reply-To: References: Message-ID: Hi Leo, the documentation has been updated to match paraview/master from maybe 2 weeks ago. If you have an older version of ParaView, you would have to look at an older version of the ParaViewWeb documentation of that example. Or update your ParaView to the current master. Seb On Tue, Aug 29, 2017 at 1:48 PM, L?o Pessanha wrote: > Hi! > > I am trying to build the example: > >> https://kitware.github.io/paraviewweb/examples/RemoteRenderer.html >> > > I can't get past the python script that serves ParaView as server > > The errors I have encountered are: > > 'No module named wslink found' that I managed to fix installing wslink > trough pip with 'pip install wslink' and copying the wslink folder to one > of the folders in the path of pvpython > > Then the following one showed up to me > > from paraview.web import wslink as pv_wslink >> ImportError: cannot import name wslink >> > > At first I tought it was a circular dependencie problem and tried > > import paraview.web.pv_wslink >> > > But got: > > File "/home/leo/remoteRenderer/pv_server.py", line 10, in >> import paraview.web.pv_wslink >> File "/opt/pv52/lib/python2.7/site-packages/paraview/web/pv_wslink.py", >> line 6, in >> from vtk.web import wslink as vtk_wslink >> ImportError: cannot import name wslink >> > > > I believe I am missing an important step needed to code with pvpython > without problems. > > Something like a 'build_essentials' package or 'paraview.web'/'vtk.web' > ones > > How can I manage the *sys.path* of pvpython in order for it to find those > modules(pv_wslink and vtk_wslink) that are missing? (Installing trough pip > adds the modules to python executable and not to the pvpython one) > > Can someone help me with this? > > Thanks in advance! > > Leonardo Pessanha > Laboratory of Computational Methods in Engineering > Federal University of Rio de Janeiro - COPPE > Rio de Janeiro, RJ, Brasil > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kashifsaeed38 at gmail.com Wed Aug 30 03:43:36 2017 From: kashifsaeed38 at gmail.com (Muhammad Kashif Saeed) Date: Wed, 30 Aug 2017 12:43:36 +0500 Subject: [Paraview] 3D structured grid Message-ID: Hi everyone, Can you tell me that by using structured grid can I get the data from each cell of the grid from already completed simulation by using DEM technique? I have attached a picture of my simulation in which different particles are mixed each other. I want to calculate the mixing index to evaluate the mixing condition. I want to use subdomain mixing index for that purpose I have to divide this simulation into the number of subdomains to find the mixing index. Please let me know how can I create these subdomains in ParaView? are the 3D structured grid of required size can be used for that purpose? Regards -- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: after1.jpg Type: image/jpeg Size: 49361 bytes Desc: not available URL: From cornelis.bockemuehl at gmail.com Wed Aug 30 05:08:40 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=c3=bchl?=) Date: Wed, 30 Aug 2017 11:08:40 +0200 Subject: [Paraview] Uncomplete display of large unstructured grid In-Reply-To: References: Message-ID: Let me add a possible answer: Do you think it might be worthwile to try compiling Paraview with Mesa on Windows (version 7)? As it seems that the "native" OpenGL support is not really stable with the latest driver - is there a chance that going through Mesa 3D would improve the situation? Or is it even impossible, so I should better not even bother trying? Thanks for any helpful hint! I mean: It is possible to do some limited working with a "ticklish software" that tends to crash regularly (first of all: always save everything immediately!), but it is not really so much fun... Regards, Cornelis Am 29.08.2017 um 19:20 schrieb Cornelis Bockem?hl: > A little after a couple of days: It turns out that while the display > is now complete, the program behaves now rather "ticklish" Doing too > much of zooming, panning etc with a large model leads to crushes of > the graphics driver (the message says explicitly!), the PV prog window > becomes completely white and the program does not react any more; has > to be killed with the task manager. > > So better save as the first action after a lengthy calculation, and > only then try everytjing else to investigate the result. > > Regards, Cornelis > > Am 26.08.2017 23:37 schrieb "Cornelis Bockem?hl" > >: > > Thanks Ken, this solved indeed already the problem! > > It was actually already my first guess, so I went to the Intel > site and installed from there a tool that was supposed to check > for potential driver updates - which found nothing! > > The driver that actually helped came finally from the Lenovo site. > > Regards, Cornelis > > Am 26.08.2017 07:42 schrieb "Ken Martin" >: > > If possible can you try updating the Intel driver for your > HD4000 and see if that makes a difference? > > https://downloadcenter.intel.com/product/81499/Intel-HD-Graphics-4000 > > > > > On Fri, Aug 25, 2017 at 11:11 PM, Cornelis Bockem?hl > > wrote: > > Hello all, > > With some self-written plugin I am generating rather large > "unstructured grids". With a model with something more > than 700'000 blocks I realized that on my Lenovo notebook > I did not get a complete display of all the blocks, so I > made tests with subsets of the data. It turns out that > with less than 1000 blocks everything works fine, with > 20'000 blocks there are already some "reductions" and > finally with the full model even more: see the attached > Powerpoint with screenshots (plus details about my system > and the Paraview version). > > My question is now if there is possibly some kind of > "graphic card overflow" happening? I could so far not test > the software with the same model on another computer. > > And whatever the reason is: is there something that I can > do about it? > > It is to say that the unstructured grid is a bit > "unconventional" by the fact that often adjacent blocks do > not have common edges and points, sharing thus only common > partial faces. With this one possibility would be that > Paraview cannot properly carry out certain optimizations > that are relying on the fact that neighbor blocks > "normally" (??) share a face, edges and points. However I > do not know whether this is an issue or not!? In this case > it might be an option to change the entire data set to a > set of just cubes that happen to touch each other. > > Regards, Cornelis > > -- > Cornelis Bockem?hl > Basel, Schweiz > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki > at: http://paraview.org/Wiki/ParaView > > > Search the list archives at: > http://markmail.org/search/?q=ParaView > > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > This communication, including all attachments, contains > confidential and legally privileged information, and it is > intended only for the use of the addressee. Access to this > email by anyone else is unauthorized. If you are not the > intended recipient, any disclosure, copying, distribution or > any action taken in reliance on it is prohibited and may be > unlawful. If you received this communication in error please > notify us immediately and destroy the original message. Thank > you. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xgarnaud at gmail.com Wed Aug 30 10:27:53 2017 From: xgarnaud at gmail.com (Xavier Garnaud) Date: Wed, 30 Aug 2017 16:27:53 +0200 Subject: [Paraview] vtkClipDataSet in a programmable filter Message-ID: Dear all, I'd like to use the vtkClipDataSet in a programmable filter, but I can't find it it paraview.vtk, and the function from vtk does not seem to work. (I am using Paraview 5.2 or 5.4 on windows). Is the function available, or is there another way to perform the clip? Best regards, Xavier -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.borduas at caboma.com Wed Aug 30 10:38:20 2017 From: jonathan.borduas at caboma.com (Jonathan Borduas) Date: Wed, 30 Aug 2017 14:38:20 +0000 Subject: [Paraview] Rendering/Screenshot with "deep color" (REPOST) In-Reply-To: References: , Message-ID: Hi Utkarsh, Thank you for your answer I have created Issue #17678 Jonathan Borduas CTO, Caboma inc. ________________________________ From: Utkarsh Ayachit Sent: Thursday, August 24, 2017 5:43:54 PM To: Jonathan Borduas Cc: paraview at paraview.org Subject: Re: [Paraview] Rendering/Screenshot with "deep color" (REPOST) Jonathan, As far as I know, no such a setting is not available in ParaView currently. It's not on our todo list. Feel free to report an issue at `https://gitlab.kitware.com/paraview/paraview/issues` so that it can be tackled in the future. Utkarsh On Wed, Aug 9, 2017 at 12:52 PM, Jonathan Borduas wrote: > Dear Paraviewers, > > As seen in the attached image, we can see the transitions between the > different grays that occur with a 24bits-per-pixel screenshot export of > ParaView. > While most image editing software and printer support 32bits-per-pixel such > as Ms Paint and Photoshop. > > Most GPU manufacturers call that ?deep color?. Some display already have > 30bpp/10bpc. > > > Is there a setting available to configure the image bit depth (Bit Per > Pixel, Bit Per Channel) in ParaView ? > If no, is there any short time plans to integrate the control over the bit > depth ? > > Best regards, > > Jonathan Borduas > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From super_achie at hotmail.com Wed Aug 30 11:37:56 2017 From: super_achie at hotmail.com (A .) Date: Wed, 30 Aug 2017 15:37:56 +0000 Subject: [Paraview] Catalyst visualization not rendering without me clicking on the screen Message-ID: Dear community, Whenever I am trying to visualize something live (i.e. with Catalyst), the rendering view is not being updated unless I pan over the view with my mouse. I noticed that automatic rendering happens when I am dealing with a larger dataset. There seems to be some kind of a threshold for when to update the rendering view, based on the data size (or based on the amount of change in data). I tried increasing the CoProcessor frequency (coprocessor.SetUpdateFrequencies(freqs)), and also the EnableLiveVisualization(True, freq), but it didn't help. Anyone has a solution for this? Best, Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Aug 30 13:38:26 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 30 Aug 2017 13:38:26 -0400 Subject: [Paraview] vtkClipDataSet in a programmable filter In-Reply-To: References: Message-ID: This works for me in 5.4.1: import vtk plane = vtk.vtkPlane() plane.SetOrigin(0, 0, 0) plane.SetNormal(0, 1, 0) clip = vtk.vtkClipDataSet() clip.SetClipFunction(plane) clip.SetInputData(self.GetInput()) clip.Update() self.GetOutput().DeepCopy(clip.GetOutput()) Make sure you set the "Output Data Set Type" to "vtkUnstructuredGrid" before you first hit Apply. I believe there is a bug that does not let you change the output data set type after you first click Apply. HTH, Cory On Wed, Aug 30, 2017 at 10:27 AM, Xavier Garnaud wrote: > Dear all, > > I'd like to use the vtkClipDataSet in a programmable filter, but I can't > find it it paraview.vtk, and the function from vtk does not seem to work. (I > am using Paraview 5.2 or 5.4 on windows). > Is the function available, or is there another way to perform the clip? > > Best regards, > > Xavier > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From j.thunes at gmail.com Wed Aug 30 14:04:20 2017 From: j.thunes at gmail.com (James Thunes) Date: Wed, 30 Aug 2017 14:04:20 -0400 Subject: [Paraview] Visualization of time course data with legacy vtk format Message-ID: Hello all, Sometime between v5.1 and the latest version (v.5.4.1) the handling of legacy vtk files changed. I use paraview to visualize FE data that I've written in the legacy vtk format. Data is written with a separate file for each time step. The naming convention is: FileXXXX.vtk with XXXX the step number. When I click the open dialog with the latest version, I no longer see the files grouped as a file series (as described in this page from the wiki: Animating legacy VTK file series ). Is this new behavior expected, and if so, is there an alternative way to visualize time series data? Thanks, James -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Wed Aug 30 16:12:02 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Wed, 30 Aug 2017 22:12:02 +0200 Subject: [Paraview] Compute quartile from cell data Message-ID: If I use a "compute quartile" filter on a data object that is an unstructured grid with only cell data I do not seem to see any output data: Is this a bug or a feature? If I convert to point data first I can see something, or if I load the same data just as a plain table it works as well, but it does not work on the cell data. One possible logic not to allow this function for cell data could be the fact that cells can have very different size, so any statistics that works on number of cells might not seem appropriate. However, I can easily generate a histogram... -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Wed Aug 30 16:14:53 2017 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Wed, 30 Aug 2017 22:14:53 +0200 Subject: [Paraview] Compute quartile from cell data In-Reply-To: References: Message-ID: Sorry, I even stated it wrong: "compute quartile" works ONLY on row (i.e. table) data for me! Which really does not make a lot of sense for me (!??) 2017-08-30 22:12 GMT+02:00 Cornelis Bockem?hl : > If I use a "compute quartile" filter on a data object that is an > unstructured grid with only cell data I do not seem to see any output data: > Is this a bug or a feature? > > If I convert to point data first I can see something, or if I load the > same data just as a plain table it works as well, but it does not work on > the cell data. > > One possible logic not to allow this function for cell data could be the > fact that cells can have very different size, so any statistics that works > on number of cells might not seem appropriate. However, I can easily > generate a histogram... > > -- > Cornelis Bockem?hl > Basel, Schweiz > -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Aug 30 16:25:05 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 30 Aug 2017 16:25:05 -0400 Subject: [Paraview] Catalyst visualization not rendering without me clicking on the screen In-Reply-To: References: Message-ID: Hi Jimmy, I haven't heard of this issue before. Could you report an issue for this at https://gitlab.kitware.com/paraview/paraview/issues ? Thanks, Andy On Wed, Aug 30, 2017 at 11:37 AM, A . wrote: > Dear community, > > > Whenever I am trying to visualize something live (i.e. with Catalyst), the > rendering view is not being updated unless I pan over the view with my > mouse. > > > I noticed that automatic rendering happens when I am dealing with a larger > dataset. There seems to be some kind of a threshold for when to update the > rendering view, based on the data size (or based on the amount of change in > data). > > > I tried increasing the CoProcessor frequency (coprocessor.SetUpdateFrequencies(freqs)), > and also the EnableLiveVisualization(True, freq), but it didn't help. > > > Anyone has a solution for this? > > > Best, > > Jimmy > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Aug 30 20:05:12 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 31 Aug 2017 00:05:12 +0000 Subject: [Paraview] [EXTERNAL] Windows Surface Book In-Reply-To: <5d884755ef424aff819a1d9234ac70d5@ES01AMSNLNT.srn.sandia.gov> References: <5d884755ef424aff819a1d9234ac70d5@ES01AMSNLNT.srn.sandia.gov> Message-ID: <3167BCAA-CFC3-4CCF-84A2-5FFE2A97B7AC@sandia.gov> Ping? From: ParaView on behalf of W Scott Date: Thursday, August 24, 2017 at 3:27 PM To: "paraview at paraview.org" Subject: [EXTERNAL] [Paraview] Windows Surface Book I have a user that is having issues running ParaView on a Windows Surface Book. Has anyone else seen this? Any advice? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Aug 30 20:54:38 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 30 Aug 2017 20:54:38 -0400 Subject: [Paraview] [EXTERNAL] Windows Surface Book In-Reply-To: <3167BCAA-CFC3-4CCF-84A2-5FFE2A97B7AC@sandia.gov> References: <5d884755ef424aff819a1d9234ac70d5@ES01AMSNLNT.srn.sandia.gov> <3167BCAA-CFC3-4CCF-84A2-5FFE2A97B7AC@sandia.gov> Message-ID: I am afraid I have no experience with Surface book. Any more details? How does it fail? On Wed, Aug 30, 2017 at 8:05 PM, Scott, W Alan wrote: > Ping? > > > > From: ParaView on behalf of W Scott > > Date: Thursday, August 24, 2017 at 3:27 PM > To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] Windows Surface Book > > > > I have a user that is having issues running ParaView on a Windows Surface > Book. Has anyone else seen this? Any advice? > > > > Thanks, > > > > Alan > > > > > > > _______________________________________________ > 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 xgarnaud at gmail.com Thu Aug 31 02:32:10 2017 From: xgarnaud at gmail.com (Xavier Garnaud) Date: Thu, 31 Aug 2017 08:32:10 +0200 Subject: [Paraview] vtkClipDataSet in a programmable filter In-Reply-To: References: Message-ID: Dear Cory, Thank you for your help. In my case, this does not work and I get the following error message: Traceback (most recent call last): File "", line 22, in File "", line 12, in RequestData TypeError: SetInputData argument 1: method requires a VTK object Maybe it is related to the fact that when I create the first programmable filter, I get this error message: [image: Inline image 1] I use Paraview 5.4.1 on windows (I get the same behavior with Paraview 5.3.0) Best regards, Xavier On Wed, Aug 30, 2017 at 7:38 PM, Cory Quammen wrote: > This works for me in 5.4.1: > > import vtk > > plane = vtk.vtkPlane() > plane.SetOrigin(0, 0, 0) > plane.SetNormal(0, 1, 0) > > clip = vtk.vtkClipDataSet() > clip.SetClipFunction(plane) > clip.SetInputData(self.GetInput()) > clip.Update() > > self.GetOutput().DeepCopy(clip.GetOutput()) > > Make sure you set the "Output Data Set Type" to "vtkUnstructuredGrid" > before you first hit Apply. I believe there is a bug that does not let > you change the output data set type after you first click Apply. > > HTH, > Cory > > On Wed, Aug 30, 2017 at 10:27 AM, Xavier Garnaud > wrote: > > Dear all, > > > > I'd like to use the vtkClipDataSet in a programmable filter, but I can't > > find it it paraview.vtk, and the function from vtk does not seem to > work. (I > > am using Paraview 5.2 or 5.4 on windows). > > Is the function available, or is there another way to perform the clip? > > > > Best regards, > > > > Xavier > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Search the list archives at: http://markmail.org/search/?q=ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 26979 bytes Desc: not available URL: From pyj3004 at gmail.com Thu Aug 31 02:36:17 2017 From: pyj3004 at gmail.com (Enoch Yejune Pae) Date: Thu, 31 Aug 2017 15:36:17 +0900 Subject: [Paraview] Mac OS issue Message-ID: Hi everyone, I am trying to use the mip viewer in paraview. I tried installing it in two of my mac, but it turns out differently. One of my mac uses the El Capitan and my other one uses Sierra. Before I compiled the MIP viewer, in Sierra the original volume rendering itself works fine except for OSPRay Based one, showing the binary mask in 3D. However, in the El Capitan OS, the volumetric rendering just comes out as a chunk of a 3D box, and cannot see the binary mask of the inner side. Anyone else had a similar problem? Also, I looked up compiling mip viewer in Paraview, and I found out that I should build Paraview from source and modify a little bit in order to do that. So I?m keep trying to compile Paraview from Source, but keep failing. In my mac OS Sierra, Qt doesn?t even build in the first place. It?s keep saying that 'You cannot configure qt separately within a top-level build.? In my Linux machine, Qt is built fine, but Paraview doesn?t build. It keeps returning a message like 'could not find or locate the qt platform plugin minimal.? I?m looking everywhere to fix this, but cannot find a clue. Anyone ever encountered any of these situations? If you had please give me a hint on how you guys solved it. Thanks Best, Enoch Pae -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuhao at shuhaowu.com Thu Aug 31 18:00:22 2017 From: shuhao at shuhaowu.com (Shuhao Wu) Date: Thu, 31 Aug 2017 18:00:22 -0400 Subject: [Paraview] Extract region enclosed by isocontour surface and slice Message-ID: <126ce47f-29c0-50d0-b157-ee1d8e8cc543@shuhaowu.com> Hello all, I'm trying to find a maximum value in a region that's enclosed by an contour. I've attached an example of this, where the region of interest is within the black box and the grey surface. Of course, I would first filter the data to be bounded by the black box before proceeding to calculate the maximum value. I'm not sure if there is an automated way to do this. My idea is to extract the region based on the intersection of the outer most contour surface. After extracting the region, I can then find the maximum value and location fairly easily. However, I'm unsure how I can accomplish this as I don't see a filter that offers functionality like this as it would rely on two input: the contour and the original data. Any advice on this would be greatly appreciated. Thanks, Shuhao -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_2017-08-31_17-53-10.png Type: image/png Size: 175626 bytes Desc: not available URL: