From M.Deij at marin.nl Wed Aug 8 04:13:29 2018 From: M.Deij at marin.nl (Deij-van Rijswijk, Menno) Date: Wed, 8 Aug 2018 08:13:29 +0000 Subject: [Paraview-developers] Hierarchy projects always rebuild Message-ID: <982742389402437589b270a7f0675be3@MAR190n2.marin.local> Hi, I?m developing some new functionality using Visual Studio and I find that when I want to do an interactive debug session on a just-built project, it takes a long time until the debugging actually starts. In the output window I find the output below. It looks like the hierarchy.txt files are constantly being updated? 1>------ Build started: Project: vtkCommonCoreHierarchy, Configuration: Debug x64 ------ 1>For vtkCommonCore - updating vtkCommonCoreHierarchy.txt 2>------ Build started: Project: vtkCommonMathHierarchy, Configuration: Debug x64 ------ 3>------ Build started: Project: vtkCommonSystemHierarchy, Configuration: Debug x64 ------ 4>------ Build started: Project: vtkClientServerHierarchy, Configuration: Debug x64 ------ 2>For vtkCommonMath - updating vtkCommonMathHierarchy.txt 3>For vtkCommonSystem - updating vtkCommonSystemHierarchy.txt 4>For vtkClientServer - updating vtkClientServerHierarchy.txt 5>------ Build started: Project: vtkCommonMiscHierarchy, Configuration: Debug x64 ------ 6>------ Build started: Project: vtkCommonTransformsHierarchy, Configuration: Debug x64 ------ 6>For vtkCommonTransforms - updating vtkCommonTransformsHierarchy.txt 5>For vtkCommonMisc - updating vtkCommonMiscHierarchy.txt 7>------ Build started: Project: vtkCommonDataModelHierarchy, Configuration: Debug x64 ------ 7>For vtkCommonDataModel - updating vtkCommonDataModelHierarchy.txt 8>------ Build started: Project: vtkCommonExecutionModelHierarchy, Configuration: Debug x64 ------ 9>------ Build started: Project: vtkCommonComputationalGeometryHierarchy, Configuration: Debug x64 ------ 8>For vtkCommonExecutionModel - updating vtkCommonExecutionModelHierarchy.txt 9>For vtkCommonComputationalGeometry - updating vtkCommonComputationalGeometryHierarchy.txt 10>------ Build started: Project: vtkImagingCoreHierarchy, Configuration: Debug x64 ------ 11>------ Build started: Project: vtkFiltersCoreHierarchy, Configuration: Debug x64 ------ 12>------ Build started: Project: vtkIOCoreHierarchy, Configuration: Debug x64 ------ 13>------ Build started: Project: vtkIOImageHierarchy, Configuration: Debug x64 ------ 11>For vtkFiltersCore - updating vtkFiltersCoreHierarchy.txt 10>For vtkImagingCore - updating vtkImagingCoreHierarchy.txt 12>For vtkIOCore - updating vtkIOCoreHierarchy.txt 13>For vtkIOImage - updating vtkIOImageHierarchy.txt 14>------ Build started: Project: vtkIOLegacyHierarchy, Configuration: Debug x64 ------ 15>------ Build started: Project: vtkIOXMLParserHierarchy, Configuration: Debug x64 ------ 14>For vtkIOLegacy - updating vtkIOLegacyHierarchy.txt 16>------ Build started: Project: vtkImagingFourierHierarchy, Configuration: Debug x64 ------ 15>For vtkIOXMLParser - updating vtkIOXMLParserHierarchy.txt 17>------ Build started: Project: vtkPVCommonHierarchy, Configuration: Debug x64 ------ 16>For vtkImagingFourier - updating vtkImagingFourierHierarchy.txt 18>------ Build started: Project: vtkFiltersStatisticsHierarchy, Configuration: Debug x64 ------ 19>------ Build started: Project: vtkParallelCoreHierarchy, Configuration: Debug x64 ------ 18>For vtkFiltersStatistics - updating vtkFiltersStatisticsHierarchy.txt 19>For vtkParallelCore - updating vtkParallelCoreHierarchy.txt 20>------ Build started: Project: vtkParallelMPIHierarchy, Configuration: Debug x64 ------ 20>For vtkParallelMPI - updating vtkParallelMPIHierarchy.txt 21>------ Build started: Project: vtkFiltersGeneralHierarchy, Configuration: Debug x64 ------ 17>For vtkPVCommon - updating vtkPVCommonHierarchy.txt 21>For vtkFiltersGeneral - updating vtkFiltersGeneralHierarchy.txt 22>------ Build started: Project: vtkFiltersSourcesHierarchy, Configuration: Debug x64 ------ 23>------ Build started: Project: vtkFiltersExtractionHierarchy, Configuration: Debug x64 ------ 22>For vtkFiltersSources - updating vtkFiltersSourcesHierarchy.txt 24>------ Build started: Project: vtkPVVTKExtensionsCoreHierarchy, Configuration: Debug x64 ------ 23>For vtkFiltersExtraction - updating vtkFiltersExtractionHierarchy.txt 24>For vtkPVVTKExtensionsCore - updating vtkPVVTKExtensionsCoreHierarchy.txt 25>------ Build started: Project: vtkPVVTKExtensionsPCGNSWriterHierarchy, Configuration: Debug x64 ------ dr. ir. Menno A. Deij-van Rijswijk | Researcher / Software Engineer | MARIN Software Group MARIN | T +31 317 49 35 06 | M.Deij at marin.nl | www.marin.nl [LinkedIn] [YouTube] [Twitter] [Facebook] MARIN news: Software Seminar, October 11, Wageningen -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image4443a2.PNG Type: image/png Size: 293 bytes Desc: image4443a2.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image060e52.PNG Type: image/png Size: 331 bytes Desc: image060e52.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image86c74e.PNG Type: image/png Size: 333 bytes Desc: image86c74e.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image6fa5bb.PNG Type: image/png Size: 253 bytes Desc: image6fa5bb.PNG URL: From wascott at sandia.gov Mon Aug 20 15:39:43 2018 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 20 Aug 2018 19:39:43 +0000 Subject: [Paraview-developers] Where, and why? Message-ID: <820f051598fb46b19c1390195841b22b@ES01AMSNLNT.srn.sandia.gov> Where should this type of question go? Discourse? Do we want to fill up Discourse with junk such as this e-mail thread? In file pqSMAdaptor.cxx, line 553, I am getting a warning print. Debug build, remote server. I am testing bug number https://gitlab.kitware.com/paraview/paraview/issues/18360, with dataset voronoi95.exo. Anyone have any idea what this means? Warning is: "had to make up a value for selection". Not very clear! 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 "When the facts change, I change my mind. What do you do, sir?" John Maynard Keynes --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Mon Aug 20 15:47:41 2018 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 20 Aug 2018 19:47:41 +0000 Subject: [Paraview-developers] [EXTERNAL] Where, and why? In-Reply-To: <820f051598fb46b19c1390195841b22b@ES01AMSNLNT.srn.sandia.gov> References: <820f051598fb46b19c1390195841b22b@ES01AMSNLNT.srn.sandia.gov> Message-ID: Discourse is set up with a "Development" category that seems appropriate for any question that might go to the paraview-developers mailing list. -Ken From: Paraview-developers [mailto:paraview-developers-bounces at public.kitware.com] On Behalf Of Scott, W Alan via Paraview-developers Sent: Monday, August 20, 2018 1:40 PM To: paraview-developers at paraview.org Subject: [EXTERNAL] [Paraview-developers] Where, and why? Where should this type of question go? Discourse? Do we want to fill up Discourse with junk such as this e-mail thread? In file pqSMAdaptor.cxx, line 553, I am getting a warning print. Debug build, remote server. I am testing bug number https://gitlab.kitware.com/paraview/paraview/issues/18360, with dataset voronoi95.exo. Anyone have any idea what this means? Warning is: "had to make up a value for selection". Not very clear! 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 "When the facts change, I change my mind. What do you do, sir?" John Maynard Keynes --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Aug 21 11:13:40 2018 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 21 Aug 2018 11:13:40 -0400 Subject: [Paraview-developers] Where, and why? In-Reply-To: <820f051598fb46b19c1390195841b22b@ES01AMSNLNT.srn.sandia.gov> References: <820f051598fb46b19c1390195841b22b@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, Like the paraview at paraview.org mailing list, we plan to retire this mailing list as well, so development questions should go into the Development category like Ken says. To answer your technical question, you helped me find a minor bug in the Exodus reader code, and I fixed it here: https://gitlab.kitware.com/paraview/paraview/merge_requests/2676 Thanks, Cory On Mon, Aug 20, 2018 at 3:39 PM Scott, W Alan via Paraview-developers wrote: > > Where should this type of question go? Discourse? Do we want to fill up Discourse with junk such as this e-mail thread? > > > > In file pqSMAdaptor.cxx, line 553, I am getting a warning print. Debug build, remote server. I am testing bug number https://gitlab.kitware.com/paraview/paraview/issues/18360, with dataset voronoi95.exo. Anyone have any idea what this means? Warning is: ?had to make up a value for selection?. Not very clear! > > > > 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 > > > > ?When the facts change, I change my mind. What do you do, sir?? > > John Maynard Keynes > > > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > ParaView development discussion is moving! Please visit https://discourse.paraview.org/ for future posts. > > 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://public.kitware.com/mailman/listinfo/paraview-developers -- Cory Quammen Staff R&D Engineer Kitware, Inc.