From fixed-term.Lukas.Eberle2 at de.bosch.com Mon Dec 4 04:20:53 2017 From: fixed-term.Lukas.Eberle2 at de.bosch.com (FIXED-TERM Eberle Lukas (CC-PS/ECL5)) Date: Mon, 4 Dec 2017 09:20:53 +0000 Subject: [Paraview-developers] Visualize point cloud UDP stream Message-ID: <4265e0b40b5347d48d66b8048619581b@de.bosch.com> To whom it may concern, I would like to visualize a real-time point cloud stream in Paraview. Up to now I have implemented a "Programmable Source" in Paraview which receives a point cloud stream over UDP. The output of the source is selected as vtkTable. I process the source with a Table To Points filter and visualize it on screen. So far so good this is working very well. Currently the Python script of the "Programmable Source" is executed only once. What I want to do is to update the source on a given frequency. I tried to put my script into a while-loop but this is not working(Paraview hangs-up). Is there a possibility to execute the "Programmable Source" within a loop or a different way to visualize a UDP stream? Thank you in advance Best regards Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Dec 12 13:23:00 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 12 Dec 2017 18:23:00 +0000 Subject: [Paraview-developers] Load-Store Window Layout/ Restore Window Layout Message-ID: In ParaView, why are there File/ Load Window Layout and Save Window Layout, but we don't have a Restore Window Layout? Shouldn't we have one? Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Dec 12 13:26:26 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 12 Dec 2017 13:26:26 -0500 Subject: [Paraview-developers] Load-Store Window Layout/ Restore Window Layout In-Reply-To: References: Message-ID: What's restore window layout? Just restore to default? Can't the user just close the active layout tab? That creates a new empty one. We can change it create a new layout with default view created, if you'd like. On Tue, Dec 12, 2017 at 1:23 PM, Scott, W Alan wrote: > In ParaView, why are there File/ Load Window Layout and Save Window Layout, > but we don?t have a Restore Window Layout? Shouldn?t we have one? > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0807 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Tue Dec 12 13:33:39 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 12 Dec 2017 13:33:39 -0500 Subject: [Paraview-developers] Load-Store Window Layout/ Restore Window Layout In-Reply-To: References: Message-ID: Oops, nvm! I remembered wrong what save window layout did. Your suggestion makes sense. Utkarsh On Tue, Dec 12, 2017 at 1:26 PM, Utkarsh Ayachit wrote: > What's restore window layout? Just restore to default? Can't the user > just close the active layout tab? That creates a new empty one. We can > change it create a new layout with default view created, if you'd > like. > > On Tue, Dec 12, 2017 at 1:23 PM, Scott, W Alan wrote: >> In ParaView, why are there File/ Load Window Layout and Save Window Layout, >> but we don?t have a Restore Window Layout? Shouldn?t we have one? >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0807 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> >> >> The most exciting phrase to hear in science >> >> is not "Eureka!" but "That's funny..." -- Isaac Asimov >> >> --------------------------------------------------------- >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> From wascott at sandia.gov Tue Dec 12 13:34:23 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 12 Dec 2017 18:34:23 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Load-Store Window Layout/ Restore Window Layout In-Reply-To: References: Message-ID: <1eb34b9a50f8434e8b581bd1e05fcd63@ES01AMSNLNT.srn.sandia.gov> Utkarsh and I talked. Window layout is actually application layout (not in the view area). I will add a feature request, and have the feature renamed something more reasonable. Thanks > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Tuesday, December 12, 2017 11:26 AM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Load-Store Window Layout/ > Restore Window Layout > > What's restore window layout? Just restore to default? Can't the user just > close the active layout tab? That creates a new empty one. We can change it > create a new layout with default view created, if you'd like. > > On Tue, Dec 12, 2017 at 1:23 PM, Scott, W Alan wrote: > > In ParaView, why are there File/ Load Window Layout and Save Window > > Layout, but we don?t have a Restore Window Layout? Shouldn?t we have > one? > > > > > > > > Thanks, > > > > > > > > Alan > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0807 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > > > > > The most exciting phrase to hear in science > > > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > > > --------------------------------------------------------- > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > From wascott at sandia.gov Wed Dec 13 13:58:17 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 13 Dec 2017 18:58:17 +0000 Subject: [Paraview-developers] Broken superbuild Message-ID: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> Hi guys, Superbuild, and ParaView, appear broken. Here is what I get: [ 1%] Built target vtkWrapPython [ 1%] Built target vtklibharu Scanning dependencies of target vtkPVCatalystHierarchy Scanning dependencies of target vtkPVServerManagerApplicationHierarchy [ 1%] Built target vtktiff gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/vtkPVServerManagerCoreHierarchy.txt', needed by 'ParaViewCore/ServerManager/SMApplication/vtkPVServerManagerApplicationHierarchy.stamp.txt'. Stop. gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/vtkPVServerManagerApplicationHierarchy.txt', needed by 'CoProcessing/Catalyst/vtkPVCatalystHierarchy.stamp.txt'. Stop. CMakeFiles/Makefile2:20823: recipe for target 'ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplicationHierarchy.dir/all' failed gmake[4]: *** [ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplicationHierarchy.dir/all] Error 2 gmake[4]: *** Waiting for unfinished jobs.... CMakeFiles/Makefile2:20945: recipe for target 'CoProcessing/Catalyst/CMakeFiles/vtkPVCatalystHierarchy.dir/all' failed gmake[4]: *** [CoProcessing/Catalyst/CMakeFiles/vtkPVCatalystHierarchy.dir/all] Error 2 Scanning dependencies of target ArrowGlyphHierarchy Scanning dependencies of target EyeDomeLightingViewHierarchy [ 1%] Built target vtklibxml2 Scanning dependencies of target MomentsHierarchy Scanning dependencies of target GMVReaderHierarchy Scanning dependencies of target AnalyzeNIfTIIOHierarchy Scanning dependencies of target CDIReaderHierarchy Scanning dependencies of target GeodesicMeasurementHierarchy [ 1%] For ArrowGlyph - updating ArrowGlyphHierarchy.txt Any ideas? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Wed Dec 13 14:05:39 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 13 Dec 2017 14:05:39 -0500 Subject: [Paraview-developers] Broken superbuild In-Reply-To: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> Message-ID: There's some build issues right now using Unix Makefiles. Try using Ninja (e.g. cmake -G Ninja ...). If ninja isn't available on your system you can get it from https://github.com/ninja-build/ninja/releases. I did that today for Cori at NERSC and it worked fine for me. Cheers, Andy On Wed, Dec 13, 2017 at 1:58 PM, Scott, W Alan wrote: > Hi guys, > > Superbuild, and ParaView, appear broken. Here is what I get: > > > > [ 1%] Built target vtkWrapPython > > [ 1%] Built target vtklibharu > > Scanning dependencies of target vtkPVCatalystHierarchy > > Scanning dependencies of target vtkPVServerManagerApplicationHierarchy > > [ 1%] Built target vtktiff > > gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/ > vtkPVServerManagerCoreHierarchy.txt', needed by > 'ParaViewCore/ServerManager/SMApplication/vtkPVServerManagerApplicationHierarchy.stamp.txt'. > Stop. > > gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/ > vtkPVServerManagerApplicationHierarchy.txt', needed by > 'CoProcessing/Catalyst/vtkPVCatalystHierarchy.stamp.txt'. Stop. > > CMakeFiles/Makefile2:20823: recipe for target 'ParaViewCore/ServerManager/ > SMApplication/CMakeFiles/vtkPVServerManagerApplicationHierarchy.dir/all' > failed > > gmake[4]: *** [ParaViewCore/ServerManager/SMApplication/CMakeFiles/ > vtkPVServerManagerApplicationHierarchy.dir/all] Error 2 > > gmake[4]: *** Waiting for unfinished jobs.... > > CMakeFiles/Makefile2:20945: recipe for target 'CoProcessing/Catalyst/ > CMakeFiles/vtkPVCatalystHierarchy.dir/all' failed > > gmake[4]: *** [CoProcessing/Catalyst/CMakeFiles/ > vtkPVCatalystHierarchy.dir/all] Error 2 > > Scanning dependencies of target ArrowGlyphHierarchy > > Scanning dependencies of target EyeDomeLightingViewHierarchy > > [ 1%] Built target vtklibxml2 > > Scanning dependencies of target MomentsHierarchy > > Scanning dependencies of target GMVReaderHierarchy > > Scanning dependencies of target AnalyzeNIfTIIOHierarchy > > Scanning dependencies of target CDIReaderHierarchy > > Scanning dependencies of target GeodesicMeasurementHierarchy > > [ 1%] For ArrowGlyph - updating ArrowGlyphHierarchy.txt > > > > > > Any ideas? > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0807 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Dec 13 14:08:54 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 13 Dec 2017 19:08:54 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> Message-ID: <8224c63feff848bea6055a4c2acdece9@ES01AMSNLNT.srn.sandia.gov> Hmmm... I?m tempted to say I would rather wait for it to work correctly. My builds are basically the tests for the superbuild... Any ETA on a fix? If it takes too long, yes, I will try Ninja. Do I need root for Ninja? From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Wednesday, December 13, 2017 12:06 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Broken superbuild There's some build issues right now using Unix Makefiles. Try using Ninja (e.g. cmake -G Ninja ...). If ninja isn't available on your system you can get it from https://github.com/ninja-build/ninja/releases. I did that today for Cori at NERSC and it worked fine for me. Cheers, Andy On Wed, Dec 13, 2017 at 1:58 PM, Scott, W Alan > wrote: Hi guys, Superbuild, and ParaView, appear broken. Here is what I get: [ 1%] Built target vtkWrapPython [ 1%] Built target vtklibharu Scanning dependencies of target vtkPVCatalystHierarchy Scanning dependencies of target vtkPVServerManagerApplicationHierarchy [ 1%] Built target vtktiff gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/vtkPVServerManagerCoreHierarchy.txt', needed by 'ParaViewCore/ServerManager/SMApplication/vtkPVServerManagerApplicationHierarchy.stamp.txt'. Stop. gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/vtkPVServerManagerApplicationHierarchy.txt', needed by 'CoProcessing/Catalyst/vtkPVCatalystHierarchy.stamp.txt'. Stop. CMakeFiles/Makefile2:20823: recipe for target 'ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplicationHierarchy.dir/all' failed gmake[4]: *** [ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplicationHierarchy.dir/all] Error 2 gmake[4]: *** Waiting for unfinished jobs.... CMakeFiles/Makefile2:20945: recipe for target 'CoProcessing/Catalyst/CMakeFiles/vtkPVCatalystHierarchy.dir/all' failed gmake[4]: *** [CoProcessing/Catalyst/CMakeFiles/vtkPVCatalystHierarchy.dir/all] Error 2 Scanning dependencies of target ArrowGlyphHierarchy Scanning dependencies of target EyeDomeLightingViewHierarchy [ 1%] Built target vtklibxml2 Scanning dependencies of target MomentsHierarchy Scanning dependencies of target GMVReaderHierarchy Scanning dependencies of target AnalyzeNIfTIIOHierarchy Scanning dependencies of target CDIReaderHierarchy Scanning dependencies of target GeodesicMeasurementHierarchy [ 1%] For ArrowGlyph - updating ArrowGlyphHierarchy.txt Any ideas? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Dec 13 14:16:21 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Dec 2017 14:16:21 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: <8224c63feff848bea6055a4c2acdece9@ES01AMSNLNT.srn.sandia.gov> References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> <8224c63feff848bea6055a4c2acdece9@ES01AMSNLNT.srn.sandia.gov> Message-ID: > Any ETA on a fix? If it takes too long, yes, I will try Ninja. Ben is actively working on it. Utkarsh From wascott at sandia.gov Wed Dec 13 14:17:03 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 13 Dec 2017 19:17:03 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> <8224c63feff848bea6055a4c2acdece9@ES01AMSNLNT.srn.sandia.gov> Message-ID: Ben's a good guy. I'll wait. Alan > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Wednesday, December 13, 2017 12:16 PM > To: Scott, W Alan ; Boeckel, Ben (External Contacts) > > Cc: Bauer, Andy (External Contacts) ; paraview- > developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild > > > Any ETA on a fix? If it takes too long, yes, I will try Ninja. > > Ben is actively working on it. > > Utkarsh From wascott at sandia.gov Wed Dec 13 19:18:25 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 14 Dec 2017 00:18:25 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> Message-ID: Using Ninja and superbuild, I get the following: cMakeVars = -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.5.0-junk/Linux-cee-rhel6-x86_64 -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_BUILD_TYPE_paraview:STRING=Debug -Dparaview_SOURCE_SELECTION:STRING=source -Dsuperbuild_download_location:PATH=/projects/viz/paraview/src/sbTarballs/ -Dparaview_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.5.0-junk/ParaView5 -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DSUPERBUILD_ALLOW_DEBUG:BOOL=ON -DENABLE_vtkm:BOOL=OFF -DENABLE_ospray:BOOL=OFF -GNinja -DENABLE_paraview:BOOL=ON -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_qt:BOOL=ON -DENABLE_hdf5:BOOL=ON -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DENABLE_qt5:BOOL=ON ..... ..... -- Building projects: cxx11, zlib, ffmpeg, szip, hdf5, bzip2, png, python, numpy, boost, freetype, libxml2, gperf, fontconfig, qt5, visitbridge, silo, paraview -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: ENABLE_qt PARAVIEW_ALWAYS_SECURE_CONNECTION SUPERBUILD_ALLOW_DEBUG -- Build files have been written to: /projects/viz/paraview/ParaView/5.5.0-junk/Linux-cee-rhel6-x86_64/Build make: *** No targets specified and no makefile found. Stop. gmake: Nothing to be done for `install'. From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: Wednesday, December 13, 2017 12:06 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Broken superbuild There's some build issues right now using Unix Makefiles. Try using Ninja (e.g. cmake -G Ninja ...). If ninja isn't available on your system you can get it from https://github.com/ninja-build/ninja/releases. I did that today for Cori at NERSC and it worked fine for me. Cheers, Andy On Wed, Dec 13, 2017 at 1:58 PM, Scott, W Alan > wrote: Hi guys, Superbuild, and ParaView, appear broken. Here is what I get: [ 1%] Built target vtkWrapPython [ 1%] Built target vtklibharu Scanning dependencies of target vtkPVCatalystHierarchy Scanning dependencies of target vtkPVServerManagerApplicationHierarchy [ 1%] Built target vtktiff gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/vtkPVServerManagerCoreHierarchy.txt', needed by 'ParaViewCore/ServerManager/SMApplication/vtkPVServerManagerApplicationHierarchy.stamp.txt'. Stop. gmake[5]: *** No rule to make target 'lib/cmake/paraview-5.4/Modules/vtkPVServerManagerApplicationHierarchy.txt', needed by 'CoProcessing/Catalyst/vtkPVCatalystHierarchy.stamp.txt'. Stop. CMakeFiles/Makefile2:20823: recipe for target 'ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplicationHierarchy.dir/all' failed gmake[4]: *** [ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplicationHierarchy.dir/all] Error 2 gmake[4]: *** Waiting for unfinished jobs.... CMakeFiles/Makefile2:20945: recipe for target 'CoProcessing/Catalyst/CMakeFiles/vtkPVCatalystHierarchy.dir/all' failed gmake[4]: *** [CoProcessing/Catalyst/CMakeFiles/vtkPVCatalystHierarchy.dir/all] Error 2 Scanning dependencies of target ArrowGlyphHierarchy Scanning dependencies of target EyeDomeLightingViewHierarchy [ 1%] Built target vtklibxml2 Scanning dependencies of target MomentsHierarchy Scanning dependencies of target GMVReaderHierarchy Scanning dependencies of target AnalyzeNIfTIIOHierarchy Scanning dependencies of target CDIReaderHierarchy Scanning dependencies of target GeodesicMeasurementHierarchy [ 1%] For ArrowGlyph - updating ArrowGlyphHierarchy.txt Any ideas? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Dec 13 20:20:41 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Dec 2017 20:20:41 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> Message-ID: > -- Build files have been written to: > /projects/viz/paraview/ParaView/5.5.0-junk/Linux-cee-rhel6-x86_64/Build > make: *** No targets specified and no makefile found. Stop. > gmake: Nothing to be done for `install'. You have to run "ninja" or "ninja-build" to build instead of "make". Utkarsh From wascott at sandia.gov Wed Dec 13 21:04:20 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 14 Dec 2017 02:04:20 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> Message-ID: <2cb63840b8ab4ba8b12276964229a2d5@ES01AMSNLNT.srn.sandia.gov> Hmmm ... that does seem like an important detail Andy forgot... :-) Let me try, will let you know. > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Wednesday, December 13, 2017 6:21 PM > To: Scott, W Alan > Cc: Bauer, Andy (External Contacts) ; paraview- > developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild > > > -- Build files have been written to: > > /projects/viz/paraview/ParaView/5.5.0-junk/Linux-cee-rhel6-x86_64/Build > > make: *** No targets specified and no makefile found. Stop. > > gmake: Nothing to be done for `install'. > > You have to run "ninja" or "ninja-build" to build instead of "make". > > Utkarsh From wascott at sandia.gov Wed Dec 13 21:29:31 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 14 Dec 2017 02:29:31 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: <2cb63840b8ab4ba8b12276964229a2d5@ES01AMSNLNT.srn.sandia.gov> References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> <2cb63840b8ab4ba8b12276964229a2d5@ES01AMSNLNT.srn.sandia.gov> Message-ID: So far, so good. Building up a ninja storm. How do I do a make install? ninja install? > -----Original Message----- > From: Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] On Behalf Of Scott, W Alan > Sent: Wednesday, December 13, 2017 7:04 PM > To: Ayachit, Utkarsh (External Contacts) > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild > > Hmmm ... that does seem like an important detail Andy forgot... :-) > > Let me try, will let you know. > > > -----Original Message----- > > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > > Sent: Wednesday, December 13, 2017 6:21 PM > > To: Scott, W Alan > > Cc: Bauer, Andy (External Contacts) ; > > paraview- developers at paraview.org > > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild > > > > > -- Build files have been written to: > > > /projects/viz/paraview/ParaView/5.5.0-junk/Linux-cee-rhel6-x86_64/Bu > > > ild > > > make: *** No targets specified and no makefile found. Stop. > > > gmake: Nothing to be done for `install'. > > > > You have to run "ninja" or "ninja-build" to build instead of "make". > > > > Utkarsh > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview- > developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From utkarsh.ayachit at kitware.com Wed Dec 13 21:31:44 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Dec 2017 21:31:44 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> <2cb63840b8ab4ba8b12276964229a2d5@ES01AMSNLNT.srn.sandia.gov> Message-ID: Yes, ?ninja install? is it. Utkarsh > On Dec 13, 2017, at 9:29 PM, Scott, W Alan wrote: > > So far, so good. Building up a ninja storm. > > > How do I do a make install? ninja install? > > >> -----Original Message----- >> From: Paraview-developers [mailto:paraview-developers- >> bounces at paraview.org] On Behalf Of Scott, W Alan >> Sent: Wednesday, December 13, 2017 7:04 PM >> To: Ayachit, Utkarsh (External Contacts) >> Cc: paraview-developers at paraview.org >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild >> >> Hmmm ... that does seem like an important detail Andy forgot... :-) >> >> Let me try, will let you know. >> >>> -----Original Message----- >>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] >>> Sent: Wednesday, December 13, 2017 6:21 PM >>> To: Scott, W Alan >>> Cc: Bauer, Andy (External Contacts) ; >>> paraview- developers at paraview.org >>> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild >>> >>>> -- Build files have been written to: >>>> /projects/viz/paraview/ParaView/5.5.0-junk/Linux-cee-rhel6-x86_64/Bu >>>> ild >>>> make: *** No targets specified and no makefile found. Stop. >>>> gmake: Nothing to be done for `install'. >>> >>> You have to run "ninja" or "ninja-build" to build instead of "make". >>> >>> Utkarsh >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q=Paraview- >> developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers From andy.bauer at kitware.com Thu Dec 14 10:06:35 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 14 Dec 2017 10:06:35 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Broken superbuild In-Reply-To: References: <77b68925c91c4c859001e133b24fa284@ES01AMSNLNT.srn.sandia.gov> <2cb63840b8ab4ba8b12276964229a2d5@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, Yeah, in hindsight I guess that would have been helpful :) On Wed, Dec 13, 2017 at 9:31 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Yes, ?ninja install? is it. > > Utkarsh > > > On Dec 13, 2017, at 9:29 PM, Scott, W Alan wrote: > > > > So far, so good. Building up a ninja storm. > > > > > > How do I do a make install? ninja install? > > > > > >> -----Original Message----- > >> From: Paraview-developers [mailto:paraview-developers- > >> bounces at paraview.org] On Behalf Of Scott, W Alan > >> Sent: Wednesday, December 13, 2017 7:04 PM > >> To: Ayachit, Utkarsh (External Contacts) > >> Cc: paraview-developers at paraview.org > >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild > >> > >> Hmmm ... that does seem like an important detail Andy forgot... :-) > >> > >> Let me try, will let you know. > >> > >>> -----Original Message----- > >>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > >>> Sent: Wednesday, December 13, 2017 6:21 PM > >>> To: Scott, W Alan > >>> Cc: Bauer, Andy (External Contacts) ; > >>> paraview- developers at paraview.org > >>> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Broken superbuild > >>> > >>>> -- Build files have been written to: > >>>> /projects/viz/paraview/ParaView/5.5.0-junk/Linux-cee-rhel6-x86_64/Bu > >>>> ild > >>>> make: *** No targets specified and no makefile found. Stop. > >>>> gmake: Nothing to be done for `install'. > >>> > >>> You have to run "ninja" or "ninja-build" to build instead of "make". > >>> > >>> Utkarsh > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Search the list archives at: http://markmail.org/search/?q=Paraview- > >> developers > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview-developers > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michal.wozniak at caboma.com Thu Dec 14 15:31:31 2017 From: michal.wozniak at caboma.com (Michal Wozniak) Date: Thu, 14 Dec 2017 20:31:31 +0000 Subject: [Paraview-developers] Superbuild cpack Message-ID: Hi, I am trying to generate a windows installer using cpack but I have a small problem. My custom Paraview has a different name eg : test.exe. it is missing all the required dependencies * vtkpqApplicationComponents * vtkpqComponents * vtkpqPython * vtkpqCore * vtkpqWidgets * vtkUtilitiesPythonInitializer every other modules & plugins dll were correctly generated. I have already changed the string Paraview in paraview.bundle.common.cmake line 48 to append my own version to the paraview_executables variable Do I need to change a hardcoded string ?paraview? somewhere else ? Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Dec 14 15:55:44 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 14 Dec 2017 15:55:44 -0500 Subject: [Paraview-developers] Superbuild cpack In-Reply-To: References: Message-ID: <20171214205544.GA15786@megas.kitware.com> On Thu, Dec 14, 2017 at 20:31:31 +0000, Michal Wozniak wrote: > I am trying to generate a windows installer using cpack but I have a small problem. > > My custom Paraview has a different name eg : test.exe. it is missing > all the required dependencies > > * vtkpqApplicationComponents > * vtkpqComponents > * vtkpqPython > * vtkpqCore > * vtkpqWidgets > * vtkUtilitiesPythonInitializer > > every other modules & plugins dll were correctly generated. > > I have already changed the string Paraview in > paraview.bundle.common.cmake line 48 to append my own version to the > paraview_executables variable > > Do I need to change a hardcoded string ?paraview? somewhere else ? What platform(s)? --Ben From michal.wozniak at caboma.com Thu Dec 14 16:29:11 2017 From: michal.wozniak at caboma.com (Michal Wozniak) Date: Thu, 14 Dec 2017 21:29:11 +0000 Subject: [Paraview-developers] Superbuild cpack In-Reply-To: <20171214205544.GA15786@megas.kitware.com> References: , <20171214205544.GA15786@megas.kitware.com> Message-ID: On windows From: Ben Boeckel Sent: Thursday, December 14, 3:55 PM Subject: Re: [Paraview-developers] Superbuild cpack To: Michal Wozniak Cc: paraview-developers at paraview.org On Thu, Dec 14, 2017 at 20:31:31 +0000, Michal Wozniak wrote: > I am trying to generate a windows installer using cpack but I have a small problem. > > My custom Paraview has a different name eg : test.exe. it is missing > all the required dependencies > > * vtkpqApplicationComponents > * vtkpqComponents > * vtkpqPython > * vtkpqCore > * vtkpqWidgets > * vtkUtilitiesPythonInitializer > > every other modules & plugins dll were correctly generated. > > I have already changed the string Paraview in > paraview.bundle.common.cmake line 48 to append my own version to the > paraview_executables variable > > Do I need to change a hardcoded string ?paraview? somewhere else ? What platform(s)? --Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Dec 14 16:30:52 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 14 Dec 2017 21:30:52 +0000 Subject: [Paraview-developers] Lets rename Layout? Message-ID: Ken and I have been trying to figure out nomenclature for the File/ Load Window Layout. This is confusing with "Layout". We have concluded that "Layout" is the wrong name for the tab that shows at the upper left of the 3d window. How about we rename it? Here were some ideas Ken came up with: View Group (nah) View Tab (nah) Multi-View (better) Canvas (My favorite) View Region (probably not). Thoughts? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Dec 14 16:37:00 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 14 Dec 2017 16:37:00 -0500 Subject: [Paraview-developers] Lets rename Layout? In-Reply-To: References: Message-ID: Another option: * View Pane On Thu, Dec 14, 2017 at 4:30 PM, Scott, W Alan wrote: > Ken and I have been trying to figure out nomenclature for the File/ Load > Window Layout. This is confusing with ?Layout?. We have concluded that > ?Layout? is the wrong name for the tab that shows at the upper left of the > 3d window. How about we rename it? Here were some ideas Ken came up with: > > > > View Group (nah) > > View Tab (nah) > > Multi-View (better) > > Canvas (My favorite) > > View Region (probably not). > > > > Thoughts? > > > > Alan > > > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0807 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > From wascott at sandia.gov Thu Dec 14 19:47:42 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 15 Dec 2017 00:47:42 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Lets rename Layout? In-Reply-To: References: Message-ID: <316a93e460354b059c6431d4495eca0e@ES01AMSNLNT.srn.sandia.gov> My two favorites, so far, in order, are * Canvas * View Pane Alan > -----Original Message----- > From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] > Sent: Thursday, December 14, 2017 2:37 PM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Lets rename Layout? > > Another option: > > * View Pane > > > > On Thu, Dec 14, 2017 at 4:30 PM, Scott, W Alan wrote: > > Ken and I have been trying to figure out nomenclature for the File/ > > Load Window Layout. This is confusing with ?Layout?. We have > > concluded that ?Layout? is the wrong name for the tab that shows at > > the upper left of the 3d window. How about we rename it? Here were > some ideas Ken came up with: > > > > > > > > View Group (nah) > > > > View Tab (nah) > > > > Multi-View (better) > > > > Canvas (My favorite) > > > > View Region (probably not). > > > > > > > > Thoughts? > > > > > > > > Alan > > > > > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0807 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > > > > > The most exciting phrase to hear in science > > > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > > > --------------------------------------------------------- > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > https://paraview.org/mailman/listinfo/paraview-developers > > From ben.boeckel at kitware.com Fri Dec 15 10:42:19 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 15 Dec 2017 10:42:19 -0500 Subject: [Paraview-developers] Superbuild cpack In-Reply-To: References: <20171214205544.GA15786@megas.kitware.com> Message-ID: <20171215154219.GA25633@megas.kitware.com> On Thu, Dec 14, 2017 at 21:29:11 +0000, Michal Wozniak wrote: > On windows Adding it to the `paraview_executables` list should be enough there. The Windows installation logic is not as robust as macOS and Linux (though work there is underway), but if those libraries aren't installed, it probably means that they're not actually linked by your application. What does this output when run on `test.exe`? dumpbin /DEPENDENTS test.exe --Ben From michal.wozniak at caboma.com Fri Dec 15 11:43:31 2017 From: michal.wozniak at caboma.com (Michal Wozniak) Date: Fri, 15 Dec 2017 16:43:31 +0000 Subject: [Paraview-developers] Superbuild cpack In-Reply-To: <20171215154219.GA25633@megas.kitware.com> References: <20171214205544.GA15786@megas.kitware.com> , <20171215154219.GA25633@megas.kitware.com> Message-ID: Hi, This is my output : File Type: EXECUTABLE IMAGE Image has the following dependencies: vtkpqApplicationComponents-pv1.0.dll vtkUtilitiesPythonInitializer-pv1.0.dll vtkpqComponents-pv1.0.dll vtkpqPython-pv1.0.dll vtkpqCore-pv1.0.dll vtkpqWidgets-pv1.0.dll QtTesting.dll vtkPVServerManagerDefault-pv1.0.dll vtkPVServerManagerCore-pv1.0.dll vtkPVClientServerCoreRendering-pv1.0.dll vtkPVClientServerCoreCore-pv1.0.dll vtkPVCommon-pv1.0.dll Qt5Widgets.dll Qt5Gui.dll Qt5Network.dll Qt5Core.dll vtksys-pv1.0.dll USER32.dll MSVCP140.dll dwmapi.dll WTSAPI32.dll VCRUNTIME140.dll api-ms-win-crt-heap-l1-1-0.dll api-ms-win-crt-environment-l1-1-0.dll api-ms-win-crt-locale-l1-1-0.dll api-ms-win-crt-runtime-l1-1-0.dll api-ms-win-crt-string-l1-1-0.dll api-ms-win-crt-math-l1-1-0.dll api-ms-win-crt-stdio-l1-1-0.dll KERNEL32.dll SHELL32.dll Summary 2000 .data 1000 .gfids 2000 .pdata BA000 .rdata 2000 .reloc 5B000 .rsrc 19000 .text 1000 .tls Michal From: Ben Boeckel Sent: December 15, 2017 10:42 AM To: Michal Wozniak Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] Superbuild cpack On Thu, Dec 14, 2017 at 21:29:11 +0000, Michal Wozniak wrote: > On windows Adding it to the `paraview_executables` list should be enough there. The Windows installation logic is not as robust as macOS and Linux (though work there is underway), but if those libraries aren't installed, it probably means that they're not actually linked by your application. What does this output when run on `test.exe`? dumpbin /DEPENDENTS test.exe --Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Fri Dec 15 16:23:51 2017 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 15 Dec 2017 16:23:51 -0500 Subject: [Paraview-developers] Superbuild cpack In-Reply-To: References: <20171214205544.GA15786@megas.kitware.com> <20171215154219.GA25633@megas.kitware.com> Message-ID: <20171215212351.GA10754@megas.kitware.com> On Fri, Dec 15, 2017 at 16:43:31 +0000, Michal Wozniak wrote: > vtkpqApplicationComponents-pv1.0.dll > vtkUtilitiesPythonInitializer-pv1.0.dll > vtkpqComponents-pv1.0.dll > vtkpqPython-pv1.0.dll > vtkpqCore-pv1.0.dll > vtkpqWidgets-pv1.0.dll So these are the missing ones... > QtTesting.dll > vtkPVServerManagerDefault-pv1.0.dll > vtkPVServerManagerCore-pv1.0.dll > vtkPVClientServerCoreRendering-pv1.0.dll > vtkPVClientServerCoreCore-pv1.0.dll > vtkPVCommon-pv1.0.dll > Qt5Widgets.dll > Qt5Gui.dll > Qt5Network.dll > Qt5Core.dll > vtksys-pv1.0.dll > USER32.dll > MSVCP140.dll > dwmapi.dll > WTSAPI32.dll > VCRUNTIME140.dll > api-ms-win-crt-heap-l1-1-0.dll > api-ms-win-crt-environment-l1-1-0.dll > api-ms-win-crt-locale-l1-1-0.dll > api-ms-win-crt-runtime-l1-1-0.dll > api-ms-win-crt-string-l1-1-0.dll > api-ms-win-crt-math-l1-1-0.dll > api-ms-win-crt-stdio-l1-1-0.dll > KERNEL32.dll > SHELL32.dll ...but these are installed (well, except for some system ones)? If you look at the output from CPack, is there anything mentioning the missing libraries that looks like an error of some kind that isn't being caught as an error? --Ben From wascott at sandia.gov Mon Dec 18 13:15:43 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 18 Dec 2017 18:15:43 +0000 Subject: [Paraview-developers] CMake change logs Message-ID: <21a191fed73e4a388c886655a6833817@ES01AMSNLNT.srn.sandia.gov> I have a request for the change logs/ revision history/ release dates for CMake. Where is this information? Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Dec 18 13:57:21 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Dec 2017 13:57:21 -0500 Subject: [Paraview-developers] CMake change logs In-Reply-To: <21a191fed73e4a388c886655a6833817@ES01AMSNLNT.srn.sandia.gov> References: <21a191fed73e4a388c886655a6833817@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, In recent years, the releases and changed logs have been posted to the Kitware blog: https://blog.kitware.com/tag/CMake/ The dates of the blog posts are within a day or two of the release of the discussed CMake version. You can also find the change logs in the CMake documentation at https://cmake.org/cmake/help/latest/release/index.html These notes do not include release dates. Hope that helps, Cory On Mon, Dec 18, 2017 at 1:15 PM, Scott, W Alan wrote: > I have a request for the change logs/ revision history/ release dates for > CMake. Where is this information? > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0807 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Dec 18 14:55:39 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 18 Dec 2017 19:55:39 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: CMake change logs In-Reply-To: References: <21a191fed73e4a388c886655a6833817@ES01AMSNLNT.srn.sandia.gov> Message-ID: <859cf92b4c364c659b453802aecfc9ee@ES01AMSNLNT.srn.sandia.gov> Perfect. Alan From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Monday, December 18, 2017 11:57 AM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] CMake change logs Alan, In recent years, the releases and changed logs have been posted to the Kitware blog: https://blog.kitware.com/tag/CMake/ The dates of the blog posts are within a day or two of the release of the discussed CMake version. You can also find the change logs in the CMake documentation at https://cmake.org/cmake/help/latest/release/index.html These notes do not include release dates. Hope that helps, Cory On Mon, Dec 18, 2017 at 1:15 PM, Scott, W Alan > wrote: I have a request for the change logs/ revision history/ release dates for CMake. Where is this information? Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: https://paraview.org/mailman/listinfo/paraview-developers -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Dec 18 18:37:21 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 18 Dec 2017 23:37:21 +0000 Subject: [Paraview-developers] Color legend presets Message-ID: I would like to propose that we reorder the color legends presets as follows: * Add an advanced icon. Default will get rid of everything other than the first page. Increase the size of the Choose Preset to show all of the default list. * In Advanced, add sub menus. These should be Common, Rainbow variant, double ended, dark to light, misc., etc. * Default will look like this. Note that for the most part I didn't invert any maps, since there is already a button to do this. * Cool to Warm * Cool to Warm (Extended) * Viridis * Plasma * Inferno * Magma * Black-Body Radiation * X-Ray * Gray Scale * Cold and Hot * Black, blue and white * Black, orange and white * 2hot * Rainbow Desaturated * erdc_rainbow_bright * erdc_rainbow_dark * Jet * Get rid of Rainbow Blended White, Gray and Black. These were things I tried, and didn't work, with our lighting model. Get rid of the second erdc_rainbow_bright/dark Get rid of coolwarm. It is Cool to Warm, which we already have. Notice that I pushed normal Rainbow to be advanced only. Thoughts? -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron.helser at kitware.com Tue Dec 19 11:06:37 2017 From: aron.helser at kitware.com (Aron Helser) Date: Tue, 19 Dec 2017 11:06:37 -0500 Subject: [Paraview-developers] Color legend presets In-Reply-To: References: Message-ID: Sounds like a great idea to me - the long colormap list gives no guidance to users. I agree that rainbow and other perceptually troublesome colormaps should be advanced (or removed). IIRC these are designed to have uniform or linear perceptual brightness? What about the others? - Viridis - Plasma - Inferno - Magma I think we'd have to decide what to do with categorical colormaps as well. Regards, Aron On Mon, Dec 18, 2017 at 6:37 PM, Scott, W Alan wrote: > I would like to propose that we reorder the color legends presets as > follows: > > > > - Add an advanced icon. Default will get rid of everything other than > the first page. Increase the size of the Choose Preset to show all of the > default list. > - In Advanced, add sub menus. These should be Common, Rainbow > variant, double ended, dark to light, misc., etc. > - Default will look like this. Note that for the most part I didn?t > invert any maps, since there is already a button to do this. > - Cool to Warm > - Cool to Warm (Extended) > - Viridis > - Plasma > - Inferno > - Magma > - Black-Body Radiation > - X-Ray > - Gray Scale > - Cold and Hot > - Black, blue and white > - Black, orange and white > - 2hot > - Rainbow Desaturated > - erdc_rainbow_bright > - erdc_rainbow_dark > - Jet > - > > > > Get rid of Rainbow Blended White, Gray and Black. These were things I > tried, and didn?t work, with our lighting model. > > Get rid of the second erdc_rainbow_bright/dark > > Get rid of coolwarm. It is Cool to Warm, which we already have. > > Notice that I pushed normal Rainbow to be advanced only. > > > > Thoughts? > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0807 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > > > The most exciting phrase to hear in science > > is not "Eureka!" but "That's funny..." -- Isaac Asimov > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > https://paraview.org/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Dec 19 12:50:32 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 19 Dec 2017 17:50:32 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Color legend presets In-Reply-To: References: Message-ID: <3f7ef8e24e1049fd9ec2669cf17898cf@ES01AMSNLNT.srn.sandia.gov> Just to reiterate here (a thread I have presented to a more limited, but very vocal audience), we NEVER will be able to remove Rainbow. There are cases it is not just the best colormap, but the only color map that fills requirements. If a customer is trying to compare screenshots or movies against historical runs, and these historical runs were Rainbow, Rainbow is the best color map. Further, if Rainbow is contractually required, we will lose users if we don?t present Rainbow as an option. But, having said that, let?s make it easy to do the right thing, and harder to do stupid stuff (such as use Rainbow as default). Here is a good writeup on the four matplotlib colormaps: https://bids.github.io/colormap/. Note that they are both perceptually uniform (not necessarily with regards to brightness), and are also very good for color blind folks. Here?s another good writeup on colormaps (from the good folks at matplotlib): https://matplotlib.org/users/colormaps.html Alan From: Aron Helser [mailto:aron.helser at kitware.com] Sent: Tuesday, December 19, 2017 9:07 AM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Color legend presets Sounds like a great idea to me - the long colormap list gives no guidance to users. I agree that rainbow and other perceptually troublesome colormaps should be advanced (or removed). IIRC these are designed to have uniform or linear perceptual brightness? What about the others? * Viridis * Plasma * Inferno * Magma I think we'd have to decide what to do with categorical colormaps as well. Regards, Aron On Mon, Dec 18, 2017 at 6:37 PM, Scott, W Alan > wrote: I would like to propose that we reorder the color legends presets as follows: * Add an advanced icon. Default will get rid of everything other than the first page. Increase the size of the Choose Preset to show all of the default list. * In Advanced, add sub menus. These should be Common, Rainbow variant, double ended, dark to light, misc., etc. * Default will look like this. Note that for the most part I didn?t invert any maps, since there is already a button to do this. * Cool to Warm * Cool to Warm (Extended) * Viridis * Plasma * Inferno * Magma * Black-Body Radiation * X-Ray * Gray Scale * Cold and Hot * Black, blue and white * Black, orange and white * 2hot * Rainbow Desaturated * erdc_rainbow_bright * erdc_rainbow_dark * Jet * Get rid of Rainbow Blended White, Gray and Black. These were things I tried, and didn?t work, with our lighting model. Get rid of the second erdc_rainbow_bright/dark Get rid of coolwarm. It is Cool to Warm, which we already have. Notice that I pushed normal Rainbow to be advanced only. Thoughts? -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: https://paraview.org/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Dec 20 13:25:59 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 20 Dec 2017 18:25:59 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Color legend presets In-Reply-To: <6283F383-EBD5-41A0-8493-486A20BE4CD0@me.com> References: <3f7ef8e24e1049fd9ec2669cf17898cf@ES01AMSNLNT.srn.sandia.gov> <6283F383-EBD5-41A0-8493-486A20BE4CD0@me.com> Message-ID: <9ff79bcbb4ca472aad25673a516c8014@ES03AMSNLNT.srn.sandia.gov> Adding the ParaView developers back into this thread. From: Francesca Samsel [mailto:figs at me.com] Sent: Wednesday, December 20, 2017 11:21 AM To: Bujack, Roxana Barbara (LANL) ; Scott, W Alan Cc: Nouanesengsy, Boonthanome (LANL) ; aron.helser at kitware.com; Moreland, Kenneth ; Patchett, John M. (LANL) ; Ahrens, James Paul (LANL) ; Rogers, David Honegger (LANL) Subject: Re: [Paraview-developers] [EXTERNAL] Re: Color legend presets Alan, We have been working on the colormap issue for over four years now. It is complex. I would suggest that the main voices sit down together with KitWare, and documentation from folks who have weighed in. One option - I will be coming out your way in mid-February for the ParaView tutorial. Would it make sense to put together an in person / skype meeting and have a discussion about color? We could meet either in ABQ or at LANL. I agree with the ParaView committee that any changes made need to be well considered and made once as opposed to smaller sequential changes. My two cents? We need the rainbow, de-sat rainbow, jet and Moreland cool warm. Beyond that we should look for a range of maps that produce accurate results on differing fronts - discrimination, uniformity, specialized use, etc. A shortened list is definitely needed but it needs to be carefully selected to include a variety of maps that best addresses a variety of needs. It might also be helpful to look at the Colormap UI to see if it could be reconfigured to categorize colormaps beyond the standards via an advanced option. Terry Turton and Colin Ware have done a good bit of perceptual testing. Looking at their findings will help guide the way to providing a relevant range of maps. Recommendations are another topic to discuss. We have tutorials up on SciVisColor.org and are working on a new series of videos specifically designed to help scientists quickly and easily select a colormap based on their data and task. Matplot lib has great documentation. We are updating our documentation. Check back mid to late January when we hope to have the updates complete. On a side note, I presented last week at AGU. The scientific community is clambering for help on the topic. Figuring out how we can best provide the guidance and broaden our impact is also worth discussing. Best to all, Francesca On Dec 20, 2017, at 11:49 AM, Bujack, Roxana Barbara > wrote: I agree that we should shorten/reorganize the list, but also that the rainbow needs to stay there. Best, Roxana On Dec 20, 2017, at 10:42 AM, Boonthanome Nouanesengsy > wrote: Hey, Not sure if you're on the Paraview developer's mailling list, but there is a discussion of changing the colormaps options in Paraview. Maybe you have opinions on this. cheers, Boonth -------- Forwarded Message -------- Subject: Re: [Paraview-developers] [EXTERNAL] Re: Color legend presets Date: Tue, 19 Dec 2017 17:50:32 +0000 From: Scott, W Alan To: Aron Helser CC: paraview-developers at paraview.org Just to reiterate here (a thread I have presented to a more limited, but very vocal audience), we NEVER will be able to remove Rainbow. There are cases it is not just the best colormap, but the only color map that fills requirements. If a customer is trying to compare screenshots or movies against historical runs, and these historical runs were Rainbow, Rainbow is the best color map. Further, if Rainbow is contractually required, we will lose users if we don?t present Rainbow as an option. But, having said that, let?s make it easy to do the right thing, and harder to do stupid stuff (such as use Rainbow as default). Here is a good writeup on the four matplotlib colormaps: https://bids.github.io/colormap/. Note that they are both perceptually uniform (not necessarily with regards to brightness), and are also very good for color blind folks. Here?s another good writeup on colormaps (from the good folks at matplotlib):https://matplotlib.org/users/colormaps.html Alan From: Aron Helser [mailto:aron.helser at kitware.com] Sent: Tuesday, December 19, 2017 9:07 AM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Color legend presets Sounds like a great idea to me - the long colormap list gives no guidance to users. I agree that rainbow and other perceptually troublesome colormaps should be advanced (or removed). IIRC these are designed to have uniform or linear perceptual brightness? What about the others? * Viridis * Plasma * Inferno * Magma I think we'd have to decide what to do with categorical colormaps as well. Regards, Aron On Mon, Dec 18, 2017 at 6:37 PM, Scott, W Alan > wrote: I would like to propose that we reorder the color legends presets as follows: * Add an advanced icon. Default will get rid of everything other than the first page. Increase the size of the Choose Preset to show all of the default list. * In Advanced, add sub menus. These should be Common, Rainbow variant, double ended, dark to light, misc., etc. * Default will look like this. Note that for the most part I didn?t invert any maps, since there is already a button to do this. * Cool to Warm * Cool to Warm (Extended) * Viridis * Plasma * Inferno * Magma * Black-Body Radiation * X-Ray * Gray Scale * Cold and Hot * Black, blue and white * Black, orange and white * 2hot * Rainbow Desaturated * erdc_rainbow_bright * erdc_rainbow_dark * Jet * Get rid of Rainbow Blended White, Gray and Black. These were things I tried, and didn?t work, with our lighting model. Get rid of the second erdc_rainbow_bright/dark Get rid of coolwarm. It is Cool to Warm, which we already have. Notice that I pushed normal Rainbow to be advanced only. Thoughts? -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0807 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 The most exciting phrase to hear in science is not "Eureka!" but "That's funny..." -- Isaac Asimov --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: https://paraview.org/mailman/listinfo/paraview-developers Francesca Samsel M.F.A. Research Associate Center for Agile Technology University of Texas at Austin figs at cat.utexas.edu 512-232-5487 www.francescasamsel.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From michal.wozniak at caboma.com Fri Dec 22 16:02:24 2017 From: michal.wozniak at caboma.com (Michal Wozniak) Date: Fri, 22 Dec 2017 21:02:24 +0000 Subject: [Paraview-developers] Superbuild cpack In-Reply-To: <20171215212351.GA10754@megas.kitware.com> References: <20171214205544.GA15786@megas.kitware.com> <20171215154219.GA25633@megas.kitware.com> , <20171215212351.GA10754@megas.kitware.com> Message-ID: Hi, I had to view the cpack logs a couple of times but I found out it couldn?t find 1 external library thus blocking the rest. The missing dependency was only giving a warning. When I added the location to my path environment, the CPACK was successful. Thank a lot for your help! Michal ________________________________ From: Ben Boeckel Sent: Friday, December 15, 2017 4:23:51 PM To: Michal Wozniak Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] Superbuild cpack On Fri, Dec 15, 2017 at 16:43:31 +0000, Michal Wozniak wrote: > vtkpqApplicationComponents-pv1.0.dll > vtkUtilitiesPythonInitializer-pv1.0.dll > vtkpqComponents-pv1.0.dll > vtkpqPython-pv1.0.dll > vtkpqCore-pv1.0.dll > vtkpqWidgets-pv1.0.dll So these are the missing ones... > QtTesting.dll > vtkPVServerManagerDefault-pv1.0.dll > vtkPVServerManagerCore-pv1.0.dll > vtkPVClientServerCoreRendering-pv1.0.dll > vtkPVClientServerCoreCore-pv1.0.dll > vtkPVCommon-pv1.0.dll > Qt5Widgets.dll > Qt5Gui.dll > Qt5Network.dll > Qt5Core.dll > vtksys-pv1.0.dll > USER32.dll > MSVCP140.dll > dwmapi.dll > WTSAPI32.dll > VCRUNTIME140.dll > api-ms-win-crt-heap-l1-1-0.dll > api-ms-win-crt-environment-l1-1-0.dll > api-ms-win-crt-locale-l1-1-0.dll > api-ms-win-crt-runtime-l1-1-0.dll > api-ms-win-crt-string-l1-1-0.dll > api-ms-win-crt-math-l1-1-0.dll > api-ms-win-crt-stdio-l1-1-0.dll > KERNEL32.dll > SHELL32.dll ...but these are installed (well, except for some system ones)? If you look at the output from CPack, is there anything mentioning the missing libraries that looks like an error of some kind that isn't being caught as an error? --Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: