From david.thompson at kitware.com Mon Apr 3 09:40:42 2017 From: david.thompson at kitware.com (David Thompson) Date: Mon, 3 Apr 2017 09:40:42 -0400 Subject: [Smtk-developers] .step/.egis reader in SMTK -> VTK In-Reply-To: References: Message-ID: <9D8FD704-5078-405C-9354-D38082BAE3BD@kitware.com> > As fas as I understand you wrote a .step .egis reader for SMTK. > We will need to write one as a paraview plugin (or even to be added in VTK) > > It looks like you are using cgma to read these files, however i can't find out how to convert to VTK after that. > > Any advices apreciated :) Hi Mathieu, We use CGMA to read STEP/IGES files into SMTK (our internal format) and then convert that to a VTK multiblock dataset (one block per vertex/edge/face) in smtk/extension/vtk/source/vtkModelMultiBlockSource.{h,cxx} . You are welcome to use the code as is (i.e., create a ParaView plugin that links to smtkCore and vtkSMTKSourceExt) or adapt it to your needs as you like. David From david.thompson at kitware.com Mon Apr 3 10:15:11 2017 From: david.thompson at kitware.com (David Thompson) Date: Mon, 3 Apr 2017 10:15:11 -0400 Subject: [Smtk-developers] Xcode 8.3 update Message-ID: <8C931AAD-4A01-4978-B510-A9EC350E4A87@kitware.com> Hi all, FYI, I updated to Xcode 8.3 on my laptop and it compiled SMTK+CMB without issue -- though I did not re-run CMake, so try_compile stuff may yet cause problems. It did emit a small number of new warnings, which I'll try to address in the next few days. David From haocheng.liu at kitware.com Tue Apr 4 10:11:10 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Tue, 4 Apr 2017 10:11:10 -0400 Subject: [Smtk-developers] Ubuntu 16.04 + Quadro M2000M (maybe Linux) NVIDIA driver does not work with CMB ? Message-ID: Hi, Recently I upgrade my NIDIA driver to 370.28, ModelBuilder refuses to open the application with an error message as "core dumped"(Cannot initialize OpenGL window). After some trial and error, I found a work-around solution as: - Using* Nouveau display driver* from xserver-xory-video-nouveau for the video card - run application in cmd as: "*LIBGL_ALWAYS_SOFTWARE=1 ./your-path-to-application*". Without setting LIBGL_ALWAYS_SOFTWARE, you would get an error message as: intel-do-flush-locked-failed-input-output-error when trying to assign a color to model entity in ModelBuilder. It's said to be a bug with UXA and SNA acceleration. -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4421 <(518)%20881-4421> -------------- next part -------------- An HTML attachment was scrubbed... URL: From haocheng.liu at kitware.com Tue Apr 4 15:00:43 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Tue, 4 Apr 2017 15:00:43 -0400 Subject: [Smtk-developers] Ubuntu 16.04 + Quadro M2000M (maybe Linux) NVIDIA driver does not work with CMB ? In-Reply-To: References: Message-ID: So here is the root cause: Recently CMB-superbuild is bumped to use ParaView 5.3.0. However, it is not happy with OpenGL drivers on Ubuntu 16.04. What you need to do is type in following commands if you want to build CMB-superbuild and run smoothly on Ubuntu16.04: ``` apt-add-repository ppa:oibaf/graphics-drivers apt-get update apt-get dist-upgrade ``` Reference link . On Tue, Apr 4, 2017 at 10:11 AM, Haocheng Liu wrote: > Hi, > > Recently I upgrade my NIDIA driver to 370.28, ModelBuilder refuses to open > the application with an error message as "core dumped"(Cannot initialize > OpenGL window). After some trial and error, I found a work-around solution > as: > > > - Using* Nouveau display driver* from xserver-xory-video-nouveau for > the video card > - run application in cmd as: "*LIBGL_ALWAYS_SOFTWARE=1 > ./your-path-to-application*". > > Without setting LIBGL_ALWAYS_SOFTWARE, you would get an error message as: > intel-do-flush-locked-failed-input-output-error > when > trying to assign a color to model entity in ModelBuilder. It's said to be a > bug with UXA and SNA acceleration. > > > -- > Best regards > Haocheng > > Haocheng LIU > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4421 <(518)%20881-4421> > -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4421 <(518)%20881-4421> -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Mon Apr 10 17:49:48 2017 From: david.thompson at kitware.com (David Thompson) Date: Mon, 10 Apr 2017 17:49:48 -0400 Subject: [Smtk-developers] SMTK test failures Message-ID: <6841D806-BEE8-49F8-AC8C-768B985B3816@kitware.com> Hi all, My latest commit appears to have caused UnitTestReadWriteMeshJSON to fail on kerbin[1]. However, I see another build of master from before I merged where a similar test failure (UnitTestWriteMesh this time) occurred[2]. I don't think my changes caused the failure (kerbin reported no issues on the branch before I merged). Is it possible this is an intermittent failure? David [1]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848471 [2]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848334 From david.thompson at kitware.com Mon Apr 10 18:37:25 2017 From: david.thompson at kitware.com (David Thompson) Date: Mon, 10 Apr 2017 18:37:25 -0400 Subject: [Smtk-developers] SMTK test failures In-Reply-To: <6841D806-BEE8-49F8-AC8C-768B985B3816@kitware.com> References: <6841D806-BEE8-49F8-AC8C-768B985B3816@kitware.com> Message-ID: > My latest commit appears to have caused UnitTestReadWriteMeshJSON to fail on kerbin[1]. However, I see another build of master from before I merged where a similar test failure (UnitTestWriteMesh this time) occurred[2]. I don't think my changes caused the failure (kerbin reported no issues on the branch before I merged). Is it possible this is an intermittent failure? Well, now that some more builds on master have occurred, it definitely appears to be an intermittent failure, and only on kerbin. Since it is mesh-related, and TJ is out, I will assign him the debugging. :-) David > [1]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848471 > [2]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848334 From haocheng.liu at kitware.com Mon Apr 10 19:48:27 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Mon, 10 Apr 2017 19:48:27 -0400 Subject: [Smtk-developers] SMTK test failures In-Reply-To: References: <6841D806-BEE8-49F8-AC8C-768B985B3816@kitware.com> Message-ID: <7B2EB44B-3EA5-43F1-85BF-5F72750E732D@kitware.com> Good luck TJ? Best rgrds Haocheng LIU On Apr 10, 2017, at 6:37 PM, David Thompson wrote: >> My latest commit appears to have caused UnitTestReadWriteMeshJSON to fail on kerbin[1]. However, I see another build of master from before I merged where a similar test failure (UnitTestWriteMesh this time) occurred[2]. I don't think my changes caused the failure (kerbin reported no issues on the branch before I merged). Is it possible this is an intermittent failure? > > Well, now that some more builds on master have occurred, it definitely appears to be an intermittent failure, and only on kerbin. Since it is mesh-related, and TJ is out, I will assign him the debugging. :-) > > David > >> [1]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848471 >> [2]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848334 > > _______________________________________________ > Smtk-developers mailing list > Smtk-developers at smtk.org > http://public.kitware.com/mailman/listinfo/smtk-developers From tj.corona at kitware.com Thu Apr 13 14:04:37 2017 From: tj.corona at kitware.com (TJ Corona) Date: Thu, 13 Apr 2017 14:04:37 -0400 Subject: [Smtk-developers] SMTK test failures In-Reply-To: <7B2EB44B-3EA5-43F1-85BF-5F72750E732D@kitware.com> References: <6841D806-BEE8-49F8-AC8C-768B985B3816@kitware.com> <7B2EB44B-3EA5-43F1-85BF-5F72750E732D@kitware.com> Message-ID: <191AF7C0-9A4C-4EAA-9704-F138D16453EC@kitware.com> Do I still get credit for fixing the issues if the problems went away by themselves? Thomas J. Corona, Ph.D. Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4443 > On Apr 10, 2017, at 7:48 PM, Haocheng Liu wrote: > > Good luck TJ? > > Best rgrds > Haocheng LIU > > On Apr 10, 2017, at 6:37 PM, David Thompson wrote: > >>> My latest commit appears to have caused UnitTestReadWriteMeshJSON to fail on kerbin[1]. However, I see another build of master from before I merged where a similar test failure (UnitTestWriteMesh this time) occurred[2]. I don't think my changes caused the failure (kerbin reported no issues on the branch before I merged). Is it possible this is an intermittent failure? >> >> Well, now that some more builds on master have occurred, it definitely appears to be an intermittent failure, and only on kerbin. Since it is mesh-related, and TJ is out, I will assign him the debugging. :-) >> >> David >> >>> [1]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848471 >>> [2]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848334 >> >> _______________________________________________ >> Smtk-developers mailing list >> Smtk-developers at smtk.org >> http://public.kitware.com/mailman/listinfo/smtk-developers > _______________________________________________ > Smtk-developers mailing list > Smtk-developers at smtk.org > http://public.kitware.com/mailman/listinfo/smtk-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Thu Apr 13 14:06:18 2017 From: david.thompson at kitware.com (David Thompson) Date: Thu, 13 Apr 2017 14:06:18 -0400 Subject: [Smtk-developers] SMTK test failures In-Reply-To: <191AF7C0-9A4C-4EAA-9704-F138D16453EC@kitware.com> References: <6841D806-BEE8-49F8-AC8C-768B985B3816@kitware.com> <7B2EB44B-3EA5-43F1-85BF-5F72750E732D@kitware.com> <191AF7C0-9A4C-4EAA-9704-F138D16453EC@kitware.com> Message-ID: > Do I still get credit for fixing the issues if the problems went away by themselves? If they never reappear as t->Infinity, then you will receive eventual credit on the projective plane. :-) David >> On Apr 10, 2017, at 7:48 PM, Haocheng Liu wrote: >> >> Good luck TJ? >> >> Best rgrds >> Haocheng LIU >> >> On Apr 10, 2017, at 6:37 PM, David Thompson wrote: >> >>>> My latest commit appears to have caused UnitTestReadWriteMeshJSON to fail on kerbin[1]. However, I see another build of master from before I merged where a similar test failure (UnitTestWriteMesh this time) occurred[2]. I don't think my changes caused the failure (kerbin reported no issues on the branch before I merged). Is it possible this is an intermittent failure? >>> >>> Well, now that some more builds on master have occurred, it definitely appears to be an intermittent failure, and only on kerbin. Since it is mesh-related, and TJ is out, I will assign him the debugging. :-) >>> >>> David >>> >>>> [1]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848471 >>>> [2]: https://open.cdash.org/viewTest.php?onlyfailed&buildid=4848334 >>> >>> _______________________________________________ >>> Smtk-developers mailing list >>> Smtk-developers at smtk.org >>> http://public.kitware.com/mailman/listinfo/smtk-developers >> _______________________________________________ >> Smtk-developers mailing list >> Smtk-developers at smtk.org >> http://public.kitware.com/mailman/listinfo/smtk-developers > From david.thompson at kitware.com Fri Apr 28 16:39:46 2017 From: david.thompson at kitware.com (David Thompson) Date: Fri, 28 Apr 2017 16:39:46 -0400 Subject: [Smtk-developers] Attribute system change Message-ID: <6BF0FD2B-85C6-429E-80BF-D7B9FF50FF34@kitware.com> Hi all, I've submitted merge requests for SMTK[1] and CMB[2] that convert SMTK's API to use shared pointers for attribute system instances. This is needed in order for the model manager to properly update associations with attributes when model entities are split or merged by modeling operations. What this means for you is that you can no longer create attribute systems like so: smtk::attribute::System someSystem; // C++ someSystem = smtk.attribute.System() # Python Instead, you should: auto someSystem = smtk::attribute::System::create(); // C++, returns a SystemPtr someSystem = smtk.attribute.System.create() # Python Note that this makes creating an attribute system the same as creating a model manager (which already has a static "create" method). David [1]: https://gitlab.kitware.com/cmb/smtk/merge_requests/567 [2]: https://gitlab.kitware.com/cmb/cmb/merge_requests/378