From alexis.girault at kitware.com Tue Apr 4 13:05:46 2017 From: alexis.girault at kitware.com (Alexis Girault) Date: Tue, 4 Apr 2017 13:05:46 -0400 Subject: [Imstk-developers] Coding session April 5th Message-ID: I'll be at the meeting to start talking about today's tasks but will leave and come back around 2pm. Alexis Girault R&D Engineer in Medical Computing Kitware, Inc. http://www.kitware.com (919) 969-6990 x325 -------------- next part -------------- An HTML attachment was scrubbed... URL: From milefn at rpi.edu Wed Apr 5 17:26:01 2017 From: milefn at rpi.edu (Milef, Nicholas Boris) Date: Wed, 5 Apr 2017 21:26:01 +0000 Subject: [Imstk-developers] Multiple UV channels, multiple Materials? Message-ID: As I'm building the Material class, I'm running into a design issue with materials. A material is a container of textures (with other properties). Right now each surface mesh has a map of textures to texture coordinates, but I'm not sure this is necessary for our use cases. What would be potential use cases with assigning different materials to multiple UVs? The reason for is that if you totally fill up a material class with textures, then you can pass texture binding limits with as little as two materials: http://gamedev.stackexchange.com/a/30101 On the other hand, if we allow users to define the texture coordinate names, then we run into the issue of Materials that can't be shared between objects, which sort of defeats the ease of use/portability of a Material. What do you all think? -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexis.girault at kitware.com Thu Apr 6 17:52:53 2017 From: alexis.girault at kitware.com (Alexis Girault) Date: Thu, 6 Apr 2017 17:52:53 -0400 Subject: [Imstk-developers] CDash not showing builds Message-ID: The migration from my.cdash to open.cdash has encountered some difficulties, with the latest merge-request builds and integration builds not showing up on cdash. I see that there are a couple branches actively being tested (surfaceMesh, spatial hashing, frame counter...). In the meantime, developers at Kitware can see the status of their build on the buildbot server . Developers outside of Kitware, feel free to get in touch with one of us to keep you posted on your build status. Zack and Ben are helping to set this up (thank you to them), we will let you know when the dashboards work correctly again. Best, Alexis Girault R&D Engineer in Medical Computing Kitware, Inc. http://www.kitware.com (919) 969-6990 x325 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexis.girault at kitware.com Fri Apr 21 09:33:32 2017 From: alexis.girault at kitware.com (Alexis Girault) Date: Fri, 21 Apr 2017 09:33:32 -0400 Subject: [Imstk-developers] Dashboard final touches Message-ID: As you saw, we had the dashboard properly updated last week by switching to open.cdash.org. That transition allowed to get the latest updates of CDash, namely commit number on the left column, correct categorization of merge-requests and master builds, and more importantly filtering by build name, allowing us to quickly visualize the builds that matter from a merge-request. This instance of CDash will have a better support in the future that the former my.cdash.org. The link to the dashboard has been updated on the website (thank you Dzenan). Today we should be transitioning to another instance of buildbot, public, and also better maintained that the current one. This update will be able to tackle two issues: - fix the current window builds errors for merge-requests and master on the dashboard: the issue is due to some external data file path exceeding the maximum path length limitation of 260, and the update will allow us to customize the build directory names to a shorter name which will shorten that path enough. - Disable continuous building of a merge-request after updates: to start the builds for the dashboard, we will have to comment `Do: test` instead of `@buildbot test`, and do it each time we want builds to occur, which will save us some computing time. We will also be able to use `Do: merge` to merge the branch. I will keep you informed of the advancements during the day. Alexis Girault R&D Engineer in Medical Computing Kitware, Inc. http://www.kitware.com (919) 969-6990 x325 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andinet.enqu at kitware.com Fri Apr 21 11:57:13 2017 From: andinet.enqu at kitware.com (Andinet Enquobahrie) Date: Fri, 21 Apr 2017 11:57:13 -0400 Subject: [Imstk-developers] Dashboard final touches In-Reply-To: References: Message-ID: Great!! Thanks for the update. Sent from my iPhone > On Apr 21, 2017, at 9:33 AM, Alexis Girault wrote: > > As you saw, we had the dashboard properly updated last week by switching to open.cdash.org. That transition allowed to get the latest updates of CDash, namely commit number on the left column, correct categorization of merge-requests and master builds, and more importantly filtering by build name, allowing us to quickly visualize the builds that matter from a merge-request. This instance of CDash will have a better support in the future that the former my.cdash.org. > > The link to the dashboard has been updated on the website (thank you Dzenan). > > Today we should be transitioning to another instance of buildbot, public, and also better maintained that the current one. This update will be able to tackle two issues: > - fix the current window builds errors for merge-requests and master on the dashboard: the issue is due to some external data file path exceeding the maximum path length limitation of 260, and the update will allow us to customize the build directory names to a shorter name which will shorten that path enough. > - Disable continuous building of a merge-request after updates: to start the builds for the dashboard, we will have to comment `Do: test` instead of `@buildbot test`, and do it each time we want builds to occur, which will save us some computing time. We will also be able to use `Do: merge` to merge the branch. > > I will keep you informed of the advancements during the day. > > Alexis Girault > R&D Engineer in Medical Computing > Kitware, Inc. > > http://www.kitware.com > (919) 969-6990 x325 > _______________________________________________ > Imstk-developers mailing list > Imstk-developers at imstk.org > http://public.kitware.com/mailman/listinfo/imstk-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: