From houssen at ipgp.fr Sat Aug 1 08:08:24 2015 From: houssen at ipgp.fr (houssen) Date: Sat, 01 Aug 2015 14:08:24 +0200 Subject: [vtk-developers] =?utf-8?q?How_to_get_=22raw=22_data_from_vtkPoly?= =?utf-8?q?Data_=3F?= Message-ID: How to get "raw" data from vtkPolyData ? My understanding is that vtkPolyData stands for "pure visualization" data (triangulation). For instance, if my raw data is a hexahedron (vtkUnstructuredGrid), then the associated vtkPolyData will "only" be a set of 8 points and 6 faces which are mandatory to render the hexahedron. From the vtkPolyData, how to get the hexahedron (as a vtkUnstrucutredGrid) ? Franck From houssen at ipgp.fr Sun Aug 2 10:26:37 2015 From: houssen at ipgp.fr (houssen) Date: Sun, 02 Aug 2015 16:26:37 +0200 Subject: [vtk-developers] =?utf-8?q?How_to_get_=22raw=22_data_from_vtkPoly?= =?utf-8?q?Data_=3F?= In-Reply-To: References: Message-ID: <37c09ccfb6a1920279636cf28fec39c2@imap.ipgp.fr> I forgot to mention : I tried this http://www.vtk.org/Wiki/VTK/Examples/Cxx/PolyData/PolyDataToUnstructuredGrid but it doesn't help, from the vtkPolyData this creates a vtkUnstructuredGrid made of 8 points and 6 quadrangles which is not what I need. I need the vtkUnstructuredGrid containing the initial "raw" data (= 8 point + 1 hexahedron). I feel like the data that have been used to create the vtkPolyData are "lost" (no way to get them back). Correct ? Franck Le 2015-08-01 14:08, houssen a ?crit?: > How to get "raw" data from vtkPolyData ? > > My understanding is that vtkPolyData stands for "pure visualization" > data (triangulation). For instance, if my raw data is a hexahedron > (vtkUnstructuredGrid), then the associated vtkPolyData will "only" be > a set of 8 points and 6 faces which are mandatory to render the > hexahedron. > > From the vtkPolyData, how to get the hexahedron (as a > vtkUnstrucutredGrid) ? > > Franck > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers From majcjc at gmail.com Sun Aug 2 22:38:23 2015 From: majcjc at gmail.com (Lin M) Date: Sun, 2 Aug 2015 22:38:23 -0400 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> Message-ID: Hi Dr. Thompson, I have a question about the inversion and projection. Currently, we evaluate the NURBS by inserting knots and making it into Bezier forms. My question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], would it be the same to evaluate u = 0.2 in the new knot vector which is a bezier form? Best, Lin On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: > Hi Dr. Thompson, > > I have added new method > vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. > > I'm now working on the point inversion part. > > Best, > Lin > > On Sun, Jul 26, 2015 at 8:05 PM, David Thompson < > david.thompson at kitware.com> wrote: > >> Hi Lin, >> >> How is triangular/tetrahedral patch interpolation going? They will be a >> basic building block of the contouring and cutting algorithms. By >> identifying points on edges, edges on surfaces, and surfaces in volumes >> that take on a single value, a single patch can be decomposed into sections >> that are inside, outside, or on an isosurface. Not all of these pieces can >> be expressed as brick patches, but they can be expressed as simplicial >> patches. >> >> David > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Sun Aug 2 22:50:09 2015 From: david.thompson at kitware.com (David Thompson) Date: Sun, 2 Aug 2015 22:50:09 -0400 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> Message-ID: <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> Hi Lin, Yes, that is correct. Inserting knot values does not change the polynomial degree or shape, it just adds control points so that the weights are uniform (as required by the B?zier basis). So, the underlying parameterization is unchanged... it just has more piecewise segments. David > On Aug 2, 2015, at 22:38, Lin M wrote: > > Hi Dr. Thompson, > > I have a question about the inversion and projection. Currently, we evaluate the NURBS by inserting knots and making it into Bezier forms. My question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], would it be the same to evaluate u = 0.2 in the new knot vector which is a bezier form? > > Best, > Lin > >> On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: >> Hi Dr. Thompson, >> >> I have added new method vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >> >> I'm now working on the point inversion part. >> >> Best, >> Lin >> >>> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson wrote: >>> Hi Lin, >>> >>> How is triangular/tetrahedral patch interpolation going? They will be a basic building block of the contouring and cutting algorithms. By identifying points on edges, edges on surfaces, and surfaces in volumes that take on a single value, a single patch can be decomposed into sections that are inside, outside, or on an isosurface. Not all of these pieces can be expressed as brick patches, but they can be expressed as simplicial patches. >>> >>> David > -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Mon Aug 3 12:44:45 2015 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Mon, 3 Aug 2015 12:44:45 -0400 Subject: [vtk-developers] newbie presentation In-Reply-To: References: Message-ID: On Sun, Aug 2, 2015 at 6:59 AM, Pindarico Volo wrote: > Followed the instructions at the link, but I keep getting "Permission > denied" when testing the connection. > > > What step is exhibiting the "permission denied" message? It would be best to keep the response on-list so others can help with the contribution process. Best, -- Casey -------------- next part -------------- An HTML attachment was scrubbed... URL: From vpindarico at gmail.com Mon Aug 3 14:35:28 2015 From: vpindarico at gmail.com (Pindarico Volo) Date: Mon, 3 Aug 2015 20:35:28 +0200 Subject: [vtk-developers] newbie presentation In-Reply-To: References: Message-ID: Sorry Casey, it was not intentional to reply to you personally. Followed instructions from https://gitlab.kitware.com/vtk/vtk/blob/master/Documentation/dev/git/develop.md : + Registered as Daniele Lugli, ok. + Forked project VTK, ok. + Local clone created, ok. - The setup script wants to test access to gitlab and this fails (followed instructions at https://help.github.com/articles/generating-ssh-keys/ and everything looks ok except the test at step5, which fails with permission denied). Thank you Daniele 2015-08-03 18:44 GMT+02:00 Casey Goodlett : > > On Sun, Aug 2, 2015 at 6:59 AM, Pindarico Volo > wrote: > >> Followed the instructions at the link, but I keep getting "Permission >> denied" when testing the connection. >> >> >> > What step is exhibiting the "permission denied" message? > > It would be best to keep the response on-list so others can help with the > contribution process. > > Best, > > -- > Casey > -------------- next part -------------- An HTML attachment was scrubbed... URL: From casey.goodlett at kitware.com Mon Aug 3 14:44:08 2015 From: casey.goodlett at kitware.com (Casey Goodlett) Date: Mon, 3 Aug 2015 14:44:08 -0400 Subject: [vtk-developers] newbie presentation In-Reply-To: References: Message-ID: Are you able to push a branch into your fork? Can you share a URL to your fork? On Mon, Aug 3, 2015 at 2:35 PM, Pindarico Volo wrote: > Sorry Casey, it was not intentional to reply to you personally. > > Followed instructions from > https://gitlab.kitware.com/vtk/vtk/blob/master/Documentation/dev/git/develop.md > : > + Registered as Daniele Lugli, ok. > + Forked project VTK, ok. > + Local clone created, ok. > - The setup script wants to test access to gitlab and this fails (followed > instructions at https://help.github.com/articles/generating-ssh-keys/ and > everything looks ok except the test at step5, which fails with permission > denied). > > Thank you > > Daniele > > > > > 2015-08-03 18:44 GMT+02:00 Casey Goodlett : > >> >> On Sun, Aug 2, 2015 at 6:59 AM, Pindarico Volo >> wrote: >> >>> Followed the instructions at the link, but I keep getting "Permission >>> denied" when testing the connection. >>> >>> >>> >> What step is exhibiting the "permission denied" message? >> >> It would be best to keep the response on-list so others can help with the >> contribution process. >> >> Best, >> >> -- >> Casey >> > > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -- Casey B Goodlett, PhD Technical Leader Kitware, Inc. - North Carolina Office http://www.kitware.com (919) 969-6990 x310 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mina.hrtn at gmail.com Mon Aug 3 16:01:31 2015 From: mina.hrtn at gmail.com (mina.hrtn at gmail.com) Date: Mon, 03 Aug 2015 15:01:31 -0500 Subject: [vtk-developers] You have a new notification from from_name. View? Message-ID: <0.0.1C.BC3.1D0CE2630289AE6.2D88@mail1.flipmailer.com> Hi, from_name wants to follow you. ****** Is from_name you friend? ****** If Yes please follow the link below: http://invites.flipmailer.com/signup_e.html?fullname=&email=vtk-developers at vtk.org&invitername=Mina.hrtn&inviterid=18718060&userid=0&token=0&emailmasterid=51620878-933e-4a55-bc52-368b0ba09a8b&from=from_name&template=invite_reminder_2_b&test=AA&src=txt_yes If No please follow the link below: http://invites.flipmailer.com/signup_e.html?fullname=&email=vtk-developers at vtk.org&invitername=Mina.hrtn&inviterid=18718060&userid=0&token=0&emailmasterid=51620878-933e-4a55-bc52-368b0ba09a8b&from=from_name&template=invite_reminder_2_b&test=AA&src=txt_no Follow the link below to remove yourself from all such emails http://invites.flipmailer.com/uns_inviter.jsp?email=vtk-developers at vtk.org&iid=51620878-933e-4a55-bc52-368b0ba09a8b&from=from_name -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Tue Aug 4 10:52:49 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Tue, 4 Aug 2015 08:52:49 -0600 Subject: [vtk-developers] VTK-py3k is ready for testing Message-ID: This should allow VTK to compile with python 3 on the major platforms. Basic stuff seems to work. https://gitlab.kitware.com/vtk/vtk/merge_requests/478 - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From will.schroeder at kitware.com Tue Aug 4 11:09:18 2015 From: will.schroeder at kitware.com (Will Schroeder) Date: Tue, 4 Aug 2015 11:09:18 -0400 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: !!! wowza this is great David, On Tue, Aug 4, 2015 at 10:52 AM, David Gobbi wrote: > This should allow VTK to compile with python 3 on the major platforms. > Basic stuff seems to work. > https://gitlab.kitware.com/vtk/vtk/merge_requests/478 > > - David > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -- William J. Schroeder, PhD Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Aug 4 15:53:55 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 4 Aug 2015 15:53:55 -0400 Subject: [vtk-developers] getting your topics into the release Message-ID: Howdy, Ben set up milestones in gitlab. For example: https://gitlab.kitware.com/vtk/vtk/milestones/1 Let's use them to flag the specific things we want included in the upcoming release. To do that, navigate to a merge request that you care about, use the Select milestone drop down to pick a target release. For code to make it into the upcoming release it should be: 1) based off of the release branch (or older) then it will merge cleanly into both the master and release branches. Otherwise we have to cherry-pick it so that when we merge it to release it doesn't come with other commits (like the one where we changed the version number for example). 2) tested in buildbot and merged into master thanks! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From hobbsk at ohio.edu Wed Aug 5 08:27:57 2015 From: hobbsk at ohio.edu (Kevin H. Hobbs) Date: Wed, 5 Aug 2015 08:27:57 -0400 Subject: [vtk-developers] CMake Segfaults while configuring VTK Message-ID: <55C2014D.5060103@ohio.edu> Stephen, My VTK Dashboard builds use CMake from my CMake dashboard build. The hosts are bubbles and murron. On the Aug. 2 the VTK builds on both hosts began segfaulting at the configure step. You had a large commit to CMake that showed up on that dashboard cycle. I switched my cmake build type from Release to Debug and ran in gdb. I get this at the end of : gdb) run ../VTK < KHH what looks like regular output > -- Check size of long long - done Detaching after fork from child process 2061. Detaching after fork from child process 2062. Detaching after fork from child process 2063. < KHH more lines like this > Detaching after fork from child process 2085. -- Configuring done Program received signal SIGSEGV, Segmentation fault. 0x00000000007e8184 in cmTarget::GetMakefile (this=0x0) at /home/kevin/kitware/CMake/Source/cmTarget.h:134 134 cmMakefile *GetMakefile() const { return this->Makefile;} (gdb) bt #0 0x00000000007e8184 in cmTarget::GetMakefile (this=0x0) at /home/kevin/kitware/CMake/Source/cmTarget.h:134 #1 0x00000000009cf1f9 in cmComputeLinkInformation::AddSharedDepItem (this=0x799a800, item="/usr/lib64/libGL.so", tgt=0x0) at /home/kevin/kitware/CMake/Source/cmComputeLinkInformation.cxx:767 #2 0x00000000009ce253 in cmComputeLinkInformation::Compute (this=0x799a800) at /home/kevin/kitware/CMake/Source/cmComputeLinkInformation.cxx:511 #3 0x0000000000a467d2 in cmGeneratorTarget::GetLinkInformation (this=0x728fa30, config="") at /home/kevin/kitware/CMake/Source/cmGeneratorTarget.cxx:3268 #4 0x00000000009f576c in getCompatibleInterfaceProperties (target=0x728fa30, ifaceProperties=std::set with 0 elements, config="") at /home/kevin/kitware/CMake/Source/cmExportFileGenerator.cxx:532 #5 0x00000000009f5f20 in cmExportFileGenerator::PopulateCompatibleInterfaceProperties ( this=0x674e430, gtarget=0x728fa30, properties=std::map with 1 elements = {...}) at /home/kevin/kitware/CMake/Source/cmExportFileGenerator.cxx:595 #6 0x0000000000adce2c in cmExportInstallFileGenerator::GenerateMainFile (this=0x674e430, os=...) at /home/kevin/kitware/CMake/Source/cmExportInstallFileGenerator.cxx:200 #7 0x00000000009f34ae in cmExportFileGenerator::GenerateImportFile (this=0x674e430) at /home/kevin/kitware/CMake/Source/cmExportFileGenerator.cxx:126 #8 0x0000000000a6ce03 in cmInstallExportGenerator::GenerateScript (this=0x13617d0, os=...) at /home/kevin/kitware/CMake/Source/cmInstallExportGenerator.cxx:164 #9 0x000000000087bf43 in cmScriptGenerator::Generate (this=0x13617d0, os=..., config="Debug", configurationTypes=std::vector of length 0, capacity 0) at /home/kevin/kitware/CMake/Source/cmScriptGenerator.cxx:42 #10 0x00000000008180dc in cmLocalGenerator::GenerateInstallRules (this=0x102ec70) at /home/kevin/kitware/CMake/Source/cmLocalGenerator.cxx:411 #11 0x00000000007dd66f in cmGlobalGenerator::Generate (this=0x102de90) at /home/kevin/kitware/CMake/Source/cmGlobalGenerator.cxx:1357 #12 0x0000000000a5da64 in cmGlobalUnixMakefileGenerator3::Generate (this=0x102de90) at /home/kevin/kitware/CMake/Source/cmGlobalUnixMakefileGenerator3.cxx:140 #13 0x00000000008e02a5 in cmake::Generate (this=0x7fffffffd800) at /home/kevin/kitware/CMake/Source/cmake.cxx:1771 #14 0x00000000008e00ec in cmake::Run (this=0x7fffffffd800, args=std::vector of length 2, capacity 2 = {...}, noconfigure=false) at /home/kevin/kitware/CMake/Source/cmake.cxx:1754 #15 0x00000000007ac620 in do_cmake (ac=2, av=0x1020cc0) at /home/kevin/kitware/CMake/Source/cmakemain.cxx:330 #16 0x00000000007abbd5 in main (ac=2, av=0x1020cc0) at /home/kevin/kitware/CMake/Source/cmakemain.cxx:190 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From sean at rogue-research.com Wed Aug 5 11:30:56 2015 From: sean at rogue-research.com (Sean McBride) Date: Wed, 5 Aug 2015 11:30:56 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: References: Message-ID: <20150805153056.753300039@mail.rogue-research.com> On Tue, 30 Jun 2015 13:58:56 -0400, Berk Geveci said: >So the idea is that we will do our best to support as much as possible >a broad set of architectures and backwards compatibility but break things >when necessary in VTK 7 and beyond. On the OS X side, I'd like to propose: - removing PowerPC support - removing Carbon support - removing OS X 10.5 support - removing Apple-gcc 4.2 support - removing Xcode 3.x support If there's consensus, I volunteer to gut the relevant stuff. I can also use clang-modernize to introduce nullptr usage, if that's something we're ready to do in master now. nullptr can be pretty easily emulated on older compilers, like ITK does. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From dave.demarle at kitware.com Wed Aug 5 11:39:02 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 5 Aug 2015 11:39:02 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: <20150805153056.753300039@mail.rogue-research.com> References: <20150805153056.753300039@mail.rogue-research.com> Message-ID: On Wed, Aug 5, 2015 at 11:30 AM, Sean McBride wrote: > - removing PowerPC support > - removing Carbon support > - removing OS X 10.5 support > - removing Apple-gcc 4.2 support > - removing Xcode 3.x support > +1 from me David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Wed Aug 5 11:44:07 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 5 Aug 2015 09:44:07 -0600 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: So, here's a brief update on python 3 status: The python-py3k merge branch compiles and runs with Python 3.2, 3.3, 3.4 and also Python 2.5, 2.6, 2.7 (I tried all six). So, yes, you can build VTK against Python 3, and you can run VTK programs with Python 3. I'll be doing a bit of cleanup of the next few days, but the current branch is very close to what I plan to merge. However: the test code in VTK is all written for Python 2, so right now the Python 3 buildbot that Ben has set up is showing all red for the testing. Converting the tests will be a lot of work, especially because the tests must continue to run with Python 2.6 and 2.7 (definitely not 2.5, though). Andrew, you mentioned that you might be able to provide some assistance, I would be very grateful for anything you have to offer. I've already begun converting the python tests in Common/Core, because these test the core features of the wrappers. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Aug 5 11:56:15 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 5 Aug 2015 11:56:15 -0400 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: Really nice work David. Thank you for extending the life of VTK by another decade. :) David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 5, 2015 at 11:44 AM, David Gobbi wrote: > So, here's a brief update on python 3 status: > > The python-py3k merge branch compiles and runs with Python 3.2, 3.3, 3.4 > and also Python 2.5, 2.6, 2.7 (I tried all six). So, yes, you can build > VTK against Python 3, and you can run VTK programs with Python 3. I'll be > doing a bit of cleanup of the next few days, but the current branch is very > close to what I plan to merge. > > However: the test code in VTK is all written for Python 2, so right now > the Python 3 buildbot that Ben has set up is showing all red for the > testing. Converting the tests will be a lot of work, especially because > the tests must continue to run with Python 2.6 and 2.7 (definitely not 2.5, > though). Andrew, you mentioned that you might be able to provide some > assistance, I would be very grateful for anything you have to offer. > > I've already begun converting the python tests in Common/Core, because > these test the core features of the wrappers. > > - David > > > > > > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.king at kitware.com Wed Aug 5 13:10:01 2015 From: brad.king at kitware.com (Brad King) Date: Wed, 05 Aug 2015 13:10:01 -0400 Subject: [vtk-developers] CMake Segfaults while configuring VTK In-Reply-To: <55C2014D.5060103@ohio.edu> References: <55C2014D.5060103@ohio.edu> Message-ID: <55C24369.5010902@kitware.com> On 08/05/2015 08:27 AM, Kevin H. Hobbs wrote: > My VTK Dashboard builds use CMake from my CMake dashboard build. Thanks for running that! > On the Aug. 2 the VTK builds on both hosts began segfaulting at > the configure step. Steve has updated the offending topic with a fix so we'll see tonight. Thanks, -Brad From will.schroeder at kitware.com Wed Aug 5 15:33:27 2015 From: will.schroeder at kitware.com (Will Schroeder) Date: Wed, 5 Aug 2015 15:33:27 -0400 Subject: [vtk-developers] [vtkusers] VTK Roadmap In-Reply-To: References: Message-ID: Berk let's not forget to add in interaction; e.g. multi-touch and more advanced interaction techniques. There are also related topics such as the impact on widgets, and potential changes to events/event processing There are also some community support infrastructure, along the lines that Bill is currently working on (remote modules) and other ways to contribute and test code. W On Tue, Jun 30, 2015 at 1:58 PM, Berk Geveci wrote: > Hi folks, > > As Dave DeMarle mentioned, we are gearing towards a VTK 6.3 release. VTK 7 > will follow very shortly (in weeks). I'd like to shed some light here on > our thinking and how we are planning to move forward. > > As was previously discussed in the VTK developers list [1] [2], we are > considering maintaining VTK 6.x for a long time (3-5 years) while moving > forward with VTK 7 and 8 in 2015 and 2016. There are some major changes > happening in the computing and C++ worlds and we would like evolve VTK more > quickly to stay up to date. Some of the major changes that we are > considering and/or working on are: > > * Major refactoring of rendering (OpenGL as well as ray tracing etc.) > * Multi/many-core support / SMP computing on CPUs and accelerators. VTK-m > integration [3]. > * Changes to data model to support zero copy interface to other data > layouts, more efficient APIs, more cell types, more dataset types etc. > * Better separation of a public, wrapped API and toolkit/C++ internal API > mainly to support efficiency > * Introduction of C++ 11 features > > Much of this will require introducing changes that break backwards > compatibility and also require newer compilers, graphics cards / drivers > etc. So the idea is that we will do our best to support as much as possible > a broad set of architectures and backwards compatibility but break things > when necessary in VTK 7 and beyond. We will maintain VTK 6.x so that folks > that are stuck on legacy systems or code bases can continue to benefit from > bug fixes. We have a way of continuing to maintain a broad set of > dashboards and also the same review process as VTK master so that we can > continue to ensure the quality of VTK 6.x as well as new releases. > > What do you guys think? Please provide feedback so that we can adjust our > plans to meet the needs of the community as much as possible. > > Best, > -berk > > [1] : http://bit.ly/1BUHFKT > [2] : http://bit.ly/1g7LSRG > [3] : http://m.vtk.org/ > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the VTK FAQ at: > http://www.vtk.org/Wiki/VTK_FAQ > > Search the list archives at: http://markmail.org/search/?q=vtkusers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtkusers > > -- William J. Schroeder, PhD Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From chaffra at gmail.com Wed Aug 5 16:13:12 2015 From: chaffra at gmail.com (Chaffra Affouda) Date: Wed, 05 Aug 2015 16:13:12 -0400 Subject: [vtk-developers] code formatting prior to merge request Message-ID: <55C26E58.4060307@gmail.com> Hi, What's the best way to format the code prior to a merge request? I am using eclipse to format the code but the kwrobot keeps rejecting the basic content. Thanks, Chaffra From dave.demarle at kitware.com Wed Aug 5 16:28:40 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 5 Aug 2015 16:28:40 -0400 Subject: [vtk-developers] code formatting prior to merge request In-Reply-To: <55C26E58.4060307@gmail.com> References: <55C26E58.4060307@gmail.com> Message-ID: I've used this a bit with eclipse and it prevents most of the pedantic problems. I'm not an eclipse guru so I can't tell you how to apply it after the fact off the top of my head. hth David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 5, 2015 at 4:13 PM, Chaffra Affouda wrote: > Hi, > > What's the best way to format the code prior to a merge request? I am > using eclipse to format the code but the kwrobot keeps rejecting the basic > content. > > Thanks, > Chaffra > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: kw_eclipse_style.xml Type: text/xml Size: 17590 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Aug 5 17:00:10 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 5 Aug 2015 17:00:10 -0400 Subject: [vtk-developers] code formatting prior to merge request In-Reply-To: <55C278A3.50802@gmail.com> References: <55C26E58.4060307@gmail.com> <55C278A3.50802@gmail.com> Message-ID: Please reply all to keep the list in on the discussion, thanks. I've never used either pretty-printer so I can't comment on their merits. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 5, 2015 at 4:57 PM, Chaffra Affouda wrote: > Thanks David, > > Is the more general way to use KWStyle or Astyle? > > > > > On 08/05/2015 04:28 PM, David E DeMarle wrote: > > I've used this a bit with eclipse and it prevents most of the pedantic > problems. > > I'm not an eclipse guru so I can't tell you how to apply it after the fact > off the top of my head. > > hth > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Aug 5, 2015 at 4:13 PM, Chaffra Affouda wrote: > >> Hi, >> >> What's the best way to format the code prior to a merge request? I am >> using eclipse to format the code but the kwrobot keeps rejecting the basic >> content. >> >> Thanks, >> Chaffra >> _______________________________________________ >> 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=vtk-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/vtk-developers >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Wed Aug 5 19:11:08 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Thu, 6 Aug 2015 09:11:08 +1000 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: Hi David, Wonderful news. Definitely be glad to help. Setting up a Python 3.4 environment in Windows 10 on my laptop now. I'll be using Anaconda Python. Once this is done, I'll maintain both a python 2.7 and Python 3.4 build and see how things go. Regards Andrew On Thu, Aug 6, 2015 at 1:44 AM, David Gobbi wrote: > So, here's a brief update on python 3 status: > > The python-py3k merge branch compiles and runs with Python 3.2, 3.3, 3.4 > and also Python 2.5, 2.6, 2.7 (I tried all six). So, yes, you can build > VTK against Python 3, and you can run VTK programs with Python 3. I'll be > doing a bit of cleanup of the next few days, but the current branch is very > close to what I plan to merge. > > However: the test code in VTK is all written for Python 2, so right now > the Python 3 buildbot that Ben has set up is showing all red for the > testing. Converting the tests will be a lot of work, especially because > the tests must continue to run with Python 2.6 and 2.7 (definitely not 2.5, > though). Andrew, you mentioned that you might be able to provide some > assistance, I would be very grateful for anything you have to offer. > > I've already begun converting the python tests in Common/Core, because > these test the core features of the wrappers. > > - David > > > > > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Aug 5 19:47:26 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 5 Aug 2015 19:47:26 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: <20150805153056.753300039@mail.rogue-research.com> References: <20150805153056.753300039@mail.rogue-research.com> Message-ID: <20150805234726.GA4284@bronto-burt.dev.benboeckel.net> On Wed, Aug 05, 2015 at 11:30:56 -0400, Sean McBride wrote: > - removing PowerPC support > - removing Carbon support > - removing OS X 10.5 support It seems we have one machine building against 10.5 right now for the superbuild (which builds Java binaries): https://buildbot.kitware.com/builders/vtk-kamino-osx-shared-release%2Bosx10.5%2Bsuperbuild Looking at the output, it is targeting 10.6's SDK with 10.5 as a minimum. Sebastien, what should we bump this to? 10.6? Most other VTK-based projects are targeting 10.7 or higher. > - removing Apple-gcc 4.2 support > - removing Xcode 3.x support > > If there's consensus, I volunteer to gut the relevant stuff. Rest looks fine with me. > I can also use clang-modernize to introduce nullptr usage, if that's > something we're ready to do in master now. nullptr can be pretty > easily emulated on older compilers, like ITK does. nullptr is probably a good place to start. I assume it also does 0 -> nullptr replacements? --Ben From david.gobbi at gmail.com Wed Aug 5 20:45:52 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 5 Aug 2015 18:45:52 -0600 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: Thanks, Andrew. I just pushed the CommonCore test updates to the branch. - David On Wed, Aug 5, 2015 at 5:11 PM, Andrew Maclean wrote: > Hi David, > > Wonderful news. > > Definitely be glad to help. > Setting up a Python 3.4 environment in Windows 10 on my laptop now. > I'll be using Anaconda Python. > > Once this is done, I'll maintain both a python 2.7 and Python 3.4 build > and see how things go. > > Regards > Andrew > > > On Thu, Aug 6, 2015 at 1:44 AM, David Gobbi wrote: > >> So, here's a brief update on python 3 status: >> >> The python-py3k merge branch compiles and runs with Python 3.2, 3.3, 3.4 >> and also Python 2.5, 2.6, 2.7 (I tried all six). So, yes, you can build >> VTK against Python 3, and you can run VTK programs with Python 3. I'll be >> doing a bit of cleanup of the next few days, but the current branch is very >> close to what I plan to merge. >> >> However: the test code in VTK is all written for Python 2, so right now >> the Python 3 buildbot that Ben has set up is showing all red for the >> testing. Converting the tests will be a lot of work, especially because >> the tests must continue to run with Python 2.6 and 2.7 (definitely not 2.5, >> though). Andrew, you mentioned that you might be able to provide some >> assistance, I would be very grateful for anything you have to offer. >> >> I've already begun converting the python tests in Common/Core, because >> these test the core features of the wrappers. >> >> - David >> >> >> >> >> >> > > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Wed Aug 5 20:51:36 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Thu, 6 Aug 2015 10:51:36 +1000 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: Ok thanks. I'll check it out soon. Just testing my builds and various scripts On Thu, Aug 6, 2015 at 10:45 AM, David Gobbi wrote: > Thanks, Andrew. I just pushed the CommonCore test updates to the branch. > > - David > > > On Wed, Aug 5, 2015 at 5:11 PM, Andrew Maclean > wrote: > >> Hi David, >> >> Wonderful news. >> >> Definitely be glad to help. >> Setting up a Python 3.4 environment in Windows 10 on my laptop now. >> I'll be using Anaconda Python. >> >> Once this is done, I'll maintain both a python 2.7 and Python 3.4 build >> and see how things go. >> >> Regards >> Andrew >> >> >> On Thu, Aug 6, 2015 at 1:44 AM, David Gobbi >> wrote: >> >>> So, here's a brief update on python 3 status: >>> >>> The python-py3k merge branch compiles and runs with Python 3.2, 3.3, 3.4 >>> and also Python 2.5, 2.6, 2.7 (I tried all six). So, yes, you can build >>> VTK against Python 3, and you can run VTK programs with Python 3. I'll be >>> doing a bit of cleanup of the next few days, but the current branch is very >>> close to what I plan to merge. >>> >>> However: the test code in VTK is all written for Python 2, so right now >>> the Python 3 buildbot that Ben has set up is showing all red for the >>> testing. Converting the tests will be a lot of work, especially because >>> the tests must continue to run with Python 2.6 and 2.7 (definitely not 2.5, >>> though). Andrew, you mentioned that you might be able to provide some >>> assistance, I would be very grateful for anything you have to offer. >>> >>> I've already begun converting the python tests in Common/Core, because >>> these test the core features of the wrappers. >>> >>> - David >>> >>> >>> >>> >>> >>> >> >> >> -- >> ___________________________________________ >> Andrew J. P. Maclean >> >> ___________________________________________ >> > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Aug 5 22:00:07 2015 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 5 Aug 2015 20:00:07 -0600 Subject: [vtk-developers] VTK Roadmap In-Reply-To: <20150805234726.GA4284@bronto-burt.dev.benboeckel.net> References: <20150805153056.753300039@mail.rogue-research.com> <20150805234726.GA4284@bronto-burt.dev.benboeckel.net> Message-ID: I'm ok with whatever target OS X version you plan to have. Sean may have a better idea of what is reasonable though. Seb On Wed, Aug 5, 2015 at 5:47 PM, Ben Boeckel wrote: > On Wed, Aug 05, 2015 at 11:30:56 -0400, Sean McBride wrote: > > - removing PowerPC support > > - removing Carbon support > > - removing OS X 10.5 support > > It seems we have one machine building against 10.5 right now for the > superbuild (which builds Java binaries): > > > https://buildbot.kitware.com/builders/vtk-kamino-osx-shared-release%2Bosx10.5%2Bsuperbuild > > Looking at the output, it is targeting 10.6's SDK with 10.5 as a > minimum. Sebastien, what should we bump this to? 10.6? Most other > VTK-based projects are targeting 10.7 or higher. > > > - removing Apple-gcc 4.2 support > > - removing Xcode 3.x support > > > > If there's consensus, I volunteer to gut the relevant stuff. > > Rest looks fine with me. > > > I can also use clang-modernize to introduce nullptr usage, if that's > > something we're ready to do in master now. nullptr can be pretty > > easily emulated on older compilers, like ITK does. > > nullptr is probably a good place to start. I assume it also does 0 -> > nullptr replacements? > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From DLRdave at aol.com Wed Aug 5 23:41:09 2015 From: DLRdave at aol.com (David Cole) Date: Wed, 5 Aug 2015 23:41:09 -0400 Subject: [vtk-developers] [vtkusers] VTK Roadmap In-Reply-To: References: <20150805153056.753300039@mail.rogue-research.com> <20150805234726.GA4284@bronto-burt.dev.benboeckel.net> Message-ID: Just as a point of information: I've got a 2007 or 2008 Mac mini at home which only has 1G of RAM and so is stuck on 10.6 as the last OS which will install and run on it... But that is still beyond the 10.5 you're talking about here. I would also be fine with discontinuing support for the older Mac stuff. D On Wednesday, August 5, 2015, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > I'm ok with whatever target OS X version you plan to have. > > Sean may have a better idea of what is reasonable though. > > Seb > > On Wed, Aug 5, 2015 at 5:47 PM, Ben Boeckel > wrote: > >> On Wed, Aug 05, 2015 at 11:30:56 -0400, Sean McBride wrote: >> > - removing PowerPC support >> > - removing Carbon support >> > - removing OS X 10.5 support >> >> It seems we have one machine building against 10.5 right now for the >> superbuild (which builds Java binaries): >> >> >> https://buildbot.kitware.com/builders/vtk-kamino-osx-shared-release%2Bosx10.5%2Bsuperbuild >> >> Looking at the output, it is targeting 10.6's SDK with 10.5 as a >> minimum. Sebastien, what should we bump this to? 10.6? Most other >> VTK-based projects are targeting 10.7 or higher. >> >> > - removing Apple-gcc 4.2 support >> > - removing Xcode 3.x support >> > >> > If there's consensus, I volunteer to gut the relevant stuff. >> >> Rest looks fine with me. >> >> > I can also use clang-modernize to introduce nullptr usage, if that's >> > something we're ready to do in master now. nullptr can be pretty >> > easily emulated on older compilers, like ITK does. >> >> nullptr is probably a good place to start. I assume it also does 0 -> >> nullptr replacements? >> >> --Ben >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at rogue-research.com Thu Aug 6 10:45:09 2015 From: sean at rogue-research.com (Sean McBride) Date: Thu, 6 Aug 2015 10:45:09 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: <20150805234726.GA4284@bronto-burt.dev.benboeckel.net> References: <20150805153056.753300039@mail.rogue-research.com> <20150805234726.GA4284@bronto-burt.dev.benboeckel.net> Message-ID: <20150806144509.240179075@mail.rogue-research.com> On Wed, 5 Aug 2015 19:47:26 -0400, Ben Boeckel said: >On Wed, Aug 05, 2015 at 11:30:56 -0400, Sean McBride wrote: >> - removing PowerPC support >> - removing Carbon support >> - removing OS X 10.5 support > >It seems we have one machine building against 10.5 right now for the >superbuild (which builds Java binaries): Rogue3 is also 10.5, but I disabled it the other day in anticipation of all this. Could someone mark it unexpected BTW... > https://buildbot.kitware.com/builders/vtk-kamino-osx-shared-release >%2Bosx10.5%2Bsuperbuild > >Looking at the output, it is targeting 10.6's SDK with 10.5 as a >minimum. Sebastien, what should we bump this to? 10.6? Most other >VTK-based projects are targeting 10.7 or higher. I'm fine with dropping only 10.5 for now, as my list is already fairly long. Once it's done, we can think about dropping 10.6 also. >> I can also use clang-modernize to introduce nullptr usage, if that's >> something we're ready to do in master now. nullptr can be pretty >> easily emulated on older compilers, like ITK does. > >nullptr is probably a good place to start. I assume it also does 0 -> >nullptr replacements? Yup: Cheers, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From berk.geveci at kitware.com Thu Aug 6 12:48:44 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 6 Aug 2015 12:48:44 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: References: <20150805153056.753300039@mail.rogue-research.com> Message-ID: +1. One minor thing: do we have access to a more recent big endian system. It would be great to keep testing VTK on a big endian system. -berk On Wed, Aug 5, 2015 at 11:39 AM, David E DeMarle wrote: > > On Wed, Aug 5, 2015 at 11:30 AM, Sean McBride > wrote: > >> - removing PowerPC support >> - removing Carbon support >> - removing OS X 10.5 support >> - removing Apple-gcc 4.2 support >> - removing Xcode 3.x support >> > > +1 from me > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From anis.kacem18 at gmail.com Thu Aug 6 13:09:49 2015 From: anis.kacem18 at gmail.com (anis kacem) Date: Thu, 6 Aug 2015 10:09:49 -0700 (MST) Subject: [vtk-developers] Geodesics on meshes - gerrit topic In-Reply-To: References: Message-ID: <1438880989847-5733312.post@n5.nabble.com> Hello Karthik, Please I am using your code to compute geodesic distance on Mesh using Fast Marching. I have a problem with some meshes : the algorithm cannot compute all distances the result was -1 for some vertices (Please find attached an image that explains what I am trying to say). Is there any condition for the mesh to use your algorithm ? Thank you for your answer ! -- View this message in context: http://vtk.1045678.n5.nabble.com/Geodesics-on-meshes-gerrit-topic-tp5722466p5733312.html Sent from the VTK - Dev mailing list archive at Nabble.com. From ben.boeckel at kitware.com Thu Aug 6 13:26:24 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 6 Aug 2015 13:26:24 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: References: <20150805153056.753300039@mail.rogue-research.com> Message-ID: <20150806172624.GA8761@megas.kitware.com> On Thu, Aug 06, 2015 at 12:48:44 -0400, Berk Geveci wrote: > One minor thing: do we have access to a more recent big endian system. It > would be great to keep testing VTK on a big endian system. We might be able to spin up a QEMU instance with a big-endian ARM setup: https://raspberrypi.stackexchange.com/questions/7279/big-endian-distribution-for-the-raspberry-pi With all the problems running on QEMU would entail, of course. Other than that, there's a Debian build for MIPS in big-endian: https://www.debian.org/ports/mips/ Would have to find a MIPS machine though. Looks like Loongson might be a way to go there: https://en.wikipedia.org/wiki/Loongson --Ben From ben.boeckel at kitware.com Thu Aug 6 13:29:50 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 6 Aug 2015 13:29:50 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: <20150806172624.GA8761@megas.kitware.com> References: <20150805153056.753300039@mail.rogue-research.com> <20150806172624.GA8761@megas.kitware.com> Message-ID: <20150806172950.GB8761@megas.kitware.com> On Thu, Aug 06, 2015 at 13:26:24 -0400, Ben Boeckel wrote: > Would have to find a MIPS machine though. Looks like Loongson might be a > way to go there: > > https://en.wikipedia.org/wiki/Loongson Nevermind, these seem to be little-endian. Debian lists these as big-endian: SGI Indy with R4x00 and R5000 CPUs, and Indigo2 with R4400 CPU (IP22). SGI O2 with R5000, R5200 and RM7000 CPU (IP32). Broadcom BCM91250A (SWARM) evaluation board (big and little-endian). MIPS Malta boards (big and little-endian, 32 and 64-bit). Cavium Octeon (big-endian). We used to have an O2 running around somewhere, but I suspect it is probably not something we should use as a buildbot :) . --Ben From sebastien.jourdain at kitware.com Thu Aug 6 13:55:54 2015 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 6 Aug 2015 11:55:54 -0600 Subject: [vtk-developers] VTK Roadmap In-Reply-To: References: <20150805153056.753300039@mail.rogue-research.com> <20150805234726.GA4284@bronto-burt.dev.benboeckel.net> Message-ID: If we can keep 10.6 running for that release, that would be great. On Wed, Aug 5, 2015 at 8:00 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > I'm ok with whatever target OS X version you plan to have. > > Sean may have a better idea of what is reasonable though. > > Seb > > On Wed, Aug 5, 2015 at 5:47 PM, Ben Boeckel > wrote: > >> On Wed, Aug 05, 2015 at 11:30:56 -0400, Sean McBride wrote: >> > - removing PowerPC support >> > - removing Carbon support >> > - removing OS X 10.5 support >> >> It seems we have one machine building against 10.5 right now for the >> superbuild (which builds Java binaries): >> >> >> https://buildbot.kitware.com/builders/vtk-kamino-osx-shared-release%2Bosx10.5%2Bsuperbuild >> >> Looking at the output, it is targeting 10.6's SDK with 10.5 as a >> minimum. Sebastien, what should we bump this to? 10.6? Most other >> VTK-based projects are targeting 10.7 or higher. >> >> > - removing Apple-gcc 4.2 support >> > - removing Xcode 3.x support >> > >> > If there's consensus, I volunteer to gut the relevant stuff. >> >> Rest looks fine with me. >> >> > I can also use clang-modernize to introduce nullptr usage, if that's >> > something we're ready to do in master now. nullptr can be pretty >> > easily emulated on older compilers, like ITK does. >> >> nullptr is probably a good place to start. I assume it also does 0 -> >> nullptr replacements? >> >> --Ben >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Thu Aug 6 14:04:44 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 6 Aug 2015 12:04:44 -0600 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: I'm planning to merge the py3k branch later today (around 4pm or so ET). This is going to cause some test failures on any dashboards that are still running python 2.5 (do any of these still exist?). Backwards compatibility for Python 2.6 and 2.7 should be excellent. They saw only to major changes: 1) The wrappers use new-style classes, i.e. every VTK class is wrapped as a type object. So type(vtkDataArray()) is vtkDataArray, unlike before when type(vtkDataArray()) was 'vtkobject'. 2) The wrappers support the new n-dimensional buffer interface, so numpy.asarray(vtk_array) creates a zero-copy numpy array from a VTK data array. Python 3.2 and higher should also work well, with some caveats: 1) VTK is still set up to use python 2 by default, so when configuring VTK with cmake, you must provide the paths to the python 3 executable, the python 3 include dir, and the python 3 library. 2) Most of the python tests and examples will only run with python 2. 3) Most of VTK's python utility modules (e.g. vtk.tk) will only run with python 2. 4) The wrappers will encode python strings to utf8 bytes before passing it to VTK. Obviously, converting the utility modules and tests to python 3 will be a lot of work. And keeping support for python 2 is a must ... all code must run with python 2.6, 2.7, and 3.2+. I'm particularly interested in hearing from people who are willing to help with these modules: vtk.wx, vtk.qt4, vtk.gtk Of course if anyone wants to convert some examples or tests, shoot an email to the list and I'll try to coordinate. If you want to update the wiki examples, then you can just log into the wiki and edit them. - David On Wed, Aug 5, 2015 at 6:51 PM, Andrew Maclean wrote: > Ok thanks. I'll check it out soon. Just testing my builds and various > scripts > > On Thu, Aug 6, 2015 at 10:45 AM, David Gobbi > wrote: > >> Thanks, Andrew. I just pushed the CommonCore test updates to the branch. >> >> - David >> >> >> On Wed, Aug 5, 2015 at 5:11 PM, Andrew Maclean > > wrote: >> >>> Hi David, >>> >>> Wonderful news. >>> >>> Definitely be glad to help. >>> Setting up a Python 3.4 environment in Windows 10 on my laptop now. >>> I'll be using Anaconda Python. >>> >>> Once this is done, I'll maintain both a python 2.7 and Python 3.4 build >>> and see how things go. >>> >>> Regards >>> Andrew >>> >>> >>> On Thu, Aug 6, 2015 at 1:44 AM, David Gobbi >>> wrote: >>> >>>> So, here's a brief update on python 3 status: >>>> >>>> The python-py3k merge branch compiles and runs with Python 3.2, 3.3, >>>> 3.4 and also Python 2.5, 2.6, 2.7 (I tried all six). So, yes, you can >>>> build VTK against Python 3, and you can run VTK programs with Python 3. >>>> I'll be doing a bit of cleanup of the next few days, but the current branch >>>> is very close to what I plan to merge. >>>> >>>> However: the test code in VTK is all written for Python 2, so right now >>>> the Python 3 buildbot that Ben has set up is showing all red for the >>>> testing. Converting the tests will be a lot of work, especially because >>>> the tests must continue to run with Python 2.6 and 2.7 (definitely not 2.5, >>>> though). Andrew, you mentioned that you might be able to provide some >>>> assistance, I would be very grateful for anything you have to offer. >>>> >>>> I've already begun converting the python tests in Common/Core, because >>>> these test the core features of the wrappers. >>>> >>>> - David >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Thu Aug 6 14:33:54 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 6 Aug 2015 12:33:54 -0600 Subject: [vtk-developers] code formatting prior to merge request In-Reply-To: References: <55C26E58.4060307@gmail.com> <55C278A3.50802@gmail.com> Message-ID: Hi Chaffra, When you edit a file, the most important thing is keep the style the same as it was before. This means that any code-styling tool like astyle or kwstyle that operates on the entire file will cause problems. You should only apply styling to the blocks of code that you, yourself, have added to the files. That makes git happy, because it can properly track all of the changes and attribute each block of code to the correct person. Also, the code must not have any hard tabs or invisible whitespace (extra spaces at the ends of lines, or extra blank lines at the end of files). The reason for this is that any changes to the code must be visible changes. Changing spaces to tabs or vice-versa is an invisible change, so tabs are not allowed. - David On Wed, Aug 5, 2015 at 3:00 PM, David E DeMarle wrote: > Please reply all to keep the list in on the discussion, thanks. > > I've never used either pretty-printer so I can't comment on their merits. > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Aug 5, 2015 at 4:57 PM, Chaffra Affouda wrote: > >> Thanks David, >> >> Is the more general way to use KWStyle or Astyle? >> >> >> >> >> On 08/05/2015 04:28 PM, David E DeMarle wrote: >> >> I've used this a bit with eclipse and it prevents most of the pedantic >> problems. >> >> I'm not an eclipse guru so I can't tell you how to apply it after the >> fact off the top of my head. >> >> hth >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> On Wed, Aug 5, 2015 at 4:13 PM, Chaffra Affouda >> wrote: >> >>> Hi, >>> >>> What's the best way to format the code prior to a merge request? I am >>> using eclipse to format the code but the kwrobot keeps rejecting the basic >>> content. >>> >>> Thanks, >>> Chaffra >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Aug 6 14:40:34 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 6 Aug 2015 14:40:34 -0400 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: <20150806184034.GA11569@megas.kitware.com> On Thu, Aug 06, 2015 at 12:04:44 -0600, David Gobbi wrote: > I'm planning to merge the py3k branch later today (around 4pm or so ET). > This is going to cause some test failures on any dashboards that are still > running python 2.5 (do any of these still exist?). Not on buildbot at least :) . > Backwards compatibility for Python 2.6 and 2.7 should be excellent. They > saw only to major changes: > 1) The wrappers use new-style classes, i.e. every VTK class is wrapped as a > type object. So type(vtkDataArray()) is vtkDataArray, unlike before when > type(vtkDataArray()) was 'vtkobject'. > 2) The wrappers support the new n-dimensional buffer interface, so > numpy.asarray(vtk_array) creates a zero-copy numpy array from a VTK data > array. > > Python 3.2 and higher should also work well, with some caveats: When I set up Windows buildbots with Python3, I'll try to use 3.2 there since most of the Linux distributions are 3.3+ already. What is OS X using these days for Python3? > 1) VTK is still set up to use python 2 by default, so when configuring VTK > with cmake, you must provide the paths to the python 3 executable, the > python 3 include dir, and the python 3 library. > 2) Most of the python tests and examples will only run with python 2. > 3) Most of VTK's python utility modules (e.g. vtk.tk) will only run with > python 2. > 4) The wrappers will encode python strings to utf8 bytes before passing it > to VTK. Yay! > Obviously, converting the utility modules and tests to python 3 will be a > lot of work. And keeping support for python 2 is a must ... all code must > run with python 2.6, 2.7, and 3.2+. Note that the `six` module is already in ThirdParty. We will probably want to add dependencies where needed to ensure it is brought in properly (or just depend on it from vtkPythonCore). We will also need to find versions of: - Twisted - Autobahn - ZopeInterface - mpi4py which support both versions (or make a py3 variant) for ThirdParty. ParaView will need a usable of pygments as well, so while we're searching, that should be on the shopping list as well. Thanks for the Python3 goodness! :) --Ben From sean at rogue-research.com Thu Aug 6 14:43:41 2015 From: sean at rogue-research.com (Sean McBride) Date: Thu, 6 Aug 2015 14:43:41 -0400 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: <20150806184341.867099609@mail.rogue-research.com> On Thu, 6 Aug 2015 12:04:44 -0600, David Gobbi said: >This is going to cause some test failures on any dashboards that are still >running python 2.5 (do any of these still exist?). OS X 10.5 uses 2.5. I just turned off my 10.5 VTK build the other day, I guess we'll see if there are any others... :) Cheers, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From david.gobbi at gmail.com Thu Aug 6 14:55:46 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 6 Aug 2015 12:55:46 -0600 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: <20150806184034.GA11569@megas.kitware.com> References: <20150806184034.GA11569@megas.kitware.com> Message-ID: On Thu, Aug 6, 2015 at 12:40 PM, Ben Boeckel wrote: > > What is OS X using these days for Python3? > OS X uses whatever Python 3 package you install yourself ;-) The ones at python.org work fine, and pip is great for add-ons. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From prabhu at aero.iitb.ac.in Thu Aug 6 23:16:18 2015 From: prabhu at aero.iitb.ac.in (Prabhu Ramachandran) Date: Fri, 7 Aug 2015 08:46:18 +0530 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: <55C42302.2000607@aero.iitb.ac.in> Hi David, Thanks a ton for the python3 work. I have been under the weather but will try and find some time to test things out. I am not sure I will be quick enough to contribute any fixes. Thanks again for the fantastic work on this. cheers, Prabhu On 8/6/15 11:34 PM, David Gobbi wrote: > I'm planning to merge the py3k branch later today (around 4pm or so ET). This is > going to cause some test failures on any dashboards that are still running > python 2.5 (do any of these still exist?). > > Backwards compatibility for Python 2.6 and 2.7 should be excellent. They saw > only to major changes: > 1) The wrappers use new-style classes, i.e. every VTK class is wrapped as a type > object. So type(vtkDataArray()) is vtkDataArray, unlike before when > type(vtkDataArray()) was 'vtkobject'. > 2) The wrappers support the new n-dimensional buffer interface, so > numpy.asarray(vtk_array) creates a zero-copy numpy array from a VTK data array. > > Python 3.2 and higher should also work well, with some caveats: > 1) VTK is still set up to use python 2 by default, so when configuring VTK with > cmake, you must provide the paths to the python 3 executable, the python 3 > include dir, and the python 3 library. > 2) Most of the python tests and examples will only run with python 2. > 3) Most of VTK's python utility modules (e.g. vtk.tk ) will only > run with python 2. > 4) The wrappers will encode python strings to utf8 bytes before passing it to VTK. > > Obviously, converting the utility modules and tests to python 3 will be a lot of > work. And keeping support for python 2 is a must ... all code must run with > python 2.6, 2.7, and 3.2+. > > I'm particularly interested in hearing from people who are willing to help with > these modules: vtk.wx, vtk.qt4, vtk.gtk > > Of course if anyone wants to convert some examples or tests, shoot an email to > the list and I'll try to coordinate. If you want to update the wiki examples, > then you can just log into the wiki and edit them. > > - David > > > On Wed, Aug 5, 2015 at 6:51 PM, Andrew Maclean > wrote: > > Ok thanks. I'll check it out soon. Just testing my builds and various scripts > > On Thu, Aug 6, 2015 at 10:45 AM, David Gobbi > wrote: > > Thanks, Andrew. I just pushed the CommonCore test updates to the branch. > > - David > > > On Wed, Aug 5, 2015 at 5:11 PM, Andrew Maclean > > wrote: > > Hi David, > > Wonderful news. > > Definitely be glad to help. > Setting up a Python 3.4 environment in Windows 10 on my laptop now. > I'll be using Anaconda Python. > > Once this is done, I'll maintain both a python 2.7 and Python 3.4 > build and see how things go. > > Regards > Andrew > > > On Thu, Aug 6, 2015 at 1:44 AM, David Gobbi > wrote: > > So, here's a brief update on python 3 status: > > The python-py3k merge branch compiles and runs with Python 3.2, > 3.3, 3.4 and also Python 2.5, 2.6, 2.7 (I tried all six). So, > yes, you can build VTK against Python 3, and you can run VTK > programs with Python 3. I'll be doing a bit of cleanup of the > next few days, but the current branch is very close to what I > plan to merge. > > However: the test code in VTK is all written for Python 2, so > right now the Python 3 buildbot that Ben has set up is showing > all red for the testing. Converting the tests will be a lot of > work, especially because the tests must continue to run with > Python 2.6 and 2.7 (definitely not 2.5, though). Andrew, you > mentioned that you might be able to provide some assistance, I > would be very grateful for anything you have to offer. > > I've already begun converting the python tests in Common/Core, > because these test the core features of the wrappers. > > - David > > > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > From david.gobbi at gmail.com Fri Aug 7 00:45:29 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 6 Aug 2015 22:45:29 -0600 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: <55C42302.2000607@aero.iitb.ac.in> References: <55C42302.2000607@aero.iitb.ac.in> Message-ID: Hi Prabhu, It's good to hear from you. I'm sure that even months down the line there will still be niggling details waiting for testing and attention. Cheers, - David On Thu, Aug 6, 2015 at 9:16 PM, Prabhu Ramachandran wrote: > Hi David, > > Thanks a ton for the python3 work. I have been under the weather but will > try > and find some time to test things out. I am not sure I will be quick > enough to > contribute any fixes. > > Thanks again for the fantastic work on this. > > cheers, > Prabhu > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Fri Aug 7 11:21:42 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Fri, 7 Aug 2015 09:21:42 -0600 Subject: [vtk-developers] The numpy dataset_adaptor and Python 3 Message-ID: Right now all of the tests in Common/Core pass with Python 3 except for TestNumpyInteface: File "/Users/dgobbi/Work/Kitware/vtk-gitlab/Common/Core/Testing/Python/TestNumpyInterface.py", line 69, in assert algs.all(1 + randomVec - 1 - randomVec < 1E-4) TypeError: unsupported operand type(s) for +: 'int' and 'VTKCompositeDataArray' The problem lies with the VTKArray class in dataset_adapter.py. The custom numeric operations work differently in Python 3, my guess is that some extra type coercion is needed. Can someone take a look? - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Fri Aug 7 19:11:05 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Fri, 7 Aug 2015 17:11:05 -0600 Subject: [vtk-developers] The numpy dataset_adaptor and Python 3 In-Reply-To: References: Message-ID: Never mind, I fixed the problem. Python 3 was ignoring the metaclass hooks. On Fri, Aug 7, 2015 at 9:21 AM, David Gobbi wrote: > Right now all of the tests in Common/Core pass with Python 3 except for > TestNumpyInteface: > > File > "/Users/dgobbi/Work/Kitware/vtk-gitlab/Common/Core/Testing/Python/TestNumpyInterface.py", > line 69, in > assert algs.all(1 + randomVec - 1 - randomVec < 1E-4) > TypeError: unsupported operand type(s) for +: 'int' and > 'VTKCompositeDataArray' > > The problem lies with the VTKArray class in dataset_adapter.py. The > custom numeric operations work differently in Python 3, my guess is that > some extra type coercion is needed. Can someone take a look? > > - David > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Sat Aug 8 00:51:13 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Sat, 8 Aug 2015 14:51:13 +1000 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. Message-ID: David you have done a fantastic job! Just letting you know that by making python 3 changes to rtImageTest.py, info.py, catch.py and expr.py, I am now getting 89% tests passed, 54 tests failed out of 481! In rtImageTest.py, Tkinter is now tkinter in Python 3. For handling renamed libraries is code like this acceptable (it works in Python 2 and 3): ################## try: # for Python2 print('Trying Python2') import Tkinter as tk print('Python2 Ok') except ImportError: # for Python3 print('Trying Python3') import tkinter as tk print('Python3 Ok') pythonTk = tk.Tk() ################## The remaining failing tests are mainly related to the print statement, failures relating to string.find [in vtkMethodParser.py], no module named exceptions etc. I need to do some thorough testing on rtImageTest.py, info.py, catch.py, expr.py, vtkMethodParser.py for both Python 2.7 and Python 3.4 I am so impressed that these few changes have worked. I'll try and get all the tests passing for Python 2 and Python 3 in the next week or so and create a merge request for review. Regards Andrew -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Sat Aug 8 08:48:22 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Sat, 8 Aug 2015 06:48:22 -0600 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: Wow, I didn't expect so many of the tests to be passing so soon. Thanks for looking into these so quickly! I just merged some fixes to my own 2 to 3 changes for Common/Core/Testing/Python and Wrapping/Python/vtk. These are mainly fixes to "print" calls that I'd been lazy with the first time. So please rebase either onto the current master or onto this commit: https://gitlab.kitware.com/dgobbi/vtk/commit/26ad0555 Cheers, - David On Fri, Aug 7, 2015 at 10:51 PM, Andrew Maclean wrote: > David you have done a fantastic job! > > > Just letting you know that by making python 3 changes to rtImageTest.py, > info.py, catch.py and expr.py, > > I am now getting 89% tests passed, 54 tests failed out of 481! > > In rtImageTest.py, Tkinter is now tkinter in Python 3. > For handling renamed libraries is code like this acceptable (it works in > Python 2 and 3): > ################## > try: > # for Python2 > print('Trying Python2') > import Tkinter as tk > print('Python2 Ok') > except ImportError: > # for Python3 > print('Trying Python3') > import tkinter as tk > print('Python3 Ok') > pythonTk = tk.Tk() > ################## > > The remaining failing tests are mainly related to the print statement, > failures relating to string.find [in vtkMethodParser.py], no module named > exceptions etc. > > I need to do some thorough testing on rtImageTest.py, info.py, catch.py, > expr.py, vtkMethodParser.py for both Python 2.7 and Python 3.4 > > I am so impressed that these few changes have worked. > > I'll try and get all the tests passing for Python 2 and Python 3 in the > next week or so and create a merge request for review. > > Regards > Andrew > > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Sat Aug 8 21:50:24 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Sun, 9 Aug 2015 11:50:24 +1000 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: Thanks for that. I rebased against the master and picked up those changes. Andrew On Sat, Aug 8, 2015 at 10:48 PM, David Gobbi wrote: > Wow, I didn't expect so many of the tests to be passing so soon. Thanks > for looking into these so quickly! > > I just merged some fixes to my own 2 to 3 changes for > Common/Core/Testing/Python and Wrapping/Python/vtk. These are mainly fixes > to "print" calls that I'd been lazy with the first time. > > So please rebase either onto the current master or onto this commit: > https://gitlab.kitware.com/dgobbi/vtk/commit/26ad0555 > > Cheers, > > - David > > On Fri, Aug 7, 2015 at 10:51 PM, Andrew Maclean > wrote: > >> David you have done a fantastic job! >> >> >> Just letting you know that by making python 3 changes to rtImageTest.py, >> info.py, catch.py and expr.py, >> >> I am now getting 89% tests passed, 54 tests failed out of 481! >> >> In rtImageTest.py, Tkinter is now tkinter in Python 3. >> For handling renamed libraries is code like this acceptable (it works in >> Python 2 and 3): >> ################## >> try: >> # for Python2 >> print('Trying Python2') >> import Tkinter as tk >> print('Python2 Ok') >> except ImportError: >> # for Python3 >> print('Trying Python3') >> import tkinter as tk >> print('Python3 Ok') >> pythonTk = tk.Tk() >> ################## >> >> The remaining failing tests are mainly related to the print statement, >> failures relating to string.find [in vtkMethodParser.py], no module named >> exceptions etc. >> >> I need to do some thorough testing on rtImageTest.py, info.py, catch.py, >> expr.py, vtkMethodParser.py for both Python 2.7 and Python 3.4 >> >> I am so impressed that these few changes have worked. >> >> I'll try and get all the tests passing for Python 2 and Python 3 in the >> next week or so and create a merge request for review. >> >> Regards >> Andrew >> >> >> -- >> ___________________________________________ >> Andrew J. P. Maclean >> >> ___________________________________________ >> > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From majcjc at gmail.com Sun Aug 9 02:47:34 2015 From: majcjc at gmail.com (Lin M) Date: Sun, 9 Aug 2015 14:47:34 +0800 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> Message-ID: Hi Dr. Thompson, I have pushed new methods to compute point inversion and projection to gitlab. It took longer time than I expected. It would be really helpful if you could review the code a little bit. Thanks! Best, Lin On Mon, Aug 3, 2015 at 10:50 AM, David Thompson wrote: > Hi Lin, > > Yes, that is correct. Inserting knot values does not change the polynomial > degree or shape, it just adds control points so that the weights are > uniform (as required by the B?zier basis). So, the underlying > parameterization is unchanged... it just has more piecewise segments. > > David > > > > On Aug 2, 2015, at 22:38, Lin M wrote: > > Hi Dr. Thompson, > > I have a question about the inversion and projection. Currently, we > evaluate the NURBS by inserting knots and making it into Bezier forms. My > question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], > would it be the same to evaluate u = 0.2 in the new knot vector which is a > bezier form? > > Best, > Lin > > On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: > >> Hi Dr. Thompson, >> >> I have added new method >> vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >> >> I'm now working on the point inversion part. >> >> Best, >> Lin >> >> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson < >> david.thompson at kitware.com> wrote: >> >>> Hi Lin, >>> >>> How is triangular/tetrahedral patch interpolation going? They will be a >>> basic building block of the contouring and cutting algorithms. By >>> identifying points on edges, edges on surfaces, and surfaces in volumes >>> that take on a single value, a single patch can be decomposed into sections >>> that are inside, outside, or on an isosurface. Not all of these pieces can >>> be expressed as brick patches, but they can be expressed as simplicial >>> patches. >>> >>> David >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Sun Aug 9 11:41:25 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Sun, 9 Aug 2015 09:41:25 -0600 Subject: [vtk-developers] Problem with Python "hasattr" Message-ID: This is related to a bug I found in vtk/numpy_support/dataset_adapter.py. According to the Python docs (both 2 and 3), hasattr() is implemented by calling getattr() and returning False if an exception occurs. Note that it doesn't say "if an AttributeError exception", it simply says "if an exception". https://docs.python.org/2/library/functions.html#hasattr This leads to some unexpected behavior in this method from dataset_adaptor.py: def __getattr__(self, name): "Forwards unknown attribute requests to VTK array." if not hasattr(self, "VTKObject") or not self.VTKObject: raise AttributeError("class has no attribute %s" % name) return getattr(self.VTKObject, name) If __getattr__() calls hasattr() on an attribute that isn't there, then infinite recursion results. In Python, infinite recursion results in a RuntimeError exception. But hasattr() by definition should catch any exception. This is where things get hairy, and where Python 2 and Python 3 are apparently different. In Python 2, hasattr() silently catches the infinite recursion as a RuntimeError. Therefore, the above __getattr__() function behaves as expected (but it wastes a ton of CPU cycles while python exhausts its stack). In Python 3, hasattr() does not catch the infinite recursion, and the RuntimeError becomes visible to the user. To make a long story short, using hasattr() in __getattr__() is very, very bad because the only way it could possibly return "False" is by triggering infinite recursion, and the consequences of the infinite recursion are different in Python 2 (where the RuntimeError is silenced by hasattr) versus Python 3 (where the RuntimeError is exposed). If anyone is curious, try running the following program on Python 2 and Python 3 to see the difference in behavior: ======= class test_hasattr: def __init__(self): self.bar = "hi" def __getattr__(self, attr): print("calling hasattr") if hasattr(self, "baz"): return "hasattr" raise AttributeError if __name__ == "__main__": c = test_hasattr() try: c.wombat except AttributeError: pass print("passed!") ======= - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Sun Aug 9 18:59:11 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Sun, 9 Aug 2015 18:59:11 -0400 Subject: [vtk-developers] Problem with Python "hasattr" In-Reply-To: References: Message-ID: <20150809225911.GA14621@bronto-burt.dev.benboeckel.net> On Sun, Aug 09, 2015 at 09:41:25 -0600, David Gobbi wrote: > https://docs.python.org/2/library/functions.html#hasattr > > This leads to some unexpected behavior in this method from > dataset_adaptor.py: > > def __getattr__(self, name): > "Forwards unknown attribute requests to VTK array." > if not hasattr(self, "VTKObject") or not self.VTKObject: > raise AttributeError("class has no attribute %s" % name) > return getattr(self.VTKObject, name) How about: def __getattr__(self, name): return getattr(self.VTKObject, name) --Ben From david.gobbi at gmail.com Sun Aug 9 19:15:00 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Sun, 9 Aug 2015 17:15:00 -0600 Subject: [vtk-developers] Problem with Python "hasattr" In-Reply-To: <20150809225911.GA14621@bronto-burt.dev.benboeckel.net> References: <20150809225911.GA14621@bronto-burt.dev.benboeckel.net> Message-ID: On Sun, Aug 9, 2015 at 4:59 PM, Ben Boeckel wrote: > > How about: > > def __getattr__(self, name): > return getattr(self.VTKObject, name) If "self" has no "VTKObject" attribute, it immediately goes into infinite recursion. The following is the solution that I used. It checks the __dict__ because I know that's where the VTKObject attribute will be kept if it exists. def __getattr__(self, name): try: o = self.__dict__["VTKObject"] except KeyError: o = None if o is None: raise AttributeError("class has no attribute %s" % name) return getattr(o, name) It could be simplified a bit except that the "VTKObject" attribute can sometimes be set to "None", and it would be confusing if the error message said " 'NoneType' object has no attribute 'name' ". The solution would be more complicated than the above if the "VTKObject" of "self" might be kept somewhere other than __dict__, for example if it was an attribute generated by a descriptor in self's type object. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Sun Aug 9 20:50:39 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Sun, 9 Aug 2015 20:50:39 -0400 Subject: [vtk-developers] Problem with Python "hasattr" In-Reply-To: References: <20150809225911.GA14621@bronto-burt.dev.benboeckel.net> Message-ID: <20150810005039.GA25145@bronto-burt.dev.benboeckel.net> On Sun, Aug 09, 2015 at 17:15:00 -0600, David Gobbi wrote: > If "self" has no "VTKObject" attribute, it immediately goes into infinite > recursion. Doh. Can't __hasattr__ just be implemented directly? :( > The following is the solution that I used. It checks the __dict__ because I > know that's where the VTKObject attribute will be kept if it exists. > > def __getattr__(self, name): > try: > o = self.__dict__["VTKObject"] > except KeyError: > o = None > if o is None: > raise AttributeError("class has no attribute %s" % name) Better: raise AttributeError("%s has no attribute %s" % (self.__class__.__name__, name)) --Ben From andrew.amaclean at gmail.com Mon Aug 10 05:00:20 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Mon, 10 Aug 2015 19:00:20 +1000 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. Message-ID: So far so good,(2to3 has been very helpful). --------------------------------------------------------------- 98% tests passed, 12 tests failed out of 489 Total Test time (real) = 1046.22 sec The following tests FAILED: 655 - vtkFiltersGeneralPython-TestMultiBlockStreamer (Failed) 676 - vtkFiltersGeneralPython-splitVectors (Failed) 677 - vtkFiltersGeneralPython-streamTracer (Failed) 1263 - vtkIONetCDFPython-NetCDFCF2DBounds (Failed) 1264 - vtkIONetCDFPython-NetCDFCFSetOutputType (Failed) 1265 - vtkIONetCDFPython-NetCDFCFSphericalCoords (Failed) 1266 - vtkIONetCDFPython-NetCDFCFUnstructured (Failed) 1267 - vtkIONetCDFPython-NetCDFReader (Failed) 1935 - vtkRenderingTkPython-cursor3D (Failed) 1936 - vtkRenderingTkPython-TestTextActor3D (Failed) 1937 - vtkRenderingTkPythvtkIONetCDFPythonon-TestTkRenderWidget (Failed) 1938 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) See: https://gitlab.kitware.com/vtk/vtk/merge_requests/514#note_26500 currently marked as WIP. --------------------------------------------------------------- David, one interesting thing that I am seeing is that the above vtkFiltersGeneralPython and vtkIONetCDFPython tests that fail actually pass in Python 2 but the image generated is different in Python 3. Could there some slight difference in the wrapping e.g the treatment of floats or ints? I may be able to get the vtkIONetCDFPython working. I suspect cursor3D.py may now be Ok. Once I fix errors in vtkRenderingTkPython I will remove the WIP: appellation. Regards Andrew On Sun, Aug 9, 2015 at 11:50 AM, Andrew Maclean wrote: > Thanks for that. > I rebased against the master and picked up those changes. > > Andrew > > On Sat, Aug 8, 2015 at 10:48 PM, David Gobbi > wrote: > >> Wow, I didn't expect so many of the tests to be passing so soon. Thanks >> for looking into these so quickly! >> >> I just merged some fixes to my own 2 to 3 changes for >> Common/Core/Testing/Python and Wrapping/Python/vtk. These are mainly fixes >> to "print" calls that I'd been lazy with the first time. >> >> So please rebase either onto the current master or onto this commit: >> https://gitlab.kitware.com/dgobbi/vtk/commit/26ad0555 >> >> Cheers, >> >> - David >> >> On Fri, Aug 7, 2015 at 10:51 PM, Andrew Maclean < >> andrew.amaclean at gmail.com> wrote: >> >>> David you have done a fantastic job! >>> >>> >>> Just letting you know that by making python 3 changes to rtImageTest.py, >>> info.py, catch.py and expr.py, >>> >>> I am now getting 89% tests passed, 54 tests failed out of 481! >>> >>> In rtImageTest.py, Tkinter is now tkinter in Python 3. >>> For handling renamed libraries is code like this acceptable (it works in >>> Python 2 and 3): >>> ################## >>> try: >>> # for Python2 >>> print('Trying Python2') >>> import Tkinter as tk >>> print('Python2 Ok') >>> except ImportError: >>> # for Python3 >>> print('Trying Python3') >>> import tkinter as tk >>> print('Python3 Ok') >>> pythonTk = tk.Tk() >>> ################## >>> >>> The remaining failing tests are mainly related to the print statement, >>> failures relating to string.find [in vtkMethodParser.py], no module named >>> exceptions etc. >>> >>> I need to do some thorough testing on rtImageTest.py, info.py, >>> catch.py, expr.py, vtkMethodParser.py for both Python 2.7 and Python 3.4 >>> >>> I am so impressed that these few changes have worked. >>> >>> I'll try and get all the tests passing for Python 2 and Python 3 in the >>> next week or so and create a merge request for review. >>> >>> Regards >>> Andrew >>> >>> >>> -- >>> ___________________________________________ >>> Andrew J. P. Maclean >>> >>> ___________________________________________ >>> >> >> > > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Mon Aug 10 10:01:44 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 10 Aug 2015 08:01:44 -0600 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: Very nice. On my machine I see only six failures. This is with Python 3.2, and apparently no NetCDF. The following tests FAILED: 354 - vtkCommonDataModelPython-TestTemplates (Failed) 969 - vtkFiltersSourcesPython-squadViewer (Failed) 1944 - vtkRenderingTkPython-cursor3D (Failed) 1945 - vtkRenderingTkPython-TestTextActor3D (Failed) 1946 - vtkRenderingTkPython-TestTkRenderWidget (Failed) 1947 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) The TestTemplates seems to be a simple syntax error, the "u" string prefix is not allowed in python 3.2. 354: File "Common/DataModel/Testing/Python/TestTemplates.py", line 56 354: value = u"hello" The squadViewer test is failing because it is still trying to import Tkinter. There were no changes with respect to floats, and the only really suspicious int related change is the change in the division operator. It looks like this is very close to prime time. After this, it's only the examples that need to be converted (and of course the Paraview and Slicer teams have a lot of work ahead of them, but our experience here should give them confidence!) - David On Mon, Aug 10, 2015 at 3:00 AM, Andrew Maclean wrote: > So far so good,(2to3 has been very helpful). > --------------------------------------------------------------- > 98% tests passed, 12 tests failed out of 489 > > Total Test time (real) = 1046.22 sec > > The following tests FAILED: > 655 - vtkFiltersGeneralPython-TestMultiBlockStreamer (Failed) > 676 - vtkFiltersGeneralPython-splitVectors (Failed) > 677 - vtkFiltersGeneralPython-streamTracer (Failed) > 1263 - vtkIONetCDFPython-NetCDFCF2DBounds (Failed) > 1264 - vtkIONetCDFPython-NetCDFCFSetOutputType (Failed) > 1265 - vtkIONetCDFPython-NetCDFCFSphericalCoords (Failed) > 1266 - vtkIONetCDFPython-NetCDFCFUnstructured (Failed) > 1267 - vtkIONetCDFPython-NetCDFReader (Failed) > 1935 - vtkRenderingTkPython-cursor3D (Failed) > 1936 - vtkRenderingTkPython-TestTextActor3D (Failed) > 1937 - vtkRenderingTkPythvtkIONetCDFPythonon-TestTkRenderWidget > (Failed) > 1938 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) > > See: https://gitlab.kitware.com/vtk/vtk/merge_requests/514#note_26500 > currently marked as WIP. > --------------------------------------------------------------- > > David, one interesting thing that I am seeing is that the above > vtkFiltersGeneralPython and vtkIONetCDFPython tests that fail actually pass > in Python 2 but the image generated is different in Python 3. Could there > some slight difference in the wrapping e.g the treatment of floats or ints? > > I may be able to get the vtkIONetCDFPython working. I suspect cursor3D.py > may now be Ok. > > Once I fix errors in vtkRenderingTkPython I will remove the WIP: > appellation. > > > Regards > Andrew > > > On Sun, Aug 9, 2015 at 11:50 AM, Andrew Maclean > wrote: > >> Thanks for that. >> I rebased against the master and picked up those changes. >> >> Andrew >> >> On Sat, Aug 8, 2015 at 10:48 PM, David Gobbi >> wrote: >> >>> Wow, I didn't expect so many of the tests to be passing so soon. Thanks >>> for looking into these so quickly! >>> >>> I just merged some fixes to my own 2 to 3 changes for >>> Common/Core/Testing/Python and Wrapping/Python/vtk. These are mainly fixes >>> to "print" calls that I'd been lazy with the first time. >>> >>> So please rebase either onto the current master or onto this commit: >>> https://gitlab.kitware.com/dgobbi/vtk/commit/26ad0555 >>> >>> Cheers, >>> >>> - David >>> >>> On Fri, Aug 7, 2015 at 10:51 PM, Andrew Maclean < >>> andrew.amaclean at gmail.com> wrote: >>> >>>> David you have done a fantastic job! >>>> >>>> >>>> Just letting you know that by making python 3 changes to >>>> rtImageTest.py, info.py, catch.py and expr.py, >>>> >>>> I am now getting 89% tests passed, 54 tests failed out of 481! >>>> >>>> In rtImageTest.py, Tkinter is now tkinter in Python 3. >>>> For handling renamed libraries is code like this acceptable (it works >>>> in Python 2 and 3): >>>> ################## >>>> try: >>>> # for Python2 >>>> print('Trying Python2') >>>> import Tkinter as tk >>>> print('Python2 Ok') >>>> except ImportError: >>>> # for Python3 >>>> print('Trying Python3') >>>> import tkinter as tk >>>> print('Python3 Ok') >>>> pythonTk = tk.Tk() >>>> ################## >>>> >>>> The remaining failing tests are mainly related to the print statement, >>>> failures relating to string.find [in vtkMethodParser.py], no module named >>>> exceptions etc. >>>> >>>> I need to do some thorough testing on rtImageTest.py, info.py, >>>> catch.py, expr.py, vtkMethodParser.py for both Python 2.7 and Python 3.4 >>>> >>>> I am so impressed that these few changes have worked. >>>> >>>> I'll try and get all the tests passing for Python 2 and Python 3 in the >>>> next week or so and create a merge request for review. >>>> >>>> Regards >>>> Andrew >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Mon Aug 10 10:05:47 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Mon, 10 Aug 2015 15:05:47 +0100 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: Hi, On Mon, Aug 10, 2015 at 3:01 PM, David Gobbi wrote: > Very nice. On my machine I see only six failures. This is with Python 3.2, > and apparently no NetCDF. > > The following tests FAILED: > 354 - vtkCommonDataModelPython-TestTemplates (Failed) > 969 - vtkFiltersSourcesPython-squadViewer (Failed) > 1944 - vtkRenderingTkPython-cursor3D (Failed) > 1945 - vtkRenderingTkPython-TestTextActor3D (Failed) > 1946 - vtkRenderingTkPython-TestTkRenderWidget (Failed) > 1947 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) > > The TestTemplates seems to be a simple syntax error, the "u" string prefix > is not allowed in python 3.2. > 354: File "Common/DataModel/Testing/Python/TestTemplates.py", line 56 > 354: value = u"hello" Is it worth requiring Python 3.3 or higher to fix this? I doubt you'll have many Python 3.2 users, even if you released now - Python 3.4 has been around for a while now. Cheers, Matthew From ken.martin at kitware.com Mon Aug 10 10:39:56 2015 From: ken.martin at kitware.com (Ken Martin) Date: Mon, 10 Aug 2015 10:39:56 -0400 Subject: [vtk-developers] vtkRendererDelegate Message-ID: <5b8b7bb9e86a0cbd863bd52b9c0bcb0a@mail.gmail.com> There is a class called vtkRendererDelegate that I?m not sure anyone is using. Currently it does nothing in VTK or PV. You could subclass off of vtkRendererDelegate AND subclass off of vtkRenderer to make it do something I suppose. It seems like maybe an early version of render passes. Does anyone know of this being used? Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 ken.martin at kitware.com 919 869-8871 (w) This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Mon Aug 10 10:55:54 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 10 Aug 2015 08:55:54 -0600 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: On Mon, Aug 10, 2015 at 8:05 AM, Matthew Brett wrote: > Hi, > > On Mon, Aug 10, 2015 at 3:01 PM, David Gobbi > wrote: > > Very nice. On my machine I see only six failures. This is with Python > 3.2, > > and apparently no NetCDF. > > > > The following tests FAILED: > > 354 - vtkCommonDataModelPython-TestTemplates (Failed) > > 969 - vtkFiltersSourcesPython-squadViewer (Failed) > > 1944 - vtkRenderingTkPython-cursor3D (Failed) > > 1945 - vtkRenderingTkPython-TestTextActor3D (Failed) > > 1946 - vtkRenderingTkPython-TestTkRenderWidget (Failed) > > 1947 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) > > > > The TestTemplates seems to be a simple syntax error, the "u" string > prefix > > is not allowed in python 3.2. > > 354: File "Common/DataModel/Testing/Python/TestTemplates.py", line > 56 > > 354: value = u"hello" > > Is it worth requiring Python 3.3 or higher to fix this? I doubt > you'll have many Python 3.2 users, even if you released now - Python > 3.4 has been around for a while now. > Out of hundreds of python tests there's a single line that won't work with Python 3.2, and you people are clamouring to drop Python 3.2. Honestly, what's up with that? I wouldn't be testing on Python 3.2 if I didn't think it would be worth supporting. There are still plenty of deployed systems around (particularly Ubuntu and Debian) that come with Python 3.2 packages, and they're far from End of Life. And honestly, supporting Python 3.2 doesn't take much effort. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Mon Aug 10 11:02:13 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Mon, 10 Aug 2015 16:02:13 +0100 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: On Mon, Aug 10, 2015 at 3:55 PM, David Gobbi wrote: > On Mon, Aug 10, 2015 at 8:05 AM, Matthew Brett > wrote: >> >> Hi, >> >> On Mon, Aug 10, 2015 at 3:01 PM, David Gobbi >> wrote: >> > Very nice. On my machine I see only six failures. This is with Python >> > 3.2, >> > and apparently no NetCDF. >> > >> > The following tests FAILED: >> > 354 - vtkCommonDataModelPython-TestTemplates (Failed) >> > 969 - vtkFiltersSourcesPython-squadViewer (Failed) >> > 1944 - vtkRenderingTkPython-cursor3D (Failed) >> > 1945 - vtkRenderingTkPython-TestTextActor3D (Failed) >> > 1946 - vtkRenderingTkPython-TestTkRenderWidget (Failed) >> > 1947 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) >> > >> > The TestTemplates seems to be a simple syntax error, the "u" string >> > prefix >> > is not allowed in python 3.2. >> > 354: File "Common/DataModel/Testing/Python/TestTemplates.py", line >> > 56 >> > 354: value = u"hello" >> >> Is it worth requiring Python 3.3 or higher to fix this? I doubt >> you'll have many Python 3.2 users, even if you released now - Python >> 3.4 has been around for a while now. > > > Out of hundreds of python tests there's a single line that won't work with > Python 3.2, and you people are clamouring to drop Python 3.2. Honestly, > what's up with that? I didn't intend to put any pressure on you, sorry if it came across that way. I made the suggestion just because many of us Python-only projects have started to drop 3.2, but no worries if you'd prefer to keep it, Cheers, Matthew From ben.boeckel at kitware.com Mon Aug 10 11:31:04 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 10 Aug 2015 11:31:04 -0400 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: <20150810153104.GA15239@megas.kitware.com> On Mon, Aug 10, 2015 at 08:55:54 -0600, David Gobbi wrote: > I wouldn't be testing on Python 3.2 if I didn't think it would be worth > supporting. There are still plenty of deployed systems around > (particularly Ubuntu and Debian) that come with Python 3.2 packages, and > they're far from End of Life. And honestly, supporting Python 3.2 doesn't > take much effort. FTR, the only Debian and Ubuntu releases with 3.2 are oldstable (wheezy, supported until February 2016; LTS until May 2018) and precise (12.04 LTS, supported until April 2017). In any case, isn't this fixed with unicode('hello')? --Ben From david.gobbi at gmail.com Mon Aug 10 12:56:59 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 10 Aug 2015 10:56:59 -0600 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: <20150810153104.GA15239@megas.kitware.com> References: <20150810153104.GA15239@megas.kitware.com> Message-ID: On Mon, Aug 10, 2015 at 9:31 AM, Ben Boeckel wrote: > On Mon, Aug 10, 2015 at 08:55:54 -0600, David Gobbi wrote: > > I wouldn't be testing on Python 3.2 if I didn't think it would be worth > > supporting. There are still plenty of deployed systems around > > (particularly Ubuntu and Debian) that come with Python 3.2 packages, and > > they're far from End of Life. And honestly, supporting Python 3.2 > doesn't > > take much effort. > > FTR, the only Debian and Ubuntu releases with 3.2 are oldstable (wheezy, > supported until February 2016; LTS until May 2018) and precise (12.04 > LTS, supported until April 2017). > > In any case, isn't this fixed with unicode('hello')? There is no unicode() in Python 3, so you'd have to make one for compatibility: if sys.hexversion >= 0x03000000: unicode = str - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Mon Aug 10 15:53:01 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 10 Aug 2015 13:53:01 -0600 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: On Mon, Aug 10, 2015 at 3:00 AM, Andrew Maclean wrote: > > 655 - vtkFiltersGeneralPython-TestMultiBlockStreamer (Failed) > 676 - vtkFiltersGeneralPython-splitVectors (Failed) > 677 - vtkFiltersGeneralPython-streamTracer (Failed) > 1263 - vtkIONetCDFPython-NetCDFCF2DBounds (Failed) > 1264 - vtkIONetCDFPython-NetCDFCFSetOutputType (Failed) > 1265 - vtkIONetCDFPython-NetCDFCFSphericalCoords (Failed) > 1266 - vtkIONetCDFPython-NetCDFCFUnstructured (Failed) > 1267 - vtkIONetCDFPython-NetCDFReader (Failed) > For the above tests, it looks like the failure was due to a typo in my wrapper code. I mistyped PY_VERSION_HEX in two locations. After I've merged this fix, you can rebase. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill.lorensen at gmail.com Mon Aug 10 16:35:37 2015 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Mon, 10 Aug 2015 16:35:37 -0400 Subject: [vtk-developers] vtkRendererDelegate In-Reply-To: <5b8b7bb9e86a0cbd863bd52b9c0bcb0a@mail.gmail.com> References: <5b8b7bb9e86a0cbd863bd52b9c0bcb0a@mail.gmail.com> Message-ID: Ken, It has 0 code coverage and was added by Francois Bertel in 2008. He may know what purpse if serves... Bill On Mon, Aug 10, 2015 at 10:39 AM, Ken Martin wrote: > There is a class called vtkRendererDelegate that I?m not sure anyone is > using. Currently it does nothing in VTK or PV. You could subclass off of > vtkRendererDelegate AND subclass off of vtkRenderer to make it do something > I suppose. It seems like maybe an early version of render passes. Does > anyone know of this being used? > > > > > > > > Ken Martin PhD > > Chairman & CFO > > Kitware Inc. > > 28 Corporate Drive > > Clifton Park NY 12065 > > ken.martin at kitware.com > > 919 869-8871 (w) > > > > > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > > > > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > -- Unpaid intern in BillsBasement at noware dot com From ben.boeckel at kitware.com Mon Aug 10 22:04:05 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 10 Aug 2015 22:04:05 -0400 Subject: [vtk-developers] vtkRendererDelegate In-Reply-To: References: <5b8b7bb9e86a0cbd863bd52b9c0bcb0a@mail.gmail.com> Message-ID: <20150811020405.GB18026@bronto-burt.dev.benboeckel.net> On Mon, Aug 10, 2015 at 16:35:37 -0400, Bill Lorensen wrote: > It has 0 code coverage and was added by Francois Bertel in 2008. He > may know what purpse if serves... Francois left in 2010 or so IIRC. --Ben From andrew.amaclean at gmail.com Tue Aug 11 08:19:34 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Tue, 11 Aug 2015 22:19:34 +1000 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: Hi All, Git and I had an argument about rebasing ... I lost the argument. [git +1, Andrew -1] Consequently I have had to create a new merge request: https://gitlab.kitware.com/vtk/vtk/merge_requests/518 I have picked up all of David's comments from the old merge request and the results (on my machine) are: 99% tests passed, 4 tests failed out of 489 Total Test time (real) = 990.25 sec The following tests FAILED: 1935 - vtkRenderingTkPython-cursor3D (Failed) 1936 - vtkRenderingTkPython-TestTextActor3D (Failed) 1937 - vtkRenderingTkPython-TestTkRenderWidget (Failed) 1938 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) Errors while running CTest If no one objects, would like to defer these fails to a later merge request. David, I have a question about Python 3.2: In reading the documentation, this version of python accepted strings like unicode('The Zen of VTK') but not u'The Zen of VTK' which is accepted in Python 2.7/3.3+. Is it safe to use: from __future__ import unicode_literals and will Python 3.2 then accept statements like: zen = u'The Zen of VTK' Can someone test this on Python 3.2, it works on Python 3.4 and Python 2.7. If it doesn't work, are there any alternatives? Regards Andrew On Tue, Aug 11, 2015 at 5:53 AM, David Gobbi wrote: > On Mon, Aug 10, 2015 at 3:00 AM, Andrew Maclean > wrote: > >> >> 655 - vtkFiltersGeneralPython-TestMultiBlockStreamer (Failed) >> 676 - vtkFiltersGeneralPython-splitVectors (Failed) >> 677 - vtkFiltersGeneralPython-streamTracer (Failed) >> 1263 - vtkIONetCDFPython-NetCDFCF2DBounds (Failed) >> 1264 - vtkIONetCDFPython-NetCDFCFSetOutputType (Failed) >> 1265 - vtkIONetCDFPython-NetCDFCFSphericalCoords (Failed) >> 1266 - vtkIONetCDFPython-NetCDFCFUnstructured (Failed) >> 1267 - vtkIONetCDFPython-NetCDFReader (Failed) >> > > For the above tests, it looks like the failure was due to a typo in my > wrapper code. > I mistyped PY_VERSION_HEX in two locations. After I've merged this fix, > you can > rebase. > > - David > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Tue Aug 11 09:40:43 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Tue, 11 Aug 2015 07:40:43 -0600 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: Hi Andrew, I've looked at TestTemplates.py, and it is going to require that I give it some special attention in order for it to provide the same coverage under Python 3 as it provides with Python 2. For proper coverage, that test needs a string that cannot be expressed in ASCII, so I'll just build such a string at the top of the program: # create a unicode string for python 2 and python 3 if sys.hexversion >= 0x03000000: francois = 'Fran\xe7ois' else: francois = unicode('Fran\xe7ois', 'latin1') On Python 3.2, only TestTemplates and the Tk tests failed. I'll fix the former and take a look at the latter. Also, if you don't mind, I'd like to cherry-pick your commit onto my python-py3k branch and submit as a new merge request. That will allow us to keep all the Python 3 commits as a contiguous set. - David On Tue, Aug 11, 2015 at 6:19 AM, Andrew Maclean wrote: > Hi All, > Git and I had an argument about rebasing ... I lost the argument. [git > +1, Andrew -1] > > Consequently I have had to create a new merge request: > https://gitlab.kitware.com/vtk/vtk/merge_requests/518 > > I have picked up all of David's comments from the old merge request and > the results (on my machine) are: > 99% tests passed, 4 tests failed out of 489 > > Total Test time (real) = 990.25 sec > > The following tests FAILED: > 1935 - vtkRenderingTkPython-cursor3D (Failed) > 1936 - vtkRenderingTkPython-TestTextActor3D (Failed) > 1937 - vtkRenderingTkPython-TestTkRenderWidget (Failed) > 1938 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) > Errors while running CTest > > If no one objects, would like to defer these fails to a later merge > request. > > David, I have a question about Python 3.2: > In reading the documentation, this version of python accepted strings like > unicode('The Zen of VTK') but not u'The Zen of VTK' which is accepted in > Python 2.7/3.3+. > > Is it safe to use: > from __future__ import unicode_literals > > and will Python 3.2 then accept statements like: > zen = u'The Zen of VTK' > > Can someone test this on Python 3.2, it works on Python 3.4 and Python 2.7. > > If it doesn't work, are there any alternatives? > > > Regards > Andrew > > > > > > > On Tue, Aug 11, 2015 at 5:53 AM, David Gobbi > wrote: > >> On Mon, Aug 10, 2015 at 3:00 AM, Andrew Maclean < >> andrew.amaclean at gmail.com> wrote: >> >>> >>> 655 - vtkFiltersGeneralPython-TestMultiBlockStreamer (Failed) >>> 676 - vtkFiltersGeneralPython-splitVectors (Failed) >>> 677 - vtkFiltersGeneralPython-streamTracer (Failed) >>> 1263 - vtkIONetCDFPython-NetCDFCF2DBounds (Failed) >>> 1264 - vtkIONetCDFPython-NetCDFCFSetOutputType (Failed) >>> 1265 - vtkIONetCDFPython-NetCDFCFSphericalCoords (Failed) >>> 1266 - vtkIONetCDFPython-NetCDFCFUnstructured (Failed) >>> 1267 - vtkIONetCDFPython-NetCDFReader (Failed) >>> >> >> For the above tests, it looks like the failure was due to a typo in my >> wrapper code. >> I mistyped PY_VERSION_HEX in two locations. After I've merged this fix, >> you can >> rebase. >> >> - David >> >> > > > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Tue Aug 11 17:05:00 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Wed, 12 Aug 2015 07:05:00 +1000 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: David, That would be really good if you do a cherry pick. I don't mind at all. While I was doing was thinking that it would be nice to have everything in the one place! Wrt the Tk stuff it seems to be an import error: ImportError: No module named 'vtkLoadPythonTkWidgets' Regards Andrew On Tue, Aug 11, 2015 at 11:40 PM, David Gobbi wrote: > Hi Andrew, > > I've looked at TestTemplates.py, and it is going to require that I give it > some special attention in order for it to provide the same coverage under > Python 3 as it provides with Python 2. > > For proper coverage, that test needs a string that cannot be expressed in > ASCII, so I'll just build such a string at the top of the program: > > # create a unicode string for python 2 and python 3 > if sys.hexversion >= 0x03000000: > francois = 'Fran\xe7ois' > else: > francois = unicode('Fran\xe7ois', 'latin1') > > On Python 3.2, only TestTemplates and the Tk tests failed. I'll fix the > former and take a look at the latter. > > Also, if you don't mind, I'd like to cherry-pick your commit onto my > python-py3k branch and submit as a new merge request. That will allow us > to keep all the Python 3 commits as a contiguous set. > > - David > > > On Tue, Aug 11, 2015 at 6:19 AM, Andrew Maclean > wrote: > >> Hi All, >> Git and I had an argument about rebasing ... I lost the argument. [git >> +1, Andrew -1] >> >> Consequently I have had to create a new merge request: >> https://gitlab.kitware.com/vtk/vtk/merge_requests/518 >> >> I have picked up all of David's comments from the old merge request and >> the results (on my machine) are: >> 99% tests passed, 4 tests failed out of 489 >> >> Total Test time (real) = 990.25 sec >> >> The following tests FAILED: >> 1935 - vtkRenderingTkPython-cursor3D (Failed) >> 1936 - vtkRenderingTkPython-TestTextActor3D (Failed) >> 1937 - vtkRenderingTkPython-TestTkRenderWidget (Failed) >> 1938 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) >> Errors while running CTest >> >> If no one objects, would like to defer these fails to a later merge >> request. >> >> David, I have a question about Python 3.2: >> In reading the documentation, this version of python accepted strings >> like unicode('The Zen of VTK') but not u'The Zen of VTK' which is accepted >> in Python 2.7/3.3+. >> >> Is it safe to use: >> from __future__ import unicode_literals >> >> and will Python 3.2 then accept statements like: >> zen = u'The Zen of VTK' >> >> Can someone test this on Python 3.2, it works on Python 3.4 and Python >> 2.7. >> >> If it doesn't work, are there any alternatives? >> >> >> Regards >> Andrew >> >> >> >> >> >> >> On Tue, Aug 11, 2015 at 5:53 AM, David Gobbi >> wrote: >> >>> On Mon, Aug 10, 2015 at 3:00 AM, Andrew Maclean < >>> andrew.amaclean at gmail.com> wrote: >>> >>>> >>>> 655 - vtkFiltersGeneralPython-TestMultiBlockStreamer (Failed) >>>> 676 - vtkFiltersGeneralPython-splitVectors (Failed) >>>> 677 - vtkFiltersGeneralPython-streamTracer (Failed) >>>> 1263 - vtkIONetCDFPython-NetCDFCF2DBounds (Failed) >>>> 1264 - vtkIONetCDFPython-NetCDFCFSetOutputType (Failed) >>>> 1265 - vtkIONetCDFPython-NetCDFCFSphericalCoords (Failed) >>>> 1266 - vtkIONetCDFPython-NetCDFCFUnstructured (Failed) >>>> 1267 - vtkIONetCDFPython-NetCDFReader (Failed) >>>> >>> >>> For the above tests, it looks like the failure was due to a typo in my >>> wrapper code. >>> I mistyped PY_VERSION_HEX in two locations. After I've merged this fix, >>> you can >>> rebase. >>> >>> - David >>> >>> >> >> >> >> -- >> ___________________________________________ >> Andrew J. P. Maclean >> >> ___________________________________________ >> > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Tue Aug 11 17:18:49 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Tue, 11 Aug 2015 15:18:49 -0600 Subject: [vtk-developers] Update: Making Tests Python 3/2 compatible. In-Reply-To: References: Message-ID: Hi Andrew, The vtk/tk/vtkLoadPythonTkWidgets.py module is imported by the other modules in vtk/tk/, and the rules for relative import changed in Python 3. Now it has to be imported with a leading "." like this: import .vtkLoadPythonTkWidgets For Python 2, "from __future__ import absolute_import" is needed. I've done the cherry-pick and have done a quick sweep through the remaining issues. This is very, very close! We'll be seeing a green dashboard for Python 3 before the day is through. https://gitlab.kitware.com/vtk/vtk/merge_requests/522 - David On Tue, Aug 11, 2015 at 3:05 PM, Andrew Maclean wrote: > David, > That would be really good if you do a cherry pick. I don't mind at > all. While I was doing was thinking that it would be nice to have > everything in the one place! > > Wrt the Tk stuff it seems to be an import error: ImportError: No module > named 'vtkLoadPythonTkWidgets' > > Regards > Andrew > > > > On Tue, Aug 11, 2015 at 11:40 PM, David Gobbi > wrote: > >> Hi Andrew, >> >> I've looked at TestTemplates.py, and it is going to require that I give >> it some special attention in order for it to provide the same coverage >> under Python 3 as it provides with Python 2. >> >> For proper coverage, that test needs a string that cannot be expressed in >> ASCII, so I'll just build such a string at the top of the program: >> >> # create a unicode string for python 2 and python 3 >> if sys.hexversion >= 0x03000000: >> francois = 'Fran\xe7ois' >> else: >> francois = unicode('Fran\xe7ois', 'latin1') >> >> On Python 3.2, only TestTemplates and the Tk tests failed. I'll fix the >> former and take a look at the latter. >> >> Also, if you don't mind, I'd like to cherry-pick your commit onto my >> python-py3k branch and submit as a new merge request. That will allow us >> to keep all the Python 3 commits as a contiguous set. >> >> - David >> >> >> On Tue, Aug 11, 2015 at 6:19 AM, Andrew Maclean < >> andrew.amaclean at gmail.com> wrote: >> >>> Hi All, >>> Git and I had an argument about rebasing ... I lost the argument. >>> [git +1, Andrew -1] >>> >>> Consequently I have had to create a new merge request: >>> https://gitlab.kitware.com/vtk/vtk/merge_requests/518 >>> >>> I have picked up all of David's comments from the old merge request and >>> the results (on my machine) are: >>> 99% tests passed, 4 tests failed out of 489 >>> >>> Total Test time (real) = 990.25 sec >>> >>> The following tests FAILED: >>> 1935 - vtkRenderingTkPython-cursor3D (Failed) >>> 1936 - vtkRenderingTkPython-TestTextActor3D (Failed) >>> 1937 - vtkRenderingTkPython-TestTkRenderWidget (Failed) >>> 1938 - vtkRenderingTkPython-TestTkRenderWindowInteractor (Failed) >>> Errors while running CTest >>> >>> If no one objects, would like to defer these fails to a later merge >>> request. >>> >>> David, I have a question about Python 3.2: >>> In reading the documentation, this version of python accepted strings >>> like unicode('The Zen of VTK') but not u'The Zen of VTK' which is accepted >>> in Python 2.7/3.3+. >>> >>> Is it safe to use: >>> from __future__ import unicode_literals >>> >>> and will Python 3.2 then accept statements like: >>> zen = u'The Zen of VTK' >>> >>> Can someone test this on Python 3.2, it works on Python 3.4 and Python >>> 2.7. >>> >>> If it doesn't work, are there any alternatives? >>> >>> >>> Regards >>> Andrew >>> >>> >>> >>> >>> >>> >>> On Tue, Aug 11, 2015 at 5:53 AM, David Gobbi >>> wrote: >>> >>>> On Mon, Aug 10, 2015 at 3:00 AM, Andrew Maclean < >>>> andrew.amaclean at gmail.com> wrote: >>>> >>>>> >>>>> 655 - vtkFiltersGeneralPython-TestMultiBlockStreamer (Failed) >>>>> 676 - vtkFiltersGeneralPython-splitVectors (Failed) >>>>> 677 - vtkFiltersGeneralPython-streamTracer (Failed) >>>>> 1263 - vtkIONetCDFPython-NetCDFCF2DBounds (Failed) >>>>> 1264 - vtkIONetCDFPython-NetCDFCFSetOutputType (Failed) >>>>> 1265 - vtkIONetCDFPython-NetCDFCFSphericalCoords (Failed) >>>>> 1266 - vtkIONetCDFPython-NetCDFCFUnstructured (Failed) >>>>> 1267 - vtkIONetCDFPython-NetCDFReader (Failed) >>>>> >>>> >>>> For the above tests, it looks like the failure was due to a typo in my >>>> wrapper code. >>>> I mistyped PY_VERSION_HEX in two locations. After I've merged this >>>> fix, you can >>>> rebase. >>>> >>>> - David >>>> >>>> >>> >>> >>> >>> -- >>> ___________________________________________ >>> Andrew J. P. Maclean >>> >>> ___________________________________________ >>> >> >> > > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Aug 11 18:40:24 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 11 Aug 2015 18:40:24 -0400 Subject: [vtk-developers] Announce: vtk 6.3.0 release candidate 2 is ready Message-ID: <20150811224024.GA30431@megas.kitware.com> The VTK developement team is happy to announce that VTK 6.3 is continuing along the release candidate stage! You can find the source, data, and new vtkpython binary packages here: http://www.vtk.org/VTK/resources/software.html#releasecandidate Please try this version of VTK and report any issues to the list or the bug tracker so that we can try to address them before VTK 6.3.0 final. Compared to rc1, this contains various bug and crash fixes. We hope you enjoy this release of VTK! As always, contact Kitware and the mailing lists for assistance. Thanks, --Ben -------------- next part -------------- Brad King (1): eaf0888 Revert "Remove forward boosts declarations" Cory Quammen (1): e5168a1 Fix crash where vtkColorTransferFunction has 0 nodes Dave DeMarle (1): bc11760 fix a bug where leftover color state would break value painter David Gobbi (1): fbcbad2 Fix normal computation in vtkContourTriangulator. Joachim Pouderoux (2): 0063d5d Fix crash in vtkPolygon::ParametrizePolygon for invalid polygons. 248d525 linking: default to not making warnings fatal errors Johan Andruejol (1): 50d2a98 Remove forward boosts declarations Sean McBride (1): 2ed04c9 Update SimpleCocoaVTK Xcode project to work with VTK 6.3 T.J. Corona (5): ffc25be Prevent str.begin() from being dereferenced if str is empty. 1f79d6b Removed double delete in vtkXdmfWriter destructor. c3a86fd XML data reader now throws an error when reading arrays with duplicate names. 5e5fb77 Force a lookup table reset after vtkAbstractArray::Reset() bce1530 Added a means to prevent private headers from being installed. From majcjc at gmail.com Wed Aug 12 08:39:14 2015 From: majcjc at gmail.com (Lin M) Date: Wed, 12 Aug 2015 20:39:14 +0800 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> Message-ID: Hi Dr. Thompson, I have finished the point inversion and projection algorithm for both 1-d, 2-d and 3-d NURBS. We can turn to more dedicated algorithms now. Best, Lin On Sun, Aug 9, 2015 at 2:47 PM, Lin M wrote: > Hi Dr. Thompson, > > I have pushed new methods to compute point inversion and projection to > gitlab. > It took longer time than I expected. It would be really helpful if you > could review the code a little bit. Thanks! > > Best, > Lin > > On Mon, Aug 3, 2015 at 10:50 AM, David Thompson < > david.thompson at kitware.com> wrote: > >> Hi Lin, >> >> Yes, that is correct. Inserting knot values does not change the >> polynomial degree or shape, it just adds control points so that the weights >> are uniform (as required by the B?zier basis). So, the underlying >> parameterization is unchanged... it just has more piecewise segments. >> >> David >> >> >> >> On Aug 2, 2015, at 22:38, Lin M wrote: >> >> Hi Dr. Thompson, >> >> I have a question about the inversion and projection. Currently, we >> evaluate the NURBS by inserting knots and making it into Bezier forms. My >> question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], >> would it be the same to evaluate u = 0.2 in the new knot vector which is a >> bezier form? >> >> Best, >> Lin >> >> On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: >> >>> Hi Dr. Thompson, >>> >>> I have added new method >>> vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >>> >>> I'm now working on the point inversion part. >>> >>> Best, >>> Lin >>> >>> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson < >>> david.thompson at kitware.com> wrote: >>> >>>> Hi Lin, >>>> >>>> How is triangular/tetrahedral patch interpolation going? They will be a >>>> basic building block of the contouring and cutting algorithms. By >>>> identifying points on edges, edges on surfaces, and surfaces in volumes >>>> that take on a single value, a single patch can be decomposed into sections >>>> that are inside, outside, or on an isosurface. Not all of these pieces can >>>> be expressed as brick patches, but they can be expressed as simplicial >>>> patches. >>>> >>>> David >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Wed Aug 12 10:47:55 2015 From: david.thompson at kitware.com (David Thompson) Date: Wed, 12 Aug 2015 10:47:55 -0400 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> Message-ID: <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Hi Lin, > I have finished the point inversion and projection algorithm for both 1-d, 2-d and 3-d NURBS. > We can turn to more dedicated algorithms now. I think that a better use of the remaining time would be to clean up and merge your work into VTK. You have made great progress and it looks really good. It would be better to polish it so it is easy to maintain and get it accepted than to push for contouring and be left with something that is not tested well enough to be maintained as VTK changes. That way you or another GSoC student can continue things next summer. It has been my experience that the only way to ensure it is maintained is to make sure it is extensively tested so that when a change to VTK is proposed, the developer making the change gets immediate feedback that the change requires work on the spline classes. So, I propose doing the following: 1. There are some style changes that need to be made. I'll push some changes off your branch to sampling/vtk, but to get started: a. There is trailing whitespace at the ends of lines in many files which are disallowed by our pre-merge scripts. b. Method names should be spelled out, so "Curv," "Surf," and "Volm" should become "Curve," "Surface," and "Volume." I know it is nice for names to have the same length, but it is nicer for other developers to be able to predict the names of methods across the entire toolkit. :-) 2. Testing should be more exhaustive testing to make sure that changes to VTK don't break things. Right now only interpolation is tested at all (and there is a lot of commented-out code in that test which should probably be removed). Other tests should include, for example, a. simplicial (triangular and tetrahedral) patch interpolation (you can do this with an image-based test and/or by checking that numeric values are within a tolerance of an analytical solution, b. point inversion for rectangular and simplicial patches c. derivative computation d. the NURBS adaptor should be tested with several shapes whose patches can be computed 3. Every class should have documentation that covers its purpose, its intended lifecycle (how should it be used, what methods must be called before others, etc.). The way field data is used to hold NURBS knot vectors should be documented and should have an example data file (which should be used in an image test to verify that it continues to work). Thanks, David > On Sun, Aug 9, 2015 at 2:47 PM, Lin M wrote: > Hi Dr. Thompson, > > I have pushed new methods to compute point inversion and projection to gitlab. > It took longer time than I expected. It would be really helpful if you could review the code a little bit. Thanks! > > Best, > Lin > > On Mon, Aug 3, 2015 at 10:50 AM, David Thompson wrote: > Hi Lin, > > Yes, that is correct. Inserting knot values does not change the polynomial degree or shape, it just adds control points so that the weights are uniform (as required by the B?zier basis). So, the underlying parameterization is unchanged... it just has more piecewise segments. > > David > > > > On Aug 2, 2015, at 22:38, Lin M wrote: > >> Hi Dr. Thompson, >> >> I have a question about the inversion and projection. Currently, we evaluate the NURBS by inserting knots and making it into Bezier forms. My question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], would it be the same to evaluate u = 0.2 in the new knot vector which is a bezier form? >> >> Best, >> Lin >> >> On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: >> Hi Dr. Thompson, >> >> I have added new method vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >> >> I'm now working on the point inversion part. >> >> Best, >> Lin >> >> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson wrote: >> Hi Lin, >> >> How is triangular/tetrahedral patch interpolation going? They will be a basic building block of the contouring and cutting algorithms. By identifying points on edges, edges on surfaces, and surfaces in volumes that take on a single value, a single patch can be decomposed into sections that are inside, outside, or on an isosurface. Not all of these pieces can be expressed as brick patches, but they can be expressed as simplicial patches. >> >> David >> >> > > From majcjc at gmail.com Wed Aug 12 11:07:45 2015 From: majcjc at gmail.com (majcjc at gmail.com) Date: Wed, 12 Aug 2015 15:07:45 +0000 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Message-ID: Thank you for your suggestions! I will polish the code and make them throughly tested before merged to VTK. Best, Lin On Wed, Aug 12, 2015 at 7:48 AM -0700, "David Thompson" wrote: Hi Lin, > I have finished the point inversion and projection algorithm for both 1-d, 2-d and 3-d NURBS. > We can turn to more dedicated algorithms now. I think that a better use of the remaining time would be to clean up and merge your work into VTK. You have made great progress and it looks really good. It would be better to polish it so it is easy to maintain and get it accepted than to push for contouring and be left with something that is not tested well enough to be maintained as VTK changes. That way you or another GSoC student can continue things next summer. It has been my experience that the only way to ensure it is maintained is to make sure it is extensively tested so that when a change to VTK is proposed, the developer making the change gets immediate feedback that the change requires work on the spline classes. So, I propose doing the following: 1. There are some style changes that need to be made. I'll push some changes off your branch to sampling/vtk, but to get started: a. There is trailing whitespace at the ends of lines in many files which are disallowed by our pre-merge scripts. b. Method names should be spelled out, so "Curv," "Surf," and "Volm" should become "Curve," "Surface," and "Volume." I know it is nice for names to have the same length, but it is nicer for other developers to be able to predict the names of methods across the entire toolkit. :-) 2. Testing should be more exhaustive testing to make sure that changes to VTK don't break things. Right now only interpolation is tested at all (and there is a lot of commented-out code in that test which should probably be removed). Other tests should include, for example, a. simplicial (triangular and tetrahedral) patch interpolation (you can do this with an image-based test and/or by checking that numeric values are within a tolerance of an analytical solution, b. point inversion for rectangular and simplicial patches c. derivative computation d. the NURBS adaptor should be tested with several shapes whose patches can be computed 3. Every class should have documentation that covers its purpose, its intended lifecycle (how should it be used, what methods must be called before others, etc.). The way field data is used to hold NURBS knot vectors should be documented and should have an example data file (which should be used in an image test to verify that it continues to work). Thanks, David > On Sun, Aug 9, 2015 at 2:47 PM, Lin M wrote: > Hi Dr. Thompson, > > I have pushed new methods to compute point inversion and projection to gitlab. > It took longer time than I expected. It would be really helpful if you could review the code a little bit. Thanks! > > Best, > Lin > > On Mon, Aug 3, 2015 at 10:50 AM, David Thompson wrote: > Hi Lin, > > Yes, that is correct. Inserting knot values does not change the polynomial degree or shape, it just adds control points so that the weights are uniform (as required by the B?zier basis). So, the underlying parameterization is unchanged... it just has more piecewise segments. > > David > > > > On Aug 2, 2015, at 22:38, Lin M wrote: > >> Hi Dr. Thompson, >> >> I have a question about the inversion and projection. Currently, we evaluate the NURBS by inserting knots and making it into Bezier forms. My question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], would it be the same to evaluate u = 0.2 in the new knot vector which is a bezier form? >> >> Best, >> Lin >> >> On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: >> Hi Dr. Thompson, >> >> I have added new method vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >> >> I'm now working on the point inversion part. >> >> Best, >> Lin >> >> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson wrote: >> Hi Lin, >> >> How is triangular/tetrahedral patch interpolation going? They will be a basic building block of the contouring and cutting algorithms. By identifying points on edges, edges on surfaces, and surfaces in volumes that take on a single value, a single patch can be decomposed into sections that are inside, outside, or on an isosurface. Not all of these pieces can be expressed as brick patches, but they can be expressed as simplicial patches. >> >> David >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Aug 12 11:19:15 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 12 Aug 2015 11:19:15 -0400 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' In-Reply-To: References: <55cb5ffd399ba_73743fe48375ba14108583e@uservoice.com> Message-ID: Hi folks, This came through VTK's uservoice. I didn't think that we stopped support any Tk widgets. Am I wrong? Best, -berk ---------- Forwarded message ---------- From: VTK Date: Wed, Aug 12, 2015 at 11:02 AM Subject: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' To: "berk.geveci" > Customer Feedback for VTK vtk.uservoice.com New suggestion 1 votes Return support for Tkinter widgets. Posted in General Tkinter is a good GUI toolkit, is cross-platform, simple to use and lightweight (as opposed to Qt), which is important for scientific users like me developing tools with graphics capabilities. I know it is not very popular, but it only needs support and usage to gain visibility and expand its user base. Lack of support from important projects like VTK don't help in the cause, so it seems to me like a vicious circle. So please, return the support for the widgets. [image: Guille Giraldo]Guille Giraldo on Aug 12, 2015 (0 comments ) Delete Mark as Spam If you would like to stop receiving these emails you may unsubscribe . [image: powered by UserVoice] -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Wed Aug 12 11:42:49 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 12 Aug 2015 09:42:49 -0600 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' In-Reply-To: References: <55cb5ffd399ba_73743fe48375ba14108583e@uservoice.com> Message-ID: That's news to me. Just yesterday, me and Andrew were testing the Tk widgets to make sure that they were compatible with the Python 3 changes on all platforms. Are they still packaged in the binary releases? - David On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci wrote: > Hi folks, > > This came through VTK's uservoice. I didn't think that we stopped support > any Tk widgets. Am I wrong? > > Best, > -berk > > ---------- Forwarded message ---------- > From: VTK > Date: Wed, Aug 12, 2015 at 11:02 AM > Subject: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter > widgets.' > To: "berk.geveci" > > > > Customer Feedback for VTK vtk.uservoice.com > > New suggestion > 1 > votes > Return support for Tkinter widgets. > > > Posted in General > > > Tkinter is a good GUI toolkit, is cross-platform, simple to use and > lightweight (as opposed to Qt), which is important for scientific users > like me developing tools with graphics capabilities. > > I know it is not very popular, but it only needs support and usage to gain > visibility and expand its user base. Lack of support from important > projects like VTK don't help in the cause, so it seems to me like a vicious > circle. > > So please, return the support for the widgets. > > [image: Guille Giraldo]Guille Giraldo > > on Aug 12, 2015 (0 comments > ) > > Delete > Mark > as Spam > > > If you would like to stop receiving these emails you may unsubscribe > > . > > [image: powered by UserVoice] > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Aug 12 11:49:54 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 12 Aug 2015 11:49:54 -0400 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' In-Reply-To: References: <55cb5ffd399ba_73743fe48375ba14108583e@uservoice.com> Message-ID: Tk is not turned on in the vtkpython binaries. Last time was probably in the Tcl binary (windows only) in 5.8 or 5.10.0. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi wrote: > That's news to me. Just yesterday, me and Andrew were testing the Tk > widgets to make sure that they were compatible with the Python 3 changes on > all platforms. Are they still packaged in the binary releases? > > - David > > > On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci > wrote: > >> Hi folks, >> >> This came through VTK's uservoice. I didn't think that we stopped support >> any Tk widgets. Am I wrong? >> >> Best, >> -berk >> >> ---------- Forwarded message ---------- >> From: VTK >> Date: Wed, Aug 12, 2015 at 11:02 AM >> Subject: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter >> widgets.' >> To: "berk.geveci" > >> >> >> Customer Feedback for VTK vtk.uservoice.com >> >> New suggestion >> 1 >> votes >> Return support for Tkinter widgets. >> >> >> Posted in General >> >> >> Tkinter is a good GUI toolkit, is cross-platform, simple to use and >> lightweight (as opposed to Qt), which is important for scientific users >> like me developing tools with graphics capabilities. >> >> I know it is not very popular, but it only needs support and usage to >> gain visibility and expand its user base. Lack of support from important >> projects like VTK don't help in the cause, so it seems to me like a vicious >> circle. >> >> So please, return the support for the widgets. >> >> [image: Guille Giraldo]Guille Giraldo >> >> on Aug 12, 2015 (0 comments >> ) >> >> Delete >> Mark >> as Spam >> >> >> If you would like to stop receiving these emails you may unsubscribe >> >> . >> >> [image: powered by UserVoice] >> >> > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Aug 12 12:08:20 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 12 Aug 2015 12:08:20 -0400 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' In-Reply-To: References: <55cb5ffd399ba_73743fe48375ba14108583e@uservoice.com> Message-ID: OK thanks for the info. I will respond and try to find out more. Maybe it's a distro that he is talking about... -berk On Wed, Aug 12, 2015 at 11:49 AM, David E DeMarle wrote: > Tk is not turned on in the vtkpython binaries. > > Last time was probably in the Tcl binary (windows only) in 5.8 or 5.10.0. > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi > wrote: > >> That's news to me. Just yesterday, me and Andrew were testing the Tk >> widgets to make sure that they were compatible with the Python 3 changes on >> all platforms. Are they still packaged in the binary releases? >> >> - David >> >> >> On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci >> wrote: >> >>> Hi folks, >>> >>> This came through VTK's uservoice. I didn't think that we stopped >>> support any Tk widgets. Am I wrong? >>> >>> Best, >>> -berk >>> >>> ---------- Forwarded message ---------- >>> From: VTK >>> Date: Wed, Aug 12, 2015 at 11:02 AM >>> Subject: [vtk.uservoice.com] New suggestion: 'Return support for >>> Tkinter widgets.' >>> To: "berk.geveci" > >>> >>> >>> Customer Feedback for VTK vtk.uservoice.com >>> >>> New suggestion >>> 1 >>> votes >>> Return support for Tkinter widgets. >>> >>> >>> Posted in General >>> >>> >>> Tkinter is a good GUI toolkit, is cross-platform, simple to use and >>> lightweight (as opposed to Qt), which is important for scientific users >>> like me developing tools with graphics capabilities. >>> >>> I know it is not very popular, but it only needs support and usage to >>> gain visibility and expand its user base. Lack of support from important >>> projects like VTK don't help in the cause, so it seems to me like a vicious >>> circle. >>> >>> So please, return the support for the widgets. >>> >>> [image: Guille Giraldo]Guille Giraldo >>> >>> on Aug 12, 2015 (0 comments >>> ) >>> >>> Delete >>> Mark >>> as Spam >>> >>> >>> If you would like to stop receiving these emails you may unsubscribe >>> >>> . >>> >>> [image: powered by UserVoice] >>> >>> >> >> _______________________________________________ >> 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=vtk-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/vtk-developers >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at rogue-research.com Wed Aug 12 13:43:52 2015 From: sean at rogue-research.com (Sean McBride) Date: Wed, 12 Aug 2015 13:43:52 -0400 Subject: [vtk-developers] VTK Roadmap In-Reply-To: References: <20150805153056.753300039@mail.rogue-research.com> Message-ID: <20150812174352.1082425218@mail.rogue-research.com> Hi, So here's a patch that removes: - Carbon support - OS X 10.5 support (and thus PowerPC support, as 10.5 was the last that supported PPC) Cheers, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From ben.boeckel at kitware.com Wed Aug 12 16:00:38 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 12 Aug 2015 16:00:38 -0400 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: <55C42302.2000607@aero.iitb.ac.in> Message-ID: <20150812200038.GA26645@megas.kitware.com> [ Back to the dev list. ] On Wed, Aug 12, 2015 at 13:27:00 -0600, David Gobbi wrote: > This morning I merged in all of the fixes that Andrew did for the VTK tests > so that they run under Python 3 (thanks to Ben for running and maintaining > the dashboard machine). We're confident now that VTK will run properly > with Python 3. I'll look at spinning up OS X and Windows builders as well to poke some of those corners of the code. Installing 3.2.5, 3.3.5, and 3.4.3 on nemesis now. Will start with 3.2 since that will test the minimum version. I'll put trey on 3.3.5 since megas is on 3.4 already. > None of the python examples have been converted to Python 3 yet, so there's > still work to be done (and I'm on vacation until the middle of next week, > so I won't be touching any of the code for a little while). Have fun! Thanks! --Ben From saeedbakhshmand at gmail.com Wed Aug 12 17:32:52 2015 From: saeedbakhshmand at gmail.com (Saeed Mahdizadeh Bakhshmand) Date: Wed, 12 Aug 2015 17:32:52 -0400 Subject: [vtk-developers] Loading an External Graph to VTK Message-ID: Hello Experts, Is there a known way of loading a graph (3D node-link graph) that is defined and saved outside of VTK(position of vertices and adjacency matrix of the graph are stored in a text file e.g.) to be loaded to VTK and visualized? My guess is that GetEdgeData and GetVertexData are responsible for accepting vtk arrays, but not sure how those arrays can perfectly contain details of a graph and what happens if this graph is being imported from elsewhere? Best, Saeed -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Wed Aug 12 18:01:30 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 12 Aug 2015 16:01:30 -0600 Subject: [vtk-developers] Loading an External Graph to VTK In-Reply-To: References: Message-ID: On Wed, Aug 12, 2015 at 3:32 PM, Saeed Mahdizadeh Bakhshmand < saeedbakhshmand at gmail.com> wrote: > Hello Experts, > > Is there a known way of loading a graph (3D node-link graph) that is > defined and saved outside of VTK(position of vertices and adjacency matrix > of the graph are stored in a text file e.g.) to be loaded to VTK and > visualized? > My guess is that GetEdgeData and GetVertexData are responsible for > accepting vtk arrays, but not sure how those arrays can perfectly contain > details of a graph and what happens if this graph is being imported from > elsewhere? > Let's back up a bit, because GetEdgeData() and GetVertexData() are not the first methods to look at. A VTK data set is always considered to be made of these: 1) Geometry (points (or vertices/nodes), and connectivity between points) 2) Attribute arrays (colors, scalars, etc. to associate with points, edges, faces, etc). The GetEdgeData() and GetVertexData() method are for dealing with attributes. But from your question, it sounds like your main concern is loading the geometry. In other words, first you have to set the geometry (the vertices, edges, and perhaps the points). Only after that is done should you worry about setting the attributes to go along with them. Unfortunately, I really don't know anything specific about dealing with graphs in VTK, all I know is how VTK deals with data generically. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From saeedbakhshmand at gmail.com Wed Aug 12 18:22:18 2015 From: saeedbakhshmand at gmail.com (Saeed Mahdizadeh Bakhshmand) Date: Wed, 12 Aug 2015 18:22:18 -0400 Subject: [vtk-developers] Loading an External Graph to VTK In-Reply-To: References: Message-ID: Right, what I am looking for is like this: http://www.vtk.org/Wiki/VTK/Examples/Cxx/InfoVis/XGMLReader Here GML can load a full graph. But what I am looking for is to import topology of the graph. When I look into vtkGraphs that is what I see for VertexData and I assume modirying topology of the graph depends on these variables: VertexData: Debug: Off Modified Time: 826248 Reference Count: 1 Registered Events: (none) Number Of Arrays: 0 Number Of Components: 0 Number Of Tuples: 0 Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) Scalars: (none) Vectors: (none) Normals: (none) TCoords: (none) Tensors: (none) GlobalIds: (none) PedigreeIds: (none) EdgeFlag: (none) On Wed, Aug 12, 2015 at 6:01 PM, David Gobbi wrote: > On Wed, Aug 12, 2015 at 3:32 PM, Saeed Mahdizadeh Bakhshmand < > saeedbakhshmand at gmail.com> wrote: > >> Hello Experts, >> >> Is there a known way of loading a graph (3D node-link graph) that is >> defined and saved outside of VTK(position of vertices and adjacency matrix >> of the graph are stored in a text file e.g.) to be loaded to VTK and >> visualized? >> My guess is that GetEdgeData and GetVertexData are responsible for >> accepting vtk arrays, but not sure how those arrays can perfectly contain >> details of a graph and what happens if this graph is being imported from >> elsewhere? >> > > Let's back up a bit, because GetEdgeData() and GetVertexData() are not the > first methods to look at. > > A VTK data set is always considered to be made of these: > > 1) Geometry (points (or vertices/nodes), and connectivity between points) > 2) Attribute arrays (colors, scalars, etc. to associate with points, > edges, faces, etc). > > The GetEdgeData() and GetVertexData() method are for dealing with > attributes. But from your question, it sounds like your main concern is > loading the geometry. In other words, first you have to set the geometry > (the vertices, edges, and perhaps the points). Only after that is done > should you worry about setting the attributes to go along with them. > > Unfortunately, I really don't know anything specific about dealing with > graphs in VTK, all I know is how VTK deals with data generically. > > - David > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Wed Aug 12 18:41:04 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 12 Aug 2015 16:41:04 -0600 Subject: [vtk-developers] Loading an External Graph to VTK In-Reply-To: References: Message-ID: I'm fairly certain that VertexData has nothing to do with the topology. If you already have 3D coordinates for the nodes in your graph, I suspect that what you need to do is set the Points along with adding all your vertices and edges. - David On Wed, Aug 12, 2015 at 4:22 PM, Saeed Mahdizadeh Bakhshmand < saeedbakhshmand at gmail.com> wrote: > Right, what I am looking for is like this: > http://www.vtk.org/Wiki/VTK/Examples/Cxx/InfoVis/XGMLReader > Here GML can load a full graph. But what I am looking for is to import > topology of the graph. > When I look into vtkGraphs that is what I see for VertexData and I assume > modirying topology of the graph depends on these variables: > > VertexData: > > Debug: Off > > Modified Time: 826248 > > Reference Count: 1 > > Registered Events: (none) > > Number Of Arrays: 0 > > Number Of Components: 0 > > Number Of Tuples: 0 > > Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) > > Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) > > Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) > > Scalars: (none) > > Vectors: (none) > > Normals: (none) > > TCoords: (none) > > Tensors: (none) > > GlobalIds: (none) > > PedigreeIds: (none) > > EdgeFlag: (none) > > > > On Wed, Aug 12, 2015 at 6:01 PM, David Gobbi > wrote: > >> On Wed, Aug 12, 2015 at 3:32 PM, Saeed Mahdizadeh Bakhshmand < >> saeedbakhshmand at gmail.com> wrote: >> >>> Hello Experts, >>> >>> Is there a known way of loading a graph (3D node-link graph) that is >>> defined and saved outside of VTK(position of vertices and adjacency matrix >>> of the graph are stored in a text file e.g.) to be loaded to VTK and >>> visualized? >>> My guess is that GetEdgeData and GetVertexData are responsible for >>> accepting vtk arrays, but not sure how those arrays can perfectly contain >>> details of a graph and what happens if this graph is being imported from >>> elsewhere? >>> >> >> Let's back up a bit, because GetEdgeData() and GetVertexData() are not >> the first methods to look at. >> >> A VTK data set is always considered to be made of these: >> >> 1) Geometry (points (or vertices/nodes), and connectivity between points) >> 2) Attribute arrays (colors, scalars, etc. to associate with points, >> edges, faces, etc). >> >> The GetEdgeData() and GetVertexData() method are for dealing with >> attributes. But from your question, it sounds like your main concern is >> loading the geometry. In other words, first you have to set the geometry >> (the vertices, edges, and perhaps the points). Only after that is done >> should you worry about setting the attributes to go along with them. >> >> Unfortunately, I really don't know anything specific about dealing with >> graphs in VTK, all I know is how VTK deals with data generically. >> >> - David >> >> >> >> >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Wed Aug 12 22:54:37 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Thu, 13 Aug 2015 12:54:37 +1000 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' (Berk Geveci) Message-ID: FYI At this stage Tk support is certainly in VTK 6.3 and the python support for Tk is Python 2.5 - 2.7 there. I did translate the Tk tests into Python a few months ago. So for VTK 6.3 binaries it should be ok to turn on Tk support. For the current master there is Tk support for both Python 2 and Python 3, however the Python Tk tests using Python 3 only work Ok on Linux and OSX (I think - not tested by by myself) however there is an issue with windows (a segfault). Andrew > ---------- Forwarded message ---------- > From: Berk Geveci > To: David E DeMarle > Cc: VTK Developers , David Gobbi < > david.gobbi at gmail.com> > Date: Wed, 12 Aug 2015 12:08:20 -0400 > Subject: Re: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: > 'Return support for Tkinter widgets.' > OK thanks for the info. I will respond and try to find out more. Maybe > it's a distro that he is talking about... > > -berk > > On Wed, Aug 12, 2015 at 11:49 AM, David E DeMarle < > dave.demarle at kitware.com> wrote: > >> Tk is not turned on in the vtkpython binaries. >> >> Last time was probably in the Tcl binary (windows only) in 5.8 or 5.10.0. >> >> >> >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi >> wrote: >> >>> That's news to me. Just yesterday, me and Andrew were testing the Tk >>> widgets to make sure that they were compatible with the Python 3 changes on >>> all platforms. Are they still packaged in the binary releases? >>> >>> - David >>> >>> >>> On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci >>> wrote: >>> >>>> Hi folks, >>>> >>>> This came through VTK's uservoice. I didn't think that we stopped >>>> support any Tk widgets. Am I wrong? >>>> >>>> Best, >>>> -berk >>>> >>>> ---------- Forwarded message ---------- >>>> From: VTK >>>> Date: Wed, Aug 12, 2015 at 11:02 AM >>>> Subject: [vtk.uservoice.com] New suggestion: 'Return support for >>>> Tkinter widgets.' >>>> To: "berk.geveci" > >>>> >>>> >>>> Customer Feedback for VTK vtk.uservoice.com >>>> >>>> New suggestion >>>> 1 >>>> votes >>>> Return support for Tkinter widgets. >>>> >>>> >>>> Posted in General >>>> >>>> >>>> Tkinter is a good GUI toolkit, is cross-platform, simple to use and >>>> lightweight (as opposed to Qt), which is important for scientific users >>>> like me developing tools with graphics capabilities. >>>> >>>> I know it is not very popular, but it only needs support and usage to >>>> gain visibility and expand its user base. Lack of support from important >>>> projects like VTK don't help in the cause, so it seems to me like a vicious >>>> circle. >>>> >>>> So please, return the support for the widgets. >>>> >>>> [image: Guille Giraldo]Guille Giraldo >>>> >>>> on Aug 12, 2015 (0 comments >>>> ) >>>> >>>> Delete >>>> Mark >>>> as Spam >>>> >>>> >>>> If you would like to stop receiving these emails you may unsubscribe >>>> >>>> . >>>> >>>> [image: powered by UserVoice] >>>> >>>> >>> >>> _______________________________________________ >>> 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=vtk-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/vtk-developers >>> >>> >>> >> > > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Wed Aug 12 23:18:26 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 12 Aug 2015 21:18:26 -0600 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' (Berk Geveci) In-Reply-To: References: Message-ID: Hi Andrew, I found some time this morning to build Tcl/Tk on my Windows system, and for me all of the Tkinter tests ran fine under Python 3 on Windows. Are you sure that you don't have a version mismatch between Python's tk and VTK's tk? Another possibility is that it's related to 64-bit Windows builds versus 32-bit Windows builds (my build was 32-bit). - David On Wed, Aug 12, 2015 at 8:54 PM, Andrew Maclean wrote: > > FYI > > At this stage Tk support is certainly in VTK 6.3 and the python support > for Tk is Python 2.5 - 2.7 there. I did translate the Tk tests into Python > a few months ago. So for VTK 6.3 binaries it should be ok to turn on Tk > support. > > For the current master there is Tk support for both Python 2 and Python 3, > however the Python Tk tests using Python 3 only work Ok on Linux and OSX (I > think - not tested by by myself) however there is an issue with windows (a > segfault). > > > Andrew > > > > >> ---------- Forwarded message ---------- >> From: Berk Geveci >> To: David E DeMarle >> Cc: VTK Developers , David Gobbi < >> david.gobbi at gmail.com> >> Date: Wed, 12 Aug 2015 12:08:20 -0400 >> Subject: Re: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: >> 'Return support for Tkinter widgets.' >> OK thanks for the info. I will respond and try to find out more. Maybe >> it's a distro that he is talking about... >> >> -berk >> >> On Wed, Aug 12, 2015 at 11:49 AM, David E DeMarle < >> dave.demarle at kitware.com> wrote: >> >>> Tk is not turned on in the vtkpython binaries. >>> >>> Last time was probably in the Tcl binary (windows only) in 5.8 or 5.10.0. >>> >>> >>> >>> David E DeMarle >>> Kitware, Inc. >>> R&D Engineer >>> 21 Corporate Drive >>> Clifton Park, NY 12065-8662 >>> Phone: 518-881-4909 >>> >>> On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi >>> wrote: >>> >>>> That's news to me. Just yesterday, me and Andrew were testing the Tk >>>> widgets to make sure that they were compatible with the Python 3 changes on >>>> all platforms. Are they still packaged in the binary releases? >>>> >>>> - David >>>> >>>> >>>> On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci >>>> wrote: >>>> >>>>> Hi folks, >>>>> >>>>> This came through VTK's uservoice. I didn't think that we stopped >>>>> support any Tk widgets. Am I wrong? >>>>> >>>>> Best, >>>>> -berk >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: VTK >>>>> Date: Wed, Aug 12, 2015 at 11:02 AM >>>>> Subject: [vtk.uservoice.com] New suggestion: 'Return support for >>>>> Tkinter widgets.' >>>>> To: "berk.geveci" > >>>>> >>>>> >>>>> Customer Feedback for VTK vtk.uservoice.com >>>>> >>>>> New suggestion >>>>> 1 >>>>> votes >>>>> Return support for Tkinter widgets. >>>>> >>>>> >>>>> Posted in General >>>>> >>>>> >>>>> Tkinter is a good GUI toolkit, is cross-platform, simple to use and >>>>> lightweight (as opposed to Qt), which is important for scientific users >>>>> like me developing tools with graphics capabilities. >>>>> >>>>> I know it is not very popular, but it only needs support and usage to >>>>> gain visibility and expand its user base. Lack of support from important >>>>> projects like VTK don't help in the cause, so it seems to me like a vicious >>>>> circle. >>>>> >>>>> So please, return the support for the widgets. >>>>> >>>>> [image: Guille Giraldo]Guille Giraldo >>>>> >>>>> on Aug 12, 2015 (0 comments >>>>> ) >>>>> >>>>> Delete >>>>> Mark >>>>> as Spam >>>>> >>>>> >>>>> If you would like to stop receiving these emails you may unsubscribe >>>>> >>>>> . >>>>> >>>>> [image: powered by UserVoice] >>>>> >>>>> >>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Wed Aug 12 23:50:59 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Thu, 13 Aug 2015 13:50:59 +1000 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' (Berk Geveci) In-Reply-To: References: Message-ID: Thanks for this David, I'll check this out. I have had Tcl problems that I resolved by putting the windows default paths last. My Python's Tk, Tcl are all 64-bit. Regards Andrew On Thu, Aug 13, 2015 at 1:18 PM, David Gobbi wrote: > Hi Andrew, > > I found some time this morning to build Tcl/Tk on my Windows system, and > for me all of the Tkinter tests ran fine under Python 3 on Windows. Are > you sure that you don't have a version mismatch between Python's tk and > VTK's tk? Another possibility is that it's related to 64-bit Windows > builds versus 32-bit Windows builds (my build was 32-bit). > > - David > > > On Wed, Aug 12, 2015 at 8:54 PM, Andrew Maclean > wrote: > >> >> FYI >> >> At this stage Tk support is certainly in VTK 6.3 and the python support >> for Tk is Python 2.5 - 2.7 there. I did translate the Tk tests into Python >> a few months ago. So for VTK 6.3 binaries it should be ok to turn on Tk >> support. >> >> For the current master there is Tk support for both Python 2 and Python >> 3, however the Python Tk tests using Python 3 only work Ok on Linux and OSX >> (I think - not tested by by myself) however there is an issue with windows >> (a segfault). >> >> >> Andrew >> >> >> >> >>> ---------- Forwarded message ---------- >>> From: Berk Geveci >>> To: David E DeMarle >>> Cc: VTK Developers , David Gobbi < >>> david.gobbi at gmail.com> >>> Date: Wed, 12 Aug 2015 12:08:20 -0400 >>> Subject: Re: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: >>> 'Return support for Tkinter widgets.' >>> OK thanks for the info. I will respond and try to find out more. Maybe >>> it's a distro that he is talking about... >>> >>> -berk >>> >>> On Wed, Aug 12, 2015 at 11:49 AM, David E DeMarle < >>> dave.demarle at kitware.com> wrote: >>> >>>> Tk is not turned on in the vtkpython binaries. >>>> >>>> Last time was probably in the Tcl binary (windows only) in 5.8 or >>>> 5.10.0. >>>> >>>> >>>> >>>> David E DeMarle >>>> Kitware, Inc. >>>> R&D Engineer >>>> 21 Corporate Drive >>>> Clifton Park, NY 12065-8662 >>>> Phone: 518-881-4909 >>>> >>>> On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi >>>> wrote: >>>> >>>>> That's news to me. Just yesterday, me and Andrew were testing the Tk >>>>> widgets to make sure that they were compatible with the Python 3 changes on >>>>> all platforms. Are they still packaged in the binary releases? >>>>> >>>>> - David >>>>> >>>>> >>>>> On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci >>>>> wrote: >>>>> >>>>>> Hi folks, >>>>>> >>>>>> This came through VTK's uservoice. I didn't think that we stopped >>>>>> support any Tk widgets. Am I wrong? >>>>>> >>>>>> Best, >>>>>> -berk >>>>>> >>>>>> ---------- Forwarded message ---------- >>>>>> From: VTK >>>>>> Date: Wed, Aug 12, 2015 at 11:02 AM >>>>>> Subject: [vtk.uservoice.com] New suggestion: 'Return support for >>>>>> Tkinter widgets.' >>>>>> To: "berk.geveci" > >>>>>> >>>>>> >>>>>> Customer Feedback for VTK vtk.uservoice.com >>>>>> >>>>>> New suggestion >>>>>> 1 >>>>>> votes >>>>>> Return support for Tkinter widgets. >>>>>> >>>>>> >>>>>> Posted in General >>>>>> >>>>>> >>>>>> Tkinter is a good GUI toolkit, is cross-platform, simple to use and >>>>>> lightweight (as opposed to Qt), which is important for scientific users >>>>>> like me developing tools with graphics capabilities. >>>>>> >>>>>> I know it is not very popular, but it only needs support and usage to >>>>>> gain visibility and expand its user base. Lack of support from important >>>>>> projects like VTK don't help in the cause, so it seems to me like a vicious >>>>>> circle. >>>>>> >>>>>> So please, return the support for the widgets. >>>>>> >>>>>> [image: Guille Giraldo]Guille Giraldo >>>>>> >>>>>> on Aug 12, 2015 (0 comments >>>>>> ) >>>>>> >>>>>> Delete >>>>>> Mark >>>>>> as Spam >>>>>> >>>>>> >>>>>> If you would like to stop receiving these emails you may unsubscribe >>>>>> >>>>>> . >>>>>> >>>>>> [image: powered by UserVoice] >>>>>> >>>>>> >>>>> -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Thu Aug 13 00:05:41 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 12 Aug 2015 22:05:41 -0600 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' (Berk Geveci) In-Reply-To: References: Message-ID: Hi Andrew, To be sure about the version, you can check inside python itself: >>> import tkinter >>> tkinter.TkVersion 8.6 To check even deeper, you can go into the DLLs folder in Python and check the properties of the DLLs that Python links too. That will provide the exact version number. - David On Wed, Aug 12, 2015 at 9:50 PM, Andrew Maclean wrote: > Thanks for this David, > > I'll check this out. I have had Tcl problems that I resolved by putting > the windows default paths last. > My Python's Tk, Tcl are all 64-bit. > > Regards > Andrew > > On Thu, Aug 13, 2015 at 1:18 PM, David Gobbi > wrote: > >> Hi Andrew, >> >> I found some time this morning to build Tcl/Tk on my Windows system, and >> for me all of the Tkinter tests ran fine under Python 3 on Windows. Are >> you sure that you don't have a version mismatch between Python's tk and >> VTK's tk? Another possibility is that it's related to 64-bit Windows >> builds versus 32-bit Windows builds (my build was 32-bit). >> >> - David >> >> >> On Wed, Aug 12, 2015 at 8:54 PM, Andrew Maclean < >> andrew.amaclean at gmail.com> wrote: >> >>> >>> FYI >>> >>> At this stage Tk support is certainly in VTK 6.3 and the python support >>> for Tk is Python 2.5 - 2.7 there. I did translate the Tk tests into Python >>> a few months ago. So for VTK 6.3 binaries it should be ok to turn on Tk >>> support. >>> >>> For the current master there is Tk support for both Python 2 and Python >>> 3, however the Python Tk tests using Python 3 only work Ok on Linux and OSX >>> (I think - not tested by by myself) however there is an issue with windows >>> (a segfault). >>> >>> >>> Andrew >>> >>> >>> >>> >>>> ---------- Forwarded message ---------- >>>> From: Berk Geveci >>>> To: David E DeMarle >>>> Cc: VTK Developers , David Gobbi < >>>> david.gobbi at gmail.com> >>>> Date: Wed, 12 Aug 2015 12:08:20 -0400 >>>> Subject: Re: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: >>>> 'Return support for Tkinter widgets.' >>>> OK thanks for the info. I will respond and try to find out more. Maybe >>>> it's a distro that he is talking about... >>>> >>>> -berk >>>> >>>> On Wed, Aug 12, 2015 at 11:49 AM, David E DeMarle < >>>> dave.demarle at kitware.com> wrote: >>>> >>>>> Tk is not turned on in the vtkpython binaries. >>>>> >>>>> Last time was probably in the Tcl binary (windows only) in 5.8 or >>>>> 5.10.0. >>>>> >>>>> >>>>> >>>>> David E DeMarle >>>>> Kitware, Inc. >>>>> R&D Engineer >>>>> 21 Corporate Drive >>>>> Clifton Park, NY 12065-8662 >>>>> Phone: 518-881-4909 >>>>> >>>>> On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi >>>>> wrote: >>>>> >>>>>> That's news to me. Just yesterday, me and Andrew were testing the Tk >>>>>> widgets to make sure that they were compatible with the Python 3 changes on >>>>>> all platforms. Are they still packaged in the binary releases? >>>>>> >>>>>> - David >>>>>> >>>>>> >>>>>> On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci >>>>> > wrote: >>>>>> >>>>>>> Hi folks, >>>>>>> >>>>>>> This came through VTK's uservoice. I didn't think that we stopped >>>>>>> support any Tk widgets. Am I wrong? >>>>>>> >>>>>>> Best, >>>>>>> -berk >>>>>>> >>>>>>> ---------- Forwarded message ---------- >>>>>>> From: VTK >>>>>>> Date: Wed, Aug 12, 2015 at 11:02 AM >>>>>>> Subject: [vtk.uservoice.com] New suggestion: 'Return support for >>>>>>> Tkinter widgets.' >>>>>>> To: "berk.geveci" > >>>>>>> >>>>>>> >>>>>>> Customer Feedback for VTK vtk.uservoice.com >>>>>>> >>>>>>> New suggestion >>>>>>> 1 >>>>>>> votes >>>>>>> Return support for Tkinter widgets. >>>>>>> >>>>>>> >>>>>>> Posted in General >>>>>>> >>>>>>> >>>>>>> Tkinter is a good GUI toolkit, is cross-platform, simple to use and >>>>>>> lightweight (as opposed to Qt), which is important for scientific users >>>>>>> like me developing tools with graphics capabilities. >>>>>>> >>>>>>> I know it is not very popular, but it only needs support and usage >>>>>>> to gain visibility and expand its user base. Lack of support from important >>>>>>> projects like VTK don't help in the cause, so it seems to me like a vicious >>>>>>> circle. >>>>>>> >>>>>>> So please, return the support for the widgets. >>>>>>> >>>>>>> [image: Guille Giraldo]Guille Giraldo >>>>>>> >>>>>>> on Aug 12, 2015 (0 comments >>>>>>> ) >>>>>>> >>>>>>> Delete >>>>>>> Mark >>>>>>> as Spam >>>>>>> >>>>>>> >>>>>>> If you would like to stop receiving these emails you may unsubscribe >>>>>>> >>>>>>> . >>>>>>> >>>>>>> [image: powered by UserVoice] >>>>>>> >>>>>>> >>>>>> > > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Thu Aug 13 07:06:38 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Thu, 13 Aug 2015 21:06:38 +1000 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' (Berk Geveci) In-Reply-To: References: Message-ID: Hi David, That really, helped, you are absolutely correct there are dll problems. The anaconda python 3.4 uses: tk86t.lib/dll and tcl86.lib/dll. Oddly enough anaconda python 2.7 uses: tk85.lib/dll and tcl85.lib/dll. Tcl uses: tk86t.lib/dll and tcl86.lib/dll. I really don't know but the "t" in tk86t.dll might mean testing. This was the only reference I could find: https://mail.python.org/pipermail/python-checkins/2015-July/137091.html So I changed the CMakeCache.txt file as follows: // TCL_LIBRARY:FILEPATH=C:/Tcl/lib/tcl86.lib TCL_LIBRARY:FILEPATH=C:/Anaconda/envs/py34/tcl/tcl86t.lib //TK_LIBRARY:FILEPATH=C:/Tcl/lib/tk86.lib TK_LIBRARY:FILEPATH=C:/Anaconda/envs/py34/tcl/tk86t.lib Rebuilt and all the tests pass using: ctest -C Debug -R vtkRenderingTkPython Tcl works as long as the Tcl path is before the Anaconda path. However the Tcl tests don't work because vtk can't find a useable init.tcl I think I have to add the path to init.tcl namely: C:C:/Anaconda/envs/py34/tcl/tcl8.6 and rebuild. I'll try this tomorrow. Regards Andrew On Thu, Aug 13, 2015 at 2:05 PM, David Gobbi wrote: > Hi Andrew, > > To be sure about the version, you can check inside python itself: > > >>> import tkinter > >>> tkinter.TkVersion > 8.6 > > To check even deeper, you can go into the DLLs folder in Python and check > the properties of the DLLs that Python links too. That will provide the > exact version number. > > - David > > On Wed, Aug 12, 2015 at 9:50 PM, Andrew Maclean > wrote: > >> Thanks for this David, >> >> I'll check this out. I have had Tcl problems that I resolved by putting >> the windows default paths last. >> My Python's Tk, Tcl are all 64-bit. >> >> Regards >> Andrew >> >> On Thu, Aug 13, 2015 at 1:18 PM, David Gobbi >> wrote: >> >>> Hi Andrew, >>> >>> I found some time this morning to build Tcl/Tk on my Windows system, and >>> for me all of the Tkinter tests ran fine under Python 3 on Windows. Are >>> you sure that you don't have a version mismatch between Python's tk and >>> VTK's tk? Another possibility is that it's related to 64-bit Windows >>> builds versus 32-bit Windows builds (my build was 32-bit). >>> >>> - David >>> >>> >>> On Wed, Aug 12, 2015 at 8:54 PM, Andrew Maclean < >>> andrew.amaclean at gmail.com> wrote: >>> >>>> >>>> FYI >>>> >>>> At this stage Tk support is certainly in VTK 6.3 and the python support >>>> for Tk is Python 2.5 - 2.7 there. I did translate the Tk tests into Python >>>> a few months ago. So for VTK 6.3 binaries it should be ok to turn on Tk >>>> support. >>>> >>>> For the current master there is Tk support for both Python 2 and Python >>>> 3, however the Python Tk tests using Python 3 only work Ok on Linux and OSX >>>> (I think - not tested by by myself) however there is an issue with windows >>>> (a segfault). >>>> >>>> >>>> Andrew >>>> >>>> >>>> >>>> >>>>> ---------- Forwarded message ---------- >>>>> From: Berk Geveci >>>>> To: David E DeMarle >>>>> Cc: VTK Developers , David Gobbi < >>>>> david.gobbi at gmail.com> >>>>> Date: Wed, 12 Aug 2015 12:08:20 -0400 >>>>> Subject: Re: [vtk-developers] Fwd: [vtk.uservoice.com] New >>>>> suggestion: 'Return support for Tkinter widgets.' >>>>> OK thanks for the info. I will respond and try to find out more. Maybe >>>>> it's a distro that he is talking about... >>>>> >>>>> -berk >>>>> >>>>> On Wed, Aug 12, 2015 at 11:49 AM, David E DeMarle < >>>>> dave.demarle at kitware.com> wrote: >>>>> >>>>>> Tk is not turned on in the vtkpython binaries. >>>>>> >>>>>> Last time was probably in the Tcl binary (windows only) in 5.8 or >>>>>> 5.10.0. >>>>>> >>>>>> >>>>>> >>>>>> David E DeMarle >>>>>> Kitware, Inc. >>>>>> R&D Engineer >>>>>> 21 Corporate Drive >>>>>> Clifton Park, NY 12065-8662 >>>>>> Phone: 518-881-4909 >>>>>> >>>>>> On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi >>>>>> wrote: >>>>>> >>>>>>> That's news to me. Just yesterday, me and Andrew were testing the >>>>>>> Tk widgets to make sure that they were compatible with the Python 3 changes >>>>>>> on all platforms. Are they still packaged in the binary releases? >>>>>>> >>>>>>> - David >>>>>>> >>>>>>> >>>>>>> On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci < >>>>>>> berk.geveci at kitware.com> wrote: >>>>>>> >>>>>>>> Hi folks, >>>>>>>> >>>>>>>> This came through VTK's uservoice. I didn't think that we stopped >>>>>>>> support any Tk widgets. Am I wrong? >>>>>>>> >>>>>>>> Best, >>>>>>>> -berk >>>>>>>> >>>>>>>> ---------- Forwarded message ---------- >>>>>>>> From: VTK >>>>>>>> Date: Wed, Aug 12, 2015 at 11:02 AM >>>>>>>> Subject: [vtk.uservoice.com] New suggestion: 'Return support for >>>>>>>> Tkinter widgets.' >>>>>>>> To: "berk.geveci" > >>>>>>>> >>>>>>>> >>>>>>>> Customer Feedback for VTK vtk.uservoice.com >>>>>>>> >>>>>>>> New suggestion >>>>>>>> 1 >>>>>>>> votes >>>>>>>> Return support for Tkinter widgets. >>>>>>>> >>>>>>>> >>>>>>>> Posted in General >>>>>>>> >>>>>>>> >>>>>>>> Tkinter is a good GUI toolkit, is cross-platform, simple to use and >>>>>>>> lightweight (as opposed to Qt), which is important for scientific users >>>>>>>> like me developing tools with graphics capabilities. >>>>>>>> >>>>>>>> I know it is not very popular, but it only needs support and usage >>>>>>>> to gain visibility and expand its user base. Lack of support from important >>>>>>>> projects like VTK don't help in the cause, so it seems to me like a vicious >>>>>>>> circle. >>>>>>>> >>>>>>>> So please, return the support for the widgets. >>>>>>>> >>>>>>>> [image: Guille Giraldo]Guille Giraldo >>>>>>>> >>>>>>>> on Aug 12, 2015 (0 comments >>>>>>>> ) >>>>>>>> >>>>>>>> Delete >>>>>>>> Mark >>>>>>>> as Spam >>>>>>>> >>>>>>>> >>>>>>>> If you would like to stop receiving these emails you may >>>>>>>> unsubscribe >>>>>>>> >>>>>>>> . >>>>>>>> >>>>>>>> [image: powered by UserVoice] >>>>>>>> >>>>>>>> >>>>>>> >> >> >> -- >> ___________________________________________ >> Andrew J. P. Maclean >> >> ___________________________________________ >> > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From saeedbakhshmand at gmail.com Thu Aug 13 12:10:27 2015 From: saeedbakhshmand at gmail.com (Saeed Mahdizadeh Bakhshmand) Date: Thu, 13 Aug 2015 12:10:27 -0400 Subject: [vtk-developers] Loading an External Graph to VTK In-Reply-To: References: Message-ID: You were right, External graphs are read to vtk as a table first and from there table is translated to a graph, I found out by looking at csv_to_graph.py file at VTK-6.1.0\Examples\Infovis\Python and this . On Wed, Aug 12, 2015 at 6:41 PM, David Gobbi wrote: > I'm fairly certain that VertexData has nothing to do with the topology. > > If you already have 3D coordinates for the nodes in your graph, I suspect > that what you need to do is set the Points along with adding all your > vertices and edges. > > - David > > > On Wed, Aug 12, 2015 at 4:22 PM, Saeed Mahdizadeh Bakhshmand < > saeedbakhshmand at gmail.com> wrote: > >> Right, what I am looking for is like this: >> http://www.vtk.org/Wiki/VTK/Examples/Cxx/InfoVis/XGMLReader >> Here GML can load a full graph. But what I am looking for is to import >> topology of the graph. >> When I look into vtkGraphs that is what I see for VertexData and I assume >> modirying topology of the graph depends on these variables: >> >> VertexData: >> >> Debug: Off >> >> Modified Time: 826248 >> >> Reference Count: 1 >> >> Registered Events: (none) >> >> Number Of Arrays: 0 >> >> Number Of Components: 0 >> >> Number Of Tuples: 0 >> >> Copy Tuple Flags: ( 1 1 1 1 1 0 1 1 ) >> >> Interpolate Flags: ( 1 1 1 1 1 0 0 1 ) >> >> Pass Through Flags: ( 1 1 1 1 1 1 1 1 ) >> >> Scalars: (none) >> >> Vectors: (none) >> >> Normals: (none) >> >> TCoords: (none) >> >> Tensors: (none) >> >> GlobalIds: (none) >> >> PedigreeIds: (none) >> >> EdgeFlag: (none) >> >> >> >> On Wed, Aug 12, 2015 at 6:01 PM, David Gobbi >> wrote: >> >>> On Wed, Aug 12, 2015 at 3:32 PM, Saeed Mahdizadeh Bakhshmand < >>> saeedbakhshmand at gmail.com> wrote: >>> >>>> Hello Experts, >>>> >>>> Is there a known way of loading a graph (3D node-link graph) that is >>>> defined and saved outside of VTK(position of vertices and adjacency matrix >>>> of the graph are stored in a text file e.g.) to be loaded to VTK and >>>> visualized? >>>> My guess is that GetEdgeData and GetVertexData are responsible for >>>> accepting vtk arrays, but not sure how those arrays can perfectly contain >>>> details of a graph and what happens if this graph is being imported from >>>> elsewhere? >>>> >>> >>> Let's back up a bit, because GetEdgeData() and GetVertexData() are not >>> the first methods to look at. >>> >>> A VTK data set is always considered to be made of these: >>> >>> 1) Geometry (points (or vertices/nodes), and connectivity between points) >>> 2) Attribute arrays (colors, scalars, etc. to associate with points, >>> edges, faces, etc). >>> >>> The GetEdgeData() and GetVertexData() method are for dealing with >>> attributes. But from your question, it sounds like your main concern is >>> loading the geometry. In other words, first you have to set the geometry >>> (the vertices, edges, and perhaps the points). Only after that is done >>> should you worry about setting the attributes to go along with them. >>> >>> Unfortunately, I really don't know anything specific about dealing with >>> graphs in VTK, all I know is how VTK deals with data generically. >>> >>> - David >>> >>> >>> >>> >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hobbsk at ohio.edu Thu Aug 13 16:37:25 2015 From: hobbsk at ohio.edu (Kevin H. Hobbs) Date: Thu, 13 Aug 2015 16:37:25 -0400 Subject: [vtk-developers] CMake Segfaults while configuring VTK In-Reply-To: <55C24369.5010902@kitware.com> References: <55C2014D.5060103@ohio.edu> <55C24369.5010902@kitware.com> Message-ID: <55CD0005.8070904@ohio.edu> On 08/05/2015 01:10 PM, Brad King wrote: > Steve has updated the offending topic with a fix so we'll see tonight. On August 8 VTK stopped configuring again. I'm about to rebuild CMake in Debug mode and rerun gdb but can either of you replicate this or is it just me? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 173 bytes Desc: OpenPGP digital signature URL: From hobbsk at ohio.edu Thu Aug 13 16:42:21 2015 From: hobbsk at ohio.edu (Kevin H. Hobbs) Date: Thu, 13 Aug 2015 16:42:21 -0400 Subject: [vtk-developers] CMake Segfaults while configuring VTK In-Reply-To: <55C24369.5010902@kitware.com> References: <55C2014D.5060103@ohio.edu> <55C24369.5010902@kitware.com> Message-ID: <55CD012D.9010201@ohio.edu> GDB gives me a different backtrace this time: Detaching after fork from child process 30288. -- Configuring done Program received signal SIGSEGV, Segmentation fault. std::string::c_str (this=0x170) at /usr/src/debug/gcc-4.8.3-20140911/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:1801 1801 { return _M_data(); } (gdb) bt #0 std::string::c_str (this=0x170) at /usr/src/debug/gcc-4.8.3-20140911/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:1801 #1 0x00000000009555b5 in cmStrictTargetComparison::operator() (this=0xf0ec48, t1=0x65064a0, t2=0x0) at /home/kevin/kitware/CMake/Source/cmGeneratorTarget.cxx:2429 #2 0x000000000071ca9d in std::_Rb_tree, std::_Select1st >, cmStrictTargetComparison, std::allocator > >::_M_lower_bound (this=0xf0ec48, __x=0x6effca0, __y=0xf0ec50, __k=@0x7fffffffb9d0: 0x0) at /usr/include/c++/4.8.3/bits/stl_tree.h:1157 #3 0x0000000000715335 in std::_Rb_tree, std::_Select1st >, cmStrictTargetComparison, std::allocator > >::find (this=0xf0ec48, __k=@0x7fffffffb9d0: 0x0) at /usr/include/c++/4.8.3/bits/stl_tree.h:1805 #4 0x000000000070e1ad in std::map > >::find (this=0xf0ec48, __x=@0x7fffffffb9d0: 0x0) at /usr/include/c++/4.8.3/bits/stl_map.h:837 #5 0x0000000000700b7a in cmGlobalGenerator::GetGeneratorTarget (this=0xf0e870, t=0x0) at /home/kevin/kitware/CMake/Source/cmGlobalGenerator.cxx:1624 #6 0x00000000008e0fb2 in cmComputeLinkInformation::AddSharedDepItem (this=0x781e920, item="/usr/lib64/libGL.so", tgt=0x0) at /home/kevin/kitware/CMake/Source/cmComputeLinkInformation.cxx:764 #7 0x00000000008dffde in cmComputeLinkInformation::Compute (this=0x781e920) at /home/kevin/kitware/CMake/Source/cmComputeLinkInformation.cxx:513 #8 0x0000000000958118 in cmGeneratorTarget::GetLinkInformation (this=0x6f88ac0, config="") at /home/kevin/kitware/CMake/Source/cmGeneratorTarget.cxx:3268 Python Exception list index out of range: #9 0x00000000009086e3 in getCompatibleInterfaceProperties (target=0x6f88ac0, ifaceProperties=std::set with 0 elements, config="") at /home/kevin/kitware/CMake/Source/cmExportFileGenerator.cxx:532 #10 0x0000000000908e8c in cmExportFileGenerator::PopulateCompatibleInterfaceProperties (this=0x64a5af0, Python Exception list index out of range: gtarget=0x6f88ac0, properties=std::map with 1 elements) at /home/kevin/kitware/CMake/Source/cmExportFileGenerator.cxx:595 #11 0x00000000009e8b3d in cmExportInstallFileGenerator::GenerateMainFile (this=0x64a5af0, os=...) at /home/kevin/kitware/CMake/Source/cmExportInstallFileGenerator.cxx:200 #12 0x00000000009063ab in cmExportFileGenerator::GenerateImportFile (this=0x64a5af0) at /home/kevin/kitware/CMake/Source/cmExportFileGenerator.cxx:126 #13 0x000000000097b80e in cmInstallExportGenerator::GenerateScript (this=0x64a3800, os=...) at /home/kevin/kitware/CMake/Source/cmInstallExportGenerator.cxx:164 #14 0x000000000079416f in cmScriptGenerator::Generate (this=0x64a3800, os=..., config="Debug", configurationTypes=std::vector of length 0, capacity 0) at /home/kevin/kitware/CMake/Source/cmScriptGenerator.cxx:42 #15 0x00000000007335ae in cmLocalGenerator::GenerateInstallRules (this=0xf10870) at /home/kevin/kitware/CMake/Source/cmLocalGenerator.cxx:411 #16 0x00000000006ff32c in cmGlobalGenerator::Generate (this=0xf0e870) at /home/kevin/kitware/CMake/Source/cmGlobalGenerator.cxx:1358 ---Type to continue, or q to quit--- #17 0x000000000096cf10 in cmGlobalUnixMakefileGenerator3::Generate (this=0xf0e870) at /home/kevin/kitware/CMake/Source/cmGlobalUnixMakefileGenerator3.cxx:140 #18 0x00000000007f5b81 in cmake::Generate (this=0x7fffffffd7c0) at /home/kevin/kitware/CMake/Source/cmake.cxx:1773 #19 0x00000000007f59c8 in cmake::Run (this=0x7fffffffd7c0, args=std::vector of length 2, capacity 2 = {...}, noconfigure=false) at /home/kevin/kitware/CMake/Source/cmake.cxx:1756 #20 0x00000000006cfd0b in do_cmake (ac=2, av=0xf010b0) at /home/kevin/kitware/CMake/Source/cmakemain.cxx:330 #21 0x00000000006cf2d0 in main (ac=2, av=0xf010b0) at /home/kevin/kitware/CMake/Source/cmakemain.cxx:190 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 173 bytes Desc: OpenPGP digital signature URL: From andrew.amaclean at gmail.com Thu Aug 13 20:19:31 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Fri, 14 Aug 2015 10:19:31 +1000 Subject: [vtk-developers] Fwd: [vtk.uservoice.com] New suggestion: 'Return support for Tkinter widgets.' (Berk Geveci) In-Reply-To: References: Message-ID: Hi All Finally got it all working. The last trick is to add: set TCL_LIBRARY=C:\Anaconda\envs\py34\tcl\tcl8.6 set TK_LIBRARY=C:\Anaconda\envs\py34\tcl\tk8.6 and then build VTK. Regards Andrew On Thu, Aug 13, 2015 at 9:06 PM, Andrew Maclean wrote: > Hi David, > That really, helped, you are absolutely correct there are dll problems. > > The anaconda python 3.4 uses: tk86t.lib/dll and tcl86.lib/dll. > Oddly enough anaconda python 2.7 uses: tk85.lib/dll and tcl85.lib/dll. > Tcl uses: tk86t.lib/dll and tcl86.lib/dll. > > I really don't know but the "t" in tk86t.dll might mean testing. > This was the only reference I could find: > https://mail.python.org/pipermail/python-checkins/2015-July/137091.html > > So I changed the CMakeCache.txt file as follows: > > // TCL_LIBRARY:FILEPATH=C:/Tcl/lib/tcl86.lib > TCL_LIBRARY:FILEPATH=C:/Anaconda/envs/py34/tcl/tcl86t.lib > > //TK_LIBRARY:FILEPATH=C:/Tcl/lib/tk86.lib > TK_LIBRARY:FILEPATH=C:/Anaconda/envs/py34/tcl/tk86t.lib > > > Rebuilt and all the tests pass using: > ctest -C Debug -R vtkRenderingTkPython > > Tcl works as long as the Tcl path is before the Anaconda path. However the > Tcl tests don't work because vtk can't find a useable init.tcl > > I think I have to add the path to init.tcl namely: C:C: path>/Anaconda/envs/py34/tcl/tcl8.6 and rebuild. > > I'll try this tomorrow. > > > Regards > Andrew > > > > On Thu, Aug 13, 2015 at 2:05 PM, David Gobbi > wrote: > >> Hi Andrew, >> >> To be sure about the version, you can check inside python itself: >> >> >>> import tkinter >> >>> tkinter.TkVersion >> 8.6 >> >> To check even deeper, you can go into the DLLs folder in Python and check >> the properties of the DLLs that Python links too. That will provide the >> exact version number. >> >> - David >> >> On Wed, Aug 12, 2015 at 9:50 PM, Andrew Maclean < >> andrew.amaclean at gmail.com> wrote: >> >>> Thanks for this David, >>> >>> I'll check this out. I have had Tcl problems that I resolved by putting >>> the windows default paths last. >>> My Python's Tk, Tcl are all 64-bit. >>> >>> Regards >>> Andrew >>> >>> On Thu, Aug 13, 2015 at 1:18 PM, David Gobbi >>> wrote: >>> >>>> Hi Andrew, >>>> >>>> I found some time this morning to build Tcl/Tk on my Windows system, >>>> and for me all of the Tkinter tests ran fine under Python 3 on Windows. >>>> Are you sure that you don't have a version mismatch between Python's tk and >>>> VTK's tk? Another possibility is that it's related to 64-bit Windows >>>> builds versus 32-bit Windows builds (my build was 32-bit). >>>> >>>> - David >>>> >>>> >>>> On Wed, Aug 12, 2015 at 8:54 PM, Andrew Maclean < >>>> andrew.amaclean at gmail.com> wrote: >>>> >>>>> >>>>> FYI >>>>> >>>>> At this stage Tk support is certainly in VTK 6.3 and the python >>>>> support for Tk is Python 2.5 - 2.7 there. I did translate the Tk tests into >>>>> Python a few months ago. So for VTK 6.3 binaries it should be ok to turn on >>>>> Tk support. >>>>> >>>>> For the current master there is Tk support for both Python 2 and >>>>> Python 3, however the Python Tk tests using Python 3 only work Ok on Linux >>>>> and OSX (I think - not tested by by myself) however there is an issue with >>>>> windows (a segfault). >>>>> >>>>> >>>>> Andrew >>>>> >>>>> >>>>> >>>>> >>>>>> ---------- Forwarded message ---------- >>>>>> From: Berk Geveci >>>>>> To: David E DeMarle >>>>>> Cc: VTK Developers , David Gobbi < >>>>>> david.gobbi at gmail.com> >>>>>> Date: Wed, 12 Aug 2015 12:08:20 -0400 >>>>>> Subject: Re: [vtk-developers] Fwd: [vtk.uservoice.com] New >>>>>> suggestion: 'Return support for Tkinter widgets.' >>>>>> OK thanks for the info. I will respond and try to find out more. >>>>>> Maybe it's a distro that he is talking about... >>>>>> >>>>>> -berk >>>>>> >>>>>> On Wed, Aug 12, 2015 at 11:49 AM, David E DeMarle < >>>>>> dave.demarle at kitware.com> wrote: >>>>>> >>>>>>> Tk is not turned on in the vtkpython binaries. >>>>>>> >>>>>>> Last time was probably in the Tcl binary (windows only) in 5.8 or >>>>>>> 5.10.0. >>>>>>> >>>>>>> >>>>>>> >>>>>>> David E DeMarle >>>>>>> Kitware, Inc. >>>>>>> R&D Engineer >>>>>>> 21 Corporate Drive >>>>>>> Clifton Park, NY 12065-8662 >>>>>>> Phone: 518-881-4909 >>>>>>> >>>>>>> On Wed, Aug 12, 2015 at 11:42 AM, David Gobbi >>>>>> > wrote: >>>>>>> >>>>>>>> That's news to me. Just yesterday, me and Andrew were testing the >>>>>>>> Tk widgets to make sure that they were compatible with the Python 3 changes >>>>>>>> on all platforms. Are they still packaged in the binary releases? >>>>>>>> >>>>>>>> - David >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Aug 12, 2015 at 9:19 AM, Berk Geveci < >>>>>>>> berk.geveci at kitware.com> wrote: >>>>>>>> >>>>>>>>> Hi folks, >>>>>>>>> >>>>>>>>> This came through VTK's uservoice. I didn't think that we stopped >>>>>>>>> support any Tk widgets. Am I wrong? >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> -berk >>>>>>>>> >>>>>>>>> ---------- Forwarded message ---------- >>>>>>>>> From: VTK >>>>>>>>> Date: Wed, Aug 12, 2015 at 11:02 AM >>>>>>>>> Subject: [vtk.uservoice.com] New suggestion: 'Return support for >>>>>>>>> Tkinter widgets.' >>>>>>>>> To: "berk.geveci" > >>>>>>>>> >>>>>>>>> >>>>>>>>> Customer Feedback for VTK vtk.uservoice.com >>>>>>>>> >>>>>>>>> New suggestion >>>>>>>>> 1 >>>>>>>>> votes >>>>>>>>> Return support for Tkinter widgets. >>>>>>>>> >>>>>>>>> >>>>>>>>> Posted in General >>>>>>>>> >>>>>>>>> >>>>>>>>> Tkinter is a good GUI toolkit, is cross-platform, simple to use >>>>>>>>> and lightweight (as opposed to Qt), which is important for scientific users >>>>>>>>> like me developing tools with graphics capabilities. >>>>>>>>> >>>>>>>>> I know it is not very popular, but it only needs support and usage >>>>>>>>> to gain visibility and expand its user base. Lack of support from important >>>>>>>>> projects like VTK don't help in the cause, so it seems to me like a vicious >>>>>>>>> circle. >>>>>>>>> >>>>>>>>> So please, return the support for the widgets. >>>>>>>>> >>>>>>>>> [image: Guille Giraldo]Guille Giraldo >>>>>>>>> >>>>>>>>> on Aug 12, 2015 (0 comments >>>>>>>>> ) >>>>>>>>> >>>>>>>>> Delete >>>>>>>>> Mark >>>>>>>>> as Spam >>>>>>>>> >>>>>>>>> >>>>>>>>> If you would like to stop receiving these emails you may >>>>>>>>> unsubscribe >>>>>>>>> >>>>>>>>> . >>>>>>>>> >>>>>>>>> [image: powered by UserVoice] >>>>>>>>> >>>>>>>>> >>>>>>>> >>> >>> >>> -- >>> ___________________________________________ >>> Andrew J. P. Maclean >>> >>> ___________________________________________ >>> >> >> > > > -- > ___________________________________________ > Andrew J. P. Maclean > > ___________________________________________ > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Fri Aug 14 05:28:27 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Fri, 14 Aug 2015 19:28:27 +1000 Subject: [vtk-developers] Making VTK/Examples Py3k compatible. Message-ID: If there are no objections, I'll look at these over the next day or do. Andrew Maclean -------------- next part -------------- An HTML attachment was scrubbed... URL: From victorsv at gmail.com Fri Aug 14 06:25:00 2015 From: victorsv at gmail.com (victor sv) Date: Fri, 14 Aug 2015 12:25:00 +0200 Subject: [vtk-developers] XDMF and hyperslabs Message-ID: Hello all, I'm trying to create and visualize an XDMF/HDF5 file containing a partitioned mesh using hyperslabs. Is this supported by Paraview/VTK ?? The HDF5 (solution1.h5) looks as follows: GROUP "/" { GROUP "Grid" { DATASET "Connectivities" { DATATYPE H5T_STD_I32BE DATASPACE SIMPLE { ( 18 ) / ( 18 ) } DATA { (0): 0, 1, 2, 3, 2, 1, 4, 5, 6, 7, 6, 5, 6, 7, 8, 9, 8, 7 } } DATASET "Coordinates" { DATATYPE H5T_IEEE_F64BE DATASPACE SIMPLE { ( 20 ) / ( 20 ) } DATA { (0): 0, 0, 1, 0, 0, 0.5, 1, 0.5, 0, 0.5, 1, 0.5, 0, 1, 1, 1, 0, 1.5, (18): 1, 1.5 } } DATASET "Solution" { DATATYPE H5T_IEEE_F64BE DATASPACE SIMPLE { ( 10 ) / ( 10 ) } DATA { (0): 0, 0, 0, 0, 1, 1, 1, 1, 1, 1 } } } } And the XDMF file to represent a 2-triangle (4 points) piece of the full mesh is: 0 1 6 solution1.h5:Grid/Connectivities 0 1 8 solution1.h5:Grid/Coordinates I'm trying to use the syntax explained at the XDMF webpage ( http://www.xdmf.org/index.php/XDMF_Model_and_Format ), but I'm feeling confused about the version of the documentation and current version of XDMF library included in VTK library. Can anyone give me some info about this? It is XDMFv3 already public ? Thanks in advance, V?ctor. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.king at kitware.com Fri Aug 14 09:30:02 2015 From: brad.king at kitware.com (Brad King) Date: Fri, 14 Aug 2015 09:30:02 -0400 Subject: [vtk-developers] CMake Segfaults while configuring VTK In-Reply-To: <55CD0005.8070904@ohio.edu> References: <55C2014D.5060103@ohio.edu> <55C24369.5010902@kitware.com> <55CD0005.8070904@ohio.edu> Message-ID: <55CDED5A.5060205@kitware.com> On 08/13/2015 04:37 PM, Kevin H. Hobbs wrote: > On 08/05/2015 01:10 PM, Brad King wrote: >> Steve has updated the offending topic with a fix so we'll see tonight. > > On August 8 VTK stopped configuring again. > > I'm about to rebuild CMake in Debug mode and rerun gdb but can either of > you replicate this or is it just me? I happened to notice earlier in the day you sent this message and have already fixed it. It was the exact same crash as before because the fix was made without a test case and then the same problem was re-introduced later. This time I fixed it and added the relevant test case. -Brad From dan.lipsa at kitware.com Fri Aug 14 12:05:28 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 14 Aug 2015 12:05:28 -0400 Subject: [vtk-developers] Saving fields (arrays not associated with points or cells) in VTK legacy or VTK xml files Message-ID: Hi all, We had a discussion on the ParaView mailing list with a user trying to save fields (arrays not associated with a point or a cell) in a VTK legacy file. Looking through VTK Users' Guide it seems that there is no documented way to do that (or I cannot see it). http://paraview.markmail.org/search/?q=Schubert%2C%20Raphael#query:Schubert%2C%20Raphael+page:1+mid:5tcph33kduxdnjfh+state:results I filed a bug for this: http://www.vtk.org/Bug/view.php?id=15653 Does anyone have experience with this? Thanks, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From will.schroeder at kitware.com Fri Aug 14 12:48:29 2015 From: will.schroeder at kitware.com (Will Schroeder) Date: Fri, 14 Aug 2015 12:48:29 -0400 Subject: [vtk-developers] Saving fields (arrays not associated with points or cells) in VTK legacy or VTK xml files In-Reply-To: References: Message-ID: Dan if memory serves me right there is a Field dataset type that supports arbitrary data. Look in the VTK textbook for more information, or see this extract: http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf On Fri, Aug 14, 2015 at 12:05 PM, Dan Lipsa wrote: > Hi all, > > We had a discussion on the ParaView mailing list with a user trying to > save fields (arrays not associated with a point or a cell) in a VTK legacy > file. Looking through VTK Users' Guide it seems that there is no documented > way to do that (or I cannot see it). > > > http://paraview.markmail.org/search/?q=Schubert%2C%20Raphael#query:Schubert%2C%20Raphael+page:1+mid:5tcph33kduxdnjfh+state:results > > I filed a bug for this: > > http://www.vtk.org/Bug/view.php?id=15653 > > > Does anyone have experience with this? > > Thanks, > Dan > > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -- William J. Schroeder, PhD Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Fri Aug 14 12:57:17 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Fri, 14 Aug 2015 12:57:17 -0400 Subject: [vtk-developers] Saving fields (arrays not associated with points or cells) in VTK legacy or VTK xml files In-Reply-To: References: Message-ID: We see that will but that doesn't quite fit the bill. The file format says: FIELD DATA FILE or SPECIFIC DATASET FILE The former contains ONLY the unaligned FieldData arrays, the later contains everything EXCEPT the FieldData arrays. The readers and writers agree with the format. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Aug 14, 2015 at 12:48 PM, Will Schroeder wrote: > Dan if memory serves me right there is a Field dataset type that supports > arbitrary data. Look in the VTK textbook for more information, or see this > extract: > > http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf > > On Fri, Aug 14, 2015 at 12:05 PM, Dan Lipsa wrote: > >> Hi all, >> >> We had a discussion on the ParaView mailing list with a user trying to >> save fields (arrays not associated with a point or a cell) in a VTK legacy >> file. Looking through VTK Users' Guide it seems that there is no documented >> way to do that (or I cannot see it). >> >> >> http://paraview.markmail.org/search/?q=Schubert%2C%20Raphael#query:Schubert%2C%20Raphael+page:1+mid:5tcph33kduxdnjfh+state:results >> >> I filed a bug for this: >> >> http://www.vtk.org/Bug/view.php?id=15653 >> >> >> Does anyone have experience with this? >> >> Thanks, >> Dan >> >> >> _______________________________________________ >> 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=vtk-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/vtk-developers >> >> >> > > > -- > William J. Schroeder, PhD > Kitware, Inc. > 28 Corporate Drive > Clifton Park, NY 12065 > will.schroeder at kitware.com > http://www.kitware.com > (518) 881-4902 > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Fri Aug 14 12:59:29 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 14 Aug 2015 12:59:29 -0400 Subject: [vtk-developers] Saving fields (arrays not associated with points or cells) in VTK legacy or VTK xml files In-Reply-To: References: Message-ID: Hi Will, Yes indeed, we have seen that for VTK Legacy files. What if one has a vtkPolyData (or any of the other dataset types) and that dataset has a field array (besides other point or cell arrays)? It does not seem to be a way to save that dataset as a POLYDATA that includes POINT_DATA, CELL_DATA and the field data. On Fri, Aug 14, 2015 at 12:48 PM, Will Schroeder wrote: > Dan if memory serves me right there is a Field dataset type that supports > arbitrary data. Look in the VTK textbook for more information, or see this > extract: > > http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf > > On Fri, Aug 14, 2015 at 12:05 PM, Dan Lipsa wrote: > >> Hi all, >> >> We had a discussion on the ParaView mailing list with a user trying to >> save fields (arrays not associated with a point or a cell) in a VTK legacy >> file. Looking through VTK Users' Guide it seems that there is no documented >> way to do that (or I cannot see it). >> >> >> http://paraview.markmail.org/search/?q=Schubert%2C%20Raphael#query:Schubert%2C%20Raphael+page:1+mid:5tcph33kduxdnjfh+state:results >> >> I filed a bug for this: >> >> http://www.vtk.org/Bug/view.php?id=15653 >> >> >> Does anyone have experience with this? >> >> Thanks, >> Dan >> >> >> _______________________________________________ >> 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=vtk-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/vtk-developers >> >> >> > > > -- > William J. Schroeder, PhD > Kitware, Inc. > 28 Corporate Drive > Clifton Park, NY 12065 > will.schroeder at kitware.com > http://www.kitware.com > (518) 881-4902 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From will.schroeder at kitware.com Fri Aug 14 13:03:22 2015 From: will.schroeder at kitware.com (Will Schroeder) Date: Fri, 14 Aug 2015 13:03:22 -0400 Subject: [vtk-developers] Saving fields (arrays not associated with points or cells) in VTK legacy or VTK xml files In-Reply-To: References: Message-ID: Ahh yes I see, the wider usage of field data came after the initial implementation which was probably in 1994 :-) so there were probably bugs backed into the cake. I don't recall the last time we changed the legacy file formats, so I'm curious is this something that is being considered? (sorry I missed the discussion) W On Fri, Aug 14, 2015 at 12:59 PM, Dan Lipsa wrote: > Hi Will, > Yes indeed, we have seen that for VTK Legacy files. What if one has a > vtkPolyData (or any of the other dataset types) and that dataset has a > field array (besides other point or cell arrays)? It does not seem to be a > way to save that dataset as a POLYDATA that includes POINT_DATA, CELL_DATA > and the field data. > > > > On Fri, Aug 14, 2015 at 12:48 PM, Will Schroeder < > will.schroeder at kitware.com> wrote: > >> Dan if memory serves me right there is a Field dataset type that supports >> arbitrary data. Look in the VTK textbook for more information, or see this >> extract: >> >> http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf >> >> On Fri, Aug 14, 2015 at 12:05 PM, Dan Lipsa >> wrote: >> >>> Hi all, >>> >>> We had a discussion on the ParaView mailing list with a user trying to >>> save fields (arrays not associated with a point or a cell) in a VTK legacy >>> file. Looking through VTK Users' Guide it seems that there is no documented >>> way to do that (or I cannot see it). >>> >>> >>> http://paraview.markmail.org/search/?q=Schubert%2C%20Raphael#query:Schubert%2C%20Raphael+page:1+mid:5tcph33kduxdnjfh+state:results >>> >>> I filed a bug for this: >>> >>> http://www.vtk.org/Bug/view.php?id=15653 >>> >>> >>> Does anyone have experience with this? >>> >>> Thanks, >>> Dan >>> >>> >>> _______________________________________________ >>> 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=vtk-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/vtk-developers >>> >>> >>> >> >> >> -- >> William J. Schroeder, PhD >> Kitware, Inc. >> 28 Corporate Drive >> Clifton Park, NY 12065 >> will.schroeder at kitware.com >> http://www.kitware.com >> (518) 881-4902 >> > > -- William J. Schroeder, PhD Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Fri Aug 14 13:06:12 2015 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 14 Aug 2015 13:06:12 -0400 Subject: [vtk-developers] Saving fields (arrays not associated with points or cells) in VTK legacy or VTK xml files In-Reply-To: References: Message-ID: Not that I know of. We were trying to help a ParaView user so we just stumbled on this. On Fri, Aug 14, 2015 at 1:03 PM, Will Schroeder wrote: > Ahh yes I see, the wider usage of field data came after the initial > implementation which was probably in 1994 :-) so there were probably bugs > backed into the cake. I don't recall the last time we changed the legacy > file formats, so I'm curious is this something that is being considered? > (sorry I missed the discussion) > > W > > On Fri, Aug 14, 2015 at 12:59 PM, Dan Lipsa wrote: > >> Hi Will, >> Yes indeed, we have seen that for VTK Legacy files. What if one has a >> vtkPolyData (or any of the other dataset types) and that dataset has a >> field array (besides other point or cell arrays)? It does not seem to be a >> way to save that dataset as a POLYDATA that includes POINT_DATA, CELL_DATA >> and the field data. >> >> >> >> On Fri, Aug 14, 2015 at 12:48 PM, Will Schroeder < >> will.schroeder at kitware.com> wrote: >> >>> Dan if memory serves me right there is a Field dataset type that >>> supports arbitrary data. Look in the VTK textbook for more information, or >>> see this extract: >>> >>> http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf >>> >>> On Fri, Aug 14, 2015 at 12:05 PM, Dan Lipsa >>> wrote: >>> >>>> Hi all, >>>> >>>> We had a discussion on the ParaView mailing list with a user trying to >>>> save fields (arrays not associated with a point or a cell) in a VTK legacy >>>> file. Looking through VTK Users' Guide it seems that there is no documented >>>> way to do that (or I cannot see it). >>>> >>>> >>>> http://paraview.markmail.org/search/?q=Schubert%2C%20Raphael#query:Schubert%2C%20Raphael+page:1+mid:5tcph33kduxdnjfh+state:results >>>> >>>> I filed a bug for this: >>>> >>>> http://www.vtk.org/Bug/view.php?id=15653 >>>> >>>> >>>> Does anyone have experience with this? >>>> >>>> Thanks, >>>> Dan >>>> >>>> >>>> _______________________________________________ >>>> 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=vtk-developers >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/vtk-developers >>>> >>>> >>>> >>> >>> >>> -- >>> William J. Schroeder, PhD >>> Kitware, Inc. >>> 28 Corporate Drive >>> Clifton Park, NY 12065 >>> will.schroeder at kitware.com >>> http://www.kitware.com >>> (518) 881-4902 >>> >> >> > > > -- > William J. Schroeder, PhD > Kitware, Inc. > 28 Corporate Drive > Clifton Park, NY 12065 > will.schroeder at kitware.com > http://www.kitware.com > (518) 881-4902 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashraymalhotra1 at gmail.com Sat Aug 15 03:39:28 2015 From: ashraymalhotra1 at gmail.com (Ashray Malhotra) Date: Sat, 15 Aug 2015 13:09:28 +0530 Subject: [vtk-developers] Filter Coefficients of Butterworth filter from Cutoff Frequency and Filter Degree Message-ID: Hello, I am working to include "Eulerian Motion Magnification" in VTK. It requires me to implement temporal filtering(time domain filtering) of image pyramids. I have already implemented the IIR filtering and was exploring the possiblity to expand this to other filtering techiques. I want to add Butterworth filtering option as well along with IIR but I can't find any suitable class already implemented in VTK(I did have a look at the vtkImageButterworthLowPass class but it takes an image as input which doesnt serve my use case). I had implemented this in python( https://github.com/ashray/Eulerian-Video-Magnification/blob/master/Code/butter.py) sometime back but there I had used scipy.signal.butter to get the filter coefficients. Can someone please tell me if there is any such functionality(to get filter coefficients of lowpass butterworth filter given the filter degree and cutoff frequencies) in VTK? Thanks a lot. Regards Ashray Malhotra -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Mon Aug 17 03:56:06 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Mon, 17 Aug 2015 17:56:06 +1000 Subject: [vtk-developers] Conversion of Python Examples to Py3k Message-ID: Currently there are 155 python examples in 21 folders and only 33 files needed to be changed. I have run each example using Python 3.4 and making changes where applicable. Unfortunately I cannot test all of them, mainly because boost is not enabled, I don't use PyQt4, I don't have Matlab etc. I also am using OpenGL2. If anyone would like to test the ones I can't test I have listed them in the merge request: https://gitlab.kitware.com/vtk/vtk/merge_requests/543 Regards Andrew -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Mon Aug 17 13:04:49 2015 From: david.thompson at kitware.com (David Thompson) Date: Mon, 17 Aug 2015 13:04:49 -0400 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Message-ID: Hi Lin, > I have some questions about the test. > 1. About simplicial interpolation. Should I test some simple cases (hard coded simple shape) or some shapes like the motorcycle? Those are 2 different types of tests. (There are many; see http://stackoverflow.com/questions/437897/what-are-unit-testing-and-integration-testing-and-what-other-types-of-testing-s for some lists of test types). The first test (simple hard-coded shape) is a unit test and the second (test of both the reader, spline-to-patch class, and patch interpolation) is an integration test. Both are important, but since you already have an integration test for the motorcycle, I think a good set of unit tests for simplicial interpolation would be enough. > If it is the latter one, how to convert the rectangular patch to simpicial patch? > > 2. About point inversion. How to test it for the simpicial patch? I only implemented the point inversion for NURBS patch. If you didn't implement it, you can't test it. :-) However, if you know what you want the test to look like, you can write the test before you implement inversion and just leave it commented out with a note. Many people think this is how development should be done in the first place, since it forces you to consider how people will use what you write. > 3. About derivative computation. Should I just test them numerically? For example, given a shape and a parametric coordinate, test the result of our implementation with ground truth. Again, since you are using the derivatives in code that is part of an integration, I think unit testing (as you suggest) is enough. David From majcjc at gmail.com Mon Aug 17 22:40:46 2015 From: majcjc at gmail.com (Lin M) Date: Tue, 18 Aug 2015 10:40:46 +0800 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Message-ID: Hi Dr. Thompson, I found you left an interface for vtkBezierPatchAdaptro::EvaluateDeriv(double Pt[3], double* Paras, int d). For 1-d curve, the derivative is always a 3*1 vector, but with the parametric dimension increasing, higher order derivatives will contain many points (it becomes matrix-by-vector differential). I can't figure out a generalized way to interpret this. That's why I declared functions to compute derivative for curve, surface and volume separately. Do you have any suggestions for that? Thanks! Best, Lin On Tue, Aug 18, 2015 at 1:04 AM, David Thompson wrote: > Hi Lin, > > > I have some questions about the test. > > 1. About simplicial interpolation. Should I test some simple cases (hard > coded simple shape) or some shapes like the motorcycle? > > Those are 2 different types of tests. (There are many; see > http://stackoverflow.com/questions/437897/what-are-unit-testing-and-integration-testing-and-what-other-types-of-testing-s > for some lists of test types). The first test (simple hard-coded shape) is > a unit test and the second (test of both the reader, spline-to-patch class, > and patch interpolation) is an integration test. > > Both are important, but since you already have an integration test for the > motorcycle, I think a good set of unit tests for simplicial interpolation > would be enough. > > > If it is the latter one, how to convert the rectangular patch to > simpicial patch? > > > > 2. About point inversion. How to test it for the simpicial patch? I only > implemented the point inversion for NURBS patch. > > If you didn't implement it, you can't test it. :-) However, if you know > what you want the test to look like, you can write the test before you > implement inversion and just leave it commented out with a note. Many > people think this is how development should be done in the first place, > since it forces you to consider how people will use what you write. > > > 3. About derivative computation. Should I just test them numerically? > For example, given a shape and a parametric coordinate, test the result of > our implementation with ground truth. > > Again, since you are using the derivatives in code that is part of an > integration, I think unit testing (as you suggest) is enough. > > David -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Tue Aug 18 08:23:43 2015 From: david.thompson at kitware.com (David Thompson) Date: Tue, 18 Aug 2015 08:23:43 -0400 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Message-ID: <96774517-8F9D-49FE-96B3-3E9AEC33742F@kitware.com> Hi Lin, It has been a while since we talked about that, and I am not sure from looking at the method whether Pt is supposed to be the input or output. If the input, then it should be named something like coord instead of Pt. If the output, then you are correct, it should be a "double*" and the documentation should spell out how much memory it must point to. (Since in general the n-th derivative is a symmetric tensor of rank n, there are (n+1)(n+2)...(n+k-1)/(k-1) partial derivatives. This is related to Pascal's simplex. See https://en.wikipedia.org/wiki/Pascal%27s_pyramid#Parallels_to_Pascal.27s_triangle_and_Multinomial_Coefficients and https://en.wikipedia.org/wiki/Differential_of_a_function#Higher-order_differentials .) It is fine to have different methods for curves, surfaces, and volumes for now. As you can see in the links above, the general pattern is that the n-th total derivative is a tensor of all possible combinations of partial derivatives with respect to the 1, 2, or 3 parametric coordinates. Call the parametric coordinates r_i for i in {1, 2, 3} and say we are taking the n-th derivative of f. Then Python code to compute one possible ordering of the partial differentials in the output array would be def pdiff(i,n): r=[] if i == 1: return [[n,],] for x in range(n+1): for y in pdiff(i-1,n-x): r.append(y+[x,]) return r which returns a list of i-tuples that all sum to n. For example pdiff(2,1) returns [[1, 0], [0, 1]] pdiff(2,2) returns [[2, 0], [1, 1], [0, 2]] pdiff(3,1) returns [[1, 0, 0], [0, 1, 0], [0, 0, 1]] pdiff(3,2) returns [[2, 0, 0], [1, 1, 0], [0, 2, 0], [1, 0, 1], [0, 1, 1], [0, 0, 2]] However, really only the first (Jacobian, a vector) and second (Hessian, a symmetric 3x3 matrix with 6 unique entries) derivatives are used very much because (a) the number of terms grows very fast with increasing derivative and (b) the first 2 derivatives are used widely for root-finding and curvature computation but further derivatives are not. David On Aug 17, 2015, at 22:40, Lin M wrote: > > Hi Dr. Thompson, > > I found you left an interface for vtkBezierPatchAdaptro::EvaluateDeriv(double Pt[3], double* Paras, int d). > For 1-d curve, the derivative is always a 3*1 vector, but with the parametric dimension increasing, higher order derivatives will contain many points (it becomes matrix-by-vector differential). I can't figure out a generalized way to interpret this. That's why I declared functions to compute derivative for curve, surface and volume separately. Do you have any suggestions for that? Thanks! > > Best, > Lin > >> On Tue, Aug 18, 2015 at 1:04 AM, David Thompson wrote: >> Hi Lin, >> >> > I have some questions about the test. >> > 1. About simplicial interpolation. Should I test some simple cases (hard coded simple shape) or some shapes like the motorcycle? >> >> Those are 2 different types of tests. (There are many; see http://stackoverflow.com/questions/437897/what-are-unit-testing-and-integration-testing-and-what-other-types-of-testing-s for some lists of test types). The first test (simple hard-coded shape) is a unit test and the second (test of both the reader, spline-to-patch class, and patch interpolation) is an integration test. >> >> Both are important, but since you already have an integration test for the motorcycle, I think a good set of unit tests for simplicial interpolation would be enough. >> >> > If it is the latter one, how to convert the rectangular patch to simpicial patch? >> > >> > 2. About point inversion. How to test it for the simpicial patch? I only implemented the point inversion for NURBS patch. >> >> If you didn't implement it, you can't test it. :-) However, if you know what you want the test to look like, you can write the test before you implement inversion and just leave it commented out with a note. Many people think this is how development should be done in the first place, since it forces you to consider how people will use what you write. >> >> > 3. About derivative computation. Should I just test them numerically? For example, given a shape and a parametric coordinate, test the result of our implementation with ground truth. >> >> Again, since you are using the derivatives in code that is part of an integration, I think unit testing (as you suggest) is enough. >> >> David > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lokeshnano at gmail.com Wed Aug 19 09:01:36 2015 From: lokeshnano at gmail.com (lokesh9) Date: Wed, 19 Aug 2015 06:01:36 -0700 (MST) Subject: [vtk-developers] how to generate kernel for Laplacian Of Gaussian Message-ID: <1439989296331-5733558.post@n5.nabble.com> i am facing a problem how to create the kernel for convolving with the vtkimage, Is kernel should be same vtkimage datatype? -- View this message in context: http://vtk.1045678.n5.nabble.com/how-to-generate-kernel-for-Laplacian-Of-Gaussian-tp5733558.html Sent from the VTK - Dev mailing list archive at Nabble.com. From lokeshnano at gmail.com Wed Aug 19 09:02:16 2015 From: lokeshnano at gmail.com (lokesh9) Date: Wed, 19 Aug 2015 06:02:16 -0700 (MST) Subject: [vtk-developers] how to generate kernel for Laplacian Of Gaussian Message-ID: <1439989336542-5733559.post@n5.nabble.com> i am facing a problem how to create the kernel for convolving with the vtkimage, Is kernel should be same vtkimage datatype? -- View this message in context: http://vtk.1045678.n5.nabble.com/how-to-generate-kernel-for-Laplacian-Of-Gaussian-tp5733559.html Sent from the VTK - Dev mailing list archive at Nabble.com. From majcjc at gmail.com Thu Aug 20 11:56:30 2015 From: majcjc at gmail.com (Lin M) Date: Thu, 20 Aug 2015 23:56:30 +0800 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: <96774517-8F9D-49FE-96B3-3E9AEC33742F@kitware.com> References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> <96774517-8F9D-49FE-96B3-3E9AEC33742F@kitware.com> Message-ID: Hi Dr. Thompson, I have added image based tests for almost all vtkFiltersBezier related class including BREP file reader, patch(simplicial) interpolation and point projection for both curve and surface example. I will complete required documents soon. Best, Lin On Tue, Aug 18, 2015 at 8:23 PM, David Thompson wrote: > Hi Lin, > > It has been a while since we talked about that, and I am not sure from > looking at the method whether Pt is supposed to be the input or output. If > the input, then it should be named something like coord instead of Pt. If > the output, then you are correct, it should be a "double*" and the > documentation should spell out how much memory it must point to. (Since in > general the n-th derivative is a symmetric tensor of rank n, there are > (n+1)(n+2)...(n+k-1)/(k-1) partial derivatives. This is related to Pascal's > simplex. See > https://en.wikipedia.org/wiki/Pascal%27s_pyramid#Parallels_to_Pascal.27s_triangle_and_Multinomial_Coefficients > and > https://en.wikipedia.org/wiki/Differential_of_a_function#Higher-order_differentials > .) > > It is fine to have different methods for curves, surfaces, and volumes for > now. As you can see in the links above, the general pattern is that the > n-th total derivative is a tensor of all possible combinations of partial > derivatives with respect to the 1, 2, or 3 parametric coordinates. Call the > parametric coordinates r_i for i in {1, 2, 3} and say we are taking the > n-th derivative of f. Then Python code to compute one possible ordering of > the partial differentials in the output array would be > > def pdiff(i,n): > r=[] > if i == 1: > return [[n,],] > for x in range(n+1): > for y in pdiff(i-1,n-x): > r.append(y+[x,]) > return r > > which returns a list of i-tuples that all sum to n. For example > > pdiff(2,1) returns [[1, 0], [0, 1]] > pdiff(2,2) returns [[2, 0], [1, 1], [0, 2]] > > pdiff(3,1) returns [[1, 0, 0], [0, 1, 0], [0, 0, 1]] > pdiff(3,2) returns [[2, 0, 0], [1, 1, 0], [0, 2, 0], [1, 0, 1], [0, 1, > 1], [0, 0, 2]] > > However, really only the first (Jacobian, a vector) and second (Hessian, a > symmetric 3x3 matrix with 6 unique entries) derivatives are used very much > because (a) the number of terms grows very fast with increasing derivative > and (b) the first 2 derivatives are used widely for root-finding and > curvature computation but further derivatives are not. > > David > > On Aug 17, 2015, at 22:40, Lin M wrote: > > Hi Dr. Thompson, > > I found you left an interface for > vtkBezierPatchAdaptro::EvaluateDeriv(double Pt[3], double* Paras, int d). > For 1-d curve, the derivative is always a 3*1 vector, but with the > parametric dimension increasing, higher order derivatives will contain > many points (it becomes matrix-by-vector differential). I can't figure out > a generalized way to interpret this. That's why I declared functions to > compute derivative for curve, surface and volume separately. Do you have > any suggestions for that? Thanks! > > Best, > Lin > > On Tue, Aug 18, 2015 at 1:04 AM, David Thompson < > david.thompson at kitware.com> wrote: > >> Hi Lin, >> >> > I have some questions about the test. >> > 1. About simplicial interpolation. Should I test some simple cases >> (hard coded simple shape) or some shapes like the motorcycle? >> >> Those are 2 different types of tests. (There are many; see >> http://stackoverflow.com/questions/437897/what-are-unit-testing-and-integration-testing-and-what-other-types-of-testing-s >> for some lists of test types). The first test (simple hard-coded shape) is >> a unit test and the second (test of both the reader, spline-to-patch class, >> and patch interpolation) is an integration test. >> >> Both are important, but since you already have an integration test for >> the motorcycle, I think a good set of unit tests for simplicial >> interpolation would be enough. >> >> > If it is the latter one, how to convert the rectangular patch to >> simpicial patch? >> > >> > 2. About point inversion. How to test it for the simpicial patch? I >> only implemented the point inversion for NURBS patch. >> >> If you didn't implement it, you can't test it. :-) However, if you know >> what you want the test to look like, you can write the test before you >> implement inversion and just leave it commented out with a note. Many >> people think this is how development should be done in the first place, >> since it forces you to consider how people will use what you write. >> >> > 3. About derivative computation. Should I just test them numerically? >> For example, given a shape and a parametric coordinate, test the result of >> our implementation with ground truth. >> >> Again, since you are using the derivatives in code that is part of an >> integration, I think unit testing (as you suggest) is enough. >> >> David > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From majcjc at gmail.com Fri Aug 21 00:58:30 2015 From: majcjc at gmail.com (Lin M) Date: Fri, 21 Aug 2015 12:58:30 +0800 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> <96774517-8F9D-49FE-96B3-3E9AEC33742F@kitware.com> Message-ID: Hi Dr. Thompson, I have finished supplementary documentation for the vtkFiltersBezier module. I think it's ready to be tested now. On Thu, Aug 20, 2015 at 11:56 PM, Lin M wrote: > Hi Dr. Thompson, > > I have added image based tests for almost all vtkFiltersBezier related > class including BREP file reader, patch(simplicial) interpolation and point > projection for both curve and surface example. > > I will complete required documents soon. > > Best, > Lin > > On Tue, Aug 18, 2015 at 8:23 PM, David Thompson < > david.thompson at kitware.com> wrote: > >> Hi Lin, >> >> It has been a while since we talked about that, and I am not sure from >> looking at the method whether Pt is supposed to be the input or output. If >> the input, then it should be named something like coord instead of Pt. If >> the output, then you are correct, it should be a "double*" and the >> documentation should spell out how much memory it must point to. (Since in >> general the n-th derivative is a symmetric tensor of rank n, there are >> (n+1)(n+2)...(n+k-1)/(k-1) partial derivatives. This is related to Pascal's >> simplex. See >> https://en.wikipedia.org/wiki/Pascal%27s_pyramid#Parallels_to_Pascal.27s_triangle_and_Multinomial_Coefficients >> and >> https://en.wikipedia.org/wiki/Differential_of_a_function#Higher-order_differentials >> .) >> >> It is fine to have different methods for curves, surfaces, and volumes >> for now. As you can see in the links above, the general pattern is that the >> n-th total derivative is a tensor of all possible combinations of partial >> derivatives with respect to the 1, 2, or 3 parametric coordinates. Call the >> parametric coordinates r_i for i in {1, 2, 3} and say we are taking the >> n-th derivative of f. Then Python code to compute one possible ordering of >> the partial differentials in the output array would be >> >> def pdiff(i,n): >> r=[] >> if i == 1: >> return [[n,],] >> for x in range(n+1): >> for y in pdiff(i-1,n-x): >> r.append(y+[x,]) >> return r >> >> which returns a list of i-tuples that all sum to n. For example >> >> pdiff(2,1) returns [[1, 0], [0, 1]] >> pdiff(2,2) returns [[2, 0], [1, 1], [0, 2]] >> >> pdiff(3,1) returns [[1, 0, 0], [0, 1, 0], [0, 0, 1]] >> pdiff(3,2) returns [[2, 0, 0], [1, 1, 0], [0, 2, 0], [1, 0, 1], [0, 1, >> 1], [0, 0, 2]] >> >> However, really only the first (Jacobian, a vector) and second (Hessian, >> a symmetric 3x3 matrix with 6 unique entries) derivatives are used very >> much because (a) the number of terms grows very fast with increasing >> derivative and (b) the first 2 derivatives are used widely for root-finding >> and curvature computation but further derivatives are not. >> >> David >> >> On Aug 17, 2015, at 22:40, Lin M wrote: >> >> Hi Dr. Thompson, >> >> I found you left an interface for >> vtkBezierPatchAdaptro::EvaluateDeriv(double Pt[3], double* Paras, int d). >> For 1-d curve, the derivative is always a 3*1 vector, but with the >> parametric dimension increasing, higher order derivatives will contain >> many points (it becomes matrix-by-vector differential). I can't figure out >> a generalized way to interpret this. That's why I declared functions to >> compute derivative for curve, surface and volume separately. Do you have >> any suggestions for that? Thanks! >> >> Best, >> Lin >> >> On Tue, Aug 18, 2015 at 1:04 AM, David Thompson < >> david.thompson at kitware.com> wrote: >> >>> Hi Lin, >>> >>> > I have some questions about the test. >>> > 1. About simplicial interpolation. Should I test some simple cases >>> (hard coded simple shape) or some shapes like the motorcycle? >>> >>> Those are 2 different types of tests. (There are many; see >>> http://stackoverflow.com/questions/437897/what-are-unit-testing-and-integration-testing-and-what-other-types-of-testing-s >>> for some lists of test types). The first test (simple hard-coded shape) is >>> a unit test and the second (test of both the reader, spline-to-patch class, >>> and patch interpolation) is an integration test. >>> >>> Both are important, but since you already have an integration test for >>> the motorcycle, I think a good set of unit tests for simplicial >>> interpolation would be enough. >>> >>> > If it is the latter one, how to convert the rectangular patch to >>> simpicial patch? >>> > >>> > 2. About point inversion. How to test it for the simpicial patch? I >>> only implemented the point inversion for NURBS patch. >>> >>> If you didn't implement it, you can't test it. :-) However, if you know >>> what you want the test to look like, you can write the test before you >>> implement inversion and just leave it commented out with a note. Many >>> people think this is how development should be done in the first place, >>> since it forces you to consider how people will use what you write. >>> >>> > 3. About derivative computation. Should I just test them numerically? >>> For example, given a shape and a parametric coordinate, test the result of >>> our implementation with ground truth. >>> >>> Again, since you are using the derivatives in code that is part of an >>> integration, I think unit testing (as you suggest) is enough. >>> >>> David >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From westcoast_gangstar at web.de Fri Aug 21 06:35:14 2015 From: westcoast_gangstar at web.de (hausfrau87) Date: Fri, 21 Aug 2015 03:35:14 -0700 (MST) Subject: [vtk-developers] VTK - How to read Tensors/Matrix per cell from a NIFTI Image? Message-ID: <1440153314674-5733583.post@n5.nabble.com> Hey guys! I'm trying to implement a MRT-DTI real-time fibertracking visualization tool based on VTK. Therefore we need to read the DTI tensors/matrices per cell stored in a NIFTI Image (.nii) and I really can't figure out how to do this. It's not a problem to retrieve a single scalar value from the NIFTI file, but I don't know how to get the tensor (3x3/4x4 matrix). We would really appreciate any help ! Since the NIFTIImageReader is supposed to read a tensor NIFTI image as a multi-component vtkImage we tried this: vtkSmartPointer extractTupel1 = vtkSmartPointer::New(); extractTupel1->SetInputConnection(reader->GetOutputPort()); extractTupel1->SetComponents(0,1,2); extractTupel1->Update(); vtkSmartPointer extractTupel2 = vtkSmartPointer::New(); extractTupel2->SetInputConnection(reader->GetOutputPort()); extractTupel2->SetComponents(3, 4, 5); extractTupel2->Update(); vtkSmartPointer extractTupel3 = vtkSmartPointer::New(); extractTupel3->SetInputConnection(reader->GetOutputPort()); extractTupel3->SetComponents(6, 7, 8); extractTupel3->Update(); extractTupel1->GetOutput()->GetPoint(pointId, tupel1); extractTupel2->GetOutput()->GetPoint(pointId, tupel2); extractTupel3->GetOutput()->GetPoint(pointId, tupel3); But it doesn't work. Maybe the GetPoint-Method is the wrong choice? Please help :) -- View this message in context: http://vtk.1045678.n5.nabble.com/VTK-How-to-read-Tensors-Matrix-per-cell-from-a-NIFTI-Image-tp5733583.html Sent from the VTK - Dev mailing list archive at Nabble.com. From majcjc at gmail.com Fri Aug 21 10:35:10 2015 From: majcjc at gmail.com (Lin M) Date: Fri, 21 Aug 2015 22:35:10 +0800 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> <96774517-8F9D-49FE-96B3-3E9AEC33742F@kitware.com> Message-ID: Hi Dr. Thompson, I have merged the branch to spline/VTK. How can I make the Cdash test work then? On Fri, Aug 21, 2015 at 12:58 PM, Lin M wrote: > Hi Dr. Thompson, > > I have finished supplementary documentation for the vtkFiltersBezier > module. I think it's ready to be tested now. > > On Thu, Aug 20, 2015 at 11:56 PM, Lin M wrote: > >> Hi Dr. Thompson, >> >> I have added image based tests for almost all vtkFiltersBezier related >> class including BREP file reader, patch(simplicial) interpolation and point >> projection for both curve and surface example. >> >> I will complete required documents soon. >> >> Best, >> Lin >> >> On Tue, Aug 18, 2015 at 8:23 PM, David Thompson < >> david.thompson at kitware.com> wrote: >> >>> Hi Lin, >>> >>> It has been a while since we talked about that, and I am not sure from >>> looking at the method whether Pt is supposed to be the input or output. If >>> the input, then it should be named something like coord instead of Pt. If >>> the output, then you are correct, it should be a "double*" and the >>> documentation should spell out how much memory it must point to. (Since in >>> general the n-th derivative is a symmetric tensor of rank n, there are >>> (n+1)(n+2)...(n+k-1)/(k-1) partial derivatives. This is related to Pascal's >>> simplex. See >>> https://en.wikipedia.org/wiki/Pascal%27s_pyramid#Parallels_to_Pascal.27s_triangle_and_Multinomial_Coefficients >>> and >>> https://en.wikipedia.org/wiki/Differential_of_a_function#Higher-order_differentials >>> .) >>> >>> It is fine to have different methods for curves, surfaces, and volumes >>> for now. As you can see in the links above, the general pattern is that the >>> n-th total derivative is a tensor of all possible combinations of partial >>> derivatives with respect to the 1, 2, or 3 parametric coordinates. Call the >>> parametric coordinates r_i for i in {1, 2, 3} and say we are taking the >>> n-th derivative of f. Then Python code to compute one possible ordering of >>> the partial differentials in the output array would be >>> >>> def pdiff(i,n): >>> r=[] >>> if i == 1: >>> return [[n,],] >>> for x in range(n+1): >>> for y in pdiff(i-1,n-x): >>> r.append(y+[x,]) >>> return r >>> >>> which returns a list of i-tuples that all sum to n. For example >>> >>> pdiff(2,1) returns [[1, 0], [0, 1]] >>> pdiff(2,2) returns [[2, 0], [1, 1], [0, 2]] >>> >>> pdiff(3,1) returns [[1, 0, 0], [0, 1, 0], [0, 0, 1]] >>> pdiff(3,2) returns [[2, 0, 0], [1, 1, 0], [0, 2, 0], [1, 0, 1], [0, 1, >>> 1], [0, 0, 2]] >>> >>> However, really only the first (Jacobian, a vector) and second (Hessian, >>> a symmetric 3x3 matrix with 6 unique entries) derivatives are used very >>> much because (a) the number of terms grows very fast with increasing >>> derivative and (b) the first 2 derivatives are used widely for root-finding >>> and curvature computation but further derivatives are not. >>> >>> David >>> >>> On Aug 17, 2015, at 22:40, Lin M wrote: >>> >>> Hi Dr. Thompson, >>> >>> I found you left an interface for >>> vtkBezierPatchAdaptro::EvaluateDeriv(double Pt[3], double* Paras, int d). >>> For 1-d curve, the derivative is always a 3*1 vector, but with the >>> parametric dimension increasing, higher order derivatives will contain >>> many points (it becomes matrix-by-vector differential). I can't figure out >>> a generalized way to interpret this. That's why I declared functions to >>> compute derivative for curve, surface and volume separately. Do you have >>> any suggestions for that? Thanks! >>> >>> Best, >>> Lin >>> >>> On Tue, Aug 18, 2015 at 1:04 AM, David Thompson < >>> david.thompson at kitware.com> wrote: >>> >>>> Hi Lin, >>>> >>>> > I have some questions about the test. >>>> > 1. About simplicial interpolation. Should I test some simple cases >>>> (hard coded simple shape) or some shapes like the motorcycle? >>>> >>>> Those are 2 different types of tests. (There are many; see >>>> http://stackoverflow.com/questions/437897/what-are-unit-testing-and-integration-testing-and-what-other-types-of-testing-s >>>> for some lists of test types). The first test (simple hard-coded shape) is >>>> a unit test and the second (test of both the reader, spline-to-patch class, >>>> and patch interpolation) is an integration test. >>>> >>>> Both are important, but since you already have an integration test for >>>> the motorcycle, I think a good set of unit tests for simplicial >>>> interpolation would be enough. >>>> >>>> > If it is the latter one, how to convert the rectangular patch to >>>> simpicial patch? >>>> > >>>> > 2. About point inversion. How to test it for the simpicial patch? I >>>> only implemented the point inversion for NURBS patch. >>>> >>>> If you didn't implement it, you can't test it. :-) However, if you know >>>> what you want the test to look like, you can write the test before you >>>> implement inversion and just leave it commented out with a note. Many >>>> people think this is how development should be done in the first place, >>>> since it forces you to consider how people will use what you write. >>>> >>>> > 3. About derivative computation. Should I just test them numerically? >>>> For example, given a shape and a parametric coordinate, test the result of >>>> our implementation with ground truth. >>>> >>>> Again, since you are using the derivatives in code that is part of an >>>> integration, I think unit testing (as you suggest) is enough. >>>> >>>> David >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Fri Aug 21 10:43:59 2015 From: david.thompson at kitware.com (David Thompson) Date: Fri, 21 Aug 2015 10:43:59 -0400 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> <96774517-8F9D-49FE-96B3-3E9AEC33742F@kitware.com> Message-ID: <6CD1A3EA-6009-46C5-A1D2-352CFAC1A0B5@kitware.com> Hi Lin, > I have merged the branch to spline/VTK. How can I make the Cdash test work then? One thing you can do is create an account on midas3.kitware.com and upload the baseline images to your account there. Make sure you make the images public so that the dashboards can get to them. (VTK's ExternalData module fetches baselines from midas3 by searching for public files with a matching MD5 checksum.) The other way is to follow the instructions: https://gitlab.kitware.com/vtk/vtk/blob/master/Documentation/dev/git/develop.md https://gitlab.kitware.com/vtk/vtk/blob/master/Documentation/dev/git/data.md to create a merge request to the main VTK repo. You should probably rebase the spline/VTK changes to VTK's master branch before submitting that merge request. David > > On Fri, Aug 21, 2015 at 12:58 PM, Lin M wrote: > Hi Dr. Thompson, > > I have finished supplementary documentation for the vtkFiltersBezier module. I think it's ready to be tested now. > > On Thu, Aug 20, 2015 at 11:56 PM, Lin M wrote: > Hi Dr. Thompson, > > I have added image based tests for almost all vtkFiltersBezier related class including BREP file reader, patch(simplicial) interpolation and point projection for both curve and surface example. > > I will complete required documents soon. > > Best, > Lin > > On Tue, Aug 18, 2015 at 8:23 PM, David Thompson wrote: > Hi Lin, > > It has been a while since we talked about that, and I am not sure from looking at the method whether Pt is supposed to be the input or output. If the input, then it should be named something like coord instead of Pt. If the output, then you are correct, it should be a "double*" and the documentation should spell out how much memory it must point to. (Since in general the n-th derivative is a symmetric tensor of rank n, there are (n+1)(n+2)...(n+k-1)/(k-1) partial derivatives. This is related to Pascal's simplex. See https://en.wikipedia.org/wiki/Pascal%27s_pyramid#Parallels_to_Pascal.27s_triangle_and_Multinomial_Coefficients and https://en.wikipedia.org/wiki/Differential_of_a_function#Higher-order_differentials .) > > It is fine to have different methods for curves, surfaces, and volumes for now. As you can see in the links above, the general pattern is that the n-th total derivative is a tensor of all possible combinations of partial derivatives with respect to the 1, 2, or 3 parametric coordinates. Call the parametric coordinates r_i for i in {1, 2, 3} and say we are taking the n-th derivative of f. Then Python code to compute one possible ordering of the partial differentials in the output array would be > > def pdiff(i,n): > r=[] > if i == 1: > return [[n,],] > for x in range(n+1): > for y in pdiff(i-1,n-x): > r.append(y+[x,]) > return r > > which returns a list of i-tuples that all sum to n. For example > > pdiff(2,1) returns [[1, 0], [0, 1]] > pdiff(2,2) returns [[2, 0], [1, 1], [0, 2]] > > pdiff(3,1) returns [[1, 0, 0], [0, 1, 0], [0, 0, 1]] > pdiff(3,2) returns [[2, 0, 0], [1, 1, 0], [0, 2, 0], [1, 0, 1], [0, 1, 1], [0, 0, 2]] > > However, really only the first (Jacobian, a vector) and second (Hessian, a symmetric 3x3 matrix with 6 unique entries) derivatives are used very much because (a) the number of terms grows very fast with increasing derivative and (b) the first 2 derivatives are used widely for root-finding and curvature computation but further derivatives are not. > > David > > On Aug 17, 2015, at 22:40, Lin M wrote: > >> Hi Dr. Thompson, >> >> I found you left an interface for vtkBezierPatchAdaptro::EvaluateDeriv(double Pt[3], double* Paras, int d). >> For 1-d curve, the derivative is always a 3*1 vector, but with the parametric dimension increasing, higher order derivatives will contain many points (it becomes matrix-by-vector differential). I can't figure out a generalized way to interpret this. That's why I declared functions to compute derivative for curve, surface and volume separately. Do you have any suggestions for that? Thanks! >> >> Best, >> Lin >> >> On Tue, Aug 18, 2015 at 1:04 AM, David Thompson wrote: >> Hi Lin, >> >> > I have some questions about the test. >> > 1. About simplicial interpolation. Should I test some simple cases (hard coded simple shape) or some shapes like the motorcycle? >> >> Those are 2 different types of tests. (There are many; see http://stackoverflow.com/questions/437897/what-are-unit-testing-and-integration-testing-and-what-other-types-of-testing-s for some lists of test types). The first test (simple hard-coded shape) is a unit test and the second (test of both the reader, spline-to-patch class, and patch interpolation) is an integration test. >> >> Both are important, but since you already have an integration test for the motorcycle, I think a good set of unit tests for simplicial interpolation would be enough. >> >> > If it is the latter one, how to convert the rectangular patch to simpicial patch? >> > >> > 2. About point inversion. How to test it for the simpicial patch? I only implemented the point inversion for NURBS patch. >> >> If you didn't implement it, you can't test it. :-) However, if you know what you want the test to look like, you can write the test before you implement inversion and just leave it commented out with a note. Many people think this is how development should be done in the first place, since it forces you to consider how people will use what you write. >> >> > 3. About derivative computation. Should I just test them numerically? For example, given a shape and a parametric coordinate, test the result of our implementation with ground truth. >> >> Again, since you are using the derivatives in code that is part of an integration, I think unit testing (as you suggest) is enough. >> >> David >> > > > From david.gobbi at gmail.com Sun Aug 23 20:59:18 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Sun, 23 Aug 2015 18:59:18 -0600 Subject: [vtk-developers] Python 3 and unicode Message-ID: Hi All, I'd like to briefly describe the way that the Python 3 wrapping currently handles unicode, before soliciting advice on how things could be improved. First, note that there are two ways you can provide a string to the wrappers: as a unicode str() object, or as an 8-bit bytes() object. These are illustrated in the following example: a = vtkStringArray() a.InsertNextValue("?") a.InsertNextValue("?".encode('latin1')) In the first case, the wrappers silently convert the python unicode str() to a C++ utf-8 string, which is stored in the array. In the second case, a unicode object is explicitly converted into a latin1-encoded bytes() object, which is stored as a C++ string. When you try to get the strings out of the array, python has no way of knowing what encoding was used. Right now, it assumes utf-8: a.GetValue(0) => '?' a.GetValue(1) => UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe7 in position 0: unexpected end of data This isn't a good situation. If the string isn't stored as utf-8 (or ascii), then retrieving it is impossible. I have an easy fix that provides a 95% solution, but I'd like advice before implementing it. Here's the fix: The wrappers will always try to decode VTK 8-bit strings as utf-8 and return a Python 3 str() object. But if that fails, then rather than raising an exception, the wrappers will keep the string in its original encoding and return it as a bytes() object. Going back to the example: a.GetValue(0) => '?' a.GetValue(1) => b'\xe7' b'\xe7'.decode('latin1') => '?' In other words, if you use something other than ascii or utf-8, then it's your responsibility to do the encoding and decoding. Or, you can leave the value as an 8-bit bytes() object and simply pass it along (for example if you are getting a string from an array, and then setting it as the filename for a reader). I think this is a good solution, but here is why it's only a 95% solution. In the above scenario, the wrappers will always attempt to decode 8-bit strings as utf-8, and only if that fails will they return a raw bytes() object. So the wrappers might return a unicode str() for something that was not stored as utf-8! In this case, you would have to: a) check to see if the value is a str() or a bytes() object b) if it is a bytes object, decode as e.g. latin1 c) if it is a str object, encode as utf-8 and then decode as e.g. latin1 Because I'm a utf-8 chauvinist, my main concern is that people who use utf-8 don't have to do anything special. It bothers me a bit that people who use other encodings need to jump through these hoops, but I can live with that. Any opinions, advice, or requests for clarification? - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From will.schroeder at kitware.com Mon Aug 24 08:27:17 2015 From: will.schroeder at kitware.com (Will Schroeder) Date: Mon, 24 Aug 2015 08:27:17 -0400 Subject: [vtk-developers] Python 3 and unicode In-Reply-To: References: Message-ID: This seems reasonable to me On Sun, Aug 23, 2015 at 8:59 PM, David Gobbi wrote: > Hi All, > > I'd like to briefly describe the way that the Python 3 wrapping currently > handles unicode, before soliciting advice on how things could be improved. > > First, note that there are two ways you can provide a string to the > wrappers: as a unicode str() object, or as an 8-bit bytes() object. These > are illustrated in the following example: > > a = vtkStringArray() > a.InsertNextValue("?") > a.InsertNextValue("?".encode('latin1')) > > In the first case, the wrappers silently convert the python unicode str() > to a C++ utf-8 string, which is stored in the array. In the second case, a > unicode object is explicitly converted into a latin1-encoded bytes() > object, which is stored as a C++ string. > > When you try to get the strings out of the array, python has no way of > knowing what encoding was used. Right now, it assumes utf-8: > > a.GetValue(0) > => '?' > a.GetValue(1) > => UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe7 in > position 0: unexpected end of data > > This isn't a good situation. If the string isn't stored as utf-8 (or > ascii), then retrieving it is impossible. I have an easy fix that provides > a 95% solution, but I'd like advice before implementing it. Here's the fix: > > The wrappers will always try to decode VTK 8-bit strings as utf-8 and > return a Python 3 str() object. But if that fails, then rather than > raising an exception, the wrappers will keep the string in its original > encoding and return it as a bytes() object. Going back to the example: > > a.GetValue(0) > => '?' > a.GetValue(1) > => b'\xe7' > b'\xe7'.decode('latin1') > => '?' > > In other words, if you use something other than ascii or utf-8, then it's > your responsibility to do the encoding and decoding. Or, you can leave the > value as an 8-bit bytes() object and simply pass it along (for example if > you are getting a string from an array, and then setting it as the filename > for a reader). > > I think this is a good solution, but here is why it's only a 95% > solution. In the above scenario, the wrappers will always attempt to > decode 8-bit strings as utf-8, and only if that fails will they return a > raw bytes() object. So the wrappers might return a unicode str() for > something that was not stored as utf-8! In this case, you would have to: > > a) check to see if the value is a str() or a bytes() object > b) if it is a bytes object, decode as e.g. latin1 > c) if it is a str object, encode as utf-8 and then decode as e.g. latin1 > > Because I'm a utf-8 chauvinist, my main concern is that people who use > utf-8 don't have to do anything special. It bothers me a bit that people > who use other encodings need to jump through these hoops, but I can live > with that. > > Any opinions, advice, or requests for clarification? > > - David > > > > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -- William J. Schroeder, PhD Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at rogue-research.com Mon Aug 24 08:53:30 2015 From: sean at rogue-research.com (Sean McBride) Date: Mon, 24 Aug 2015 08:53:30 -0400 Subject: [vtk-developers] Python 3 and unicode In-Reply-To: References: Message-ID: <20150824125330.1612993343@mail.rogue-research.com> On Sun, 23 Aug 2015 18:59:18 -0600, David Gobbi said: >Because I'm a utf-8 chauvinist, my main concern is that people who use >utf-8 don't have to do anything special. It bothers me a bit that people >who use other encodings need to jump through these hoops, but I can live >with that. > >Any opinions, advice, or requests for clarification? I guess I'm more of a "utf-8 chauvinist" than you are, because I don't even see what the problem is. :) Why add any of the complication? Just require people to use UTF-8. No other 8 bit encoding should be used in this day and age. And there is no VTK+Py3 legacy to support, so let's not add a kludge now. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng sean at rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montr?al, Qu?bec, Canada From david.gobbi at gmail.com Mon Aug 24 10:48:54 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 24 Aug 2015 08:48:54 -0600 Subject: [vtk-developers] Python 3 and unicode In-Reply-To: <20150824125330.1612993343@mail.rogue-research.com> References: <20150824125330.1612993343@mail.rogue-research.com> Message-ID: On Mon, Aug 24, 2015 at 6:53 AM, Sean McBride wrote: > > Why add any of the complication? Just require people to use UTF-8. On Windows, kwsys and most IO classes still do filesystem operations using the local 8-bit encoding. Which is silly, I know, considering that Windows provided unicode APIs 22 years ago. But I don't see anyone volunteering to fix this, which means that, right now, some people will have to use encodings other than utf-8 for their filenames. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Aug 24 10:56:06 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 24 Aug 2015 10:56:06 -0400 Subject: [vtk-developers] Python 3 and unicode In-Reply-To: <20150824125330.1612993343@mail.rogue-research.com> References: <20150824125330.1612993343@mail.rogue-research.com> Message-ID: <20150824145606.GB22341@megas.kitware.com> On Mon, Aug 24, 2015 at 08:53:30 -0400, Sean McBride wrote: > On Sun, 23 Aug 2015 18:59:18 -0600, David Gobbi said: > >Because I'm a utf-8 chauvinist, my main concern is that people who use > >utf-8 don't have to do anything special. It bothers me a bit that people > >who use other encodings need to jump through these hoops, but I can live > >with that. > > > >Any opinions, advice, or requests for clarification? > > I guess I'm more of a "utf-8 chauvinist" than you are, because I don't > even see what the problem is. :) > > Why add any of the complication? Just require people to use UTF-8. > No other 8 bit encoding should be used in this day and age. And there > is no VTK+Py3 legacy to support, so let's not add a kludge now. Agreed. Anyone using these *nix-originated languages (basically read as: not the JVM, the CLR, or JavaScript) has to deal with utf-8 anyways, so just assume it since there's little reason to prefer another encoding over it. This does bring the question of what we do for handling the JVM's utf-16 internal encodings for the Java wrappers. Do they also assume utf-8 at the boundaries? I have no idea about Tcl. We should probably add some utf-8-oriented tests while we're solving this so that we don't break it in the future :) . --Ben From ben.boeckel at kitware.com Mon Aug 24 11:10:39 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 24 Aug 2015 11:10:39 -0400 Subject: [vtk-developers] Python 3 and unicode In-Reply-To: References: <20150824125330.1612993343@mail.rogue-research.com> Message-ID: <20150824151039.GC22341@megas.kitware.com> On Mon, Aug 24, 2015 at 08:48:54 -0600, David Gobbi wrote: > On Windows, kwsys and most IO classes still do filesystem operations using > the local 8-bit encoding. Which is silly, I know, considering that Windows > provided unicode APIs 22 years ago. But I don't see anyone volunteering to > fix this, which means that, right now, some people will have to use > encodings other than utf-8 for their filenames. FWIW, POSIX filenames are arbitrary bytestrings, so it's not *technically* different there either. And there's no indication or place to query what encoding should be used either since it's more a property of the one who wrote the file than the one who is reading it (so LANG might not help). In any case, won't just handing over raw bytes for invalid utf-8 sequences be fine at that point (if we tried to normalize, I could see a problem though)? --Ben From david.gobbi at gmail.com Mon Aug 24 11:42:36 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 24 Aug 2015 09:42:36 -0600 Subject: [vtk-developers] Python 3 and unicode In-Reply-To: <20150824151039.GC22341@megas.kitware.com> References: <20150824125330.1612993343@mail.rogue-research.com> <20150824151039.GC22341@megas.kitware.com> Message-ID: On Mon, Aug 24, 2015 at 9:10 AM, Ben Boeckel wrote: > On Mon, Aug 24, 2015 at 08:48:54 -0600, David Gobbi wrote: > > On Windows, kwsys and most IO classes still do filesystem operations > using > > the local 8-bit encoding. Which is silly, I know, considering that > Windows > > provided unicode APIs 22 years ago. But I don't see anyone volunteering > to > > fix this, which means that, right now, some people will have to use > > encodings other than utf-8 for their filenames. > > FWIW, POSIX filenames are arbitrary bytestrings, so it's not > *technically* different there either. And there's no indication or place > to query what encoding should be used either since it's more a property > of the one who wrote the file than the one who is reading it (so LANG > might not help). > It's quite different. At the file-system level, Windows always uses UTF-16. So on Windows, if you always use the unicode (wide char) APIs, then as a developer you are always safe. The user can't screw you up by switching the code page. > In any case, won't just handing over raw bytes for invalid utf-8 > sequences be fine at that point (if we tried to normalize, I could see a > problem though)? That's my gut feeling. And we won't normalize (in the wrappers) because that would screw things up. Thankfully, the python encoders/decoders don't normalize, either, so round-trip conversions between utf-8 and unicode works. Normalization can definitely be an issue with filenames, however, because 1) OS X uses NFD, 2) Windows prefers NFC, 3) POSIX doesn't care. I was quite surprised the first time I did a non-ascii directory listing in OS X, and the accented characters were decomposed. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Mon Aug 24 13:44:10 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 24 Aug 2015 13:44:10 -0400 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: References: Message-ID: <20150824174410.GA2872@megas.kitware.com> On Tue, Aug 04, 2015 at 08:52:49 -0600, David Gobbi wrote: > This should allow VTK to compile with python 3 on the major platforms. > Basic stuff seems to work. > https://gitlab.kitware.com/vtk/vtk/merge_requests/478 Now that master has had green builds, the Python3 dashboards are now marked as 'expected'. Branches which are older than the latest master may see them turn red since they are missing requisite support. In addition, nemesis' MSVC 2015 builder is marked as 'expected'. --Ben From david.gobbi at gmail.com Mon Aug 24 13:54:11 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 24 Aug 2015 11:54:11 -0600 Subject: [vtk-developers] VTK-py3k is ready for testing In-Reply-To: <20150824174410.GA2872@megas.kitware.com> References: <20150824174410.GA2872@megas.kitware.com> Message-ID: On Mon, Aug 24, 2015 at 11:44 AM, Ben Boeckel wrote: > On Tue, Aug 04, 2015 at 08:52:49 -0600, David Gobbi wrote: > > This should allow VTK to compile with python 3 on the major platforms. > > Basic stuff seems to work. > > https://gitlab.kitware.com/vtk/vtk/merge_requests/478 > > Now that master has had green builds, the Python3 dashboards are now > marked as 'expected'. Branches which are older than the latest master > may see them turn red since they are missing requisite support. Nice. Thanks. - David -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.amaclean at gmail.com Mon Aug 24 20:12:29 2015 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Tue, 25 Aug 2015 10:12:29 +1000 Subject: [vtk-developers] How to build VTK with Python3. Message-ID: For those who want to build VTK with Python 3 here are some instructions and scripts that I have written for both Windows and Linux. Please feel free to edit as appropriate and feed back any improvements to the list. It was a bit wordy so the instructions are in the file called "How to build VTK with Python 3.md" Edit the scripts changing paths to suit your particular environment, also for DevelopmenrEnvPy3k change the extension to cmd. Regards Andrew -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: How to build VTK with Python 3.md Type: application/octet-stream Size: 2863 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DevelopmentEnvPy3k.change_ext_to_cmd Type: application/octet-stream Size: 2451 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: py3k_dev_env.sh Type: application/x-sh Size: 1402 bytes Desc: not available URL: From sharadmaheshwari19 at gmail.com Tue Aug 25 09:20:56 2015 From: sharadmaheshwari19 at gmail.com (Sharad Maheshwari) Date: Tue, 25 Aug 2015 18:50:56 +0530 Subject: [vtk-developers] Getting started with open Source Contribution for VTK Message-ID: Hello, This is Sharad Maheshwari from India.I am interested in open source contributing for VTK.I am currently interning in a Graphics company and working in C++ for the tools development of GPUs I'd really like to start in the open source paradigm and thus would be grateful if you could provide me with the starting points about the projects here,how do I start contributing in these,or any of such sorts.. Thank you Regards, Sharad Maheshwari -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Aug 25 10:30:15 2015 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 25 Aug 2015 10:30:15 -0400 Subject: [vtk-developers] Getting started with open Source Contribution for VTK In-Reply-To: References: Message-ID: Hi Sharad, The general model is that: * contributions from everyone are invited * people work on whatever aspects are needful for their own work * use this mailing list to discuss things for advice and to reach consensus on large changes * we have a software process (http://www.vtk.org/contributing-code/) in place to maintain code quality There are lots of things going on as usual, see the this blog post ( http://www.kitware.com/blog/home/post/728), the release notes (under http://www.vtk.org/Wiki/VTK/Roadmap) and commit log to see what people have been working on. Welcome to VTK! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Aug 25, 2015 at 9:20 AM, Sharad Maheshwari < sharadmaheshwari19 at gmail.com> wrote: > Hello, > This is Sharad Maheshwari from India.I am interested in open source > contributing for VTK.I am currently interning in a Graphics company and > working in C++ for the tools development of GPUs > I'd really like to start in the open source paradigm and thus would be > grateful if you could provide me with the starting points about the > projects here,how do I start contributing in these,or any of such sorts.. > > Thank you > > Regards, > Sharad Maheshwari > > _______________________________________________ > 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=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Tue Aug 25 10:44:55 2015 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 25 Aug 2015 10:44:55 -0400 Subject: [vtk-developers] Potential Change to Viewport Coordinates Message-ID: <2268d04aae700353578960f15421ecaa@mail.gmail.com> So there is an odd issue with normalized viewport coordinates that has been around for a long time. If you draw a rectangle from 0.0 to 1.0 I would expect it to completely cover the viewport. But currently it is logically missing a half pixel on the left and right/top and bottom. See the picture below of what is happening given a small four pixel window. I seem to recall we originally wanted pixels to be based on their centers and then later as we added more coordinate systems realized we had an issue but left it as it was. The idea here would be to make viewport coordinates(and normalized VPC) behave like display coordinates with a left corner origin. The only difference between them and display coordinates would be that they are relative to their viewport. This change would require about 15 updated valid images as some labels move a tad here and there. Thoughts? Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 ken.martin at kitware.com 919 869-8871 (w) This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 17921 bytes Desc: not available URL: From david.gobbi at gmail.com Tue Aug 25 13:09:40 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Tue, 25 Aug 2015 11:09:40 -0600 Subject: [vtk-developers] Potential Change to Viewport Coordinates In-Reply-To: <2268d04aae700353578960f15421ecaa@mail.gmail.com> References: <2268d04aae700353578960f15421ecaa@mail.gmail.com> Message-ID: Hi Ken, This change looks good. OpenGL defines the viewport as going from (0, 0, winWidth, winHeight) in display coords, and the definition of Normalized Viewport Coordinates should follow naturally from that. Also, using pixel centers doesn't work well if you want your displays to be resolution-independent. Consider retina displays, for example: they take the original pixel, and divide it into four. This causes the centers of the pixels at the outer corners of the viewport to shift. But if everything is computed relative to the outside corners of those corner pixels, then dealing with different resolutions is no big deal. I'm guessing that this change should have no impact on most users, because users generally stick to WorldCoords and DisplayCoords. - David On Tue, Aug 25, 2015 at 8:44 AM, Ken Martin wrote: > So there is an odd issue with normalized viewport coordinates that has > been around for a long time. If you draw a rectangle from 0.0 to 1.0 I > would expect it to completely cover the viewport. But currently it is > logically missing a half pixel on the left and right/top and bottom. See > the picture below of what is happening given a small four pixel window. I > seem to recall we originally wanted pixels to be based on their centers and > then later as we added more coordinate systems realized we had an issue but > left it as it was. The idea here would be to make viewport coordinates(and > normalized VPC) behave like display coordinates with a left corner origin. > The only difference between them and display coordinates would be that they > are relative to their viewport. This change would require about 15 updated > valid images as some labels move a tad here and there. Thoughts? > > > > > > > > Ken Martin PhD > > Chairman & CFO > > Kitware Inc. > > 28 Corporate Drive > > Clifton Park NY 12065 > > ken.martin at kitware.com > > 919 869-8871 (w) > > > > > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 17921 bytes Desc: not available URL: From david.lonie at kitware.com Wed Aug 26 15:02:30 2015 From: david.lonie at kitware.com (David Lonie) Date: Wed, 26 Aug 2015 15:02:30 -0400 Subject: [vtk-developers] vtkInteratorStyle python subclass instantiation: TypeError: method requires a string argument Message-ID: I'm updating some code for a client to use current VTK master, and there's an error while instantiating a python class that derives from vtkInteractorStyle. It seems to be related to __init__ taking an extra parameter which is used by the subclass to initialize some internals. A minimal example that reproduces the error: test.py: import vtk class MyInteractorStyle(vtk.vtkInteractorStyleUser): def __init__(self, arg): pass obj = MyInteractorStyle(2) $ vtkpython test.py Traceback (most recent call last): File "/tmp/test.py", line 7, in obj = MyInteractorStyle(2) TypeError: method requires a string argument Removing the extra argument from __init__ will make the error go away. This worked a few months ago last time we bumped their VTK version. Is this a bug? Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.lonie at kitware.com Thu Aug 27 09:56:24 2015 From: david.lonie at kitware.com (David Lonie) Date: Thu, 27 Aug 2015 09:56:24 -0400 Subject: [vtk-developers] vtkInteratorStyle python subclass instantiation: TypeError: method requires a string argument In-Reply-To: References: Message-ID: On Wed, Aug 26, 2015 at 3:02 PM, David Lonie wrote: > I'm updating some code for a client to use current VTK master, and there's > an error while instantiating a python class that derives from > vtkInteractorStyle. It seems to be related to __init__ taking an extra > parameter which is used by the subclass to initialize some internals. > > A minimal example that reproduces the error: > > test.py: > import vtk > > class MyInteractorStyle(vtk.vtkInteractorStyleUser): > def __init__(self, arg): > pass > > obj = MyInteractorStyle(2) > > $ vtkpython test.py > Traceback (most recent call last): > File "/tmp/test.py", line 7, in > obj = MyInteractorStyle(2) > TypeError: method requires a string argument > > Removing the extra argument from __init__ will make the error go away. > > This worked a few months ago last time we bumped their VTK version. Is > this a bug? > It looks like the issue is in PyVTKObject_New, which treats all __init__ arguments as SWIG pointers for object initialization. I'm not familiar with the usecase for that, is there some additional check we can perform to pass over regular arguments? Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Thu Aug 27 10:09:52 2015 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 27 Aug 2015 08:09:52 -0600 Subject: [vtk-developers] vtkInteratorStyle python subclass instantiation: TypeError: method requires a string argument In-Reply-To: References: Message-ID: Hi David, Yes, it seems to be a bug related to the py3k modifications. I believe that the swig-pointer initializer is still used in some places (it allows a person to create a python-wrapped VTK object, if all they have is a pointer to the object). I'm going away for a few days but I'll take a look when I get back. - David On Thu, Aug 27, 2015 at 7:56 AM, David Lonie wrote: > On Wed, Aug 26, 2015 at 3:02 PM, David Lonie > wrote: > >> I'm updating some code for a client to use current VTK master, and >> there's an error while instantiating a python class that derives from >> vtkInteractorStyle. It seems to be related to __init__ taking an extra >> parameter which is used by the subclass to initialize some internals. >> >> A minimal example that reproduces the error: >> >> test.py: >> import vtk >> >> class MyInteractorStyle(vtk.vtkInteractorStyleUser): >> def __init__(self, arg): >> pass >> >> obj = MyInteractorStyle(2) >> >> $ vtkpython test.py >> Traceback (most recent call last): >> File "/tmp/test.py", line 7, in >> obj = MyInteractorStyle(2) >> TypeError: method requires a string argument >> >> Removing the extra argument from __init__ will make the error go away. >> >> This worked a few months ago last time we bumped their VTK version. Is >> this a bug? >> > > It looks like the issue is in PyVTKObject_New, which treats all __init__ > arguments as SWIG pointers for object initialization. I'm not familiar with > the usecase for that, is there some additional check we can perform to pass > over regular arguments? > > Dave > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.lonie at kitware.com Thu Aug 27 10:12:00 2015 From: david.lonie at kitware.com (David Lonie) Date: Thu, 27 Aug 2015 10:12:00 -0400 Subject: [vtk-developers] vtkInteratorStyle python subclass instantiation: TypeError: method requires a string argument In-Reply-To: References: Message-ID: Thanks David. It looks like I can easily refactor the argument out in this case, so I'll just do that in the meantime. On Thu, Aug 27, 2015 at 10:09 AM, David Gobbi wrote: > Hi David, > > Yes, it seems to be a bug related to the py3k modifications. I believe > that the swig-pointer initializer is still used in some places (it allows a > person to create a python-wrapped VTK object, if all they have is a pointer > to the object). > > I'm going away for a few days but I'll take a look when I get back. > > - David > > > On Thu, Aug 27, 2015 at 7:56 AM, David Lonie > wrote: > >> On Wed, Aug 26, 2015 at 3:02 PM, David Lonie >> wrote: >> >>> I'm updating some code for a client to use current VTK master, and >>> there's an error while instantiating a python class that derives from >>> vtkInteractorStyle. It seems to be related to __init__ taking an extra >>> parameter which is used by the subclass to initialize some internals. >>> >>> A minimal example that reproduces the error: >>> >>> test.py: >>> import vtk >>> >>> class MyInteractorStyle(vtk.vtkInteractorStyleUser): >>> def __init__(self, arg): >>> pass >>> >>> obj = MyInteractorStyle(2) >>> >>> $ vtkpython test.py >>> Traceback (most recent call last): >>> File "/tmp/test.py", line 7, in >>> obj = MyInteractorStyle(2) >>> TypeError: method requires a string argument >>> >>> Removing the extra argument from __init__ will make the error go away. >>> >>> This worked a few months ago last time we bumped their VTK version. Is >>> this a bug? >>> >> >> It looks like the issue is in PyVTKObject_New, which treats all __init__ >> arguments as SWIG pointers for object initialization. I'm not familiar with >> the usecase for that, is there some additional check we can perform to pass >> over regular arguments? >> >> Dave >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Thu Aug 27 12:40:04 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 27 Aug 2015 12:40:04 -0400 Subject: [vtk-developers] VTK and ParaView for HPCWire awards! Message-ID: VTK and ParaView have witnessed significant growth thanks to all of the members of the community. To recognize VTK and ParaView?s development, please nominate them for 2015 HPCwire Readers? and Editors? Choice Awards. Please nominate VTK and ParaView for ?Best HPC Visualization Product or Technology.? Nominations can be made at http://www.hpcwire.com/2015-hpcwire-readers-choice-awards/. Thank you for your support! -berk -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Fri Aug 28 10:36:55 2015 From: berk.geveci at kitware.com (Berk Geveci) Date: Fri, 28 Aug 2015 10:36:55 -0400 Subject: [vtk-developers] Removed Examples/SMP Message-ID: Hi folks, Just a quick to mention that we removed the Examples/SMP directory. This contained some half-baked examples that no longer represents well the direction the SMP work is going. The best examples are in Filters/SMP. These will also disappear in time as we integrate the SMP functionality more directly into core algorithms. Best, -berk -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Fri Aug 28 10:41:05 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Fri, 28 Aug 2015 10:41:05 -0400 Subject: [vtk-developers] New volume rendering feature Message-ID: Folks, We have a branch (https://gitlab.kitware.com/vtk/vtk/merge_requests/601) that enables uses to export Depth and Color texture from volume mapper. This is something useful if you are doing deferred rendering of some sort of remote rendering. Along with this, we have pushed some other bug fixes and few new features which we will report in a blog soon. Please let us know if you have any questions. Thanks -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Fri Aug 28 15:41:25 2015 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Fri, 28 Aug 2015 15:41:25 -0400 Subject: [vtk-developers] New volume rendering feature In-Reply-To: References: Message-ID: In addition to this work, there have been some exciting progress in the OpenGL2 GPU volume mapper. While we work on a blog demonstrating the new features, here is the high-level bulletin: - Support for multi-component datasets wherein each component can be represented independently or in a way such that all the component values are utilized to lookup the final color and opacity. - A major performance improvement (~300%) was achieved by optimizing the computation of the lighting model. - The new volume mapper now supports the OpenGL 3.2 core context and offloads most of the calculations including bias and scale computations to the GPU Please let us know if you have any questions or concerns. - Aashish On Fri, Aug 28, 2015 at 10:41 AM, Aashish Chaudhary < aashish.chaudhary at kitware.com> wrote: > Folks, > > We have a branch (https://gitlab.kitware.com/vtk/vtk/merge_requests/601) > that enables uses to export Depth and Color texture from volume mapper. > This is something useful if you are doing deferred rendering of some sort > of remote rendering. Along with this, we have pushed some other bug fixes > and few new features which we will report in a blog soon. > > Please let us know if you have any questions. > > Thanks > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. * > *| http://www.kitware.com/company/team/chaudhary.html > * > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Sat Aug 29 10:02:31 2015 From: ken.martin at kitware.com (Ken Martin) Date: Sat, 29 Aug 2015 10:02:31 -0400 Subject: [vtk-developers] A few dashboard issues Message-ID: <98b6c03aa6c019e8921cd68d12b1155a@mail.gmail.com> Please take a look in case any of these 3 ring a bell... /Users/builder/external/VTK/Filters/Extraction/vtkExtractArraysOverTime.cxx:1045:2: warning: no newline at end of file In file included from /home/kitware/dashboards/buildbot/vtk-megas-linux-shared-release_extdeps_openmp_python_qt_qt5/source/GUISupport/Qt/Q4VTKWidgetPlugin.h:36:0, from /home/kitware/dashboards/buildbot/vtk-megas-linux-shared-release_extdeps_openmp_python_qt_qt5/source/GUISupport/Qt/Q4VTKWidgetPlugin.cxx:37: /usr/include/qt5/QtDesigner/QDesignerCustomWidgetInterface:4:4: warning: #warning Header is deprecated. Please include instead. [-Wcpp] # warning Header is deprecated. Please include instead. cutPolygon test is failing a few places as of a couple days ago https://open.cdash.org/testDetails.php?test=367901134&build=3981240 Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 ken.martin at kitware.com 919 869-8871 (w) This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From EVENDUAN at outlook.com Sun Aug 30 02:33:16 2015 From: EVENDUAN at outlook.com (=?gb2312?B?ts671Lrq?=) Date: Sun, 30 Aug 2015 14:33:16 +0800 Subject: [vtk-developers] A problem of marchingcubes Message-ID: I want use the following code to extract the lung parenchyma from CT Sequence Datasets. But when I set the skinExtractor?s value under 300,it will be an debug error and can?t get the lung parenchyma I want . So what?s wrong with my code. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: MarchingCubes.cpp URL: From ben.boeckel at kitware.com Sun Aug 30 08:55:13 2015 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Sun, 30 Aug 2015 08:55:13 -0400 Subject: [vtk-developers] A few dashboard issues In-Reply-To: <98b6c03aa6c019e8921cd68d12b1155a@mail.gmail.com> References: <98b6c03aa6c019e8921cd68d12b1155a@mail.gmail.com> Message-ID: <20150830125512.GA2721@bronto-burt.dev.benboeckel.net> On Sat, Aug 29, 2015 at 10:02:31 -0400, Ken Martin wrote: > In file included from > /home/kitware/dashboards/buildbot/vtk-megas-linux-shared-release_extdeps_openmp_python_qt_qt5/source/GUISupport/Qt/Q4VTKWidgetPlugin.h:36:0, > > from > /home/kitware/dashboards/buildbot/vtk-megas-linux-shared-release_extdeps_openmp_python_qt_qt5/source/GUISupport/Qt/Q4VTKWidgetPlugin.cxx:37: > > /usr/include/qt5/QtDesigner/QDesignerCustomWidgetInterface:4:4: > warning: #warning Header > is deprecated. Please include > instead. [-Wcpp] > > # warning Header is > deprecated. Please include > instead. I think I already have a branch for this warning: https://gitlab.kitware.com/vtk/vtk/merge_requests/419 --Ben From bill.hoffman at kitware.com Mon Aug 31 17:10:32 2015 From: bill.hoffman at kitware.com (Bill Hoffman) Date: Mon, 31 Aug 2015 17:10:32 -0400 Subject: [vtk-developers] Happy Birthday CMake! Message-ID: <55E4C2C8.1040501@kitware.com> Today is the 15th birthday of CMake: http://www.kitware.com/blog/home/post/959 Thanks to everyone that has used and contributed to CMake over the years! -Bill From majcjc at gmail.com Sat Aug 15 09:51:55 2015 From: majcjc at gmail.com (Lin M) Date: Sat, 15 Aug 2015 13:51:55 -0000 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Message-ID: Hi Dr. Thompson, I have found some surfaces model in brep format from http://www.opencascade.org/showroom/shapegallery/gal5/ and I think the motorcycle is correct. The reason why it looks odd in the seat area is because those surfaces need some bool operation which we haven't implemented yet. I try to load the model of suitcase, boat and F1 and all of them displayed correctly, I suppose. :-) P.S. Best, Lin On Sat, Aug 15, 2015 at 2:45 PM, Lin M wrote: > Hi Dr. Thompson, > > I finally make the vtkBrepReader work (partially, it can only load surface > patches). The problem is that I can not find enough data source. None of > the files in CGM/test contains nurbs surface and the only one with Bezier > surface is moto.brep. It looks like this > As you can see, the seats area looks strange in the rendered shape. So I > really need some mroe simpler nurbs shape to test my implementation. Can > you give some advice where I should look for? Thanks! > > Best, > Lin > ? > > > On Wed, Aug 12, 2015 at 11:07 PM, wrote: > >> Thank you for your suggestions! >> >> I will polish the code and make them throughly tested before merged to >> VTK. >> >> Best, >> Lin >> >> >> >> On Wed, Aug 12, 2015 at 7:48 AM -0700, "David Thompson" < >> david.thompson at kitware.com> wrote: >> >> Hi Lin, >> >> > I have finished the point inversion and projection algorithm for both >> 1-d, 2-d and 3-d NURBS. >> > We can turn to more dedicated algorithms now. >> >> I think that a better use of the remaining time would be to clean up and >> merge your work into VTK. You have made great progress and it looks really >> good. It would be better to polish it so it is easy to maintain and get it >> accepted than to push for contouring and be left with something that is not >> tested well enough to be maintained as VTK changes. That way you or another >> GSoC student can continue things next summer. >> >> It has been my experience that the only way to ensure it is maintained is >> to make sure it is extensively tested so that when a change to VTK is >> proposed, the developer making the change gets immediate feedback that the >> change requires work on the spline classes. So, I propose doing the >> following: >> >> 1. There are some style changes that need to be made. I'll push some >> changes off your branch to sampling/vtk, but to get started: >> a. There is trailing whitespace at the ends of lines in many files >> which are disallowed by our pre-merge scripts. >> b. Method names should be spelled out, so "Curv," "Surf," and "Volm" >> should become "Curve," "Surface," and "Volume." I know it is nice for names >> to have the same length, but it is nicer for other developers to be able to >> predict the names of methods across the entire toolkit. :-) >> >> 2. Testing should be more exhaustive testing to make sure that changes to >> VTK don't break things. Right now only interpolation is tested at all (and >> there is a lot of commented-out code in that test which should probably be >> removed). Other tests should include, for example, >> a. simplicial (triangular and tetrahedral) patch interpolation (you can >> do this with an image-based test and/or by checking that numeric values are >> within a tolerance of an analytical solution, >> b. point inversion for rectangular and simplicial patches >> c. derivative computation >> d. the NURBS adaptor should be tested with several shapes whose patches >> can be computed >> >> 3. Every class should have documentation that covers its purpose, its >> intended lifecycle (how should it be used, what methods must be called >> before others, etc.). The way field data is used to hold NURBS knot vectors >> should be documented and should have an example data file (which should be >> used in an image test to verify that it continues to work). >> >> Thanks, >> David >> >> > On Sun, Aug 9, 2015 at 2:47 PM, Lin M wrote: >> > Hi Dr. Thompson, >> > >> > I have pushed new methods to compute point inversion and projection to >> gitlab. >> > It took longer time than I expected. It would be really helpful if you >> could review the code a little bit. Thanks! >> > >> > Best, >> > Lin >> > >> > On Mon, Aug 3, 2015 at 10:50 AM, David Thompson < >> david.thompson at kitware.com> wrote: >> > Hi Lin, >> > >> > Yes, that is correct. Inserting knot values does not change the >> polynomial degree or shape, it just adds control points so that the weights >> are uniform (as required by the B?zier basis). So, the underlying >> parameterization is unchanged... it just has more piecewise segments. >> > >> > David >> > >> > >> > >> > On Aug 2, 2015, at 22:38, Lin M wrote: >> > >> >> Hi Dr. Thompson, >> >> >> >> I have a question about the inversion and projection. Currently, we >> evaluate the NURBS by inserting knots and making it into Bezier forms. My >> question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], >> would it be the same to evaluate u = 0.2 in the new knot vector which is a >> bezier form? >> >> >> >> Best, >> >> Lin >> >> >> >> On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: >> >> Hi Dr. Thompson, >> >> >> >> I have added new method >> vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >> >> >> >> I'm now working on the point inversion part. >> >> >> >> Best, >> >> Lin >> >> >> >> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson < >> david.thompson at kitware.com> wrote: >> >> Hi Lin, >> >> >> >> How is triangular/tetrahedral patch interpolation going? They will be >> a basic building block of the contouring and cutting algorithms. By >> identifying points on edges, edges on surfaces, and surfaces in volumes >> that take on a single value, a single patch can be decomposed into sections >> that are inside, outside, or on an isosurface. Not all of these pieces can >> be expressed as brick patches, but they can be expressed as simplicial >> patches. >> >> >> >> David >> >> >> >> >> > >> > >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.PNG Type: image/png Size: 357636 bytes Desc: not available URL: From david.thompson at kitware.com Sat Aug 15 12:11:47 2015 From: david.thompson at kitware.com (David Thompson) Date: Sat, 15 Aug 2015 16:11:47 -0000 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Message-ID: Hi Lin, You are correct; most of the surfaces in those models that look strange just need to be trimmed by their neighbors. Trimming is an operation closely related to isocontouring (which would be the next step); it cuts a patch where the distance to another patch becomes 0. Isocontouring is more general in that the function specifying the location of the cut does not need to be the distance to another curve or surface. The motorcycle would make a good image-based test of both the interpolation and reader classes! David > On Aug 15, 2015, at 09:51, Lin M wrote: > > Hi Dr. Thompson, > > I have found some surfaces model in brep format from http://www.opencascade.org/showroom/shapegallery/gal5/ and I think the motorcycle is correct. The reason why it looks odd in the seat area is because those surfaces need some bool operation which we haven't implemented yet. > > I try to load the model of suitcase, boat and F1 and all of them displayed correctly, I suppose. :-) > > P.S. > > Best, > Lin > >> On Sat, Aug 15, 2015 at 2:45 PM, Lin M wrote: >> Hi Dr. Thompson, >> >> I finally make the vtkBrepReader work (partially, it can only load surface patches). The problem is that I can not find enough data source. None of the files in CGM/test contains nurbs surface and the only one with Bezier surface is moto.brep. It looks like this >> >> As you can see, the seats area looks strange in the rendered shape. So I really need some mroe simpler nurbs shape to test my implementation. Can you give some advice where I should look for? Thanks! >> >> Best, >> Lin >> ? >> >> >>> On Wed, Aug 12, 2015 at 11:07 PM, wrote: >>> Thank you for your suggestions! >>> >>> I will polish the code and make them throughly tested before merged to VTK. >>> >>> Best, >>> Lin >>> >>> >>> >>> On Wed, Aug 12, 2015 at 7:48 AM -0700, "David Thompson" wrote: >>> >>> Hi Lin, >>> >>> > I have finished the point inversion and projection algorithm for both 1-d, 2-d and 3-d NURBS. >>> > We can turn to more dedicated algorithms now. >>> >>> I think that a better use of the remaining time would be to clean up and merge your work into VTK. You have made great progress and it looks really good. It would be better to polish it so it is easy to maintain and get it accepted than to push for contouring and be left with something that is not tested well enough to be maintained as VTK changes. That way you or another GSoC student can continue things next summer. >>> >>> It has been my experience that the only way to ensure it is maintained is to make sure it is extensively tested so that when a change to VTK is proposed, the developer making the change gets immediate feedback that the change requires work on the spline classes. So, I propose doing the following: >>> >>> 1. There are some style changes that need to be made. I'll push some changes off your branch to sampling/vtk, but to get started: >>> a. There is trailing whitespace at the ends of lines in many files which are disallowed by our pre-merge scripts. >>> b. Method names should be spelled out, so "Curv," "Surf," and "Volm" should become "Curve," "Surface," and "Volume." I know it is nice for names to have the same length, but it is nicer for other developers to be able to predict the names of methods across the entire toolkit. :-) >>> >>> 2. Testing should be more exhaustive testing to make sure that changes to VTK don't break things. Right now only interpolation is tested at all (and there is a lot of commented-out code in that test which should probably be removed). Other tests should include, for example, >>> a. simplicial (triangular and tetrahedral) patch interpolation (you can do this with an image-based test and/or by checking that numeric values are within a tolerance of an analytical solution, >>> b. point inversion for rectangular and simplicial patches >>> c. derivative computation >>> d. the NURBS adaptor should be tested with several shapes whose patches can be computed >>> >>> 3. Every class should have documentation that covers its purpose, its intended lifecycle (how should it be used, what methods must be called before others, etc.). The way field data is used to hold NURBS knot vectors should be documented and should have an example data file (which should be used in an image test to verify that it continues to work). >>> >>> Thanks, >>> David >>> >>> > On Sun, Aug 9, 2015 at 2:47 PM, Lin M wrote: >>> > Hi Dr. Thompson, >>> > >>> > I have pushed new methods to compute point inversion and projection to gitlab. >>> > It took longer time than I expected. It would be really helpful if you could review the code a little bit. Thanks! >>> > >>> > Best, >>> > Lin >>> > >>> > On Mon, Aug 3, 2015 at 10:50 AM, David Thompson wrote: >>> > Hi Lin, >>> > >>> > Yes, that is correct. Inserting knot values does not change the polynomial degree or shape, it just adds control points so that the weights are uniform (as required by the B?zier basis). So, the underlying parameterization is unchanged... it just has more piecewise segments. >>> > >>> > David >>> > >>> > >>> > >>> > On Aug 2, 2015, at 22:38, Lin M wrote: >>> > >>> >> Hi Dr. Thompson, >>> >> >>> >> I have a question about the inversion and projection. Currently, we evaluate the NURBS by inserting knots and making it into Bezier forms. My question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], would it be the same to evaluate u = 0.2 in the new knot vector which is a bezier form? >>> >> >>> >> Best, >>> >> Lin >>> >> >>> >> On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: >>> >> Hi Dr. Thompson, >>> >> >>> >> I have added new method vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >>> >> >>> >> I'm now working on the point inversion part. >>> >> >>> >> Best, >>> >> Lin >>> >> >>> >> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson wrote: >>> >> Hi Lin, >>> >> >>> >> How is triangular/tetrahedral patch interpolation going? They will be a basic building block of the contouring and cutting algorithms. By identifying points on edges, edges on surfaces, and surfaces in volumes that take on a single value, a single patch can be decomposed into sections that are inside, outside, or on an isosurface. Not all of these pieces can be expressed as brick patches, but they can be expressed as simplicial patches. >>> >> >>> >> David >>> >> >>> >> >>> > >>> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.PNG Type: image/png Size: 357636 bytes Desc: not available URL: From majcjc at gmail.com Mon Aug 17 01:30:31 2015 From: majcjc at gmail.com (Lin M) Date: Mon, 17 Aug 2015 05:30:31 -0000 Subject: [vtk-developers] Triangular patch interpolation In-Reply-To: References: <2A7813C2-E2FD-42B2-A9B3-A7AF6B3D9E6B@kitware.com> <80E1624E-A9E6-4988-AB30-6139442A6580@kitware.com> <6FBE294D-9FC8-4563-BD61-EEA0F36A97D8@kitware.com> Message-ID: Hi Dr. Thompson, I have some questions about the test. 1. About simplicial interpolation. Should I test some simple cases (hard coded simple shape) or some shapes like the motorcycle? If it is the latter one, how to convert the rectangular patch to simpicial patch? 2. About point inversion. How to test it for the simpicial patch? I only implemented the point inversion for NURBS patch 3. About derivative computation. Should I just test them numerically? For example, given a shape and a parametric coordinate, test the result of our implementation with ground truth. Best, Lin On Sun, Aug 16, 2015 at 12:11 AM, David Thompson wrote: > Hi Lin, > > You are correct; most of the surfaces in those models that look strange > just need to be trimmed by their neighbors. Trimming is an operation > closely related to isocontouring (which would be the next step); it cuts a > patch where the distance to another patch becomes 0. Isocontouring is more > general in that the function specifying the location of the cut does not > need to be the distance to another curve or surface. > > The motorcycle would make a good image-based test of both the > interpolation and reader classes! > > David > > On Aug 15, 2015, at 09:51, Lin M wrote: > > Hi Dr. Thompson, > > I have found some surfaces model in brep format from > http://www.opencascade.org/showroom/shapegallery/gal5/ and I think the > motorcycle is correct. The reason why it looks odd in the seat area is > because those surfaces need some bool operation which we haven't > implemented yet. > > I try to load the model of suitcase, boat and F1 and all of them displayed > correctly, I suppose. :-) > > P.S. > > Best, > Lin > > On Sat, Aug 15, 2015 at 2:45 PM, Lin M wrote: > >> Hi Dr. Thompson, >> >> I finally make the vtkBrepReader work (partially, it can only load >> surface patches). The problem is that I can not find enough data source. >> None of the files in CGM/test contains nurbs surface and the only one with >> Bezier surface is moto.brep. It looks like this >> As you can see, the seats area looks strange in the rendered shape. So I >> really need some mroe simpler nurbs shape to test my implementation. Can >> you give some advice where I should look for? Thanks! >> >> Best, >> Lin >> ? >> >> >> On Wed, Aug 12, 2015 at 11:07 PM, wrote: >> >>> Thank you for your suggestions! >>> >>> I will polish the code and make them throughly tested before merged to >>> VTK. >>> >>> Best, >>> Lin >>> >>> >>> >>> On Wed, Aug 12, 2015 at 7:48 AM -0700, "David Thompson" < >>> david.thompson at kitware.com> wrote: >>> >>> Hi Lin, >>> >>> > I have finished the point inversion and projection algorithm for both >>> 1-d, 2-d and 3-d NURBS. >>> > We can turn to more dedicated algorithms now. >>> >>> I think that a better use of the remaining time would be to clean up and >>> merge your work into VTK. You have made great progress and it looks really >>> good. It would be better to polish it so it is easy to maintain and get it >>> accepted than to push for contouring and be left with something that is not >>> tested well enough to be maintained as VTK changes. That way you or another >>> GSoC student can continue things next summer. >>> >>> It has been my experience that the only way to ensure it is maintained >>> is to make sure it is extensively tested so that when a change to VTK is >>> proposed, the developer making the change gets immediate feedback that the >>> change requires work on the spline classes. So, I propose doing the >>> following: >>> >>> 1. There are some style changes that need to be made. I'll push some >>> changes off your branch to sampling/vtk, but to get started: >>> a. There is trailing whitespace at the ends of lines in many files >>> which are disallowed by our pre-merge scripts. >>> b. Method names should be spelled out, so "Curv," "Surf," and "Volm" >>> should become "Curve," "Surface," and "Volume." I know it is nice for names >>> to have the same length, but it is nicer for other developers to be able to >>> predict the names of methods across the entire toolkit. :-) >>> >>> 2. Testing should be more exhaustive testing to make sure that changes >>> to VTK don't break things. Right now only interpolation is tested at all >>> (and there is a lot of commented-out code in that test which should >>> probably be removed). Other tests should include, for example, >>> a. simplicial (triangular and tetrahedral) patch interpolation (you >>> can do this with an image-based test and/or by checking that numeric values >>> are within a tolerance of an analytical solution, >>> b. point inversion for rectangular and simplicial patches >>> c. derivative computation >>> d. the NURBS adaptor should be tested with several shapes whose >>> patches can be computed >>> >>> 3. Every class should have documentation that covers its purpose, its >>> intended lifecycle (how should it be used, what methods must be called >>> before others, etc.). The way field data is used to hold NURBS knot vectors >>> should be documented and should have an example data file (which should be >>> used in an image test to verify that it continues to work). >>> >>> Thanks, >>> David >>> >>> > On Sun, Aug 9, 2015 at 2:47 PM, Lin M wrote: >>> > Hi Dr. Thompson, >>> > >>> > I have pushed new methods to compute point inversion and projection to >>> gitlab. >>> > It took longer time than I expected. It would be really helpful if you >>> could review the code a little bit. Thanks! >>> > >>> > Best, >>> > Lin >>> > >>> > On Mon, Aug 3, 2015 at 10:50 AM, David Thompson < >>> david.thompson at kitware.com> wrote: >>> > Hi Lin, >>> > >>> > Yes, that is correct. Inserting knot values does not change the >>> polynomial degree or shape, it just adds control points so that the weights >>> are uniform (as required by the B?zier basis). So, the underlying >>> parameterization is unchanged... it just has more piecewise segments. >>> > >>> > David >>> > >>> > >>> > >>> > On Aug 2, 2015, at 22:38, Lin M wrote: >>> > >>> >> Hi Dr. Thompson, >>> >> >>> >> I have a question about the inversion and projection. Currently, we >>> evaluate the NURBS by inserting knots and making it into Bezier forms. My >>> question is that if I evaluate u = 0.2 in original knot vector [0,1,2,3], >>> would it be the same to evaluate u = 0.2 in the new knot vector which is a >>> bezier form? >>> >> >>> >> Best, >>> >> Lin >>> >> >>> >> On Mon, Jul 27, 2015 at 1:26 AM, Lin M wrote: >>> >> Hi Dr. Thompson, >>> >> >>> >> I have added new method >>> vtkPatachInterpolation::InterpolateOnSimplicialPatch() and pushed to gitlab. >>> >> >>> >> I'm now working on the point inversion part. >>> >> >>> >> Best, >>> >> Lin >>> >> >>> >> On Sun, Jul 26, 2015 at 8:05 PM, David Thompson < >>> david.thompson at kitware.com> wrote: >>> >> Hi Lin, >>> >> >>> >> How is triangular/tetrahedral patch interpolation going? They will be >>> a basic building block of the contouring and cutting algorithms. By >>> identifying points on edges, edges on surfaces, and surfaces in volumes >>> that take on a single value, a single patch can be decomposed into sections >>> that are inside, outside, or on an isosurface. Not all of these pieces can >>> be expressed as brick patches, but they can be expressed as simplicial >>> patches. >>> >> >>> >> David >>> >> >>> >> >>> > >>> > >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.PNG Type: image/png Size: 357636 bytes Desc: not available URL: