From bill.q.hdp at gmail.com Sat Jul 1 03:01:21 2017 From: bill.q.hdp at gmail.com (Bill Q) Date: Sat, 1 Jul 2017 15:01:21 +0800 Subject: [vtkusers] Issues with coordinate conversion, possible VTK bugs? In-Reply-To: References: Message-ID: Hi Andras, Thanks a ton! We are building a software that has a very specific purpose, other than the visualization part, everything else is tailored to the demands. To make it lightweight, we have to build a custom software. That's why we have taken the more difficult approach. Otherwise, we would have chosen an open-source solution. Thanks again for pointing out the solution. Many thanks. Bill On Sat, Jul 1, 2017 at 8:36 AM, Andras Lasso wrote: > The highlighted code lines perform point picking in world coordinates. If > you need more information then read the entire class and related classes, > maybe add a breakpoint and run it step-by-step in a debugger to see how it > works exactly. > > > > Playing with these, learning about low-level details is fun and useful > experience. However, I would strongly recommend not to develop yet another > DICOM viewer from scratch. There are several existing open source medical > image computing and visualization applications that are used by thousands > of people worldwide, they are used in operating rooms, used as a basis of > FDA-approved products, have been around for several years, stable, > feature-rich, etc. that can be extended to fit your needs. Most of them use > VTK! > > Andras > > > > *From:* Bill Q [mailto:bill.q.hdp at gmail.com] > *Sent:* Thursday, June 29, 2017 8:16 PM > *To:* Andras Lasso > *Cc:* Elvis Stansvik ; VTK Users < > vtkusers at vtk.org> > > *Subject:* Re: [vtkusers] Issues with coordinate conversion, possible VTK > bugs? > > > > Thanks Andras, > > > > I read through the links, but I wasn't able to identify the part that is > relevant to my questions. > > > > Would you be more specific? > > > Many thanks. > > Bill > > > > On Tue, Jun 6, 2017 at 11:01 AM, Andras Lasso wrote: > > See how it is implemented 3D Slicer and MITK: > > > > https://github.com/Slicer/Slicer/blob/master/Libs/MRML/DisplayableManager/ > vtkThreeDViewInteractorStyle.cxx#L812-L848 > > > > > https://github.com/MITK/MITK/blob/master/Modules/Core/src/ > Rendering/mitkBaseRenderer.cpp#L600-L640 > > > > > Andras > > > > *From:* vtkusers [mailto:vtkusers-bounces at vtk.org] *On Behalf Of *Bill Q > *Sent:* Monday, June 5, 2017 3:56 PM > *To:* Elvis Stansvik > *Cc:* VTK Users > *Subject:* Re: [vtkusers] Issues with coordinate conversion, possible VTK > bugs? > > > > Hi Elvis, > > I did give it a try. But still, it didn't work. I think I must have missed > something since there mush have hundreds of people tried to do the same > thing, getting the world coordinate from the vtk screen. The only way it > worked so far is to use a world picker. All other ways would return > different settings with z valued at 88 something. Where is the z value > coming from? Does the actor add the z in the renderer? > > > > Would someone know the correct way doing it give some advices? > > > Many thanks. > > Bill > > > > On Sat, May 27, 2017 at 4:06 AM, Elvis Stansvik < > elvis.stansvik at orexplore.com> wrote: > > 2017-05-26 20:08 GMT+02:00 Bill Q : > > Hi Elvis and Dan, > > Thank you very much for the response. After setting the render window > > SetNumberOfLayers(2) and setting the renderer with text SetLayer(1), both > > the layers with the DICOM images and the layer with the text can show up. > > But, the problem still persists. I still cannot get the correct world > > coordinates by using the following function: > > > > def display_to_world2(self, pt): > > worldPt = [0, 0, 0, 0] > > vtk.vtkInteractorObserver.ComputeDisplayToWorld(self.renderer_dicom, > > pt[0], pt[1], 0, worldPt) > > return worldPt[0] / worldPt[3], worldPt[1] / worldPt[3], worldPt[2] / > > worldPt[3] > > > > The z returned is always 86.33. > > > > Meanwhile, I cannot use the world picker either, because it still picks > the > > text's world coordinate. > > > > So, either I can make the above function work on the DICOM renderer or I > > have to make the world picker not picking up anything on the text > renderer. > > I am not sure how I can get any of these two ways done. > > > > Any suggestions would be greatly appreciated! > > Could you try turning interaction off on the renderer you use for your > "foreground" objects. In my code I have: > > auto foregroundRenderer = vtkSmartPointer::New(); > foregroundRenderer->InteractiveOff(); > foregroundRenderer->SetLayer(1); > ... > GetRenderWindow()->SetNumberOfLayers(2); > > Hope that helps, it's the last idea I have :p > > > Elvis > > > > > > > Many thanks. > > > > > > Bill > > > > On Thu, May 25, 2017 at 12:14 AM, Elvis Stansvik > > wrote: > >> > >> Den 24 maj 2017 5:27 em skrev "Bill Q" : > >> > > >> > Hi Dan, > >> > After set the layer, I got this error: > >> > > >> > VTK-7.1.0\Rendering\Core\vtkRendererCollection.cxx, line 61 > >> > vtkRendererCollection (000000001192E3A0): Invalid layer for renderer: > not > >> > rendered. > >> > > >> > And the text renderer didn't show up. > >> > >> You'll need to call SetNumberOfLayers(2) on your render window first I > >> think. > >> > >> Elvis > >> > >> > > >> > Many thanks. > >> > > >> > > >> > Bill > >> > > >> > On Wed, May 24, 2017 at 11:06 PM, Dan Lipsa > >> > wrote: > >> >> > >> >> Bill, > >> >> Try using SetLayer(1) for the renderer that has the text. > >> >> > >> >> Dan > >> >> > >> >> > >> >> On Wed, May 24, 2017 at 10:34 AM, Bill Q > wrote: > >> >>> > >> >>> Hi Dan, > >> >>> Thanks a ton for the example. The example used 4 different > viewports. > >> >>> However, for my application, I need to set all renderers under the > same > >> >>> viewport. The problem is that if I add a second renderer into the > render > >> >>> window and using the default viewport, it will cover the first > renderer and > >> >>> nothing on the first renderer will show up. I am wondering if I did > the > >> >>> whole thing wrong. > >> >>> > >> >>> My purpose is to display some DICOM images, some texts, and scales > on > >> >>> the same screen. Also, I would like to make the scales zoom with > the DICOM > >> >>> images but the texts stay put. Most importantly, I would like to > get the > >> >>> world coordinates on the DICOM image when users click on the > screen, so I > >> >>> can mark the click properly. > >> >>> > >> >>> What should be done in order to get this working? > >> >>> > >> >>> > >> >>> Many thanks. > >> >>> > >> >>> > >> >>> Bill > >> >>> > >> >>> On Wed, May 24, 2017 at 12:02 AM, Dan Lipsa > >> >>> wrote: > >> >>>> > >> >>>> Not sure what is going on. Do the objects you are rendering have > the > >> >>>> same world coordinates? Are both renderers added to the rendering > window? > >> >>>> Here is an example with multiple renderer (they are over different > >> >>>> viewports but they could have the same viewport as well) > >> >>>> > >> >>>> http://www.vtk.org/Wiki/VTK/Examples/Cxx/Visualization/ > MultipleViewports > > >> >>>> > >> >>>> On Tue, May 23, 2017 at 11:39 AM, Bill Q > >> >>>> wrote: > >> >>>>> > >> >>>>> I just gave it a try. But when I added another renderer into the > >> >>>>> window that I used for text actors, it overlaps and covered the > first > >> >>>>> renderer. So the first renderer won't show up. Is there a > solution? > >> >>>>> > >> >>>>> Many thanks. > >> >>>>> > >> >>>>> > >> >>>>> Bill > >> >>>>> > >> >>>>> On Tue, May 23, 2017 at 10:16 PM, Dan Lipsa < > dan.lipsa at kitware.com> > >> >>>>> wrote: > >> >>>>>> > >> >>>>>> I think moving those text actors on a different renderer will > solve > >> >>>>>> your problem. > >> >>>>>> > >> >>>>>> Dan > >> >>>>>> > >> >>>>>> > >> >>>>>> On Tue, May 23, 2017 at 9:40 AM, Bill Q > >> >>>>>> wrote: > >> >>>>>>> > >> >>>>>>> Hi Dan, > >> >>>>>>> Thanks a lot for the reply. Yes, that's exactly the case. If I > >> >>>>>>> remove the text actors, the world picker would return the > correct > >> >>>>>>> coordinates. So, what method should I use in order to get the > correct > >> >>>>>>> coordinates no matter how many actors I put in with the dicom > image reader > >> >>>>>>> actor? > >> >>>>>>> > >> >>>>>>> Many thanks. > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> Bill > >> >>>>>>> > >> >>>>>>> On Mon, May 22, 2017 at 10:04 PM, Dan Lipsa > >> >>>>>>> wrote: > >> >>>>>>>> > >> >>>>>>>> Bill, > >> >>>>>>>> For display_to_world, the picker picks up only what is visible > >> >>>>>>>> (closes to the camera). You might have several objects > (several values in > >> >>>>>>>> world coordinates) that end up over the same display > coordinate. This might > >> >>>>>>>> explain why adding those text actors changes what you pick. > >> >>>>>>>> > >> >>>>>>>> Dan > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>>> On Sun, May 21, 2017 at 5:25 AM, Bill Q > >> >>>>>>>> wrote: > >> >>>>>>>>> > >> >>>>>>>>> Can anybody help? Many thanks. > >> >>>>>>>>> > >> >>>>>>>>> Many thanks. > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> Bill > >> >>>>>>>>> > >> >>>>>>>>> On Fri, May 19, 2017 at 11:20 PM, Bill Q < > bill.q.hdp at gmail.com> > >> >>>>>>>>> wrote: > >> >>>>>>>>>> > >> >>>>>>>>>> Hello Everyone, > >> >>>>>>>>>> I encountered a weird problem in coordinate conversion. > >> >>>>>>>>>> > >> >>>>>>>>>> In order to check the accuracy, I converted from display to > >> >>>>>>>>>> world, and from world back to display. Using the following > ways: > >> >>>>>>>>>> > >> >>>>>>>>>> self.world_picker = vtk.vtkWorldPointPicker() > >> >>>>>>>>>> > >> >>>>>>>>>> def display_to_world(self, pt): > >> >>>>>>>>>> self.world_picker.Pick(pt[0], pt[1], 0, self.ren) > >> >>>>>>>>>> picker_pt = self.world_picker.GetPickPosition() > >> >>>>>>>>>> picker_pt = (picker_pt[0], picker_pt[1], 0) > >> >>>>>>>>>> return picker_pt > >> >>>>>>>>>> > >> >>>>>>>>>> def world_to_display(self, pt): > >> >>>>>>>>>> if len(pt) == 3: > >> >>>>>>>>>> pt = pt + (1.0,) > >> >>>>>>>>>> elif len(pt) == 2: > >> >>>>>>>>>> pt = pt + (0.0, 1.0) > >> >>>>>>>>>> self.ren.SetWorldPoint(pt) > >> >>>>>>>>>> self.ren.WorldToDisplay() > >> >>>>>>>>>> pt = self.ren.GetDisplayPoint() > >> >>>>>>>>>> pt = (pt[0], pt[1]) > >> >>>>>>>>>> return pt > >> >>>>>>>>>> > >> >>>>>>>>>> pt = [5, 5] > >> >>>>>>>>>> > >> >>>>>>>>>> world_pt = self. world_to_display(pt) > >> >>>>>>>>>> > >> >>>>>>>>>> display_pt = self. world_to_display(world_pt) > >> >>>>>>>>>> > >> >>>>>>>>>> In some cases, it's quite accurate, which means pt equals > >> >>>>>>>>>> display_pt. But, in some cases, the result is simply wrong. > For example, for > >> >>>>>>>>>> (5, 5), after conversions back to display, the coordinate > becomes (20.89, > >> >>>>>>>>>> 20.89). > >> >>>>>>>>>> > >> >>>>>>>>>> Any ideas? > >> >>>>>>>>>> > >> >>>>>>>>>> > >> >>>>>>>>>> Many thanks. > >> >>>>>>>>>> > >> >>>>>>>>>> > >> >>>>>>>>>> Bill > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> _______________________________________________ > >> >>>>>>>>> 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 > > >> >>>>>>>>> > >> >>>>>>>> > >> >>>>>>> > >> >>>>>> > >> >>>>> > >> >>>> > >> >>> > >> >> > >> > > >> > > >> > _______________________________________________ > >> > 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 > > >> > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonid_dulman at yahoo.co.uk Sat Jul 1 04:58:18 2017 From: leonid_dulman at yahoo.co.uk (Leonid Dulman) Date: Sat, 1 Jul 2017 08:58:18 +0000 (UTC) Subject: [vtkusers] Announce: VTKAda version 8.0.0 release 01/07/2017 References: <1576463547.4130530.1498899498131.ref@mail.yahoo.com> Message-ID: <1576463547.4130530.1498899498131@mail.yahoo.com> I'm pleased to announce VTKAda version 8.0.0 ?free edition ?release 01/07/2017VTKAda is Ada-2012 ?port to VTK (Visualization Toolkit by Kitware, Inc) and Qt5 application and UI framework by NokiaVTK version 8.0.0, Qt version 5.9.0 open source and vtkc.dll,vtkc2.dll,qt5c.dll(libvtkc.so,libvtkc2.so,libqt5c.so) were built with Microsoft Visual Studio 2015 ?in Windows (WIN32)and gcc ?in Linux ?x86-64Package was tested with gnat gpl 2017 ada compiler in Windows 10 ?64bit,Debian 8.5 x86-64 As a role ADA is used in embeded systems, but with VTKADA(+QTADA) you can build any desktop applications with?powerful 2D/3D rendering and imaging (games, animations, emulations) GUI, Database connection, server/client, Internet browsing and many others thinks. VTKADA you can be used without QTADA subsystem? Qt5Ada and VTKAda for Windows, Linux (Unix) is available fromhttps://drive.google.com/folderview?id=0B2QuZLoe-yiPbmNQRl83M1dTRVE&usp=sharing (google drive. It can be mounted as virtual drive or directory or viewed with Web Browser)?? Leonid Dulman (leonid.dulman at gmail.com) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ansha.kamath at gmail.com Sat Jul 1 06:29:48 2017 From: ansha.kamath at gmail.com (anusha_kamath) Date: Sat, 1 Jul 2017 03:29:48 -0700 (MST) Subject: [vtkusers] Unknown CMake command "vtk_add_test_cxx" Message-ID: <1498904988843-5743844.post@n5.nabble.com> I have built VTK with cmake 3.7.2 and Visual Studio 2012 on a windows 10 machine.But i came across the followingg error while compiling the example in VTK-7.1.1\Rendering\OpenVR\Testing\Cxx with cmake. CMake Error at CMakeLists.txt:3 (vtk_add_test_cxx): Unknown CMake command "vtk_add_test_cxx". I have added the function vtk_add_test_cxx in vtkTestingMacros.cmake file as suggested in https://gitlab.kitware.com/Wu/vtk/commit/dbb4c57325301815a2500ae244d3e7e60a1030fe#9a1b095f3cbd05f3c789b96f70be522fdf858e70_133_135 but didnt seem to solve.Is there any way to correct this? Thanks for any help! -- View this message in context: http://vtk.1045678.n5.nabble.com/Unknown-CMake-command-vtk-add-test-cxx-tp5743844.html Sent from the VTK - Users mailing list archive at Nabble.com. From bill.lorensen at gmail.com Sat Jul 1 10:32:31 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Sat, 1 Jul 2017 10:32:31 -0400 Subject: [vtkusers] Coloring a glyph or Append polydata In-Reply-To: References: Message-ID: This example may help... https://lorensen.github.io/VTKExamples/site/Cxx/Visualization/ColorGlyphs/ On Fri, Jun 30, 2017 at 8:54 PM, abcd efgh wrote: > Hi, > > I have large number of cubes at certain x,y,z postions, So I am combining > them into Glyph3D or Append Polydata. I want to color them individually. > Please let me know the procedure. > Current method: > take a cube source, > insert point, > instert tuple for color, > repeat above for all cubes. > Finally combine them in poly and glyph. > I am getting only one color for all, Red or blue. > When I use ClipPolydata, sliced cubes are black in color, Even though > scalars property should be same as input. However if I use Append polydata > and clip using vtkClipPloydata, I am getting white color(same as cube). I > want to color each cube and slice it using vtkClipPolydata and see the > respective colors. Please let me know if u know the method. > > Thanks > > _______________________________________________ > 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 > -- Unpaid intern in BillsBasement at noware dot com From 2448.rok at gmail.com Sat Jul 1 11:07:46 2017 From: 2448.rok at gmail.com (oblakr) Date: Sat, 1 Jul 2017 08:07:46 -0700 (MST) Subject: [vtkusers] Constructing a surface from a boundary curve In-Reply-To: References: <1474308642161-5740429.post@n5.nabble.com> Message-ID: <1498921666855-5743846.post@n5.nabble.com> Hi, Thanks for the link, however this is not completely optimal for my case: - the input data for my case is not a contour, since the points do not necessarily lie on the same plane - vtkVoxelContourFilter expects coordinates to be integer values, and when I try the example the resulting surface does not completely "touch" the original contours - as if its outline were somewhat smoothed. I need the algorithm to produce a surface that exactly matches the input outline. Is there a name for a generic algorithm that produces a surface from a given 3D boundary (nonplanar)? Thanks and best regards, Rok -- View this message in context: http://vtk.1045678.n5.nabble.com/Constructing-a-surface-from-a-boundary-curve-tp5740429p5743846.html Sent from the VTK - Users mailing list archive at Nabble.com. From woshizyc at gmail.com Sat Jul 1 11:26:00 2017 From: woshizyc at gmail.com (woshizyc at gmail.com) Date: Sat, 1 Jul 2017 23:26:00 +0800 Subject: [vtkusers] vertex and voxel correspondence using vtkMarchingCubes Message-ID: <201707012238004290730@gmail.com> Hi, experts, Is there any way that I can get the corresponding voxel of the vertices on the isosurface obtained using vtkMarchingCubes. I want to map the intensity of each voxel to the vertex on the surface, I first transform the image into a volume with equal intensity and obtain its polydata representation using marching cube in vtk. How can I get the vertex-to-voxel correspondence? Thanks a lot. zyc woshizyc at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From lasso at queensu.ca Sat Jul 1 12:10:36 2017 From: lasso at queensu.ca (Andras Lasso) Date: Sat, 1 Jul 2017 16:10:36 +0000 Subject: [vtkusers] Building medical imaging applications from scratch Message-ID: (changed the subject to reflect the slightly shifted topic of the discussion) Need for a ?lightweight? application is a commonly cited reason for starting development of a medical application from scratch (using just VTK+Qt). However, most of the time this is not a well-founded reason. For example, if you already use Qt and VTK, adding an open-source application framework (3D Slicer, MITK, etc. ? if it is not strictly medical application then there are several others, for example ParaView) increases the total amount of third-party libraries (in term of line of source code) by about 5%. This is very little price to pay for the hundreds of man-years of effort that went into development and testing of these frameworks. When you apply for regulatory approval for commercial applications, 3D Slicer is considered software of unknown pedigree, the same way as VTK, and other libraries that you may use. Overall, you get somewhat increased documentation work, but you can save several years of software development effort. We find that with 3D Slicer you need to write approximately 0.01%-0.1% of application-specific code for a new medical application ? see this illustration: https://1drv.ms/b/s!Arm_AFxB9yqHr_hDpop7_CaxXoO4cA. I know that it is more fun to just start to develop something from scratch, compared to learning from others; it is also useful for understanding details by getting first-hand experience, etc., but when the end result is important ? you want to have an application that clinicians can use, try a new method in the operating room, you want to release a product faster, etc. ? then it is hard to justify the duplicated effort. I know that the VTK list is read by many people ? VTK developers, users, application developers. I would be interested in hearing about opinion and experiences of others. Not necessarily in the medical imaging domain: for example ParaView developers may see a similar trend of people developing custom scientific visualization applications from scratch, instead of customizing/extending ParaView. Andras From: Bill Q [mailto:bill.q.hdp at gmail.com] Sent: Saturday, July 1, 2017 9:01 AM To: Andras Lasso Cc: Elvis Stansvik ; VTK Users Subject: Re: [vtkusers] Issues with coordinate conversion, possible VTK bugs? Hi Andras, Thanks a ton! We are building a software that has a very specific purpose, other than the visualization part, everything else is tailored to the demands. To make it lightweight, we have to build a custom software. That's why we have taken the more difficult approach. Otherwise, we would have chosen an open-source solution. Thanks again for pointing out the solution. Many thanks. Bill On Sat, Jul 1, 2017 at 8:36 AM, Andras Lasso > wrote: The highlighted code lines perform point picking in world coordinates. If you need more information then read the entire class and related classes, maybe add a breakpoint and run it step-by-step in a debugger to see how it works exactly. Playing with these, learning about low-level details is fun and useful experience. However, I would strongly recommend not to develop yet another DICOM viewer from scratch. There are several existing open source medical image computing and visualization applications that are used by thousands of people worldwide, they are used in operating rooms, used as a basis of FDA-approved products, have been around for several years, stable, feature-rich, etc. that can be extended to fit your needs. Most of them use VTK! Andras From: Bill Q [mailto:bill.q.hdp at gmail.com] Sent: Thursday, June 29, 2017 8:16 PM To: Andras Lasso > Cc: Elvis Stansvik >; VTK Users > Subject: Re: [vtkusers] Issues with coordinate conversion, possible VTK bugs? Thanks Andras, I read through the links, but I wasn't able to identify the part that is relevant to my questions. Would you be more specific? Many thanks. Bill On Tue, Jun 6, 2017 at 11:01 AM, Andras Lasso > wrote: See how it is implemented 3D Slicer and MITK: https://github.com/Slicer/Slicer/blob/master/Libs/MRML/DisplayableManager/vtkThreeDViewInteractorStyle.cxx#L812-L848 https://github.com/MITK/MITK/blob/master/Modules/Core/src/Rendering/mitkBaseRenderer.cpp#L600-L640 Andras From: vtkusers [mailto:vtkusers-bounces at vtk.org] On Behalf Of Bill Q Sent: Monday, June 5, 2017 3:56 PM To: Elvis Stansvik > Cc: VTK Users > Subject: Re: [vtkusers] Issues with coordinate conversion, possible VTK bugs? Hi Elvis, I did give it a try. But still, it didn't work. I think I must have missed something since there mush have hundreds of people tried to do the same thing, getting the world coordinate from the vtk screen. The only way it worked so far is to use a world picker. All other ways would return different settings with z valued at 88 something. Where is the z value coming from? Does the actor add the z in the renderer? Would someone know the correct way doing it give some advices? Many thanks. Bill On Sat, May 27, 2017 at 4:06 AM, Elvis Stansvik > wrote: 2017-05-26 20:08 GMT+02:00 Bill Q >: > Hi Elvis and Dan, > Thank you very much for the response. After setting the render window > SetNumberOfLayers(2) and setting the renderer with text SetLayer(1), both > the layers with the DICOM images and the layer with the text can show up. > But, the problem still persists. I still cannot get the correct world > coordinates by using the following function: > > def display_to_world2(self, pt): > worldPt = [0, 0, 0, 0] > vtk.vtkInteractorObserver.ComputeDisplayToWorld(self.renderer_dicom, > pt[0], pt[1], 0, worldPt) > return worldPt[0] / worldPt[3], worldPt[1] / worldPt[3], worldPt[2] / > worldPt[3] > > The z returned is always 86.33. > > Meanwhile, I cannot use the world picker either, because it still picks the > text's world coordinate. > > So, either I can make the above function work on the DICOM renderer or I > have to make the world picker not picking up anything on the text renderer. > I am not sure how I can get any of these two ways done. > > Any suggestions would be greatly appreciated! Could you try turning interaction off on the renderer you use for your "foreground" objects. In my code I have: auto foregroundRenderer = vtkSmartPointer::New(); foregroundRenderer->InteractiveOff(); foregroundRenderer->SetLayer(1); ... GetRenderWindow()->SetNumberOfLayers(2); Hope that helps, it's the last idea I have :p Elvis > > > Many thanks. > > > Bill > > On Thu, May 25, 2017 at 12:14 AM, Elvis Stansvik > > wrote: >> >> Den 24 maj 2017 5:27 em skrev "Bill Q" >: >> > >> > Hi Dan, >> > After set the layer, I got this error: >> > >> > VTK-7.1.0\Rendering\Core\vtkRendererCollection.cxx, line 61 >> > vtkRendererCollection (000000001192E3A0): Invalid layer for renderer: not >> > rendered. >> > >> > And the text renderer didn't show up. >> >> You'll need to call SetNumberOfLayers(2) on your render window first I >> think. >> >> Elvis >> >> > >> > Many thanks. >> > >> > >> > Bill >> > >> > On Wed, May 24, 2017 at 11:06 PM, Dan Lipsa > >> > wrote: >> >> >> >> Bill, >> >> Try using SetLayer(1) for the renderer that has the text. >> >> >> >> Dan >> >> >> >> >> >> On Wed, May 24, 2017 at 10:34 AM, Bill Q > wrote: >> >>> >> >>> Hi Dan, >> >>> Thanks a ton for the example. The example used 4 different viewports. >> >>> However, for my application, I need to set all renderers under the same >> >>> viewport. The problem is that if I add a second renderer into the render >> >>> window and using the default viewport, it will cover the first renderer and >> >>> nothing on the first renderer will show up. I am wondering if I did the >> >>> whole thing wrong. >> >>> >> >>> My purpose is to display some DICOM images, some texts, and scales on >> >>> the same screen. Also, I would like to make the scales zoom with the DICOM >> >>> images but the texts stay put. Most importantly, I would like to get the >> >>> world coordinates on the DICOM image when users click on the screen, so I >> >>> can mark the click properly. >> >>> >> >>> What should be done in order to get this working? >> >>> >> >>> >> >>> Many thanks. >> >>> >> >>> >> >>> Bill >> >>> >> >>> On Wed, May 24, 2017 at 12:02 AM, Dan Lipsa > >> >>> wrote: >> >>>> >> >>>> Not sure what is going on. Do the objects you are rendering have the >> >>>> same world coordinates? Are both renderers added to the rendering window? >> >>>> Here is an example with multiple renderer (they are over different >> >>>> viewports but they could have the same viewport as well) >> >>>> >> >>>> http://www.vtk.org/Wiki/VTK/Examples/Cxx/Visualization/MultipleViewports >> >>>> >> >>>> On Tue, May 23, 2017 at 11:39 AM, Bill Q > >> >>>> wrote: >> >>>>> >> >>>>> I just gave it a try. But when I added another renderer into the >> >>>>> window that I used for text actors, it overlaps and covered the first >> >>>>> renderer. So the first renderer won't show up. Is there a solution? >> >>>>> >> >>>>> Many thanks. >> >>>>> >> >>>>> >> >>>>> Bill >> >>>>> >> >>>>> On Tue, May 23, 2017 at 10:16 PM, Dan Lipsa > >> >>>>> wrote: >> >>>>>> >> >>>>>> I think moving those text actors on a different renderer will solve >> >>>>>> your problem. >> >>>>>> >> >>>>>> Dan >> >>>>>> >> >>>>>> >> >>>>>> On Tue, May 23, 2017 at 9:40 AM, Bill Q > >> >>>>>> wrote: >> >>>>>>> >> >>>>>>> Hi Dan, >> >>>>>>> Thanks a lot for the reply. Yes, that's exactly the case. If I >> >>>>>>> remove the text actors, the world picker would return the correct >> >>>>>>> coordinates. So, what method should I use in order to get the correct >> >>>>>>> coordinates no matter how many actors I put in with the dicom image reader >> >>>>>>> actor? >> >>>>>>> >> >>>>>>> Many thanks. >> >>>>>>> >> >>>>>>> >> >>>>>>> Bill >> >>>>>>> >> >>>>>>> On Mon, May 22, 2017 at 10:04 PM, Dan Lipsa >> >>>>>>> > wrote: >> >>>>>>>> >> >>>>>>>> Bill, >> >>>>>>>> For display_to_world, the picker picks up only what is visible >> >>>>>>>> (closes to the camera). You might have several objects (several values in >> >>>>>>>> world coordinates) that end up over the same display coordinate. This might >> >>>>>>>> explain why adding those text actors changes what you pick. >> >>>>>>>> >> >>>>>>>> Dan >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> >> >>>>>>>> On Sun, May 21, 2017 at 5:25 AM, Bill Q > >> >>>>>>>> wrote: >> >>>>>>>>> >> >>>>>>>>> Can anybody help? Many thanks. >> >>>>>>>>> >> >>>>>>>>> Many thanks. >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> Bill >> >>>>>>>>> >> >>>>>>>>> On Fri, May 19, 2017 at 11:20 PM, Bill Q > >> >>>>>>>>> wrote: >> >>>>>>>>>> >> >>>>>>>>>> Hello Everyone, >> >>>>>>>>>> I encountered a weird problem in coordinate conversion. >> >>>>>>>>>> >> >>>>>>>>>> In order to check the accuracy, I converted from display to >> >>>>>>>>>> world, and from world back to display. Using the following ways: >> >>>>>>>>>> >> >>>>>>>>>> self.world_picker = vtk.vtkWorldPointPicker() >> >>>>>>>>>> >> >>>>>>>>>> def display_to_world(self, pt): >> >>>>>>>>>> self.world_picker.Pick(pt[0], pt[1], 0, self.ren) >> >>>>>>>>>> picker_pt = self.world_picker.GetPickPosition() >> >>>>>>>>>> picker_pt = (picker_pt[0], picker_pt[1], 0) >> >>>>>>>>>> return picker_pt >> >>>>>>>>>> >> >>>>>>>>>> def world_to_display(self, pt): >> >>>>>>>>>> if len(pt) == 3: >> >>>>>>>>>> pt = pt + (1.0,) >> >>>>>>>>>> elif len(pt) == 2: >> >>>>>>>>>> pt = pt + (0.0, 1.0) >> >>>>>>>>>> self.ren.SetWorldPoint(pt) >> >>>>>>>>>> self.ren.WorldToDisplay() >> >>>>>>>>>> pt = self.ren.GetDisplayPoint() >> >>>>>>>>>> pt = (pt[0], pt[1]) >> >>>>>>>>>> return pt >> >>>>>>>>>> >> >>>>>>>>>> pt = [5, 5] >> >>>>>>>>>> >> >>>>>>>>>> world_pt = self. world_to_display(pt) >> >>>>>>>>>> >> >>>>>>>>>> display_pt = self. world_to_display(world_pt) >> >>>>>>>>>> >> >>>>>>>>>> In some cases, it's quite accurate, which means pt equals >> >>>>>>>>>> display_pt. But, in some cases, the result is simply wrong. For example, for >> >>>>>>>>>> (5, 5), after conversions back to display, the coordinate becomes (20.89, >> >>>>>>>>>> 20.89). >> >>>>>>>>>> >> >>>>>>>>>> Any ideas? >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> Many thanks. >> >>>>>>>>>> >> >>>>>>>>>> >> >>>>>>>>>> Bill >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> _______________________________________________ >> >>>>>>>>> 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 >> >>>>>>>>> >> >>>>>>>> >> >>>>>>> >> >>>>>> >> >>>>> >> >>>> >> >>> >> >> >> > >> > >> > _______________________________________________ >> > 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 >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill.lorensen at gmail.com Sat Jul 1 12:24:05 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Sat, 1 Jul 2017 12:24:05 -0400 Subject: [vtkusers] Constructing a surface from a boundary curve In-Reply-To: <1498921666855-5743846.post@n5.nabble.com> References: <1474308642161-5740429.post@n5.nabble.com> <1498921666855-5743846.post@n5.nabble.com> Message-ID: I did a google search for non planar contour surface construction and found nothing that processed non-planar contours On Sat, Jul 1, 2017 at 11:07 AM, oblakr <2448.rok at gmail.com> wrote: > Hi, > Thanks for the link, however this is not completely optimal for my case: > - the input data for my case is not a contour, since the points do not > necessarily lie on the same plane > - vtkVoxelContourFilter expects coordinates to be integer values, and when I > try the example the resulting surface does not completely "touch" the > original contours - as if its outline were somewhat smoothed. I need the > algorithm to produce a surface that exactly matches the input outline. > > Is there a name for a generic algorithm that produces a surface from a given > 3D boundary (nonplanar)? > > Thanks and best regards, > Rok > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Constructing-a-surface-from-a-boundary-curve-tp5740429p5743846.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -- Unpaid intern in BillsBasement at noware dot com From bill.lorensen at gmail.com Sat Jul 1 12:28:31 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Sat, 1 Jul 2017 12:28:31 -0400 Subject: [vtkusers] vertex and voxel correspondence using vtkMarchingCubes In-Reply-To: <201707012238004290730@gmail.com> References: <201707012238004290730@gmail.com> Message-ID: You can use vtkProbeFilter to do this, but if the surface was extracted from the voxel volume, all values will be the same. If you want to sample a different volume, here are two examples https://lorensen.github.io/VTKExamples/site/Cxx/Visualization/IsosurfaceSampling/ https://lorensen.github.io/VTKExamples/site/Cxx/Medical/TissueLens/ Bill On Sat, Jul 1, 2017 at 11:26 AM, woshizyc at gmail.com wrote: > Hi, experts, > > Is there any way that I can get the corresponding voxel of the vertices on > the isosurface obtained using vtkMarchingCubes. > > I want to map the intensity of each voxel to the vertex on the surface, I > first transform the image into a volume with equal intensity and obtain its > polydata representation using marching cube in vtk. How can I get the > vertex-to-voxel correspondence? > > Thanks a lot. > > zyc > > > ________________________________ > woshizyc at gmail.com > > _______________________________________________ > 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 > -- Unpaid intern in BillsBasement at noware dot com From 2448.rok at gmail.com Sat Jul 1 17:53:12 2017 From: 2448.rok at gmail.com (oblakr) Date: Sat, 1 Jul 2017 14:53:12 -0700 (MST) Subject: [vtkusers] Hole filling - getting individual components Message-ID: <1498945992223-5743851.post@n5.nabble.com> Hi, I have a model with holes in it, which I am able to fill with the fillHolesFilter (thus getting the poly data with all holes filled). However, I want to separate all the added surfaces (individual filled holes) into separate polydatas, but I don't see this functionality in the fillHolesFilter. I was thinking about doing something by intersecting the original model with the filled model, but I don't know what method to use and how to do it efficiently. Does anybody know of a good way of doing this? Thanks and best regards, Rok -- View this message in context: http://vtk.1045678.n5.nabble.com/Hole-filling-getting-individual-components-tp5743851.html Sent from the VTK - Users mailing list archive at Nabble.com. From bill.lorensen at gmail.com Sat Jul 1 20:14:12 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Sat, 1 Jul 2017 20:14:12 -0400 Subject: [vtkusers] Hole filling - getting individual components In-Reply-To: <1498945992223-5743851.post@n5.nabble.com> References: <1498945992223-5743851.post@n5.nabble.com> Message-ID: Do you need each hole or just all of the holes as a single component? I think I have a solution. I'll post an example tomorrow. On Sat, Jul 1, 2017 at 5:53 PM, oblakr <2448.rok at gmail.com> wrote: > Hi, > > I have a model with holes in it, which I am able to fill with the > fillHolesFilter (thus getting the poly data with all holes filled). > > However, I want to separate all the added surfaces (individual filled holes) > into separate polydatas, but I don't see this functionality in the > fillHolesFilter. > > I was thinking about doing something by intersecting the original model with > the filled model, but I don't know what method to use and how to do it > efficiently. Does anybody know of a good way of doing this? > > Thanks and best regards, > Rok > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Hole-filling-getting-individual-components-tp5743851.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -- Unpaid intern in BillsBasement at noware dot com From 2448.rok at gmail.com Sun Jul 2 02:31:10 2017 From: 2448.rok at gmail.com (oblakr) Date: Sat, 1 Jul 2017 23:31:10 -0700 (MST) Subject: [vtkusers] Hole filling - getting individual components In-Reply-To: References: <1498945992223-5743851.post@n5.nabble.com> Message-ID: <1498977070809-5743853.post@n5.nabble.com> Hi, It would be preferable if they are separate but even if they are a single component I can manually split them based on connectivity. -- View this message in context: http://vtk.1045678.n5.nabble.com/Hole-filling-getting-individual-components-tp5743851p5743853.html Sent from the VTK - Users mailing list archive at Nabble.com. From bill.lorensen at gmail.com Sun Jul 2 10:51:39 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Sun, 2 Jul 2017 10:51:39 -0400 Subject: [vtkusers] Hole filling - getting individual components In-Reply-To: <1498977070809-5743853.post@n5.nabble.com> References: <1498945992223-5743851.post@n5.nabble.com> <1498977070809-5743853.post@n5.nabble.com> Message-ID: I just added this example to the VTK Examples: https://lorensen.github.io/VTKExamples/site/Cxx/Meshes/IdentifyHoles/ On Sun, Jul 2, 2017 at 2:31 AM, oblakr <2448.rok at gmail.com> wrote: > Hi, > > It would be preferable if they are separate but even if they are a single > component I can manually split them based on connectivity. > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Hole-filling-getting-individual-components-tp5743851p5743853.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -- Unpaid intern in BillsBasement at noware dot com From 2448.rok at gmail.com Sun Jul 2 13:55:49 2017 From: 2448.rok at gmail.com (oblakr) Date: Sun, 2 Jul 2017 10:55:49 -0700 (MST) Subject: [vtkusers] Hole filling - getting individual components In-Reply-To: References: <1498945992223-5743851.post@n5.nabble.com> <1498977070809-5743853.post@n5.nabble.com> Message-ID: <1499018149877-5743858.post@n5.nabble.com> Hi, this solves my problem. Thank you very much, very appreciated. Best regards, Rok -- View this message in context: http://vtk.1045678.n5.nabble.com/Hole-filling-getting-individual-components-tp5743851p5743858.html Sent from the VTK - Users mailing list archive at Nabble.com. From bill.lorensen at gmail.com Sun Jul 2 14:00:54 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Sun, 2 Jul 2017 14:00:54 -0400 Subject: [vtkusers] Hole filling - getting individual components In-Reply-To: <1499018149877-5743858.post@n5.nabble.com> References: <1498945992223-5743851.post@n5.nabble.com> <1498977070809-5743853.post@n5.nabble.com> <1499018149877-5743858.post@n5.nabble.com> Message-ID: IF you see errors or improvemens please follow the procedure here: https://lorensen.github.io/VTKExamples/site/Instructions/ForDevelopers/ Also, tell all of your friends about the VTK Examples. https://lorensen.github.io/VTKExamples/site/ On Jul 2, 2017 1:55 PM, "oblakr" <2448.rok at gmail.com> wrote: > Hi, > > this solves my problem. Thank you very much, very appreciated. > > Best regards, > Rok > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Hole-filling-getting-individual-components-tp5743851p5743858.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From l1q1d at yahoo.it Mon Jul 3 02:41:14 2017 From: l1q1d at yahoo.it (L1q1d) Date: Mon, 3 Jul 2017 06:41:14 +0000 (UTC) Subject: [vtkusers] Contourf plot with dynamic resize References: <1994849194.5571465.1499064074501.ref@mail.yahoo.com> Message-ID: <1994849194.5571465.1499064074501@mail.yahoo.com> Hi to all, this is my first post in the mailing list. I'm trying to develop a plot application thant is able to create the controuf similar to matlab https://it.mathworks.com/help/matlab/ref/contourf.html I succeed in creating something like it but?my actual issues are place the plot in the center and?resize dynamically?with the window. This is the code that I'm using so far: void CreateBaseData(vtkImageData* image) { datastructure * dataInput = new datastructure(FILEPATH); image->SetDimensions(dataInput->shape()->Xsize, dataInput->shape()->Ysize, 1); // image->SetSpacing(dataInput->shape()->Xres,dataInput->shape()->Yres,0); // image->SetOrigin(dataInput->shape()->Xmin,dataInput->shape()->Ymin,0); image->AllocateScalars(VTK_DOUBLE,1); for(unsigned int x = 0; x < dataInput->shape()->Xsize; x++) { for(unsigned int y = 0; y < dataInput->shape()->Ysize; y++) { double* pixel = static_cast(image->GetScalarPointer(x,y,0)); pixel[0] = dataInput->z[y][x]; } } delete dataInput; //image->Modified(); } void RenderWindowUISingleInheritance::ModifiedHandler() { ui->qvtkWidget->GetRenderWindow()->Render(); } // Constructor RenderWindowUISingleInheritance::RenderWindowUISingleInheritance(QWidget *parent) : QMainWindow(parent), ui(new Ui::RenderWindowUISingleInheritanceUI) { ui->setupUi(this); vtkSmartPointer style = vtkSmartPointer::New(); ui->qvtkWidget->GetRenderWindow()->GetInteractor()->SetInteractorStyle(style); int numberOfContours = 15; double scalarRange[2]; float levels[] = { 0.4, 1.0, 2.0, 4, 10.0, 20.0, 40, 100, 200, 400, 1000, 2000, 4000, 10000, 20000, 40000 }; vtkSmartPointer colorImage = vtkSmartPointer::New(); vtkSmartPointer lut = vtkSmartPointer::New(); vtkSmartPointer convert = vtkSmartPointer::New(); vtkSmartPointer bf = vtkSmartPointer::New(); vtkSmartPointer filledContourMapper = vtkSmartPointer::New(); vtkSmartPointer contourLineMapperer =vtkSmartPointer::New(); vtkSmartPointer ren1 = vtkSmartPointer::New(); vtkSmartPointer filledContourActor =vtkSmartPointer::New(); vtkSmartPointer contourLineActor = vtkSmartPointer::New(); vtkSmartPointer cubeAxesActor = vtkSmartPointer::New(); vtkSmartPointer scalarBarActor =vtkSmartPointer::New(); CreateBaseData(colorImage); colorImage->GetScalarRange(scalarRange); int l_min; int l_max; for (l_min=numberOfContours-1;l_min>=0;l_min--) { if (levels[l_min] <= scalarRange[0]) break; } for (l_max=0;l_max scalarRange[1]) break; } numberOfContours = l_max - l_min; // colormap::setColorMap(lut,1,1); char label[10]; for (vtkIdType i = l_min; i < numberOfContours+1; ++i) { //std::cout << lut->GetAnnotatedValue(i).ToString() << std::endl; sprintf(label,"%4.2f",levels[i]); lut->SetAnnotation(i, label); } convert->SetInputData(colorImage); bf->SetInputConnection(convert->GetOutputPort()); bf->SetNumberOfContours(numberOfContours); for (int i=l_min;iSetValue(i,levels[i]); } bf->GenerateContourEdgesOn(); filledContourMapper->SetInputConnection(bf->GetOutputPort()); filledContourMapper->SetScalarModeToUseCellData(); // filledContourMapper->SetColorModeToMapScalars(); filledContourMapper->SetScalarRange(0,numberOfContours); filledContourMapper->SetLookupTable(lut); filledContourActor->SetMapper(filledContourMapper); filledContourActor->PickableOn(); filledContourActor->GetPosition2Coordinate()->SetValue(0.17, 0.8); filledContourActor->GetPositionCoordinate()->SetCoordinateSystemToNormalizedViewport(); filledContourActor->GetPositionCoordinate()->SetValue(0.82, 0.1); filledContourActor->SetWidth( 0.7 ); filledContourActor->SetHeight( 0.1 ); filledContourActor->SetPosition( 0.1, 0.01 ); contourLineMapperer->SetInputData(bf->GetContourEdgesOutput()); contourLineMapperer->ScalarVisibilityOn(); contourLineActor->SetMapper(contourLineMapperer); contourLineActor->GetProperty()->SetLineWidth(0.5); contourLineActor->GetProperty()->SetColor(0., 0., 0.); scalarBarActor->SetLookupTable(filledContourMapper->GetLookupTable()); scalarBarActor->SetNumberOfLabels(numberOfContours); scalarBarActor->SetOrientationToHorizontal(); scalarBarActor->SetPosition(0.05,0.2); scalarBarActor->SetWidth(0.9); scalarBarActor->SetHeight(0.05); scalarBarActor->SetDrawTickLabels(0); scalarBarActor->SetDrawAnnotations(1); scalarBarActor->GetAnnotationTextProperty()->SetFontFamilyToCourier(); //scalarBar->GetAnnotationTextProperty()->SetVerticalJustificationToCentered(); scalarBarActor->GetAnnotationTextProperty()->BoldOff(); scalarBarActor->GetAnnotationTextProperty()->ItalicOff(); scalarBarActor->GetAnnotationTextProperty()->ShadowOff() ; scalarBarActor->GetAnnotationTextProperty()->SetColor(0, 0, 0); scalarBarActor->GetAnnotationTextProperty()->SetJustificationToRight(); scalarBarActor->SetUseBounds(true); // cubeAxesActor->SetBounds(filledContourMapper->GetBounds()); cubeAxesActor->SetCamera(ren1->GetActiveCamera()); cubeAxesActor->GetTitleTextProperty(0)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->GetLabelTextProperty(0)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->GetTitleTextProperty(1)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->GetLabelTextProperty(1)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->DrawXGridlinesOn(); cubeAxesActor->DrawYGridlinesOn(); cubeAxesActor->DrawZGridlinesOff(); cubeAxesActor->GetXAxesLinesProperty()->SetColor(0.0, 0.0,0.0); cubeAxesActor->GetYAxesLinesProperty()->SetColor(0.0, 0.0,0.0); cubeAxesActor->GetYAxesGridlinesProperty ()->SetColor(0,0,0); cubeAxesActor->GetXAxesGridlinesProperty ()->SetColor(0,0,0); cubeAxesActor->SetTickLocationToOutside(); // cubeAxesActor->SetGridLineLocation(cubeAxesActor->VTK_GRID_LINES_CLOSEST); ren1->SetBackground(1, 1, 1); // Add the actors ren1->AddActor(filledContourActor); ren1->AddActor(contourLineActor); ren1->AddActor(scalarBarActor); // ren1->AddActor(cubeAxesActor); ren1->ResetCamera(); // VTK/Qt wedded ui->qvtkWidget->GetRenderWindow()->AddRenderer(ren1); ui->qvtkWidget->GetRenderWindow()->AddObserver(vtkCommand::ModifiedEvent,this,&RenderWindowUISingleInheritance::ModifiedHandler); // Set up action signals and slots connect(ui->actionExit, SIGNAL(triggered()), this, SLOT(slotExit())); } void RenderWindowUISingleInheritance::slotExit() { qApp->exit(); } RenderWindowUISingleInheritance::~RenderWindowUISingleInheritance() { delete ui; }; Do you have any suggestion? Thanks Mattia -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill.lorensen at gmail.com Mon Jul 3 10:41:37 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Mon, 3 Jul 2017 10:41:37 -0400 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems Message-ID: Please include vtk users mailing list... Also I've changed the subject... The gears have lots of long skinny triangles. I suspect this is causing problems with the boolean algorithm. Bill On Mon, Jul 3, 2017 at 2:36 AM, Nabil KHALIFA wrote: > Hi Bill, > > I have a problem about hole filling. > I want to apply boolean operation (subtraction) on meshes using VTK filter, > but i get an open mesh at the end. > I followed the example in the vtk examples using > BooleanOperationPolyDataFilter. > Do you have any idea on how to solve it. > Please find attached my input data and the output. > > Many thanks. > > On 2 July 2017 at 20:00, Bill Lorensen wrote: >> >> IF you see errors or improvemens please follow the procedure here: >> https://lorensen.github.io/VTKExamples/site/Instructions/ForDevelopers/ >> >> Also, tell all of your friends about the VTK Examples. >> https://lorensen.github.io/VTKExamples/site/ >> >> >> >> On Jul 2, 2017 1:55 PM, "oblakr" <2448.rok at gmail.com> wrote: >>> >>> Hi, >>> >>> this solves my problem. Thank you very much, very appreciated. >>> >>> Best regards, >>> Rok >>> >>> >>> >>> -- >>> View this message in context: >>> http://vtk.1045678.n5.nabble.com/Hole-filling-getting-individual-components-tp5743851p5743858.html >>> Sent from the VTK - Users mailing list archive at Nabble.com. >>> _______________________________________________ >>> 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 >> >> >> _______________________________________________ >> 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 >> > > > > -- > Nabil Khalifa -- Unpaid intern in BillsBasement at noware dot com From nabil.bhk at gmail.com Mon Jul 3 10:54:40 2017 From: nabil.bhk at gmail.com (Nabil KHALIFA) Date: Mon, 3 Jul 2017 16:54:40 +0200 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: Message-ID: so add new points and remesh could solve it? On 3 July 2017 at 16:41, Bill Lorensen wrote: > Please include vtk users mailing list... Also I've changed the subject... > > The gears have lots of long skinny triangles. I suspect this is > causing problems with the boolean algorithm. > > Bill > > > > On Mon, Jul 3, 2017 at 2:36 AM, Nabil KHALIFA wrote: > > Hi Bill, > > > > I have a problem about hole filling. > > I want to apply boolean operation (subtraction) on meshes using VTK > filter, > > but i get an open mesh at the end. > > I followed the example in the vtk examples using > > BooleanOperationPolyDataFilter. > > Do you have any idea on how to solve it. > > Please find attached my input data and the output. > > > > Many thanks. > > > > On 2 July 2017 at 20:00, Bill Lorensen wrote: > >> > >> IF you see errors or improvemens please follow the procedure here: > >> https://lorensen.github.io/VTKExamples/site/Instructions/ForDevelopers/ > >> > >> Also, tell all of your friends about the VTK Examples. > >> https://lorensen.github.io/VTKExamples/site/ > >> > >> > >> > >> On Jul 2, 2017 1:55 PM, "oblakr" <2448.rok at gmail.com> wrote: > >>> > >>> Hi, > >>> > >>> this solves my problem. Thank you very much, very appreciated. > >>> > >>> Best regards, > >>> Rok > >>> > >>> > >>> > >>> -- > >>> View this message in context: > >>> http://vtk.1045678.n5.nabble.com/Hole-filling-getting- > individual-components-tp5743851p5743858.html > >>> Sent from the VTK - Users mailing list archive at Nabble.com. > >>> _______________________________________________ > >>> 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 > >> > >> > >> _______________________________________________ > >> 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 > >> > > > > > > > > -- > > Nabil Khalifa > > > > -- > Unpaid intern in BillsBasement at noware dot com > -- Nabil Khalifa -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill.lorensen at gmail.com Mon Jul 3 10:55:47 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Mon, 3 Jul 2017 10:55:47 -0400 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: Message-ID: Maybe. On Mon, Jul 3, 2017 at 10:54 AM, Nabil KHALIFA wrote: > so add new points and remesh could solve it? > > On 3 July 2017 at 16:41, Bill Lorensen wrote: >> >> Please include vtk users mailing list... Also I've changed the subject... >> >> The gears have lots of long skinny triangles. I suspect this is >> causing problems with the boolean algorithm. >> >> Bill >> >> >> >> On Mon, Jul 3, 2017 at 2:36 AM, Nabil KHALIFA wrote: >> > Hi Bill, >> > >> > I have a problem about hole filling. >> > I want to apply boolean operation (subtraction) on meshes using VTK >> > filter, >> > but i get an open mesh at the end. >> > I followed the example in the vtk examples using >> > BooleanOperationPolyDataFilter. >> > Do you have any idea on how to solve it. >> > Please find attached my input data and the output. >> > >> > Many thanks. >> > >> > On 2 July 2017 at 20:00, Bill Lorensen wrote: >> >> >> >> IF you see errors or improvemens please follow the procedure here: >> >> https://lorensen.github.io/VTKExamples/site/Instructions/ForDevelopers/ >> >> >> >> Also, tell all of your friends about the VTK Examples. >> >> https://lorensen.github.io/VTKExamples/site/ >> >> >> >> >> >> >> >> On Jul 2, 2017 1:55 PM, "oblakr" <2448.rok at gmail.com> wrote: >> >>> >> >>> Hi, >> >>> >> >>> this solves my problem. Thank you very much, very appreciated. >> >>> >> >>> Best regards, >> >>> Rok >> >>> >> >>> >> >>> >> >>> -- >> >>> View this message in context: >> >>> >> >>> http://vtk.1045678.n5.nabble.com/Hole-filling-getting-individual-components-tp5743851p5743858.html >> >>> Sent from the VTK - Users mailing list archive at Nabble.com. >> >>> _______________________________________________ >> >>> 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 >> >> >> >> >> >> _______________________________________________ >> >> 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 >> >> >> > >> > >> > >> > -- >> > Nabil Khalifa >> >> >> >> -- >> Unpaid intern in BillsBasement at noware dot com > > > > > -- > Nabil Khalifa -- Unpaid intern in BillsBasement at noware dot com From lasso at queensu.ca Mon Jul 3 15:55:30 2017 From: lasso at queensu.ca (Andras Lasso) Date: Mon, 3 Jul 2017 19:55:30 +0000 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: , Message-ID: Unfortunately, these Boolean filters in VTK are not reliable. Result mesh contains errors - parts missing, strange shapes are added - maybe in about 10% of the cases, even if triangles are not particularly skinny. By slightly changing the inputs we sometimes get correct results. When we need something that works every time then we convert input meshes to images, perform Boolean operations on images, and convert the resulting image to mesh. Unfortunately, depending on the image resolution, this is a computationally expensive and somewhat lossy operation. Andras From: Bill Lorensen Sent: Monday, July 3, 2017 10:55 To: Nabil KHALIFA Cc: VTK Users Subject: Re: [vtkusers] BooleanOperationPolyDataFilter Problems Maybe. On Mon, Jul 3, 2017 at 10:54 AM, Nabil KHALIFA wrote: > so add new points and remesh could solve it? > > On 3 July 2017 at 16:41, Bill Lorensen wrote: >> >> Please include vtk users mailing list... Also I've changed the subject... >> >> The gears have lots of long skinny triangles. I suspect this is >> causing problems with the boolean algorithm. >> >> Bill >> >> >> >> On Mon, Jul 3, 2017 at 2:36 AM, Nabil KHALIFA wrote: >> > Hi Bill, >> > >> > I have a problem about hole filling. >> > I want to apply boolean operation (subtraction) on meshes using VTK >> > filter, >> > but i get an open mesh at the end. >> > I followed the example in the vtk examples using >> > BooleanOperationPolyDataFilter. >> > Do you have any idea on how to solve it. >> > Please find attached my input data and the output. >> > >> > Many thanks. >> > >> > On 2 July 2017 at 20:00, Bill Lorensen wrote: >> >> >> >> IF you see errors or improvemens please follow the procedure here: >> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Florensen.github.io%2FVTKExamples%2Fsite%2FInstructions%2FForDevelopers%2F&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=7TrWdbqhROVAZ%2FkirfbouGxWHK3ao42xSh78nQ8sSto%3D&reserved=0 >> >> >> >> Also, tell all of your friends about the VTK Examples. >> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Florensen.github.io%2FVTKExamples%2Fsite%2F&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=U6GgNwnVexHn7JpP0uCm8ASB3yveF2KvDKW7ueSZeHQ%3D&reserved=0 >> >> >> >> >> >> >> >> On Jul 2, 2017 1:55 PM, "oblakr" <2448.rok at gmail.com> wrote: >> >>> >> >>> Hi, >> >>> >> >>> this solves my problem. Thank you very much, very appreciated. >> >>> >> >>> Best regards, >> >>> Rok >> >>> >> >>> >> >>> >> >>> -- >> >>> View this message in context: >> >>> >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvtk.1045678.n5.nabble.com%2FHole-filling-getting-individual-components-tp5743851p5743858.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=sAthK51ooo%2Fi0UkieLq7iwb994ZAclIm%2FFippUm3lTA%3D&reserved=0 >> >>> Sent from the VTK - Users mailing list archive at Nabble.com. >> >>> _______________________________________________ >> >>> Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=MB6rWyBCbuekwXWN8Z1%2BsuRcF3qTV51vE0NstzloX%2Bk%3D&reserved=0 >> >>> >> >>> Visit other Kitware open-source projects at >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=hIDaAaAc5azASvnL3px8RMsZBulWgojg5kYctDjwqI8%3D&reserved=0 >> >>> >> >>> Please keep messages on-topic and check the VTK FAQ at: >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=l0AzlWmePhB8whpUIwLrz9sOp9uPltI3o0vAXo5r0hE%3D&reserved=0 >> >>> >> >>> Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=5Rs8GMP0wjoR4Nu5S62KkYwq8FAWrCuEsOZF09cjFZw%3D&reserved=0 >> >>> >> >>> Follow this link to subscribe/unsubscribe: >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=d3QJvJacVIEoT7GVeDkjR8HqEZvIX8xGkD7pKTYwgA4%3D&reserved=0 >> >> >> >> >> >> _______________________________________________ >> >> Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=MB6rWyBCbuekwXWN8Z1%2BsuRcF3qTV51vE0NstzloX%2Bk%3D&reserved=0 >> >> >> >> Visit other Kitware open-source projects at >> >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=hIDaAaAc5azASvnL3px8RMsZBulWgojg5kYctDjwqI8%3D&reserved=0 >> >> >> >> Please keep messages on-topic and check the VTK FAQ at: >> >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=g6u3xcPxGnENX4VNvfx56kdfVbostNPggk9%2FroN9vSo%3D&reserved=0 >> >> >> >> Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=ta72sZ4HGNzvBuhWyGKuEFULbtB%2BLwrP1gSwIY6iPpE%3D&reserved=0 >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=AoJCMaG12hkbcbj6g4dY71yAG9u3myNDgxpJgZyDTlU%3D&reserved=0 >> >> >> > >> > >> > >> > -- >> > Nabil Khalifa >> >> >> >> -- >> Unpaid intern in BillsBasement at noware dot com > > > > > -- > Nabil Khalifa -- Unpaid intern in BillsBasement at noware dot com _______________________________________________ Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=nqp4K6a9I2aXvXZ2t%2Bq3WVbgIGoy91wqbH65vYMj%2F7w%3D&reserved=0 Visit other Kitware open-source projects at https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=NqvtyqsJQgpmcTmzubWC864fWcHEp5W12SdZdX%2FrTFU%3D&reserved=0 Please keep messages on-topic and check the VTK FAQ at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=g6u3xcPxGnENX4VNvfx56kdfVbostNPggk9%2FroN9vSo%3D&reserved=0 Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=ta72sZ4HGNzvBuhWyGKuEFULbtB%2BLwrP1gSwIY6iPpE%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=AoJCMaG12hkbcbj6g4dY71yAG9u3myNDgxpJgZyDTlU%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nabil.bhk at gmail.com Mon Jul 3 16:41:20 2017 From: nabil.bhk at gmail.com (Nabil KHALIFA) Date: Mon, 3 Jul 2017 22:41:20 +0200 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: Message-ID: Thank you Andras for your reply. By the way, do you recommande any other library? On 3 July 2017 at 21:55, Andras Lasso wrote: > Unfortunately, these Boolean filters in VTK are not reliable. Result mesh > contains errors - parts missing, strange shapes are added - maybe in about > 10% of the cases, even if triangles are not particularly skinny. By > slightly changing the inputs we sometimes get correct results. > > > > When we need something that works every time then we convert input meshes > to images, perform Boolean operations on images, and convert the resulting > image to mesh. Unfortunately, depending on the image resolution, this is a > computationally expensive and somewhat lossy operation. > > > > Andras > > > > *From: *Bill Lorensen > *Sent: *Monday, July 3, 2017 10:55 > *To: *Nabil KHALIFA > *Cc: *VTK Users > *Subject: *Re: [vtkusers] BooleanOperationPolyDataFilter Problems > > > > > Maybe. > > > On Mon, Jul 3, 2017 at 10:54 AM, Nabil KHALIFA > wrote: > > so add new points and remesh could solve it? > > > > On 3 July 2017 at 16:41, Bill Lorensen wrote: > >> > >> Please include vtk users mailing list... Also I've changed the > subject... > >> > >> The gears have lots of long skinny triangles. I suspect this is > >> causing problems with the boolean algorithm. > >> > >> Bill > >> > >> > >> > >> On Mon, Jul 3, 2017 at 2:36 AM, Nabil KHALIFA > wrote: > >> > Hi Bill, > >> > > >> > I have a problem about hole filling. > >> > I want to apply boolean operation (subtraction) on meshes using VTK > >> > filter, > >> > but i get an open mesh at the end. > >> > I followed the example in the vtk examples using > >> > BooleanOperationPolyDataFilter. > >> > Do you have any idea on how to solve it. > >> > Please find attached my input data and the output. > >> > > >> > Many thanks. > >> > > >> > On 2 July 2017 at 20:00, Bill Lorensen > wrote: > >> >> > >> >> IF you see errors or improvemens please follow the procedure here: > >> >> https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Florensen.github.io%2FVTKExamples%2Fsite%2FInstructions% > 2FForDevelopers%2F&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534250463&sdata=7TrWdbqhROVAZ% > 2FkirfbouGxWHK3ao42xSh78nQ8sSto%3D&reserved=0 > >> >> > >> >> Also, tell all of your friends about the VTK Examples. > >> >> https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Florensen.github.io%2FVTKExamples%2Fsite%2F& > data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf% > 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata= > U6GgNwnVexHn7JpP0uCm8ASB3yveF2KvDKW7ueSZeHQ%3D&reserved=0 > >> >> > >> >> > >> >> > >> >> On Jul 2, 2017 1:55 PM, "oblakr" <2448.rok at gmail.com> wrote: > >> >>> > >> >>> Hi, > >> >>> > >> >>> this solves my problem. Thank you very much, very appreciated. > >> >>> > >> >>> Best regards, > >> >>> Rok > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> View this message in context: > >> >>> > >> >>> https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fvtk.1045678.n5.nabble.com%2FHole-filling- > getting-individual-components-tp5743851p5743858.html&data= > 02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf% > 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata= > sAthK51ooo%2Fi0UkieLq7iwb994ZAclIm%2FFippUm3lTA%3D&reserved=0 > >> >>> Sent from the VTK - Users mailing list archive at Nabble.com. > >> >>> _______________________________________________ > >> >>> Powered by https://na01.safelinks.protection.outlook.com/?url= > www.kitware.com&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534250463&sdata=MB6rWyBCbuekwXWN8Z1% > 2BsuRcF3qTV51vE0NstzloX%2Bk%3D&reserved=0 > >> >>> > >> >>> Visit other Kitware open-source projects at > >> >>> https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource. > html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf% > 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata= > hIDaAaAc5azASvnL3px8RMsZBulWgojg5kYctDjwqI8%3D&reserved=0 > >> >>> > >> >>> Please keep messages on-topic and check the VTK FAQ at: > >> >>> https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01% > 7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf% > 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata= > l0AzlWmePhB8whpUIwLrz9sOp9uPltI3o0vAXo5r0hE%3D&reserved=0 > >> >>> > >> >>> Search the list archives at: https://na01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org% > 2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534250463&sdata=5Rs8GMP0wjoR4Nu5S62KkYwq8FAWrC > uEsOZF09cjFZw%3D&reserved=0 > >> >>> > >> >>> Follow this link to subscribe/unsubscribe: > >> >>> https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo% > 2Fvtkusers&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534250463&sdata=d3QJvJacVIEoT7GVeDkjR8HqEZvIX8 > xGkD7pKTYwgA4%3D&reserved=0 > >> >> > >> >> > >> >> _______________________________________________ > >> >> Powered by https://na01.safelinks.protection.outlook.com/?url= > www.kitware.com&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534250463&sdata=MB6rWyBCbuekwXWN8Z1% > 2BsuRcF3qTV51vE0NstzloX%2Bk%3D&reserved=0 > >> >> > >> >> Visit other Kitware open-source projects at > >> >> https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource. > html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf% > 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata= > hIDaAaAc5azASvnL3px8RMsZBulWgojg5kYctDjwqI8%3D&reserved=0 > >> >> > >> >> Please keep messages on-topic and check the VTK FAQ at: > >> >> https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01% > 7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf% > 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata= > g6u3xcPxGnENX4VNvfx56kdfVbostNPggk9%2FroN9vSo%3D&reserved=0 > >> >> > >> >> Search the list archives at: https://na01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org% > 2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534260472&sdata=ta72sZ4HGNzvBuhWyGKuEFULbtB% > 2BLwrP1gSwIY6iPpE%3D&reserved=0 > >> >> > >> >> Follow this link to subscribe/unsubscribe: > >> >> https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo% > 2Fvtkusers&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534260472&sdata=AoJCMaG12hkbcbj6g4dY71yAG9u3my > NDgxpJgZyDTlU%3D&reserved=0 > >> >> > >> > > >> > > >> > > >> > -- > >> > Nabil Khalifa > >> > >> > >> > >> -- > >> Unpaid intern in BillsBasement at noware dot com > > > > > > > > > > -- > > Nabil Khalifa > > > > -- > Unpaid intern in BillsBasement at noware dot com > _______________________________________________ > Powered by https://na01.safelinks.protection.outlook.com/?url= > www.kitware.com&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534260472&sdata=nqp4K6a9I2aXvXZ2t% > 2Bq3WVbgIGoy91wqbH65vYMj%2F7w%3D&reserved=0 > > Visit other Kitware open-source projects at https://na01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com% > 2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534260472&sdata=NqvtyqsJQgpmcTmzubWC864fWcHEp5 > W12SdZdX%2FrTFU%3D&reserved=0 > > Please keep messages on-topic and check the VTK FAQ at: > https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01% > 7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf% > 7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata= > g6u3xcPxGnENX4VNvfx56kdfVbostNPggk9%2FroN9vSo%3D&reserved=0 > > Search the list archives at: https://na01.safelinks. > protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org% > 2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534260472&sdata=ta72sZ4HGNzvBuhWyGKuEFULbtB% > 2BLwrP1gSwIY6iPpE%3D&reserved=0 > > Follow this link to subscribe/unsubscribe: > https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo% > 2Fvtkusers&data=02%7C01%7Classo%40queensu.ca% > 7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b > 925c%7C1%7C0%7C636346905534260472&sdata=AoJCMaG12hkbcbj6g4dY71yAG9u3my > NDgxpJgZyDTlU%3D&reserved=0 > -- Nabil Khalifa -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaxellx at gmail.com Mon Jul 3 17:46:39 2017 From: xaxellx at gmail.com (Alexander Devaykin) Date: Mon, 3 Jul 2017 23:46:39 +0200 Subject: [vtkusers] How does VTK OSPRay-based volume rendering produce smooth images? Message-ID: Hello everyone, I wonder how does OSPRay-based volume renderer in VTK, used in ParaView, is able to produce volume images with smooth surface from the first pass (without buffer accumulation). OSPRay raw volume rendering e.g. using OSPRay demos, results in very densly sampled volumes. It looks like only one sample per voxel is taken which results in one pixel per voxel colored in the first pass at some regions (image 1). Only after several accumulation passes the rendering produces smooth image (image 3). In contrast to that, volume rendering in ParaView via OSPRay shows smooth image after first pass (image 4) with a little bit of densly sampled artifacts. It actually looks like no frames accumulation is active at all, because I no difference is visible between moving and resting camera. Zooming in also keeps the image smooth (image 5). Any articles or hints about what is going on behind the scenes? I'm digging into the VTK source code but no understanding so far. OSPRay seems to be configured just like I do in my application, but VTK seems to do the magic somewhere else. Screenshots or standalone OSPRay and ParaView-OSPRay renderings are attachend. Best Regards, Alexander Devaykin -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 1 - ospray.png Type: image/png Size: 168469 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2 - ospray_zoomin.png Type: image/png Size: 686835 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3 - osray_accumulated.png Type: image/png Size: 128333 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4 - paraview_ospray.png Type: image/png Size: 172406 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 5 - paraview_ospray_zoomin.png Type: image/png Size: 661160 bytes Desc: not available URL: From lasso at queensu.ca Mon Jul 3 18:50:42 2017 From: lasso at queensu.ca (Andras Lasso) Date: Mon, 3 Jul 2017 22:50:42 +0000 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: Message-ID: I don?t know about any good Boolean mesh operation implementation with BSD-type license. VTK got quite close to a working solution, so I think it would worth investing time into fixing the remaining problems. Although in the past couple of years many people wanted to use this feature, nobody had enough resources to get these problems fixed. Maybe some kind of crowdfunding scheme would work? Andras From: Nabil KHALIFA [mailto:nabil.bhk at gmail.com] Sent: Monday, July 3, 2017 4:41 PM To: Andras Lasso Cc: Bill Lorensen ; VTK Users Subject: Re: [vtkusers] BooleanOperationPolyDataFilter Problems Thank you Andras for your reply. By the way, do you recommande any other library? On 3 July 2017 at 21:55, Andras Lasso > wrote: Unfortunately, these Boolean filters in VTK are not reliable. Result mesh contains errors - parts missing, strange shapes are added - maybe in about 10% of the cases, even if triangles are not particularly skinny. By slightly changing the inputs we sometimes get correct results. When we need something that works every time then we convert input meshes to images, perform Boolean operations on images, and convert the resulting image to mesh. Unfortunately, depending on the image resolution, this is a computationally expensive and somewhat lossy operation. Andras From: Bill Lorensen Sent: Monday, July 3, 2017 10:55 To: Nabil KHALIFA Cc: VTK Users Subject: Re: [vtkusers] BooleanOperationPolyDataFilter Problems Maybe. On Mon, Jul 3, 2017 at 10:54 AM, Nabil KHALIFA > wrote: > so add new points and remesh could solve it? > > On 3 July 2017 at 16:41, Bill Lorensen > wrote: >> >> Please include vtk users mailing list... Also I've changed the subject... >> >> The gears have lots of long skinny triangles. I suspect this is >> causing problems with the boolean algorithm. >> >> Bill >> >> >> >> On Mon, Jul 3, 2017 at 2:36 AM, Nabil KHALIFA > wrote: >> > Hi Bill, >> > >> > I have a problem about hole filling. >> > I want to apply boolean operation (subtraction) on meshes using VTK >> > filter, >> > but i get an open mesh at the end. >> > I followed the example in the vtk examples using >> > BooleanOperationPolyDataFilter. >> > Do you have any idea on how to solve it. >> > Please find attached my input data and the output. >> > >> > Many thanks. >> > >> > On 2 July 2017 at 20:00, Bill Lorensen > wrote: >> >> >> >> IF you see errors or improvemens please follow the procedure here: >> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Florensen.github.io%2FVTKExamples%2Fsite%2FInstructions%2FForDevelopers%2F&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=7TrWdbqhROVAZ%2FkirfbouGxWHK3ao42xSh78nQ8sSto%3D&reserved=0 >> >> >> >> Also, tell all of your friends about the VTK Examples. >> >> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Florensen.github.io%2FVTKExamples%2Fsite%2F&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=U6GgNwnVexHn7JpP0uCm8ASB3yveF2KvDKW7ueSZeHQ%3D&reserved=0 >> >> >> >> >> >> >> >> On Jul 2, 2017 1:55 PM, "oblakr" <2448.rok at gmail.com> wrote: >> >>> >> >>> Hi, >> >>> >> >>> this solves my problem. Thank you very much, very appreciated. >> >>> >> >>> Best regards, >> >>> Rok >> >>> >> >>> >> >>> >> >>> -- >> >>> View this message in context: >> >>> >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvtk.1045678.n5.nabble.com%2FHole-filling-getting-individual-components-tp5743851p5743858.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=sAthK51ooo%2Fi0UkieLq7iwb994ZAclIm%2FFippUm3lTA%3D&reserved=0 >> >>> Sent from the VTK - Users mailing list archive at Nabble.com. >> >>> _______________________________________________ >> >>> Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=MB6rWyBCbuekwXWN8Z1%2BsuRcF3qTV51vE0NstzloX%2Bk%3D&reserved=0 >> >>> >> >>> Visit other Kitware open-source projects at >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=hIDaAaAc5azASvnL3px8RMsZBulWgojg5kYctDjwqI8%3D&reserved=0 >> >>> >> >>> Please keep messages on-topic and check the VTK FAQ at: >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=l0AzlWmePhB8whpUIwLrz9sOp9uPltI3o0vAXo5r0hE%3D&reserved=0 >> >>> >> >>> Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=5Rs8GMP0wjoR4Nu5S62KkYwq8FAWrCuEsOZF09cjFZw%3D&reserved=0 >> >>> >> >>> Follow this link to subscribe/unsubscribe: >> >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=d3QJvJacVIEoT7GVeDkjR8HqEZvIX8xGkD7pKTYwgA4%3D&reserved=0 >> >> >> >> >> >> _______________________________________________ >> >> Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=MB6rWyBCbuekwXWN8Z1%2BsuRcF3qTV51vE0NstzloX%2Bk%3D&reserved=0 >> >> >> >> Visit other Kitware open-source projects at >> >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534250463&sdata=hIDaAaAc5azASvnL3px8RMsZBulWgojg5kYctDjwqI8%3D&reserved=0 >> >> >> >> Please keep messages on-topic and check the VTK FAQ at: >> >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=g6u3xcPxGnENX4VNvfx56kdfVbostNPggk9%2FroN9vSo%3D&reserved=0 >> >> >> >> Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=ta72sZ4HGNzvBuhWyGKuEFULbtB%2BLwrP1gSwIY6iPpE%3D&reserved=0 >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=AoJCMaG12hkbcbj6g4dY71yAG9u3myNDgxpJgZyDTlU%3D&reserved=0 >> >> >> > >> > >> > >> > -- >> > Nabil Khalifa >> >> >> >> -- >> Unpaid intern in BillsBasement at noware dot com > > > > > -- > Nabil Khalifa -- Unpaid intern in BillsBasement at noware dot com _______________________________________________ Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=nqp4K6a9I2aXvXZ2t%2Bq3WVbgIGoy91wqbH65vYMj%2F7w%3D&reserved=0 Visit other Kitware open-source projects at https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=NqvtyqsJQgpmcTmzubWC864fWcHEp5W12SdZdX%2FrTFU%3D&reserved=0 Please keep messages on-topic and check the VTK FAQ at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=g6u3xcPxGnENX4VNvfx56kdfVbostNPggk9%2FroN9vSo%3D&reserved=0 Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=ta72sZ4HGNzvBuhWyGKuEFULbtB%2BLwrP1gSwIY6iPpE%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtkusers&data=02%7C01%7Classo%40queensu.ca%7Cbf27503aaa3f48e8f9c008d4c22399bf%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636346905534260472&sdata=AoJCMaG12hkbcbj6g4dY71yAG9u3myNDgxpJgZyDTlU%3D&reserved=0 -- Nabil Khalifa -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Mon Jul 3 19:30:57 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 3 Jul 2017 17:30:57 -0600 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: Message-ID: There is new boolean filter that has been sitting in an MR for a year now: https://gitlab.kitware.com/vtk/vtk/merge_requests/1752 I was asked to review it, but I don't do much mesh work. I've only written one mesh-generating algorithm in all my years with VTK. So if anyone is interested in getting a better boolean mesh filter into VTK, please try the one in the linked MR and let us know how well it works for you. - David On Mon, Jul 3, 2017 at 4:50 PM, Andras Lasso wrote: > I don?t know about any good Boolean mesh operation implementation with > BSD-type license. VTK got quite close to a working solution, so I think it > would worth investing time into fixing the remaining problems. > > > > Although in the past couple of years many people wanted to use this > feature, nobody had enough resources to get these problems fixed. Maybe > some kind of crowdfunding scheme would work? > > > > Andras > > > > *From:* Nabil KHALIFA [mailto:nabil.bhk at gmail.com] > *Sent:* Monday, July 3, 2017 4:41 PM > *To:* Andras Lasso > *Cc:* Bill Lorensen ; VTK Users > > > *Subject:* Re: [vtkusers] BooleanOperationPolyDataFilter Problems > > > > Thank you Andras for your reply. > > By the way, do you recommande any other library? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill.lorensen at gmail.com Mon Jul 3 19:44:21 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Mon, 3 Jul 2017 19:44:21 -0400 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: Message-ID: <08463BAC-C59C-4EDE-8A51-0F92C6584784@gmail.com> I'll take a look at this MR. I'll try it on the user's challenging data. Also, there is this one https://github.com/seanm/midas-journal-726 But it uses a gpled library. Could be a candidate for a Remote module. I remember I tried it a few years back and it performed pretty well. Sent from my iPad > On Jul 3, 2017, at 7:30 PM, David Gobbi wrote: > > There is new boolean filter that has been sitting in an MR for a year now: > https://gitlab.kitware.com/vtk/vtk/merge_requests/1752 > I was asked to review it, but I don't do much mesh work. I've only written one mesh-generating algorithm in all my years with VTK. > > So if anyone is interested in getting a better boolean mesh filter into VTK, please try the one in the linked MR and let us know how well it works for you. > > - David > > >> On Mon, Jul 3, 2017 at 4:50 PM, Andras Lasso wrote: >> I don?t know about any good Boolean mesh operation implementation with BSD-type license. VTK got quite close to a working solution, so I think it would worth investing time into fixing the remaining problems. >> >> >> >> Although in the past couple of years many people wanted to use this feature, nobody had enough resources to get these problems fixed. Maybe some kind of crowdfunding scheme would work? >> >> >> >> Andras >> >> >> >> From: Nabil KHALIFA [mailto:nabil.bhk at gmail.com] >> Sent: Monday, July 3, 2017 4:41 PM >> To: Andras Lasso >> Cc: Bill Lorensen ; VTK Users >> >> >> Subject: Re: [vtkusers] BooleanOperationPolyDataFilter Problems >> >> >> Thank you Andras for your reply. >> >> By the way, do you recommande any other library? >> > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rustem.khabetdinov at gmail.com Tue Jul 4 09:15:38 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Tue, 4 Jul 2017 16:15:38 +0300 Subject: [vtkusers] Question about visualization Message-ID: Hello, Is there any way to visualize set of eigenvalues/eigenvectors using vtk? For example, I have this data: eigenvalues = (-22812140527.70874, -17173061888.51663 ,577143888297.0613) eigenvectors = (-0.50657551, 0.04671729, -0.860929), (-0.01544831, -0.99886247, -0.04511221),(0.86205719, 0.00955284, -0.50672097) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Tue Jul 4 09:54:26 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 4 Jul 2017 06:54:26 -0700 (MST) Subject: [vtkusers] Control VTK frame rate Message-ID: <1499176466330-5743876.post@n5.nabble.com> I had rendered actors to the render window. As I increase the number of actors the frame rate decreases and the rendering is slow. Is there any possible way to set the frame rate or increase the rendering speed as the number of actors increase. I tried to use ImmediateRenderingMode but I could not find any difference in rendering speed/ Frame Rate. I am trying to move the actor based on the input which is generated every millisecond i.e 1000 datapoints for 1 second and apply it to the actors to make a rotation. Sample code that I use: vtkSource s = new vtksource; vtktransform t = new vtktransform; vtktransformpolydatafilter tf = new vtktransformpolydatafilter; tf->setinputconnection(s->getoutputport()); tf->settransform(t); vtkpolydatamapper map = new vtkpolydatamapper; map->setinputconnection(tf->getoutputport()); vtkactor act = new vtkactor; act->setmapper(map); while(true) { t->Identity(); t->RotateZ(SomeInputData); // SomeInputData changes every millisecond and transform is in a loop t->update(); renderer->addActor(act); renderer->modified(); renderWindow->render(); } As the number of actors rendered to the same window increases the frame rate decreases. I used renderer->GetLastRenderTimeInSeconds(); to get the frame rate (i.e 1/time) Any solutions or suggestions would be helpful. Thanks for taking time to read the post. Regards, Kay -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876.html Sent from the VTK - Users mailing list archive at Nabble.com. From longbowzhangchina at gmail.com Tue Jul 4 11:44:14 2017 From: longbowzhangchina at gmail.com (longbowzhang) Date: Tue, 4 Jul 2017 08:44:14 -0700 (MST) Subject: [vtkusers] Question about visualization In-Reply-To: References: Message-ID: <1499183054490-5743877.post@n5.nabble.com> Basically you try to visualize a 3-by-3 symmetric matrix. The natural choice is to use an ellipsoid. Unfortunately, you have *negative* eigenvalues. Therefore, the most elegant visualization should be this SuperquadricTensorGlyph . The code is based on OpenGL, rather than VTK. Hope this could help or inspire you to some extent. Longbow -- View this message in context: http://vtk.1045678.n5.nabble.com/Question-about-visualization-tp5743875p5743877.html Sent from the VTK - Users mailing list archive at Nabble.com. From elvis.stansvik at orexplore.com Tue Jul 4 12:24:43 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Tue, 4 Jul 2017 18:24:43 +0200 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <1499176466330-5743876.post@n5.nabble.com> References: <1499176466330-5743876.post@n5.nabble.com> Message-ID: Den 4 juli 2017 3:54 em skrev "kay" : > > I had rendered actors to the render window. As I increase the number of > actors the frame rate decreases and the rendering is slow. Is there any > possible way to set the frame rate or increase the rendering speed as the > number of actors increase. > > I tried to use ImmediateRenderingMode but I could not find any difference in > rendering speed/ Frame Rate. > > I am trying to move the actor based on the input which is generated every > millisecond i.e 1000 datapoints for 1 second and apply it to the actors to > make a rotation. Why do you need such a high frame rate? I don't think a human can really perceive any differences at such high rates. 60 FPS or so is normally the target to strive for (with monitors). Elvis > > Sample code that I use: > > vtkSource s = new vtksource; > vtktransform t = new vtktransform; > vtktransformpolydatafilter tf = new vtktransformpolydatafilter; > tf->setinputconnection(s->getoutputport()); > tf->settransform(t); > vtkpolydatamapper map = new vtkpolydatamapper; > map->setinputconnection(tf->getoutputport()); > vtkactor act = new vtkactor; > act->setmapper(map); > while(true) > { > t->Identity(); > t->RotateZ(SomeInputData); // SomeInputData changes every millisecond and > transform is in a loop > t->update(); > renderer->addActor(act); > renderer->modified(); > renderWindow->render(); > } > > As the number of actors rendered to the same window increases the frame rate > decreases. > I used renderer->GetLastRenderTimeInSeconds(); to get the frame rate (i.e > 1/time) > > Any solutions or suggestions would be helpful. > Thanks for taking time to read the post. > > Regards, > Kay > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From f2014141 at pilani.bits-pilani.ac.in Tue Jul 4 12:25:13 2017 From: f2014141 at pilani.bits-pilani.ac.in (Rishabh Mittar) Date: Tue, 4 Jul 2017 21:55:13 +0530 Subject: [vtkusers] Error While Building VTK 8 with Oculus SDK In-Reply-To: References: Message-ID: Thanks David, that did the trick. However,while I was testing with the TestDragon example, the example built successfully and while running the exe I got the following errors on the vtkOutput Window: WARNING :In C:\VTK\src\IO\PLY\vtkPLYReader.cxx,line 126 vtkPLYReader(004F5C00): Could not open PLY file ERROR:In C:\VTK\src\Common\ExecutionModel\vtkExecutive.cxx,line 784 vtkCompositeDataPipeline(00513938):Algorithm vtkPLYReader(004F5C00) returned failure for request:vtkInformation(00531CA8) Debug:Off Modified Time:1033 Reference Count:1 Registered Events:(none) Request:REQUEST_DATA FORWARD_DIRECTION:0 FROM_OUTPUT_PORT: ALGORITHM_AFTER_FORWARD:1 ERROR:In C:\VTK\src\Rendering\Oculus\vtkOculusRenderWindow.cxx,line 354 vtkOculusRenderWindow(004FF050):Failed to create LibOVR session This is how my call to Open the file looks like: const char* fileName = vtkTestUtilities::ExpandDataFileName( argc, argv, "C:/Users/User/Desktop/TestDragon/src/dragon.ply"); Have also tried: const char* fileName = vtkTestUtilities::ExpandDataFileName( argc, argv, "dragon.ply"); But I still get the same result. I am using the file dragon.ply file from https://midas3.kitware.com/midas/download/?items=318673,1 Any ideas on how what is the issue? -- Rishabh Mittar On Jun 30, 2017 11:52 PM, "David E DeMarle" wrote: > Build VTK in release mode. To do so, under ninja, cmake configure your VTK > build tree with CMAKE_BUILD_TYPE=Release. Or under visual studio choose > release in the Visual Studio UI after the cmake config when you open up the > vtk solution. > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 <(518)%20881-4909> > > On Fri, Jun 30, 2017 at 2:14 PM, Rishabh Mittar < > f2014141 at pilani.bits-pilani.ac.in> wrote: > >> Hello vtkusers, >> >> I am trying to build VTK 8.0 with Oculus SDK on Windows. >> >> While building the Solution file on Visual Studio, I am getting the >> following errors: >> >> error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' >> doesn't match value '2' in vtkOculusCamera.obj >> C:\VTK_OCULUS\bin\Rendering\Oculus\LibOVR.lib(OVR_CAPI_Util.obj) >> >> Error 3 error LNK2038: mismatch detected for 'RuntimeLibrary': value >> 'MT_StaticRelease' doesn't match value 'MDd_DynamicDebug' in >> vtkOculusCamera.obj >> C:\VTK_OCULUS\bin\Rendering\Oculus\LibOVR.lib(OVR_CAPI_Util.obj) >> >> I researched a bit and found out that the problem is due to the Oculus >> SDK having a 'release' build and VTK requires a 'debug' version. >> However I am unable to figure out a solution to the problem. >> I am using VTK 8.0.0 and Oculus windows release 1.15.0 from >> >> https://developer.oculus.com/downloads/native-windows/ >> >> I am using Visual Studio 2013 to build the solution file. >> Can anyone suggest a way out? >> >> -- >> Rishabh Mittar >> >> _______________________________________________ >> 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 >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Tue Jul 4 12:33:18 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 4 Jul 2017 09:33:18 -0700 (MST) Subject: [vtkusers] Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> Message-ID: <1499185998567-5743880.post@n5.nabble.com> By rendering more number of actor, I get a frame rate of 7-9 but i am trying to improve it to 12-14. And I get no where near 60 FPS though my display settings are set to 60. At frame rate of 7-9 and 12-14 there is huge visible difference, which I am trying to improve. I think I use more than sufficient hardware configuration. My hardware configuration 32GB RAM, 4GB NVIDIA M2000M Graphic Card, Core-7i processor Regards -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743880.html Sent from the VTK - Users mailing list archive at Nabble.com. From dave.demarle at kitware.com Tue Jul 4 12:56:09 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 4 Jul 2017 12:56:09 -0400 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <1499185998567-5743880.post@n5.nabble.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> Message-ID: Make sure you are using the openGL2 backend. More importantly, avoid using multiple actors. They are heavyweight objects and won't support high rates for more than perhaps a few hundred instances. Instead use appendpolydata or something similar to bring everything together into one or a handful of actors. On Jul 4, 2017 12:33 PM, "kay" wrote: > By rendering more number of actor, I get a frame rate of 7-9 but i am > trying > to improve it to 12-14. And I get no where near 60 FPS though my display > settings are set to 60. At frame rate of 7-9 and 12-14 there is huge > visible > difference, which I am trying to improve. > > I think I use more than sufficient hardware configuration. My hardware > configuration 32GB RAM, 4GB NVIDIA M2000M Graphic Card, Core-7i processor > > Regards > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Control-VTK-frame-rate-tp5743876p5743880.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Tue Jul 4 14:23:12 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 4 Jul 2017 11:23:12 -0700 (MST) Subject: [vtkusers] Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> Message-ID: <1499192592082-5743882.post@n5.nabble.com> I am using the latest version of OpenGL backend. I could consider combining polydata to use fewer actors as you suggested. But each of the actor perform transforms like rotation and translation independently of other. Regards -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743882.html Sent from the VTK - Users mailing list archive at Nabble.com. From elvis.stansvik at orexplore.com Tue Jul 4 15:09:56 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Tue, 4 Jul 2017 21:09:56 +0200 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <1499185998567-5743880.post@n5.nabble.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> Message-ID: 2017-07-04 18:33 GMT+02:00 kay : > By rendering more number of actor, I get a frame rate of 7-9 but i am trying > to improve it to 12-14. And I get no where near 60 FPS though my display > settings are set to 60. At frame rate of 7-9 and 12-14 there is huge visible > difference, which I am trying to improve. Your display settings have nothing to do with how well VTK can perform. What I meant was: Why are you moving your actor at such a high frequency (1000 times per second)? To me it doesn't make sense to try to move it that often (you're probably swamping VTK with render requests). I would try to move it maybe 60 times per second, or at least in that ballpark. Where are these high frequency events coming from? If you by any chance is using Qt 5.5, and these are mouse/touch events, you could be suffering from QTBUG-40889 (fixed in 5.6). Elvis > > I think I use more than sufficient hardware configuration. My hardware > configuration 32GB RAM, 4GB NVIDIA M2000M Graphic Card, Core-7i processor > > Regards > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743880.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 From xoviat at tamu.edu Tue Jul 4 16:06:07 2017 From: xoviat at tamu.edu (Geoffrey Garner) Date: Tue, 4 Jul 2017 15:06:07 -0500 Subject: [vtkusers] Possible to load VTK file from memory? Message-ID: <595bf52e.48cdca0a.4a3d0.a342@mx.google.com> All: Is it possible to load a VTK from memory (string), or would I need to implement a new reader class for this? Regards, Geoffrey -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Tue Jul 4 16:26:37 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 4 Jul 2017 13:26:37 -0700 (MST) Subject: [vtkusers] Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> Message-ID: <1499199997785-5743885.post@n5.nabble.com> My Input data is generated by the realtime system, so the high frequency of data. But the VTK application I am trying to build is not a real time system. To explain further, the pseudo code that I posted before works by calling render in a loop. double realTimevariable; // This variable is updated by the real time system every millisecond while(true) { t->Identity(); t->RotateZ(realTimevariable); // realTimevariable takes the value at this point of time t->update(); renderer->addActor(act); renderer->modified(); renderWindow->render(); } Each time the loop is run value of the realTimeVariable is taken from the memory at that instance of time. This process works for less number of actors and frame rate is 12-14, but if the actors are doubled the frame rate goes down by 7-9 which is visible to the eye. From what I understand, this looping of render call (renderWindow->Render();) is what you mentioned "swamping VTK with render requests", Please correct me if I am wrong. And I dont want to control data to 60 times per second, as I want VTK to render as often as it can (Minimum of 12 FPS) I am not using QT, just basic vtk pipeline in C++. -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743885.html Sent from the VTK - Users mailing list archive at Nabble.com. From bill.lorensen at gmail.com Tue Jul 4 16:30:57 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Tue, 4 Jul 2017 16:30:57 -0400 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <1499199997785-5743885.post@n5.nabble.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> Message-ID: How many actors do you have? On Jul 4, 2017 4:26 PM, "kay" wrote: > My Input data is generated by the realtime system, so the high frequency of > data. But the VTK application I am trying to build is not a real time > system. To explain further, the pseudo code that I posted before works by > calling render in a loop. > > double realTimevariable; // This variable is updated by the real time > system > every millisecond > while(true) > { > t->Identity(); > t->RotateZ(realTimevariable); // realTimevariable takes the value at > this > point of time > t->update(); > renderer->addActor(act); > renderer->modified(); > renderWindow->render(); > } > > Each time the loop is run value of the realTimeVariable is taken from the > memory at that instance of time. > This process works for less number of actors and frame rate is 12-14, but > if > the actors are doubled the frame rate goes down by 7-9 which is visible to > the eye. From what I understand, this looping of render call > (renderWindow->Render();) is what you mentioned "swamping VTK with render > requests", Please correct me if I am wrong. > > And I dont want to control data to 60 times per second, as I want VTK to > render as often as it can (Minimum of 12 FPS) > > I am not using QT, just basic vtk pipeline in C++. > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Control-VTK-frame-rate-tp5743876p5743885.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Tue Jul 4 16:35:16 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 4 Jul 2017 13:35:16 -0700 (MST) Subject: [vtkusers] Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> Message-ID: <1499200516699-5743887.post@n5.nabble.com> If I use 120 Actors I get a frame rate of 12-14, but if I use more than 240 I get a frame rate of 7-9 And all the actors are loaded from STL/OBJ files Regards Kay -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743887.html Sent from the VTK - Users mailing list archive at Nabble.com. From bill.lorensen at gmail.com Tue Jul 4 16:54:17 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Tue, 4 Jul 2017 16:54:17 -0400 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <1499200516699-5743887.post@n5.nabble.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> Message-ID: Do they all change during the simulation? Sent from my iPad > On Jul 4, 2017, at 4:35 PM, kay wrote: > > If I use 120 Actors I get a frame rate of 12-14, > but if I use more than 240 I get a frame rate of 7-9 > > And all the actors are loaded from STL/OBJ files > > Regards > Kay > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743887.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 From jayavardhanravi at outlook.com Tue Jul 4 16:56:35 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 4 Jul 2017 13:56:35 -0700 (MST) Subject: [vtkusers] Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> Message-ID: <1499201795505-5743889.post@n5.nabble.com> The actors are loaded with data from STL/OBJ files only once, but the transform like rotation are make the actors to change every time the loop is run. -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743889.html Sent from the VTK - Users mailing list archive at Nabble.com. From sean at rogue-research.com Tue Jul 4 16:57:01 2017 From: sean at rogue-research.com (Sean McBride) Date: Tue, 4 Jul 2017 16:57:01 -0400 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: <08463BAC-C59C-4EDE-8A51-0F92C6584784@gmail.com> References: <08463BAC-C59C-4EDE-8A51-0F92C6584784@gmail.com> Message-ID: <20170704205701.374780187@mail.rogue-research.com> On Mon, 3 Jul 2017 19:44:21 -0400, Bill Lorensen said: >Also, there is this one >https://github.com/seanm/midas-journal-726 >But it uses a gpled library. Could be a candidate for a Remote module. I >remember I tried it a few years back and it performed pretty well. I don't recommend it. It depends on libGTS, which, besides licensing issues, has not seen a release in over 10 years: There's clearly no future there. :( Besides, we were using it, and found it crashed a lot. We've had better luck with VTK's class, but it too crashes on occasion and gives wrong results. 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 bill.lorensen at gmail.com Tue Jul 4 17:13:12 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Tue, 4 Jul 2017 17:13:12 -0400 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: <20170704205701.374780187@mail.rogue-research.com> References: <08463BAC-C59C-4EDE-8A51-0F92C6584784@gmail.com> <20170704205701.374780187@mail.rogue-research.com> Message-ID: <4F472638-8D47-48E3-B06D-D39BABF41A40@gmail.com> Sean, Thanks for the evaluation. I agree. I think the LoopBoolean looks like a good way to go. Sent from my iPad > On Jul 4, 2017, at 4:57 PM, Sean McBride wrote: > > On Mon, 3 Jul 2017 19:44:21 -0400, Bill Lorensen said: > >> Also, there is this one >> https://github.com/seanm/midas-journal-726 >> But it uses a gpled library. Could be a candidate for a Remote module. I >> remember I tried it a few years back and it performed pretty well. > > I don't recommend it. It depends on libGTS, which, besides licensing issues, has not seen a release in over 10 years: > > > > There's clearly no future there. :( Besides, we were using it, and found it crashed a lot. We've had better luck with VTK's class, but it too crashes on occasion and gives wrong results. > > 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 bill.lorensen at gmail.com Tue Jul 4 17:16:18 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Tue, 4 Jul 2017 17:16:18 -0400 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <1499201795505-5743889.post@n5.nabble.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> Message-ID: <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> Are they transformed independently or in unison? Also, how is the transformed applied? In the pipeline, or directly to the actor? Sent from my iPad > On Jul 4, 2017, at 4:56 PM, kay wrote: > > The actors are loaded with data from STL/OBJ files only once, but the > transform like rotation are make the actors to change every time the loop is > run. > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743889.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 From jayavardhanravi at outlook.com Tue Jul 4 17:18:53 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 4 Jul 2017 14:18:53 -0700 (MST) Subject: [vtkusers] Control VTK frame rate In-Reply-To: <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> Message-ID: <1499203133740-5743893.post@n5.nabble.com> Transforms are independent and are applied directly to the actor -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743893.html Sent from the VTK - Users mailing list archive at Nabble.com. From bill.lorensen at gmail.com Tue Jul 4 17:32:42 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Tue, 4 Jul 2017 17:32:42 -0400 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> Message-ID: <482BD2B0-016B-49FF-8996-C59B6AB53340@gmail.com> That seems to rule out Appending the models. Are you using SetUserMatrix on the actors? Also, use a SetInputData on the mappers after Updating the last filters in the pipeline. Sent from my iPad > On Jul 4, 2017, at 5:16 PM, Bill Lorensen wrote: > > Are they transformed independently or in unison? Also, how is the transformed applied? In the pipeline, or directly to the actor? > > Sent from my iPad > >> On Jul 4, 2017, at 4:56 PM, kay wrote: >> >> The actors are loaded with data from STL/OBJ files only once, but the >> transform like rotation are make the actors to change every time the loop is >> run. >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743889.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 From david.thompson at kitware.com Tue Jul 4 17:42:05 2017 From: david.thompson at kitware.com (David Thompson) Date: Tue, 4 Jul 2017 17:42:05 -0400 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <482BD2B0-016B-49FF-8996-C59B6AB53340@gmail.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> <482BD2B0-016B-49FF-8996-C59B6AB53340@gmail.com> Message-ID: <8B94F360-6181-49A8-8DE0-CF1D1DC0E79E@kitware.com> Hi all, You might try the vtkGlyph3DMapper. It can take in a bunch of "source" polydata objects plus a set of points with point-data specifying orientation, scaling, and the index of which polydata to draw at each point. More recently, David Lonie added a way for it to take in a multiblock dataset and let each point specify the index of a top-level block to render (again, with point-data specifying per-instance transforms). That would leave you with a single actor and an easy way to update per-instance transforms. David > On Jul 4, 2017, at 5:32 PM, Bill Lorensen wrote: > > That seems to rule out Appending the models. Are you using SetUserMatrix on the actors? Also, use a SetInputData on the mappers after Updating the last filters in the pipeline. > > Sent from my iPad > >> On Jul 4, 2017, at 5:16 PM, Bill Lorensen wrote: >> >> Are they transformed independently or in unison? Also, how is the transformed applied? In the pipeline, or directly to the actor? >> >> Sent from my iPad >> >>> On Jul 4, 2017, at 4:56 PM, kay wrote: >>> >>> The actors are loaded with data from STL/OBJ files only once, but the >>> transform like rotation are make the actors to change every time the loop is >>> run. >>> >>> >>> >>> -- >>> View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743889.html >>> Sent from the VTK - Users mailing list archive at Nabble.com. >>> _______________________________________________ >>> 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 > _______________________________________________ > 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 From siva.yedithi at gmail.com Tue Jul 4 18:38:35 2017 From: siva.yedithi at gmail.com (Neel Patel 0-0-0) Date: Tue, 4 Jul 2017 15:38:35 -0700 (MST) Subject: [vtkusers] problems with multithreading in VTK with winforms Message-ID: <1499207915344-5743896.post@n5.nabble.com> Hello all. I have a couple problems trying to do multithreading with VTK using winforms. Currently I have a form with a pictureBox and a RenderControlWindow, where the pictureBox is used for streaming data while the RenderWindow is used to display images on the side. From some previous reading, I've tried to implement a solution where updates to my image are done on one thread and the rendering is done on the main form thread. The problem is that when I try to re-render the window itself doesn't change. Some code below, at least what I think might be relevant can post more if need be. Update Thread: vtkImageImport imageImport = null; o = new Thread(() => { byte[] myByteArray = new byte[data.Size]; int idx = 0; for (int k = 0; k < D; k++) { for (int j = 0; j < H; j++) { for (int i = 0; i < W; i++) { idx = k * W * H + j * W + i; myByteArray[idx] = (byte)data.Get(idx); } } } // Copy byte array into VTK // Based on: http://stackoverflow.com/questions/31670753/use-c-sharp-byte-image-data-in-vtk vtkUnsignedCharArray myCharArray = vtkUnsignedCharArray.New(); GCHandle gPointer = GCHandle.Alloc(myByteArray, GCHandleType.Pinned); // Import image data imageImport = vtkImageImport.New(); imageImport.SetDataSpacing(1, 1, 1); imageImport.SetDataOrigin(0, 0, 0); imageImport.SetDataExtent(0, W - 1, 0, H - 1, 0, D - 1); imageImport.SetWholeExtent(0, W - 1, 0, H - 1, 0, D - 1); imageImport.SetDataScalarTypeToUnsignedChar(); imageImport.SetNumberOfScalarComponents(1); imageImport.SetImportVoidPointer(gPointer.AddrOfPinnedObject()); imageImport.Update(); if (InvokeRequired) { this.Invoke(new Action(() => renderInMain())); Thread.Sleep(1000); } }); o.Start(); } Rendering Method called in main thread: public void renderInMain() { lock (_lock) { vtkRenderer renderer = renderWindowControl1.RenderWindow.GetRenderers().GetFirstRenderer(); vtkImageActor actor = vtkImageActor.New(); vtkMatrix4x4 resliceAxes = vtkMatrix4x4.New(); vtkImageReslice reslice = vtkImageReslice.New(); vtkLookupTable table = vtkLookupTable.New(); renderer.RemoveAllViewProps(); //renderer.Modified(); //renderer.Render(); // Get extent and calculate the center of the volume int[] extent = imageImport.GetOutput().GetWholeExtent(); double[] spacing = imageImport.GetOutput().GetSpacing(); double[] origin = imageImport.GetOutput().GetOrigin(); double[] center = new double[3]; center[0] = origin[0] + spacing[0] * 0.5 * (extent[0] + extent[1]); center[1] = origin[1] + spacing[1] * 0.5 * (extent[2] + extent[3]); center[2] = origin[2] + spacing[2] * 0.5 * (extent[4] + extent[5]); // Matrices for axial, coronal, sagittal, oblique view orientations double[] axialElements = { 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1 }; double[] coronalElements = { 1, 0, 0, 0, 0, 0, 1, 0, 0,-1, 0, 0, 0, 0, 0, 1 }; double[] sagittalElements = { 0, 0,-1, 0, 1, 0, 0, 0, 0,-1, 0, 0, 0, 0, 0, 1 }; double[] obliqueElements = { 1, 0, 0, 0, 0, 0.866025, -0.5, 0, 0, 0.5, 0.866025, 0, 0, 0, 0, 1 }; // Set the slice orientation GCHandle sagittalElements_ptr = GCHandle.Alloc(coronalElements, GCHandleType.Pinned); resliceAxes.DeepCopy(sagittalElements_ptr.AddrOfPinnedObject()); Thread.Sleep(1000); // Set the point through which to slice resliceAxes.SetElement(0, 3, center[0]); resliceAxes.SetElement(1, 3, center[1]); resliceAxes.SetElement(2, 3, center[2]); resliceAxes.Modified(); Thread.Sleep(1000); // Extract a slice in the desired orientation reslice.SetInputConnection(imageImport.GetOutputPort()); reslice.SetOutputDimensionality(2); reslice.SetResliceAxes(resliceAxes); reslice.SetInterpolationModeToLinear(); reslice.Modified(); Thread.Sleep(1000); // Create a greyscale lookup table table.SetRange(0, 255); // image intensity range table.SetValueRange(0.0, 1); // from black to white table.SetSaturationRange(0.0, 0.0); // no color saturation table.SetRampToLinear(); table.Build(); // Map the image through the lookup table vtkImageMapToColors color = vtkImageMapToColors.New(); color.SetLookupTable(table); color.SetInputConnection(reslice.GetOutputPort()); // Display the image actor.SetInput(color.GetOutput()); actor.Modified(); Console.WriteLine("Exit"); Thread.Sleep(1000); // Set up renderer //if (renderFlag == 1) //{ renderer.ResetCamera(); renderer.AddActor(actor); renderer.SetBackground(0, 0, 0); renderer.Modified(); renderer.Render(); } } Another curious thing is that if I run this normally the renderWindow doesn't change, but if I run it while debugging it seems to work fine and the window changes to what it should be. Any help or insight would be greatly appreciated. Thanks! Regards, Neel -- View this message in context: http://vtk.1045678.n5.nabble.com/problems-with-multithreading-in-VTK-with-winforms-tp5743896.html Sent from the VTK - Users mailing list archive at Nabble.com. From girish.lande at agiliad.com Wed Jul 5 00:58:21 2017 From: girish.lande at agiliad.com (Girish Lande) Date: Wed, 5 Jul 2017 10:28:21 +0530 Subject: [vtkusers] dynamic sectioning class Message-ID: Hi Experts, Is there any class in VTK library which provides dynamic sectioning for selected object (such as 3D Image volume data or Surface objects). Dynamic sectioning is used to create a section through a part/ assembly. This can be useful when you have a complex project and want to see hidden details. Clicking on different surfaces on the 3D model allows us to view the section from different angles. Left clicking and holding on the red cross representation allows the plane of the section to be moved to different depths. For e.g See attached images. -- thanks & regards, Girish -- ------------------------------------------------------------ ------------------------------------------------------------- *Disclaimer:* This email message including any attachments is confidential, and may be privileged and proprietary to Agiliad. If you are not the intended recipient, please notify us immediately by replying to this message and destroy all copies of this message including any attachments. You are NOT authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. Thank you. ------------------------------------------------------------ ------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Sect-View-1.png Type: image/png Size: 4638 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Sect-View-3.png Type: image/png Size: 9159 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Sect-View-4.png Type: image/png Size: 7144 bytes Desc: not available URL: From f2014141 at pilani.bits-pilani.ac.in Wed Jul 5 02:43:10 2017 From: f2014141 at pilani.bits-pilani.ac.in (Rishabh Mittar) Date: Wed, 5 Jul 2017 12:13:10 +0530 Subject: [vtkusers] Error While Building VTK 8 with Oculus SDK In-Reply-To: References: Message-ID: Directly put the file path in reader->SetFileName(); And it removed the error. However it is still giving the Failed to Create LibOVR session error, even though it is launching the Oculus App at the background. Any thoughts? -- Rishabh Mittar On Jul 4, 2017 9:55 PM, "Rishabh Mittar" wrote: > Thanks David, that did the trick. > > However,while I was testing with the TestDragon example, the example built > successfully and while running the exe I got the following errors on the > vtkOutput Window: > > WARNING :In C:\VTK\src\IO\PLY\vtkPLYReader.cxx,line 126 > vtkPLYReader(004F5C00): Could not open PLY file > > ERROR:In C:\VTK\src\Common\ExecutionModel\vtkExecutive.cxx,line 784 > vtkCompositeDataPipeline(00513938):Algorithm vtkPLYReader(004F5C00) > returned failure for request:vtkInformation(00531CA8) > Debug:Off > Modified Time:1033 > Reference Count:1 > Registered Events:(none) > Request:REQUEST_DATA > FORWARD_DIRECTION:0 > FROM_OUTPUT_PORT: > ALGORITHM_AFTER_FORWARD:1 > > ERROR:In C:\VTK\src\Rendering\Oculus\vtkOculusRenderWindow.cxx,line 354 > vtkOculusRenderWindow(004FF050):Failed to create LibOVR session > > This is how my call to Open the file looks like: > const char* fileName = > vtkTestUtilities::ExpandDataFileName( > argc, argv, "C:/Users/User/Desktop/TestDragon/src/dragon.ply"); > > Have also tried: > const char* fileName = > vtkTestUtilities::ExpandDataFileName( > argc, argv, "dragon.ply"); > > But I still get the same result. > I am using the file dragon.ply file from > https://midas3.kitware.com/midas/download/?items=318673,1 > > Any ideas on how what is the issue? > > > > -- > Rishabh Mittar > > > > > > > > On Jun 30, 2017 11:52 PM, "David E DeMarle" > wrote: > >> Build VTK in release mode. To do so, under ninja, cmake configure your >> VTK build tree with CMAKE_BUILD_TYPE=Release. Or under visual studio choose >> release in the Visual Studio UI after the cmake config when you open up the >> vtk solution. >> >> David E DeMarle >> Kitware, Inc. >> Principal Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 <(518)%20881-4909> >> >> On Fri, Jun 30, 2017 at 2:14 PM, Rishabh Mittar < >> f2014141 at pilani.bits-pilani.ac.in> wrote: >> >>> Hello vtkusers, >>> >>> I am trying to build VTK 8.0 with Oculus SDK on Windows. >>> >>> While building the Solution file on Visual Studio, I am getting the >>> following errors: >>> >>> error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' >>> doesn't match value '2' in vtkOculusCamera.obj >>> C:\VTK_OCULUS\bin\Rendering\Oculus\LibOVR.lib(OVR_CAPI_Util.obj) >>> >>> Error 3 error LNK2038: mismatch detected for 'RuntimeLibrary': value >>> 'MT_StaticRelease' doesn't match value 'MDd_DynamicDebug' in >>> vtkOculusCamera.obj >>> C:\VTK_OCULUS\bin\Rendering\Oculus\LibOVR.lib(OVR_CAPI_Util.obj) >>> >>> I researched a bit and found out that the problem is due to the Oculus >>> SDK having a 'release' build and VTK requires a 'debug' version. >>> However I am unable to figure out a solution to the problem. >>> I am using VTK 8.0.0 and Oculus windows release 1.15.0 from >>> >>> https://developer.oculus.com/downloads/native-windows/ >>> >>> I am using Visual Studio 2013 to build the solution file. >>> Can anyone suggest a way out? >>> >>> -- >>> Rishabh Mittar >>> >>> _______________________________________________ >>> 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 >>> >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From kor1581 at gmail.com Wed Jul 5 07:24:39 2017 From: kor1581 at gmail.com (K O ranjith) Date: Wed, 5 Jul 2017 16:54:39 +0530 Subject: [vtkusers] Multiview port dicom viewer zoom in problem Message-ID: Hello, I have created a multi view port (6 viewports in one window) mri dicom viewer for displaying a list of DICOM files in a single window in Qt. I used vtkDICOMReader, vtkImageActor, vtkImageSliceMapper and QVTKWidget. The DICOM images are displaying as expected but have two issues. 1) Main issue is, while zooming in the images in view ports, after a particular level of zoom the images disappearing. But after zoom out to the previous particular level the image reappearing again. This happening in case of all the view ports. Also no issue for zoom out. 2) The images are displaying in smaller size than the view ports size. Why this happening? Please help.. My code something like this, and attached few screen shots vtkSmartPointer m_vtkDcmDir; vtkSmartPointer m_vtkDcmRdr vtkSmartPointer::New(); vtkSmartPointer m_aVtkStrFNames; QVTKWidget m_vtkWgtWin; m_vtkWgtWin = new QVTKWidget(); m_vtkDcmDir->SetDirectoryName("E:/Projects/mri/evaluate/Qt/ImageViewer/VTK/VTKtest/ReadDICOM/DICOMSeries"); m_vtkDcmDir->*Update*(); // Iterate through all of the studies that are present. m_iNoStudies = m_vtkDcmDir->GetNumberOfStudies(); for(int i = 0; i < m_iNoStudies; i++) { int j1 = m_vtkDcmDir ->GetFirstSeriesForStudy(i); int j2 = m_vtkDcmDir ->GetLastSeriesForStudy(i); for (int j = j1; j <= j2; j++) { m_aVtkStrFNames = m_vtkDcmDir->GetFileNamesForSeries(j); // do something with the files m_vtkDcmRdr ->*SetFileNames*(m_aVtkStrFNames); m_vtkDcmRdr ->*Update*(); } } // Define viewport ranges double xmins[6] = {0, .33, .66, 0, .33, .66}; double xmaxs[6] = {.33, .66, 1, .33, .66, 1}; double ymins[6] = {0, 0, 0, .5, .5, .5}; double ymaxs[6]= {.5, .5, .5, 1, 1, 1}; for(unsigned i = 0; i < 6; i++) { vtkSmartPointer imageActor = vtkSmartPointer< vtkImageActor>::New(); imageActor->*SetInputData*(m_vtkDcmRdr->GetOutput()); vtkSmartPointer imageMapper = vtkImageSliceMapper::SafeDownCast(imageActor->*GetMapper*()); imageActor->SetMapper(imageMapper); imageMapper->SetInputData(m_vtkDcmRdr->GetOutput()); imageMapper->*SetSliceNumber*(i+1); vtkSmartPointer vtkRen = vtkSmartPointer::New(); vtkRen->*SetViewport*(xmins[i],ymins[i],xmaxs[i],ymaxs[i]); vtkRen->AddActor(imageActor); vtkRen->*ResetCamera*(); m_vtkWgtWin->*GetRenderWindow*()->*AddRenderer*(vtkRen); } m_vtkWgtWin->*GetRenderWindow*()->*Render*(); m_vtkWgtWin->update(); m_vtkWgtWin->show(); -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: after_zoomin.jpg Type: image/jpeg Size: 325586 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: While_starting.jpg Type: image/jpeg Size: 315847 bytes Desc: not available URL: From updega2 at berkeley.edu Wed Jul 5 07:42:28 2017 From: updega2 at berkeley.edu (updega2) Date: Wed, 5 Jul 2017 04:42:28 -0700 (MST) Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: <4F472638-8D47-48E3-B06D-D39BABF41A40@gmail.com> References: <08463BAC-C59C-4EDE-8A51-0F92C6584784@gmail.com> <20170704205701.374780187@mail.rogue-research.com> <4F472638-8D47-48E3-B06D-D39BABF41A40@gmail.com> Message-ID: <1499254948035-5743900.post@n5.nabble.com> Hi, I authored the LoopBoolean a few years ago because we wanted a more reliable vtk-based boolean to use in our software. I've mentioned this before I believe on the merge requests, but I think it may be helpful to say it again here. When the booleans fail (current and the LoopBoolean), it is typically during re-triangulation due to vtkDelaunay2D. I developed the LoopBoolean using vtk 6.0. After vtk 6.0, some changes were made to the vtkDelaunay2D code, which caused many more issues in the LoopBoolean. I tried working with the vtkDelaunay2D author to fix some of the Delaunay bugs, and we got a couple fixed, but a few remain. So, in our software, we actually have a copy of the vtkDelaunay2D code from the vtk 6.0 pipeline, and the LoopBoolean calls that. The code works well for our purposes. It still isn't bug free as the code is tolerance-based, and there are orientation tests that may fail from time to time due to tolerance issues. Also, I'll admit that error checking could be better. I would like to go back and improve this part of the code, but haven't had the time yet. Adam -- View this message in context: http://vtk.1045678.n5.nabble.com/BooleanOperationPolyDataFilter-Problems-tp5743863p5743900.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Wed Jul 5 08:29:33 2017 From: ken.martin at kitware.com (Ken Martin) Date: Wed, 5 Jul 2017 08:29:33 -0400 Subject: [vtkusers] Control VTK frame rate In-Reply-To: <1499203133740-5743893.post@n5.nabble.com> References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> <1499203133740-5743893.post@n5.nabble.com> Message-ID: That doesn't seem to match the pseudo code you posted, where the transform is applied to a filter (shared by all the actors, well the only actor). Maybe an updated bit of pseudo code would help. In general with lots of actors you want to make sure mapper->StaticOn(); and ren->RemoveCuller(ren->GetCullers()->GetLastItem()); make sure it is a release build, and make sure your transformation is happening on the actor, not a filter such as trransformpolydata. On Tue, Jul 4, 2017 at 5:18 PM, kay wrote: > Transforms are independent and are applied directly to the actor > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Control-VTK-frame-rate-tp5743876p5743893.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 dave.demarle at kitware.com Wed Jul 5 09:09:18 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 5 Jul 2017 09:09:18 -0400 Subject: [vtkusers] Possible to load VTK file from memory? In-Reply-To: <595bf52e.48cdca0a.4a3d0.a342@mx.google.com> References: <595bf52e.48cdca0a.4a3d0.a342@mx.google.com> Message-ID: The *.vtk (legacy) and *.vt? (xml) readers should support this via SetInputString and ReadFromInputStringOn() methods from their parent classes. Other file formats that vtk has readers for may or may not have the capability yet. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 <(518)%20881-4909> On Tue, Jul 4, 2017 at 4:06 PM, Geoffrey Garner wrote: > All: > > > > Is it possible to load a VTK from memory (string), or would I need to > implement a new reader class for this? > > > > > > Regards, > > > > > > Geoffrey > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Wed Jul 5 10:04:37 2017 From: jayavardhanravi at outlook.com (kay) Date: Wed, 5 Jul 2017 07:04:37 -0700 (MST) Subject: [vtkusers] Control VTK frame rate In-Reply-To: References: <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> <1499203133740-5743893.post@n5.nabble.com> Message-ID: <1499263477439-5743904.post@n5.nabble.com> Thank you Ken Martin. I could not post all the code, as the system is huge. Sorry that I missed some parts in pseudo code. Hope you understand. Making these changes had increased the frame rate from 7-9 to 16-17. This fixed the low frame rate. You post has really helped me Thank you Ken Martin for the time Regards, Kay -- View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743904.html Sent from the VTK - Users mailing list archive at Nabble.com. From elvis.stansvik at orexplore.com Wed Jul 5 11:39:35 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Wed, 5 Jul 2017 17:39:35 +0200 Subject: [vtkusers] Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> <1499203133740-5743893.post@n5.nabble.com> Message-ID: Den 5 juli 2017 2:29 em skrev "Ken Martin" : > > That doesn't seem to match the pseudo code you posted, where the transform is applied to a filter (shared by all the actors, well the only actor). Maybe an updated bit of pseudo code would help. The code snippet confuses me as well, since it looks like a new actor is added to the renderer in each iteration of the while(true). If that's true, the number of actors would grow fast and unboundedly. Unless I'm missing something here. Elvis > > In general with lots of actors you want to make sure > > mapper->StaticOn(); > > and > > ren->RemoveCuller(ren->GetCullers()->GetLastItem()); > > make sure it is a release build, and make sure your transformation is happening on the actor, not a filter such as trransformpolydata. > > > > On Tue, Jul 4, 2017 at 5:18 PM, kay wrote: >> >> Transforms are independent and are applied directly to the actor >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743893.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 > > > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > 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 > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Wed Jul 5 11:41:06 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 5 Jul 2017 09:41:06 -0600 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: <1499254948035-5743900.post@n5.nabble.com> References: <08463BAC-C59C-4EDE-8A51-0F92C6584784@gmail.com> <20170704205701.374780187@mail.rogue-research.com> <4F472638-8D47-48E3-B06D-D39BABF41A40@gmail.com> <1499254948035-5743900.post@n5.nabble.com> Message-ID: The instability of vtkDelaunay2D is definitely a problem for these kinds of filters. It isn't just a matter of vtkDelaunay2D having bugs... the problem is that in order for the algorithm to be robust, it must use exact math. So a lot of the work that has gone into fixing bugs seems to have just changed the situations that cause it to crash. A few years ago I wrote a filter called vtkContourTriangulator that can sometimes be used as a stable replacement for vtkDelaunay2D. However, vtkContourTriangulator is not as fast as vtkDelaunay2D, nor does it produce high-quality triangles (i.e. it does triangulation, but not Delaunay triangulation). - David On Wed, Jul 5, 2017 at 5:42 AM, updega2 wrote: > Hi, I authored the LoopBoolean a few years ago because we wanted a more > reliable vtk-based boolean to use in our software. > > I've mentioned this before I believe on the merge requests, but I think it > may be helpful to say it again here. When the booleans fail (current and > the > LoopBoolean), it is typically during re-triangulation due to vtkDelaunay2D. > I developed the LoopBoolean using vtk 6.0. After vtk 6.0, some changes were > made to the vtkDelaunay2D code, which caused many more issues in the > LoopBoolean. I tried working with the vtkDelaunay2D author to fix some of > the Delaunay bugs, and we got a couple fixed, but a few remain. > > So, in our software, we actually have a copy of the vtkDelaunay2D code from > the vtk 6.0 pipeline, and the LoopBoolean calls that. The code works well > for our purposes. It still isn't bug free as the code is tolerance-based, > and there are orientation tests that may fail from time to time due to > tolerance issues. Also, I'll admit that error checking could be better. I > would like to go back and improve this part of the code, but haven't had > the > time yet. > > Adam > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/ > BooleanOperationPolyDataFilter-Problems-tp5743863p5743900.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Jul 5 11:46:46 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 5 Jul 2017 11:46:46 -0400 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: <08463BAC-C59C-4EDE-8A51-0F92C6584784@gmail.com> <20170704205701.374780187@mail.rogue-research.com> <4F472638-8D47-48E3-B06D-D39BABF41A40@gmail.com> <1499254948035-5743900.post@n5.nabble.com> Message-ID: > > A few years ago I wrote a filter called vtkContourTriangulator that can > sometimes be used as a stable replacement for vtkDelaunay2D. However, > vtkContourTriangulator is not as fast as vtkDelaunay2D, nor does it produce > high-quality triangles (i.e. it does triangulation, but not Delaunay > triangulation). > It's worth mentioning that I quickly tried swapping vtkContourTriangulator in place of vtkDelaunay2D a while back, but didn't quite get it to work. I didn't spend a lot of time on it, though, so it may be worth investigating again if someone wants to try. The quality of the triangles isn't that important for the boolean operations IMHO, and you can get some high-aspect ratio triangles with the constrained Delaunay triangulation that the boolean operation filters currently use. - Cory > - David > > On Wed, Jul 5, 2017 at 5:42 AM, updega2 wrote: > >> Hi, I authored the LoopBoolean a few years ago because we wanted a more >> reliable vtk-based boolean to use in our software. >> >> I've mentioned this before I believe on the merge requests, but I think it >> may be helpful to say it again here. When the booleans fail (current and >> the >> LoopBoolean), it is typically during re-triangulation due to >> vtkDelaunay2D. >> I developed the LoopBoolean using vtk 6.0. After vtk 6.0, some changes >> were >> made to the vtkDelaunay2D code, which caused many more issues in the >> LoopBoolean. I tried working with the vtkDelaunay2D author to fix some of >> the Delaunay bugs, and we got a couple fixed, but a few remain. >> >> So, in our software, we actually have a copy of the vtkDelaunay2D code >> from >> the vtk 6.0 pipeline, and the LoopBoolean calls that. The code works well >> for our purposes. It still isn't bug free as the code is tolerance-based, >> and there are orientation tests that may fail from time to time due to >> tolerance issues. Also, I'll admit that error checking could be better. I >> would like to go back and improve this part of the code, but haven't had >> the >> time yet. >> >> Adam >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.c >> om/BooleanOperationPolyDataFilter-Problems-tp5743863p5743900.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> > > > _______________________________________________ > 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 > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean at rogue-research.com Wed Jul 5 11:52:40 2017 From: sean at rogue-research.com (Sean McBride) Date: Wed, 5 Jul 2017 11:52:40 -0400 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: References: Message-ID: <20170705155240.363916148@mail.rogue-research.com> On Mon, 3 Jul 2017 22:50:42 +0000, Andras Lasso said: >Although in the past couple of years many people wanted to use this >feature, nobody had enough resources to get these problems fixed. Maybe >some kind of crowdfunding scheme would work? We (Rogue Research) spoke to Kitware about contracting them to get BooleanOperationPolyDataFilter working better. I've been waiting for my boss to send off the paperwork... I'll give him a kick today, as I'd really like to see this class working better! :) 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 nabil.bhk at gmail.com Wed Jul 5 14:32:21 2017 From: nabil.bhk at gmail.com (Nabil KHALIFA) Date: Wed, 5 Jul 2017 20:32:21 +0200 Subject: [vtkusers] BooleanOperationPolyDataFilter Problems In-Reply-To: <20170705155240.363916148@mail.rogue-research.com> References: <20170705155240.363916148@mail.rogue-research.com> Message-ID: That's great to hear! On 5 Jul 2017 5:52 p.m., "Sean McBride" wrote: > On Mon, 3 Jul 2017 22:50:42 +0000, Andras Lasso said: > > >Although in the past couple of years many people wanted to use this > >feature, nobody had enough resources to get these problems fixed. Maybe > >some kind of crowdfunding scheme would work? > > We (Rogue Research) spoke to Kitware about contracting them to get > BooleanOperationPolyDataFilter working better. I've been waiting for my > boss to send off the paperwork... I'll give him a kick today, as I'd really > like to see this class working better! :) > > Cheers, > > -- > ____________________________________________________________ > Sean McBride, B. Eng sean at rogue-research.com > Rogue Research www.rogue-research.com > Mac Software Developer Montr?al, Qu?bec, Canada > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mpreisig at geomod.ch Thu Jul 6 02:55:48 2017 From: mpreisig at geomod.ch (Matthias Preisig) Date: Thu, 6 Jul 2017 08:55:48 +0200 Subject: [vtkusers] vtkInteractorStyleRubberBandPick: Set selection mode without pressing key Message-ID: The class vtkInteractorStyleRubberBandPick allows selection of a rectangular window, when 'r' is pressed, and selection of a 1x1 window, when 'p' is pressed. 1) Is there a way to get the key that is currently pressed (the current selection mode)? 2) Is it possible to set the selection mode 'r' or 'p' in the code (i'm using pyqt and would like to choose the mode by checking a box in a gui)? Matthias -------------- next part -------------- An HTML attachment was scrubbed... URL: From kor1581 at gmail.com Thu Jul 6 08:02:18 2017 From: kor1581 at gmail.com (K O ranjith) Date: Thu, 6 Jul 2017 17:32:18 +0530 Subject: [vtkusers] How to get mouse button details from vtkInteractorStyleImage Message-ID: Hello, I'm inheriting vtkInteractorStyleImage for customizing mouse events in an image viewer. In vtkInteractorStyleImage, have any method to get the details of which mouse button is pressed(Left/ Right/Middle) like GetKeySym() for keyborad keys. I know about the virtual functions like OnRightButtonDown (). Have any direct way to get from the vtkInteractorStyleImage object...? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Thu Jul 6 08:15:47 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 6 Jul 2017 08:15:47 -0400 Subject: [vtkusers] How does VTK OSPRay-based volume rendering produce smooth images? In-Reply-To: References: Message-ID: Most likely the only difference is that VTK sets up OSPRay's volume sampling differently than the OSPRay demos do. You will find how it is setup here: https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/OSPRay/vtkOSPRayVolumeMapperNode.cxx#L255 Note also: starting with ParaView 5.3, if you start ParaView with --enable-streaming, and set "Progressive Passes" on the Properties panel to something higher than one, ParaView will do progressive refinement like you see in the OSPRay demos. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Jul 3, 2017 at 5:46 PM, Alexander Devaykin wrote: > Hello everyone, > > I wonder how does OSPRay-based volume renderer in VTK, used in ParaView, > is able to produce volume images with smooth surface from the first pass > (without buffer accumulation). > > OSPRay raw volume rendering e.g. using OSPRay demos, results in very > densly sampled volumes. It looks like only one sample per voxel is taken > which results in one pixel per voxel colored in the first pass at some > regions (image 1). Only after several accumulation passes the rendering > produces smooth image (image 3). > > In contrast to that, volume rendering in ParaView via OSPRay shows smooth > image after first pass (image 4) with a little bit of densly sampled > artifacts. It actually looks like no frames accumulation is active at all, > because I no difference is visible between moving and resting camera. > Zooming in also keeps the image smooth (image 5). > > Any articles or hints about what is going on behind the scenes? I'm > digging into the VTK source code but no understanding so far. OSPRay seems > to be configured just like I do in my application, but VTK seems to do the > magic somewhere else. > > Screenshots or standalone OSPRay and ParaView-OSPRay renderings are > attachend. > > Best Regards, > Alexander Devaykin > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron.helser at kitware.com Thu Jul 6 11:41:07 2017 From: aron.helser at kitware.com (Aron Helser) Date: Thu, 6 Jul 2017 11:41:07 -0400 Subject: [vtkusers] Compatible version of Twisted and AutobahnPython for vtkWeb in VTK 8.0.0 In-Reply-To: <1498783427165.58560@sphic.org.cn> References: <1498783427165.58560@sphic.org.cn> Message-ID: Hi! VTK uses a 'third-party' repo with an import of some other libraries. You can look there for specific versions that match different VTK versions. VTK 8 uses a pretty up-to-date Twisted (17.1 or 2?) but a much older Autobahn with some Python 3 compatibility code back-ported. Here's the repos: https://gitlab.kitware.com/third-party Regards, Aron On Thu, Jun 29, 2017 at 8:43 PM, ??? wrote: > Hi all, > > > I'd like to know what is the compatible version of Twisted and > AutobahnPython for vtkWeb in VTK 8.0.0. Thanks in advance. > > > > Regards, > > > Zhuangming Shen > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From milefn at rpi.edu Thu Jul 6 15:30:52 2017 From: milefn at rpi.edu (Milef, Nicholas Boris) Date: Thu, 6 Jul 2017 19:30:52 +0000 Subject: [vtkusers] Separating actors for different render passes Message-ID: Is there currently a way to separate actors into custom render passes? If I'm not mistaken, opaque objects currently get rendered before translucent objects, but is there a way to add additional geometry passes (or before opaque geometry, or between translucent and opaque geometry, etc.)? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Thu Jul 6 16:18:14 2017 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 6 Jul 2017 16:18:14 -0400 Subject: [vtkusers] Separating actors for different render passes In-Reply-To: References: Message-ID: With the render passes you can setup as many passes as you want in whatever order you want. This shows an example where the render process is all driven by passes. https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/OpenGL2/Testing/Cxx/TestSobelGradientMagnitudePass.cxx As an example for shadow maps when needed we use nested opaque passes to render the scene from the view of the light sources which we then use in another opaque pass to compute lighting from the view of the camera. Render passes also have hooks that mappers call so that passes can modify the mapper shader code etc while executing. Passes can also use information properties on actors to filter them in other passes. For example an outer render pass can add information on actors that causes some of them to not be rendered (or to be rendered differently) by other passes ala // ---------------------------------------------------------------------------- // Description: // Opaque pass with key checking. // \pre s_exists: s!=0 void vtkDefaultPass::RenderFilteredOpaqueGeometry(const vtkRenderState *s) { assert("pre: s_exists" && s!=0); int c=s->GetPropArrayCount(); int i=0; while(iGetPropArray()[i]; if(p->HasKeys(s->GetRequiredKeys())) { int rendered= p->RenderFilteredOpaqueGeometry(s->GetRenderer(),s->GetRequiredKeys()); this->NumberOfRenderedProps+=rendered; } ++i; } } On Thu, Jul 6, 2017 at 3:30 PM, Milef, Nicholas Boris wrote: > Is there currently a way to separate actors into custom render passes? If > I'm not mistaken, opaque objects currently get rendered before translucent > objects, but is there a way to add additional geometry passes (or before > opaque geometry, or between translucent and opaque geometry, etc.)? > > _______________________________________________ > 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 > > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 adarshdesai.dsp at gmail.com Fri Jul 7 00:12:58 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Thu, 6 Jul 2017 21:12:58 -0700 Subject: [vtkusers] VTK planeWidget using call back or overriden function Message-ID: Hi, I want to use VTK plane to cut the polydata using mouse. CUrrently I can place the plane and cut the polydata using the plane using some keypress. Now i want to use the Plane widget and as soon as i stop placing the plane near the polydata, the plane should cut it. I have tried with Callback with LeftButtonRelease event , and OverRiding the LeftButtonUp methods. But these methods are not working correctly. Anyone with a good idea? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.dura at ibv.upv.es Fri Jul 7 07:44:50 2017 From: juan.dura at ibv.upv.es (juanibv) Date: Fri, 7 Jul 2017 04:44:50 -0700 (MST) Subject: [vtkusers] Sort vtkPoints by one coordinate Message-ID: <1499427890601-5743925.post@n5.nabble.com> Points have 3 coordinates: (x,y,z) Is there a simplest method for sorting vtkPoints by one coordinate? e.g. y -- View this message in context: http://vtk.1045678.n5.nabble.com/Sort-vtkPoints-by-one-coordinate-tp5743925.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Fri Jul 7 08:48:04 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 7 Jul 2017 08:48:04 -0400 Subject: [vtkusers] Fwd: Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> <1499203133740-5743893.post@n5.nabble.com> <65D987BE62E58141AA480A59A8B5BBEA79D904D0@srv-mail.diana.local> Message-ID: On list in case it use useful to others ---------- Forwarded message ---------- From: Ken Martin Date: Fri, Jul 7, 2017 at 8:47 AM Subject: Re: [vtkusers] Control VTK frame rate To: Andreas Buykx The default culler checks the bounding box of every actor/prop and if they are outside of the view frustum it does not render them. So the performance question becomes: is checking the actor's bounding box (with the pipeline mtime check) faster than the time savings of sometimes not rendering the actor? So when the actors will all typically be visible and there are lots of them (or their filter pipelines are long) removing the culler can save time because you may be CPU bound on checking pipeline mtime. Oddly enough checking pipeline mtime can be fairly time consuming for lots of pipelines/actors. So making the mapper static and removing the culler basically cuts out all pipeline mtime checks reducing the CPU load which with a fast GPU the CPU can often be the bottleneck for lots of VTK actors. On Fri, Jul 7, 2017 at 5:07 AM, Andreas Buykx wrote: > Hi, could you please explain what the removal of the last culler is about? > In what situations is it needed? I looked in the VTK7.1.0 and found that a > small number of tests does this but do not understand why it is needed in > these tests and not in others. > > > > Thanks a lot, > > Andreas Buykx > > > > *From:* vtkusers [mailto:vtkusers-bounces at vtk.org] *On Behalf Of *Ken > Martin > *Sent:* Wednesday, July 05, 2017 2:30 PM > *To:* kay > *Cc:* vtk > *Subject:* Re: [vtkusers] Control VTK frame rate > > > > That doesn't seem to match the pseudo code you posted, where the transform > is applied to a filter (shared by all the actors, well the only actor). > Maybe an updated bit of pseudo code would help. > > > > In general with lots of actors you want to make sure > > > > mapper->StaticOn(); > > > > and > > > > ren->RemoveCuller(ren->GetCullers()->GetLastItem()); > > > > make sure it is a release build, and make sure your transformation is > happening on the actor, not a filter such as trransformpolydata. > > > > > > > > On Tue, Jul 4, 2017 at 5:18 PM, kay wrote: > > Transforms are independent and are applied directly to the actor > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.c > om/Control-VTK-frame-rate-tp5743876p5743893.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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 > > > > > > -- > > Ken Martin PhD > > Distinguished Engineer > Kitware Inc. > > 28 Corporate Drive > Clifton Park NY 12065 > > > > 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. > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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. -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 cory.quammen at kitware.com Fri Jul 7 09:32:03 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 7 Jul 2017 09:32:03 -0400 Subject: [vtkusers] Fwd: Control VTK frame rate In-Reply-To: References: <1499176466330-5743876.post@n5.nabble.com> <1499185998567-5743880.post@n5.nabble.com> <1499199997785-5743885.post@n5.nabble.com> <1499200516699-5743887.post@n5.nabble.com> <1499201795505-5743889.post@n5.nabble.com> <16D8F5D0-5FD7-45A5-90E9-B4696B834A8A@gmail.com> <1499203133740-5743893.post@n5.nabble.com> <65D987BE62E58141AA480A59A8B5BBEA79D904D0@srv-mail.diana.local> Message-ID: Ken, That's great info to know. Thanks, Cory On Fri, Jul 7, 2017 at 8:48 AM, Ken Martin wrote: > On list in case it use useful to others > > > ---------- Forwarded message ---------- > From: Ken Martin > Date: Fri, Jul 7, 2017 at 8:47 AM > Subject: Re: [vtkusers] Control VTK frame rate > To: Andreas Buykx > > > The default culler checks the bounding box of every actor/prop and if they > are outside of the view frustum it does not render them. So the performance > question becomes: > > is checking the actor's bounding box (with the pipeline mtime check) faster > than the time savings of sometimes not rendering the actor? > > So when the actors will all typically be visible and there are lots of them > (or their filter pipelines are long) removing the culler can save time > because you may be CPU bound on checking pipeline mtime. Oddly enough > checking pipeline mtime can be fairly time consuming for lots of > pipelines/actors. So making the mapper static and removing the culler > basically cuts out all pipeline mtime checks reducing the CPU load which > with a fast GPU the CPU can often be the bottleneck for lots of VTK actors. > > > > On Fri, Jul 7, 2017 at 5:07 AM, Andreas Buykx wrote: >> >> Hi, could you please explain what the removal of the last culler is about? >> In what situations is it needed? I looked in the VTK7.1.0 and found that a >> small number of tests does this but do not understand why it is needed in >> these tests and not in others. >> >> >> >> Thanks a lot, >> >> Andreas Buykx >> >> >> >> From: vtkusers [mailto:vtkusers-bounces at vtk.org] On Behalf Of Ken Martin >> Sent: Wednesday, July 05, 2017 2:30 PM >> To: kay >> Cc: vtk >> Subject: Re: [vtkusers] Control VTK frame rate >> >> >> >> That doesn't seem to match the pseudo code you posted, where the transform >> is applied to a filter (shared by all the actors, well the only actor). >> Maybe an updated bit of pseudo code would help. >> >> >> >> In general with lots of actors you want to make sure >> >> >> >> mapper->StaticOn(); >> >> >> >> and >> >> >> >> ren->RemoveCuller(ren->GetCullers()->GetLastItem()); >> >> >> >> make sure it is a release build, and make sure your transformation is >> happening on the actor, not a filter such as trransformpolydata. >> >> >> >> >> >> >> >> On Tue, Jul 4, 2017 at 5:18 PM, kay wrote: >> >> Transforms are independent and are applied directly to the actor >> >> >> >> -- >> View this message in context: >> http://vtk.1045678.n5.nabble.com/Control-VTK-frame-rate-tp5743876p5743893.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> >> >> >> >> >> -- >> >> Ken Martin PhD >> >> Distinguished Engineer >> Kitware Inc. >> >> 28 Corporate Drive >> Clifton Park NY 12065 >> >> >> >> 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. > > > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > 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. > > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > 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 > > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From majid.msadeghi at yahoo.com Fri Jul 7 13:28:54 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Fri, 7 Jul 2017 17:28:54 +0000 (UTC) Subject: [vtkusers] vtkcutter and vtkimagereslice? References: <209719412.760480.1499448534584.ref@mail.yahoo.com> Message-ID: <209719412.760480.1499448534584@mail.yahoo.com> Dear All, Can I use vtkcutter (or any other method) to get a slice of a vtkpolydata (for slicing MRI volume to get 2D), the way vtkimagereslice gives output form a volume Image data? The reason I want to be able to reslice polydata is that later I want to do other operations on it. Thanks for the help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From adarshdesai.dsp at gmail.com Fri Jul 7 14:53:23 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Fri, 7 Jul 2017 11:53:23 -0700 Subject: [vtkusers] VtkPlaneWidget handles disappear Message-ID: Hi I am using vtkPlanewidget , but once the next frame is loaded its handles disappear. it will appear only if i call Off() method and On() method the problem is, I am using them with callback, hence once i press mouse, entire widget will disappear for Off() and appears for On(). I want the handles to be available for all frames. is there a way just to turn on handles every frame? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andx_roo at live.com Fri Jul 7 20:53:51 2017 From: Andx_roo at live.com (Andaharoo) Date: Fri, 7 Jul 2017 17:53:51 -0700 (MST) Subject: [vtkusers] Using Volume Renderings Piecewise opacity function with vtkImageViewer2 Message-ID: <1499475231119-5743930.post@n5.nabble.com> Currently I am using vtkImageViewer2 to display the slices of a volume. Works alright but doesn't handle rotations all that well. Right now I want to apply my transfer function used in volume rendering to these slices. To do this I could simply give the vtkColorTransferFunction to the image actors property and it would work like so: imageViewer->GetImageActor()->GetProperty()->SetLookupTable(colorTransferFunction); Now I'm looking to apply the opacity as well which is defined separately as a vtkPiecewiseFunction. Is there an easier way to do this without manually creating a lookup table from the two functions? -- View this message in context: http://vtk.1045678.n5.nabble.com/Using-Volume-Renderings-Piecewise-opacity-function-with-vtkImageViewer2-tp5743930.html Sent from the VTK - Users mailing list archive at Nabble.com. From rccm.kyoshimi at gmail.com Fri Jul 7 22:41:52 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Sat, 8 Jul 2017 11:41:52 +0900 Subject: [vtkusers] Sort vtkPoints by one coordinate In-Reply-To: <1499427890601-5743925.post@n5.nabble.com> References: <1499427890601-5743925.post@n5.nabble.com> Message-ID: Hi juanibv, Employing vtkPriorityQueue is relatively simple method of sorting vtkPoints by one coordinate. I attached a sample. Regards, yoshimi 2017-07-07 20:44 GMT+09:00 juanibv : > Points have 3 coordinates: (x,y,z) > Is there a simplest method for sorting vtkPoints by one coordinate? e.g. y > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Sort-vtkPoints-by-one-coordinate-tp5743925.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: SortPoints.tar.gz Type: application/x-gzip Size: 887 bytes Desc: not available URL: From rccm.kyoshimi at gmail.com Sun Jul 9 01:54:49 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Sun, 9 Jul 2017 14:54:49 +0900 Subject: [vtkusers] VtkPlaneWidget handles disappear In-Reply-To: References: Message-ID: Hi, You can use ImplicitPlaneWidget2 to do this. The following example may be helpful. https://lorensen.github.io/VTKExamples/site/Cxx/Widgets/ImplicitPlaneWidget2/ Thanks, yoshimi 2017-07-08 3:53 GMT+09:00 abcd efgh : > Hi > > I am using vtkPlanewidget , but once the next frame is loaded its handles > disappear. > it will appear only if i call Off() method and On() method > the problem is, I am using them with callback, hence once i press mouse, > entire widget will disappear for Off() and appears for On(). > I want the handles to be available for all frames. is there a way just to > turn on handles every frame? > > Thanks. > > _______________________________________________ > 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 > From milefn at rpi.edu Sun Jul 9 16:33:38 2017 From: milefn at rpi.edu (Milef, Nicholas Boris) Date: Sun, 9 Jul 2017 20:33:38 +0000 Subject: [vtkusers] Separating actors for different render passes In-Reply-To: References: , Message-ID: Thanks Ken! This is just what I was looking for. A couple of followup questions: 1. Is it possible to have an actor with different shaders for different passes? Or would we need to use separate actors/mappers since each mapper only has one shader? Recompiling shaders on the fly isn't an option for us. 2. Is it possible to replace the default vtkDefaultPass for the vtkRenderer with a different subclass of vtkDefaultPass or at least disable the default vtkDefaultPass? I couldn't find any API commands that would allow me to do this without subclassing the vtkRenderer, but I could've missed something. ________________________________ From: Ken Martin [ken.martin at kitware.com] Sent: Thursday, July 06, 2017 4:18 PM To: Milef, Nicholas Boris Cc: vtkusers at vtk.org Subject: Re: [vtkusers] Separating actors for different render passes With the render passes you can setup as many passes as you want in whatever order you want. This shows an example where the render process is all driven by passes. https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/OpenGL2/Testing/Cxx/TestSobelGradientMagnitudePass.cxx As an example for shadow maps when needed we use nested opaque passes to render the scene from the view of the light sources which we then use in another opaque pass to compute lighting from the view of the camera. Render passes also have hooks that mappers call so that passes can modify the mapper shader code etc while executing. Passes can also use information properties on actors to filter them in other passes. For example an outer render pass can add information on actors that causes some of them to not be rendered (or to be rendered differently) by other passes ala // ---------------------------------------------------------------------------- // Description: // Opaque pass with key checking. // \pre s_exists: s!=0 void vtkDefaultPass::RenderFilteredOpaqueGeometry(const vtkRenderState *s) { assert("pre: s_exists" && s!=0); int c=s->GetPropArrayCount(); int i=0; while(iGetPropArray()[i]; if(p->HasKeys(s->GetRequiredKeys())) { int rendered= p->RenderFilteredOpaqueGeometry(s->GetRenderer(),s->GetRequiredKeys()); this->NumberOfRenderedProps+=rendered; } ++i; } } On Thu, Jul 6, 2017 at 3:30 PM, Milef, Nicholas Boris > wrote: Is there currently a way to separate actors into custom render passes? If I'm not mistaken, opaque objects currently get rendered before translucent objects, but is there a way to add additional geometry passes (or before opaque geometry, or between translucent and opaque geometry, etc.)? _______________________________________________ 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 -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 ken.martin at kitware.com Sun Jul 9 21:03:01 2017 From: ken.martin at kitware.com (Ken Martin) Date: Sun, 9 Jul 2017 21:03:01 -0400 Subject: [vtkusers] Separating actors for different render passes In-Reply-To: References: Message-ID: On Sun, Jul 9, 2017 at 4:33 PM, Milef, Nicholas Boris wrote: > Thanks Ken! This is just what I was looking for. A couple of followup > questions: > > 1. Is it possible to have an actor with different shaders for different > passes? > The passes can modify a mapper's shader but a mapper does not store shaders per pass. > Or would we need to use separate actors/mappers since each mapper only has > one shader? Recompiling shaders on the fly isn't an option for us. > VTK caches and shares shaders between mappers so once a given shader program has been used once it will be not recompiled for the duration of the run. > 2. Is it possible to replace the default vtkDefaultPass for the > vtkRenderer with a different subclass of vtkDefaultPass or at least disable > the default vtkDefaultPass? I couldn't find any API commands that would > allow me to do this without subclassing the vtkRenderer, but I could've > missed something. > When you specify a render pass on the renderer, whatever render pass you specify takes full control of the render process and the default process is skipped. Thanks Ken > ------------------------------ > *From:* Ken Martin [ken.martin at kitware.com] > *Sent:* Thursday, July 06, 2017 4:18 PM > *To:* Milef, Nicholas Boris > *Cc:* vtkusers at vtk.org > *Subject:* Re: [vtkusers] Separating actors for different render passes > > With the render passes you can setup as many passes as you want in > whatever order you want. This shows an example where the render process is > all driven by passes. > > https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/Ope > nGL2/Testing/Cxx/TestSobelGradientMagnitudePass.cxx > > As an example for shadow maps when needed we use nested opaque passes to > render the scene from the view of the light sources which we then use in > another opaque pass to compute lighting from the view of the camera. > > Render passes also have hooks that mappers call so that passes can modify > the mapper shader code etc while executing. > > Passes can also use information properties on actors to filter them in > other passes. For example an outer render pass can add information on > actors that causes some of them to not be rendered (or to be rendered > differently) by other passes ala > > // ------------------------------------------------------------ > ---------------- > // Description: > // Opaque pass with key checking. > // \pre s_exists: s!=0 > void vtkDefaultPass::RenderFilteredOpaqueGeometry(const vtkRenderState *s) > { > assert("pre: s_exists" && s!=0); > > int c=s->GetPropArrayCount(); > int i=0; > while(i { > vtkProp *p=s->GetPropArray()[i]; > if(p->HasKeys(s->GetRequiredKeys())) > { > int rendered= > p->RenderFilteredOpaqueGeometry(s->GetRenderer(),s->GetRequi > redKeys()); > this->NumberOfRenderedProps+=rendered; > } > ++i; > } > } > > > > > On Thu, Jul 6, 2017 at 3:30 PM, Milef, Nicholas Boris > wrote: > >> Is there currently a way to separate actors into custom render passes? If >> I'm not mistaken, opaque objects currently get rendered before translucent >> objects, but is there a way to add additional geometry passes (or before >> opaque geometry, or between translucent and opaque geometry, etc.)? >> >> _______________________________________________ >> 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 >> >> > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > 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. > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 clement.douarre at gmail.com Mon Jul 10 04:29:13 2017 From: clement.douarre at gmail.com (=?UTF-8?B?Q2zDqW1lbnQgRC4=?=) Date: Mon, 10 Jul 2017 10:29:13 +0200 Subject: [vtkusers] segfault with MarchingCubes Message-ID: Hello all, I am trying to use the Marching Cubes algorithm to show a 3D surface of a 3D image given by a Python (numpy array). I thought I had it all mapped out, things were going great with arrays of small size (generated and rendered 3D isosurfaces), but now that I'm working with arrays of slightly bigger size, the programm crashes with Python error 11 SIGSEGV which means seg fault. What worries me a bit is that the array I'm using is not that big, 150*150*150, and I have a fairly recent computer who shouldn't have any problem handling it. Code MWE is below (in Python) =========================================== Code snippet ======================= import numpy as np import vtk # Creating a numpy array representing a 3D image npa=np.zeros((150,150,150)).astype(np.uint8) npa[100:102,100:102,100:102]=255 # Importing it as object vtk (based on vtk example http://www.vtk.org/Wiki/VTK/Examples/Python/vtkWithNumpy) dataImporter = vtk.vtkImageImport() dataString = npa.tostring() [hh, ww, dd] = npa.shape dataImporter.CopyImportVoidPointer(dataString, len(dataString)) dataImporter.SetDataScalarTypeToUnsignedChar() dataImporter.SetNumberOfScalarComponents(3) dataImporter.SetDataExtent(0, dd - 1, 0, ww - 1, 0, hh - 1) dataImporter.SetWholeExtent(0, dd - 1, 0, ww - 1, 0, hh - 1) dataImporter.Update() vol = dataImporter.GetOutputPort() # (print(dataImporter.GetOutput().GetClassName()) yields "vtk.ImageData") # Use MarchingCubes to generate iso-surface surface = vtk.vtkMarchingCubes(); surface.SetInputConnection(vol); surface.ComputeNormalsOn(); surface.ComputeScalarsOn(); isoValue = 128 surface.SetValue(0, isoValue); #This line causes segfault if npa is "too big" surface.Update(); # .... rest of pipeline # decimator = vtk.vtkDecimatePro(); .... # smoother = vtk.vtkSmoothPolyDataFilter(); .... # connectivityFilter = vtk.vtkPolyDataConnectivityFilter(); .... # mesh = vtk.vtkPolyData(); .... # mapper = vtk.vtkPolyDataMapper(); .... # actor = vtk.vtkActor(); .... =========================================== End of code snippet ======================= So I have a couple of questions here : 1/ Is this a problem of input for MarchingCubes being too big ? Or is this segfault indicating something else ? - arguments for the former : Reducing the size of npa in this code makes it work - arguments for the latter : This code I'm showing is a MWE for my code which is more complicated, and in my code, this code portion fails with a large array, but succeeds if I reduce in size *another* array which has nothing to do with MarchingCubes() (again, that other array is not that big, so I don't think I'm reaching the limits of Python memory or anything like that...) 2/ Am I doing the whole import numpy thing correctly ? I've based myself on the vtk example, but I am unsure of whether it is the recommended way for my case or if it was case specific Thanks everyone, Cl?ment -------------- next part -------------- An HTML attachment was scrubbed... URL: From majid.msadeghi at yahoo.com Mon Jul 10 04:33:05 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Mon, 10 Jul 2017 08:33:05 +0000 (UTC) Subject: [vtkusers] vtkcutter and vtkimagereslice? In-Reply-To: <209719412.760480.1499448534584@mail.yahoo.com> References: <209719412.760480.1499448534584.ref@mail.yahoo.com> <209719412.760480.1499448534584@mail.yahoo.com> Message-ID: <398796018.2312445.1499675585641@mail.yahoo.com> Dear All, Can I use vtkcutter (or any other method) to get a slice of a vtkpolydata not as contour but real values of it (for slicing MRI volume to get 2D), the way vtkimagereslice gives output form a volume Image data? Thanks for the help. On Friday, July 7, 2017, 8:30:57 PM GMT+3, Majid Mohammad sadeghi via vtkusers wrote: Dear All, Can I use vtkcutter (or any other method) to get a slice of a vtkpolydata (for slicing MRI volume to get 2D), the way vtkimagereslice gives output form a volume Image data? The reason I want to be able to reslice polydata is that later I want to do other operations on it. Thanks for the help. _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From satwik.k8 at gmail.com Mon Jul 10 08:41:11 2017 From: satwik.k8 at gmail.com (Satwik) Date: Mon, 10 Jul 2017 05:41:11 -0700 (MST) Subject: [vtkusers] MouseWheelBackwardCallback Message-ID: <1499690471415-5743938.post@n5.nabble.com> Hi, I'm trying to call Mouse wheel backward callback event to update image on vtk window. In my UI , there are 3 WPF controls and 1 vtk window. when i perform mouse wheel operation on vtk window , image gets update. Its,s fine. But when i perform mouse wheel on WPF controllers, image on VTK window also gets updated. I don't want to update image when i'm scrolling on WPF controllers. If anybody knws plz help!!!!! Regards, Satwik -- View this message in context: http://vtk.1045678.n5.nabble.com/MouseWheelBackwardCallback-tp5743938.html Sent from the VTK - Users mailing list archive at Nabble.com. From david.gobbi at gmail.com Mon Jul 10 08:48:57 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 10 Jul 2017 06:48:57 -0600 Subject: [vtkusers] segfault with MarchingCubes In-Reply-To: References: Message-ID: Hi Cl?ment, The "number of scalar components" should be 1 for your data: dataImporter.SetNumberOfScalarComponents(1) There are a couple places where you can improve efficiency: # directly create an array of the desired type npa=np.zeros((150,150,150), np.uint8) # directly pass the array to VTK (without tostring()) dataImporter.CopyImportVoidPointer(npa, npa.size) Cheers, - David On Mon, Jul 10, 2017 at 2:29 AM, Cl?ment D. wrote: > Hello all, > > I am trying to use the Marching Cubes algorithm to show a 3D surface of a > 3D image given by a Python (numpy array). > I thought I had it all mapped out, things were going great with arrays of > small size (generated and rendered 3D isosurfaces), but now that I'm > working with arrays of slightly bigger size, the programm crashes with > Python error 11 SIGSEGV which means seg fault. What worries me a bit is > that the array I'm using is not that big, 150*150*150, and I have a fairly > recent computer who shouldn't have any problem handling it. > > Code MWE is below (in Python) > > =========================================== Code snippet > ======================= > > import numpy as np > import vtk > > # Creating a numpy array representing a 3D image > npa=np.zeros((150,150,150)).astype(np.uint8) > npa[100:102,100:102,100:102]=255 > > # Importing it as object vtk (based on vtk example > http://www.vtk.org/Wiki/VTK/Examples/Python/vtkWithNumpy) > dataImporter = vtk.vtkImageImport() > dataString = npa.tostring() > [hh, ww, dd] = npa.shape > dataImporter.CopyImportVoidPointer(dataString, len(dataString)) > dataImporter.SetDataScalarTypeToUnsignedChar() > dataImporter.SetNumberOfScalarComponents(3) > dataImporter.SetDataExtent(0, dd - 1, 0, ww - 1, 0, hh - 1) > dataImporter.SetWholeExtent(0, dd - 1, 0, ww - 1, 0, hh - 1) > dataImporter.Update() > vol = dataImporter.GetOutputPort() > # (print(dataImporter.GetOutput().GetClassName()) yields "vtk.ImageData") > > # Use MarchingCubes to generate iso-surface > surface = vtk.vtkMarchingCubes(); > surface.SetInputConnection(vol); > surface.ComputeNormalsOn(); > surface.ComputeScalarsOn(); > isoValue = 128 > surface.SetValue(0, isoValue); > > #This line causes segfault if npa is "too big" > surface.Update(); > > # .... rest of pipeline > # decimator = vtk.vtkDecimatePro(); .... > # smoother = vtk.vtkSmoothPolyDataFilter(); .... > # connectivityFilter = vtk.vtkPolyDataConnectivityFilter(); .... > # mesh = vtk.vtkPolyData(); .... > # mapper = vtk.vtkPolyDataMapper(); .... > # actor = vtk.vtkActor(); .... > > > =========================================== End of code snippet > ======================= > > > > So I have a couple of questions here : > 1/ Is this a problem of input for MarchingCubes being too big ? Or is this > segfault indicating something else ? > - arguments for the former : Reducing the size of npa in this code makes > it work > - arguments for the latter : This code I'm showing is a MWE for my code > which is more complicated, and in my code, this code portion fails with a > large array, but succeeds if I reduce in size *another* array which has > nothing to do with MarchingCubes() (again, that other array is not that > big, so I don't think I'm reaching the limits of Python memory or anything > like that...) > > 2/ Am I doing the whole import numpy thing correctly ? I've based myself > on the vtk example, but I am unsure of whether it is the recommended way > for my case or if it was case specific > > > Thanks everyone, > Cl?ment > -------------- next part -------------- An HTML attachment was scrubbed... URL: From clement.douarre at gmail.com Mon Jul 10 09:00:16 2017 From: clement.douarre at gmail.com (=?UTF-8?B?Q2zDqW1lbnQgRC4=?=) Date: Mon, 10 Jul 2017 15:00:16 +0200 Subject: [vtkusers] segfault with MarchingCubes In-Reply-To: References: Message-ID: Great David, thanks again. The SetNumberOfScalarComponents(3) was indeed a residual of a not-careful-enough copy-paste from another part of the code. Everything's working now, and thanks for the optimisation tips ! 2017-07-10 14:48 GMT+02:00 David Gobbi : > Hi Cl?ment, > > The "number of scalar components" should be 1 for your data: > > dataImporter.SetNumberOfScalarComponents(1) > > There are a couple places where you can improve efficiency: > > # directly create an array of the desired type > npa=np.zeros((150,150,150), np.uint8) > > # directly pass the array to VTK (without tostring()) > dataImporter.CopyImportVoidPointer(npa, npa.size) > > Cheers, > - David > > > On Mon, Jul 10, 2017 at 2:29 AM, Cl?ment D. > wrote: > >> Hello all, >> >> I am trying to use the Marching Cubes algorithm to show a 3D surface of a >> 3D image given by a Python (numpy array). >> I thought I had it all mapped out, things were going great with arrays of >> small size (generated and rendered 3D isosurfaces), but now that I'm >> working with arrays of slightly bigger size, the programm crashes with >> Python error 11 SIGSEGV which means seg fault. What worries me a bit is >> that the array I'm using is not that big, 150*150*150, and I have a fairly >> recent computer who shouldn't have any problem handling it. >> >> Code MWE is below (in Python) >> >> =========================================== Code snippet >> ======================= >> >> import numpy as np >> import vtk >> >> # Creating a numpy array representing a 3D image >> npa=np.zeros((150,150,150)).astype(np.uint8) >> npa[100:102,100:102,100:102]=255 >> >> # Importing it as object vtk (based on vtk example >> http://www.vtk.org/Wiki/VTK/Examples/Python/vtkWithNumpy) >> dataImporter = vtk.vtkImageImport() >> dataString = npa.tostring() >> [hh, ww, dd] = npa.shape >> dataImporter.CopyImportVoidPointer(dataString, len(dataString)) >> dataImporter.SetDataScalarTypeToUnsignedChar() >> dataImporter.SetNumberOfScalarComponents(3) >> dataImporter.SetDataExtent(0, dd - 1, 0, ww - 1, 0, hh - 1) >> dataImporter.SetWholeExtent(0, dd - 1, 0, ww - 1, 0, hh - 1) >> dataImporter.Update() >> vol = dataImporter.GetOutputPort() >> # (print(dataImporter.GetOutput().GetClassName()) yields "vtk.ImageData") >> >> # Use MarchingCubes to generate iso-surface >> surface = vtk.vtkMarchingCubes(); >> surface.SetInputConnection(vol); >> surface.ComputeNormalsOn(); >> surface.ComputeScalarsOn(); >> isoValue = 128 >> surface.SetValue(0, isoValue); >> >> #This line causes segfault if npa is "too big" >> surface.Update(); >> >> # .... rest of pipeline >> # decimator = vtk.vtkDecimatePro(); .... >> # smoother = vtk.vtkSmoothPolyDataFilter(); .... >> # connectivityFilter = vtk.vtkPolyDataConnectivityFilter(); .... >> # mesh = vtk.vtkPolyData(); .... >> # mapper = vtk.vtkPolyDataMapper(); .... >> # actor = vtk.vtkActor(); .... >> >> >> =========================================== End of code snippet >> ======================= >> >> >> >> So I have a couple of questions here : >> 1/ Is this a problem of input for MarchingCubes being too big ? Or is >> this segfault indicating something else ? >> - arguments for the former : Reducing the size of npa in this code makes >> it work >> - arguments for the latter : This code I'm showing is a MWE for my code >> which is more complicated, and in my code, this code portion fails with a >> large array, but succeeds if I reduce in size *another* array which has >> nothing to do with MarchingCubes() (again, that other array is not that >> big, so I don't think I'm reaching the limits of Python memory or anything >> like that...) >> >> 2/ Am I doing the whole import numpy thing correctly ? I've based myself >> on the vtk example, but I am unsure of whether it is the recommended way >> for my case or if it was case specific >> >> >> Thanks everyone, >> Cl?ment >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From majid.msadeghi at yahoo.com Mon Jul 10 09:51:29 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Mon, 10 Jul 2017 13:51:29 +0000 (UTC) Subject: [vtkusers] Matrix Rotation for Imgae Reslice Help References: <2053204549.2490494.1499694689265.ref@mail.yahoo.com> Message-ID: <2053204549.2490494.1499694689265@mail.yahoo.com> Hello to everyone, I have a 4x4 transformation matrix which I am using for Image Reslice and it works fine. Now I want to know how to rotate this matrix 90 degrees around an arbitrary axis so that I can reslice image in the new direction? When I use vtkTransform as: vtkSmartPointer Transform= vtkSmartPointer::New();??? Transform->SetMatrix(OriginalMatrix); ????Transform->RotateWXYZ(90, ArbitraryAxis);??? Transform->Inverse(); ??? Transform->Update(); ??? Transform->GetInverse(NewMatrix); It does not give me the right matrix. Can anybody give me a hint on where to start? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Wiggerl at Linhuber.info Mon Jul 10 10:46:55 2017 From: Wiggerl at Linhuber.info (Willy) Date: Mon, 10 Jul 2017 07:46:55 -0700 (MST) Subject: [vtkusers] Best way to visualize a RGB Volume? Message-ID: <1499698015709-5743942.post@n5.nabble.com> Hi, i want to visualize a RGB Volume and have a little problem. i do not think that there is a perfect solution, but maybe i am missing something. Here i my problem: There are three different Methods to visualize a RGB Volume: 1. Method: IndependentComponentsOn: three components (R,G,B), each with Colortransferfunction and opacityfunction 2. Method: IndependentComponentsOff: two components, first with Colortransferfunction and second with opacityfunction 3. Method: IndependentComponentsOff: four components, 1-3(R,G,B) with Colortransferfunction and fourth with opacityfunction Here are the disadvantages for each Method: 1. Method: It is not possible to create a colorTransferFunction or opacityFunction for the intensity value of a color(voxel), it is only possible to set these functions for each components seperate. This can lead to falsified colors if the user changes these functions somehow (if you have the same color and opacity function for all components). 2. Method: the two components must have the same data type. the color component needs at least 3 byte, but there is no 3 byte type => 4 bytes for each component => 8 bytes per voxel => huge overhead. Moreover the image quality for maximum intensity BlendMode is not as good as for the 1. Method. If you have (in the volume) for example a green wall with value 250 and a red area behind it (for the current camera position) with value 200, you can't see the red area at all. In the first method the red area is displayed as yellow area (that is better). 3. Method: No colorFunction Is there a Method without disadvantages? MfG Ludwig -- View this message in context: http://vtk.1045678.n5.nabble.com/Best-way-to-visualize-a-RGB-Volume-tp5743942.html Sent from the VTK - Users mailing list archive at Nabble.com. From sankhesh.jhaveri at kitware.com Mon Jul 10 11:14:52 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 10 Jul 2017 15:14:52 +0000 Subject: [vtkusers] Using Volume Renderings Piecewise opacity function with vtkImageViewer2 In-Reply-To: <1499475231119-5743930.post@n5.nabble.com> References: <1499475231119-5743930.post@n5.nabble.com> Message-ID: I don?t think so. You?ll have to create a lookup table manually from the two functions. ? On Fri, Jul 7, 2017 at 8:54 PM Andaharoo wrote: > Currently I am using vtkImageViewer2 to display the slices of a volume. > Works > alright but doesn't handle rotations all that well. Right now I want to > apply my transfer function used in volume rendering to these slices. To do > this I could simply give the vtkColorTransferFunction to the image actors > property and it would work like so: > > > imageViewer->GetImageActor()->GetProperty()->SetLookupTable(colorTransferFunction); > > Now I'm looking to apply the opacity as well which is defined separately as > a vtkPiecewiseFunction. Is there an easier way to do this without manually > creating a lookup table from the two functions? > > > > -- > View this message in context: > http://vtk.1045678.n5.nabble.com/Using-Volume-Renderings-Piecewise-opacity-function-with-vtkImageViewer2-tp5743930.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Mon Jul 10 11:26:35 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 10 Jul 2017 15:26:35 +0000 Subject: [vtkusers] Best way to visualize a RGB Volume? In-Reply-To: <1499698015709-5743942.post@n5.nabble.com> References: <1499698015709-5743942.post@n5.nabble.com> Message-ID: Hi Ludwig, Just so I understand, you?d like to be able to pass the RGB volume through a color lookup table too? IMHO, if you have a RGB volume, adding a fourth component for opacity and setting an opacity function with IndependentComponentsOff is the best method. *Note* that with two dependent components, the first component values are used to lookup colors from the color transfer function i.e. the first component can be as small as 1 byte (unsigned char). Hth, Sankhesh ? On Mon, Jul 10, 2017 at 10:47 AM Willy wrote: > Hi, > > i want to visualize a RGB Volume and have a little problem. i do not think > that there is a perfect solution, but maybe i am missing something. > > Here i my problem: > > There are three different Methods to visualize a RGB Volume: > 1. Method: IndependentComponentsOn: three components (R,G,B), each with > Colortransferfunction and opacityfunction > 2. Method: IndependentComponentsOff: two components, first with > Colortransferfunction and second with opacityfunction > 3. Method: IndependentComponentsOff: four components, 1-3(R,G,B) with > Colortransferfunction and fourth with opacityfunction > > Here are the disadvantages for each Method: > 1. Method: It is not possible to create a colorTransferFunction or > opacityFunction for the intensity value of a color(voxel), it is only > possible to set these functions for each components seperate. This can lead > to falsified colors if the user changes these functions somehow (if > you > have the same color and opacity function for all components). > 2. Method: the two components must have the same data type. the color > component needs at least 3 byte, but there is no 3 byte type => 4 bytes for > each component => 8 bytes per voxel => huge overhead. Moreover the image > quality for maximum intensity BlendMode is not as good as for the 1. > Method. > If you have (in the volume) for example a green wall with value 250 and a > red area behind it (for the current camera position) with value 200, you > can't see the red area at all. In the first method the red area is > displayed > as yellow area (that is better). > 3. Method: No colorFunction > > Is there a Method without disadvantages? > > MfG > Ludwig > > > > -- > View this message in context: > http://vtk.1045678.n5.nabble.com/Best-way-to-visualize-a-RGB-Volume-tp5743942.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Mon Jul 10 11:30:01 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 10 Jul 2017 15:30:01 +0000 Subject: [vtkusers] VTK planeWidget using call back or overriden function In-Reply-To: References: Message-ID: Perhaps, you could take a look at the ImplicitPlaneWidget2 example for using a plane to clip a polydata? ? On Fri, Jul 7, 2017 at 12:13 AM abcd efgh wrote: > Hi, > > I want to use VTK plane to cut the polydata using mouse. CUrrently I can > place the plane and cut the polydata using the plane using some keypress. > Now i want to use the Plane widget and as soon as i stop placing the plane > near the polydata, the plane should cut it. I have tried with Callback with > LeftButtonRelease event , and OverRiding the LeftButtonUp methods. But these > methods are not working correctly. Anyone with a good idea? > > Thanks > _______________________________________________ > 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 > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Wiggerl at Linhuber.info Mon Jul 10 11:42:33 2017 From: Wiggerl at Linhuber.info (Willy) Date: Mon, 10 Jul 2017 08:42:33 -0700 (MST) Subject: [vtkusers] Best way to visualize a RGB Volume? In-Reply-To: References: <1499698015709-5743942.post@n5.nabble.com> Message-ID: <1499701353534-5743947.post@n5.nabble.com> two components: if i use 1 byte for the first component i can only see 256 different colors, but i have 2^16 colors. I would need 8 byte to display that (4 per component) four components: just 4 bytes in total, but no color function. -- View this message in context: http://vtk.1045678.n5.nabble.com/Best-way-to-visualize-a-RGB-Volume-tp5743942p5743947.html Sent from the VTK - Users mailing list archive at Nabble.com. From rustem.khabetdinov at gmail.com Tue Jul 11 07:41:41 2017 From: rustem.khabetdinov at gmail.com (Rustem Khabetdinov) Date: Tue, 11 Jul 2017 14:41:41 +0300 Subject: [vtkusers] Question about visualization In-Reply-To: <1499183054490-5743877.post@n5.nabble.com> References: <1499183054490-5743877.post@n5.nabble.com> Message-ID: As far as I know there is tensorglyph in vtk that allows to visualize superquadrics. I've tried to use it but it gives me incorrect glyph. It always gives me sphere instead of ellipsoid. 2017-07-04 18:44 GMT+03:00 longbowzhang : > Basically you try to visualize a 3-by-3 symmetric matrix. > The natural choice is to use an ellipsoid. > > Unfortunately, you have *negative* eigenvalues. > Therefore, the most elegant visualization should be this > SuperquadricTensorGlyph > rGlyphs.pdf> > . > The code > is based on OpenGL, rather than VTK. > > Hope this could help or inspire you to some extent. > > Longbow > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Question-about-visualization-tp5743875p5743877.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Tue Jul 11 08:13:57 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 11 Jul 2017 08:13:57 -0400 Subject: [vtkusers] Question about visualization In-Reply-To: References: <1499183054490-5743877.post@n5.nabble.com> Message-ID: Rustem, Indeed there is a superquadric source in VTK and ParaView. You can try this source in paraview to see what paramters you need to specify to get the glyph you want. Dan On Tue, Jul 11, 2017 at 7:41 AM, Rustem Khabetdinov < rustem.khabetdinov at gmail.com> wrote: > As far as I know there is tensorglyph in vtk that allows to visualize > superquadrics. I've tried to use it but it gives me incorrect glyph. It > always gives me sphere instead of ellipsoid. > > 2017-07-04 18:44 GMT+03:00 longbowzhang : > >> Basically you try to visualize a 3-by-3 symmetric matrix. >> The natural choice is to use an ellipsoid. >> >> Unfortunately, you have *negative* eigenvalues. >> Therefore, the most elegant visualization should be this >> SuperquadricTensorGlyph >> > adricTensorGlyphs.pdf> >> . >> The code >> is based on OpenGL, rather than VTK. >> >> Hope this could help or inspire you to some extent. >> >> Longbow >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.c >> om/Question-about-visualization-tp5743875p5743877.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> > > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From EZ7543 at wayne.edu Tue Jul 11 13:01:09 2017 From: EZ7543 at wayne.edu (Teek) Date: Tue, 11 Jul 2017 10:01:09 -0700 (MST) Subject: [vtkusers] VTK Surface & Volume Intersection Question Message-ID: <1499792469848-5743953.post@n5.nabble.com> Hi VTK Users, So currently I have a vtkVolume created from DICOM slices. On the other hand, I also have a vtkSphereSoure->vtkActor which is tracking the motion of my mouse. I was wondering if there was a way to detect when the vtkActor and vtkVolume intersect. I don't need to exactly know how they intersect or the points that intersect themselves - just when they intersect, like a boolean of sorts. Originally I was thinking that maybe I could just get the center position of the sphere in my application loop and check if that point lies within the rendering of the volume but I'm not sure if that's the best method, nor if there are any VTK classes for that. I was wondering if there are any VTK classes that can already do this or would i have to manually do it. I was looking through a couple examples and they seem to all deal with vtkPolyData and not a volume itself. I would appreciate any help. Regards, Teek -- View this message in context: http://vtk.1045678.n5.nabble.com/VTK-Surface-Volume-Intersection-Question-tp5743953.html Sent from the VTK - Users mailing list archive at Nabble.com. From ruvva at yahoo.com Tue Jul 11 14:41:07 2017 From: ruvva at yahoo.com (Koteswara Rao Ruvva) Date: Tue, 11 Jul 2017 18:41:07 +0000 (UTC) Subject: [vtkusers] Polydata cross-section contours In-Reply-To: <2101341144.2891648.1498503431895@mail.yahoo.com> References: <2101341144.2891648.1498503431895.ref@mail.yahoo.com> <2101341144.2891648.1498503431895@mail.yahoo.com> Message-ID: <1414077023.3673656.1499798467053@mail.yahoo.com> I am adding more details to this question. Basically I am comparing two polydata sets (target and source). These are STL files with triangular facets. I am comparing the polydata sets in the following way:?1. Using the ImplicitPolyDataDistance function to get the distance from a point on the source to target polydata. I use this to find the distance ?at mouse locations. This works perfect.2. Creating cross-section contours of source and contour using the vtkCutter and visually compare the contours. However, I want to the source contour to be within + or - 0.2mm tolerance from target contour. It would be easy for me if I have two more contours with +0.2 offset and -0.2 offset from the target contour. This makes my visual comparison easier. I tried to render the target contour with 0.4 thickness which solves this problem partly, but when I zoom in, the thickness does not change. Appreciate your feedback. Thank you. On Monday, June 26, 2017, 11:57:11 AM PDT, Koteswara Rao Ruvva wrote: Hello All, I need to create offset contours for a contour (polygon) that is created by vtkCutter. Basically I need to create an inner and outer contours by a specific offset for cutter contour. I am wondering if there is a way in VTK to get this. Thank youRao -------------- next part -------------- An HTML attachment was scrubbed... URL: From xoviat at tamu.edu Wed Jul 12 13:28:10 2017 From: xoviat at tamu.edu (Geoffrey Garner) Date: Wed, 12 Jul 2017 12:28:10 -0500 Subject: [vtkusers] VTK OpenVR module Message-ID: <59665c29.55c7ca0a.672c4.f914@mx.google.com> All: I seem to be unable to locate the vtkRenderingOpenVRModule.h header. Does anyone know where this is located? Regards, Geoffrey -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Jul 12 13:34:53 2017 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 12 Jul 2017 13:34:53 -0400 Subject: [vtkusers] VTK OpenVR module In-Reply-To: <59665c29.55c7ca0a.672c4.f914@mx.google.com> References: <59665c29.55c7ca0a.672c4.f914@mx.google.com> Message-ID: CMake should create it for you in the VTK build tree. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Jul 12, 2017 at 1:28 PM, Geoffrey Garner wrote: > All: > > > > I seem to be unable to locate the vtkRenderingOpenVRModule.h header. Does > anyone know where this is located? > > > > > > Regards, > > > > > > Geoffrey > > > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amine.aboufirass at gmail.com Thu Jul 13 10:32:01 2017 From: amine.aboufirass at gmail.com (awa5114) Date: Thu, 13 Jul 2017 07:32:01 -0700 (MST) Subject: [vtkusers] Plotting animations of VTK timeseries Message-ID: <1499956321124-5743962.post@n5.nabble.com> I have an FEM program that ouputs time series of unstructured grid vtk files with file extensions corresponding to the time steps. Currently I use paraview to open and visualize animations generated from the various scalar, vector and tensor data contained within these vtk files. The issue is that in Paraview it is difficult or not possible to visualize 2 or more data animations (based on vtk time series) simultaneously. In the work I do it will soon become necessary to run dozens of calculations and output dozens of vtk timeseries simultaneously. Each timeseries would contain a hundred or so vtk files and would correspond to an independent Paraview model to look at and analyze. I would like to figure out whether there is a programmatic way to load up these vtk files, filter them accordingly (applying for example the same data filter) and visualize all animations on one window, perhaps attaching a little tag to each animation so that I know what I'm looking at. Of course this could be quite demanding on the processor so I'm OK with saving the "batch animation" containing all my different models and visualizing it after the saving is done. Any ideas on how one may accomplish this? Thanks. -- View this message in context: http://vtk.1045678.n5.nabble.com/Plotting-animations-of-VTK-timeseries-tp5743962.html Sent from the VTK - Users mailing list archive at Nabble.com. From sonam.wangyal at ryerson.ca Thu Jul 13 13:19:26 2017 From: sonam.wangyal at ryerson.ca (Sonam Wangyal) Date: Thu, 13 Jul 2017 13:19:26 -0400 Subject: [vtkusers] vtkDICOMImageReader(): Anyway to change the metadata? Message-ID: Hello! This is my first post in this community and just as a heads up I am a complete newbie. I am currently working on a project to segment ventricles from MRI scans of the brain (in MATLAB). I wanted to then extract the surface using vtkDiscreteMarchingCubes() and write it into an STL file using vtkSTLWriter(). My problem is with the PixelSpacing, the documentation says if there are multiple DICOM images then the 'z' value is the Spacing Between the Slices. But I am receiving (0.859375, 0.859375, 0.0). I don't know why it is giving me a 0.0, it should be a 5. I have tried with an single DICOM and it works properly it gave me a Slice Thickness which coincidentally is the same value as the Spacing Between the Slices. SO MY QUESTION IS: is there anyway to manually change the value? My code is down below, THANKS FOR YOUR HELP! import vtk PathDicom = "./DICOMs/" reader = vtk.vtkDICOMImageReader() reader.SetDirectoryName(PathDicom) reader.Update() print(reader.GetPixelSpacing()) dmc = vtk.vtkDiscreteMarchingCubes() dmc.SetInputConnection(reader.GetOutputPort()) dmc.GenerateValues(1, 1, 1) dmc.Update() writer = vtk.vtkSTLWriter() writer.SetInputConnection(dmc.GetOutputPort()) writer.SetFileTypeToBinary() writer.SetFileName("ventricle.stl") writer.Write() Cheers, Sonam Wangyal Electrical Engineering | BEng Candidate The Faculty of Engineering and Architectural Science E: sonam.wangyal at ryerson.ca C: 647.779.2560 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Thu Jul 13 16:23:20 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 13 Jul 2017 14:23:20 -0600 Subject: [vtkusers] vtkDICOMImageReader(): Anyway to change the metadata? In-Reply-To: References: Message-ID: Hi Sonam, The filter vtkImageChangeInformation can modify the spacing of the data: ici = vtk.vtkImageChangeInformation() ici.SetInputConnection(reader.GetOutputPort()) ici.SetOutputSpacing(0.859375, 0.859375, 5.0) - David On Thu, Jul 13, 2017 at 11:19 AM, Sonam Wangyal wrote: > Hello! > > This is my first post in this community and just as a heads up I am a > complete newbie. I am currently working on a project to segment ventricles > from MRI scans of the brain (in MATLAB). I wanted to then extract the > surface using vtkDiscreteMarchingCubes() and write it into an STL file > using vtkSTLWriter(). > > My problem is with the PixelSpacing, the documentation says if there are > multiple DICOM images then the 'z' value is the Spacing Between the Slices. > But I am receiving (0.859375, 0.859375, 0.0). I don't know why it is giving > me a 0.0, it should be a 5. I have tried with an single DICOM and it works > properly it gave me a Slice Thickness which coincidentally is the same > value as the Spacing Between the Slices. > > SO MY QUESTION IS: is there anyway to manually change the value? My code > is down below, THANKS FOR YOUR HELP! > > import vtk > > PathDicom = "./DICOMs/" > reader = vtk.vtkDICOMImageReader() > reader.SetDirectoryName(PathDicom) > reader.Update() > > print(reader.GetPixelSpacing()) > > dmc = vtk.vtkDiscreteMarchingCubes() > dmc.SetInputConnection(reader.GetOutputPort()) > dmc.GenerateValues(1, 1, 1) > dmc.Update() > > writer = vtk.vtkSTLWriter() > writer.SetInputConnection(dmc.GetOutputPort()) > writer.SetFileTypeToBinary() > writer.SetFileName("ventricle.stl") > writer.Write() > > Cheers, > *Sonam Wangyal* > Electrical Engineering | BEng Candidate > The Faculty of Engineering and Architectural Science > E: sonam.wangyal at ryerson.ca > C: 647.779.2560 <(647)%20779-2560> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sonam.wangyal at ryerson.ca Thu Jul 13 16:27:47 2017 From: sonam.wangyal at ryerson.ca (sonamwangyal) Date: Thu, 13 Jul 2017 13:27:47 -0700 (MST) Subject: [vtkusers] vtkDICOMImageReader(): Anyway to change the metadata? In-Reply-To: References: Message-ID: Thanks I used pydicom to get the metadata and used what you suggested and it worked! Thank you! Sent from my iPhone > On Jul 13, 2017, at 4:23 PM, David Gobbi [via VTK] wrote: > > Hi Sonam, > > The filter vtkImageChangeInformation can modify the spacing of the data: > > ici = vtk.vtkImageChangeInformation() > ici.SetInputConnection(reader.GetOutputPort()) > ici.SetOutputSpacing(0.859375, 0.859375, 5.0) > > - David > >> On Thu, Jul 13, 2017 at 11:19 AM, Sonam Wangyal <[hidden email]> wrote: >> Hello! >> >> This is my first post in this community and just as a heads up I am a complete newbie. I am currently working on a project to segment ventricles from MRI scans of the brain (in MATLAB). I wanted to then extract the surface using vtkDiscreteMarchingCubes() and write it into an STL file using vtkSTLWriter(). >> >> My problem is with the PixelSpacing, the documentation says if there are multiple DICOM images then the 'z' value is the Spacing Between the Slices. But I am receiving (0.859375, 0.859375, 0.0). I don't know why it is giving me a 0.0, it should be a 5. I have tried with an single DICOM and it works properly it gave me a Slice Thickness which coincidentally is the same value as the Spacing Between the Slices. >> >> SO MY QUESTION IS: is there anyway to manually change the value? My code is down below, THANKS FOR YOUR HELP! >> >> import vtk >> >> PathDicom = "./DICOMs/" >> reader = vtk.vtkDICOMImageReader() >> reader.SetDirectoryName(PathDicom) >> reader.Update() >> >> print(reader.GetPixelSpacing()) >> >> dmc = vtk.vtkDiscreteMarchingCubes() >> dmc.SetInputConnection(reader.GetOutputPort()) >> dmc.GenerateValues(1, 1, 1) >> dmc.Update() >> >> writer = vtk.vtkSTLWriter() >> writer.SetInputConnection(dmc.GetOutputPort()) >> writer.SetFileTypeToBinary() >> writer.SetFileName("ventricle.stl") >> writer.Write() >> >> Cheers, >> Sonam Wangyal >> > > _______________________________________________ > 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 > > > If you reply to this email, your message will be added to the discussion below: > http://vtk.1045678.n5.nabble.com/vtkDICOMImageReader-Anyway-to-change-the-metadata-tp5743964p5743965.html > To start a new topic under VTK - Users, email ml+s1045678n1224199h20 at n5.nabble.com > To unsubscribe from VTK - Users, click here. > NAML -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkDICOMImageReader-Anyway-to-change-the-metadata-tp5743964p5743966.html Sent from the VTK - Users mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From siva.yedithi at gmail.com Thu Jul 13 20:30:03 2017 From: siva.yedithi at gmail.com (Neel Patel 0-0-0) Date: Thu, 13 Jul 2017 17:30:03 -0700 (MST) Subject: [vtkusers] Issues with rendering streaming 3D data Message-ID: <1499992203443-5743967.post@n5.nabble.com> Hi all. I'm trying to render streaming 3d data and I have a couple questions. 1) Does anyone have experience doing this and if so how did you structure your code to update data and render it, and how fast was it? 2) I have some code that does work for about a couple seconds before I get an exception in Kitware.VTK.dll as I'm using ActiViz. If I take out the render call in the code below, it seems to be ok. It only seems to have a problem rendering. try { byte[] myByteArray =StreamObject.Bytes; GCHandle gPointer = GCHandle.Alloc(myByteArray, GCHandleType.Pinned); imageImport.SetImportVoidPointer(gPointer.AddrOfPinnedObject()); imageImport.Update(); imageImport.Modified(); // Set up renderer vtkRenderer renderer = renderWindowControl1.RenderWindow.GetRenderers().GetFirstRenderer(); //renderer.ResetCamera(); // Create transfer mapping scalar value to opacity vtkPiecewiseFunction opacityTransferFunction = vtkPiecewiseFunction.New(); opacityTransferFunction.AddPoint(70, 0.0); opacityTransferFunction.AddPoint(255, 0.1); // Create transfer mapping scalar value to color vtkColorTransferFunction colorTransferFunction = vtkColorTransferFunction.New(); colorTransferFunction.AddRGBPoint(0.0, 0.0, 0.0, 0.0); //colorTransferFunction.AddRGBPoint(100.0, 0.0, 0.0, 1.0); colorTransferFunction.AddRGBPoint(255.0, 1.0, 1.0, 1.0); // The property describes how the data will look vtkVolumeProperty volumeProperty = vtkVolumeProperty.New(); volumeProperty.SetColor(colorTransferFunction); volumeProperty.SetScalarOpacity(opacityTransferFunction); //volumeProperty.ShadeOn(); //volumeProperty.SetInterpolationTypeToLinear(); // The mapper / ray cast function know how to render the data vtkVolumeRayCastCompositeFunction compositeFunction = vtkVolumeRayCastCompositeFunction.New(); vtkVolumeRayCastMapper volumeMapper = vtkVolumeRayCastMapper.New(); volumeMapper.SetVolumeRayCastFunction(compositeFunction); // Link the volume render object to the byte array data // volumeMapper.SetInput(myVtkImageData); volumeMapper.SetInput(imageImport.GetOutput()); volumeMapper.Modified(); // The volume holds the mapper and the property and can be used to position/orient the volume vtkVolume volume = vtkVolume.New(); volume.SetMapper(volumeMapper); volume.SetProperty(volumeProperty); volume.Modified(); // Add volume to renderer renderer.AddVolume(volume); renderer.SetBackground(0, 0, 0); renderer.Modified(); renderer.GetRenderWindow().Render(); gPointer.Free(); myByteArray = null; } catch (Exception ex) { throw; } The issue is that when the program starts the first pass through the renderer goes through and it displays as it should, the second time I get an access violation exception. If I use similar coed for 2D however it seems to run fine. Any help, tips, general advice on streaming with VTK are welcome. Regards, Neel -- View this message in context: http://vtk.1045678.n5.nabble.com/Issues-with-rendering-streaming-3D-data-tp5743967.html Sent from the VTK - Users mailing list archive at Nabble.com. From ajohnston at transmin.com Fri Jul 14 20:33:18 2017 From: ajohnston at transmin.com (ajohnston) Date: Fri, 14 Jul 2017 17:33:18 -0700 (MST) Subject: [vtkusers] vtk axes change x y and z Message-ID: <1500078798192-5743969.post@n5.nabble.com> Hi, I am trying to hide an axis when it is perpendicular to the view plane, i.e., very short on the screen. It seems that xaxis, yaxis and zaxis change as the camera rotates around the scene. We've been trying to use the GetOrientation of the camera to know when to hide the x y or z axis, but then the axis names keep changing, so we get random results. Also, I would like to use the angles calculated to rotate the alignment of the axes labels. When we do that, the labels get tiny, probably because they are getting scaled to the horizontal text height. Previous versions posts seem to have this solution, but vtkAxesActor does not give me that method. axes->GetYAxisCaptionActor2D ()->GetTextActor()->SetTextScaleModeToNone(); Cheers, Adam -- View this message in context: http://vtk.1045678.n5.nabble.com/vtk-axes-change-x-y-and-z-tp5743969.html Sent from the VTK - Users mailing list archive at Nabble.com. From tjlp at netease.com Sat Jul 15 23:45:44 2017 From: tjlp at netease.com (Liu_tj) Date: Sun, 16 Jul 2017 11:45:44 +0800 (CST) Subject: [vtkusers] How to change the cross hair shape of vtkHandleWidget Message-ID: <35d86a13.7.15d498080a6.Coremail.tjlp@netease.com> Hi, I try to use vtkHandleWidget to display a point on DICOM image. If I use vtkPointHandleRepresentation2D as the reprsentation of the widget, it will display a cross hair at the point I click; if I use vtkPointHandleRepresentation3D, it will display a point. So, how can I change the cross hair to a point if I use vtkPointHandleRepresentation2D? Thanks Liu Peng -------------- next part -------------- An HTML attachment was scrubbed... URL: From adarshdesai.dsp at gmail.com Sun Jul 16 02:48:44 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Sat, 15 Jul 2017 23:48:44 -0700 Subject: [vtkusers] Widgets not working in a renderer Message-ID: Hello, I have 4 renderers in a window, in 3 of them widgets work. However in one of them widgets dont work. I havent done any specific changes for that renderer. Thanks all. -------------- next part -------------- An HTML attachment was scrubbed... URL: From adarshdesai.dsp at gmail.com Sun Jul 16 04:15:12 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Sun, 16 Jul 2017 01:15:12 -0700 Subject: [vtkusers] Problem with shadows Message-ID: Hello, I am new to vtk. I have a 3D polydata, I cut it using vtkClipPolydata. Now there are some shadow kind of thing, I have called functions to turn off shadows as well as backface culling as off. But still shadow kind of effect remains and the Poly data is sometimes dark due to this. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Sun Jul 16 08:21:14 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Sun, 16 Jul 2017 06:21:14 -0600 Subject: [vtkusers] Problem with shadows In-Reply-To: References: Message-ID: Clipping a data set adds scalars to the data set. These scalars are probably causing the strange coloring that you are seeing. You can tell the mapper to ignore the scalars, and use the vtkProperty color instead: mapper->ScalarVisibilityOff(); - David On Sun, Jul 16, 2017 at 2:15 AM, abcd efgh wrote: > Hello, > > I am new to vtk. I have a 3D polydata, I cut it using vtkClipPolydata. > Now there are some shadow kind of thing, I have called functions to turn > off shadows > as well as backface culling as off. But still shadow kind of effect > remains and the Poly data is sometimes dark due to this. > > Thanks > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaxellx at gmail.com Sun Jul 16 18:28:50 2017 From: xaxellx at gmail.com (Alexander Devaykin) Date: Mon, 17 Jul 2017 00:28:50 +0200 Subject: [vtkusers] How does VTK OSPRay-based volume rendering produce smooth images? In-Reply-To: References: Message-ID: Hello, sorry for late reply and thank you for the answers! I actually managed to achieve nice smooth surface of the volume thanks to your help! And I didn't see any significant performance change at least on the datasets at hand. Best regards, Alexander On Thu, Jul 6, 2017 at 7:52 PM, Brownlee, Carson wrote: > The smoothness of the resulting image is based on several factors, > notably: number of accumulation passes, number of samples per pixel, > samplingStep, and adaptive sampling settings. Please see the OSRPay > documentation for an explanation of each. > > The volume renderer in VTK appears smoother because the samplingStep and > adaptive sampling settings were set for taking more samples than the > viewers that come with OSPRay, which were designed speed in mind and rely > on progressive rendering to smooth the image after the first frame. We > assumed that with VTK and ParaView that most users would not be using > progressive refinement, which unfortunately is likely a mostly unknown > feature in ParaView. > Carson > ------------------------------ > *From:* David E DeMarle [dave.demarle at kitware.com] > *Sent:* Thursday, July 06, 2017 7:15 AM > *To:* Alexander Devaykin; Brownlee, Carson > *Cc:* vtkusers at vtk.org > *Subject:* Re: [vtkusers] How does VTK OSPRay-based volume rendering > produce smooth images? > > Most likely the only difference is that VTK sets up OSPRay's volume > sampling differently than the OSPRay demos do. > You will find how it is setup here: > https://gitlab.kitware.com/vtk/vtk/blob/master/Rendering/OSPRay/ > vtkOSPRayVolumeMapperNode.cxx#L255 > > Note also: starting with ParaView 5.3, if you start ParaView with > --enable-streaming, and set "Progressive Passes" on the Properties panel to > something higher than one, ParaView will do progressive refinement like you > see in the OSPRay demos. > > > > David E DeMarle > Kitware, Inc. > Principal Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Mon, Jul 3, 2017 at 5:46 PM, Alexander Devaykin > wrote: > >> Hello everyone, >> >> I wonder how does OSPRay-based volume renderer in VTK, used in ParaView, >> is able to produce volume images with smooth surface from the first pass >> (without buffer accumulation). >> >> OSPRay raw volume rendering e.g. using OSPRay demos, results in very >> densly sampled volumes. It looks like only one sample per voxel is taken >> which results in one pixel per voxel colored in the first pass at some >> regions (image 1). Only after several accumulation passes the rendering >> produces smooth image (image 3). >> >> In contrast to that, volume rendering in ParaView via OSPRay shows smooth >> image after first pass (image 4) with a little bit of densly sampled >> artifacts. It actually looks like no frames accumulation is active at all, >> because I no difference is visible between moving and resting camera. >> Zooming in also keeps the image smooth (image 5). >> >> Any articles or hints about what is going on behind the scenes? I'm >> digging into the VTK source code but no understanding so far. OSPRay seems >> to be configured just like I do in my application, but VTK seems to do the >> magic somewhere else. >> >> Screenshots or standalone OSPRay and ParaView-OSPRay renderings are >> attachend. >> >> Best Regards, >> Alexander Devaykin >> >> _______________________________________________ >> 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 >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From majid.msadeghi at yahoo.com Mon Jul 17 10:49:48 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Mon, 17 Jul 2017 14:49:48 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> Message-ID: <1078907182.2222362.1500302988072@mail.yahoo.com> Hi everyone, I am using vtkBooleanOperationPolyDataFilter, and it works fine except after the operation it smoothes the polydata, which I dont want. Is there a way to stop that? Or is there another library for boolean operations on polydata? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Jul 17 11:00:48 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 17 Jul 2017 10:00:48 -0500 Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <1078907182.2222362.1500302988072@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> Message-ID: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/Examples/Cxx/Visualization/FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFilter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > _______________________________________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From majid.msadeghi at yahoo.com Mon Jul 17 11:21:13 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Mon, 17 Jul 2017 15:21:13 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> Message-ID: <1784503810.2268640.1500304873791@mail.yahoo.com> Dear Cory, Thanks for the reply, I set the actors property to? SetInterpolationToFlat(); as you said, but the result is the same I put a picture before and after boolean operation here. Any suggestion? Are you familier with any other library? Current boolean operation takes about 150 seconds on my system, do you think this is normal? On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen wrote: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/Examples/Cxx/Visualization/FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFilter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > _______________________________________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From sankhesh.jhaveri at kitware.com Mon Jul 17 11:23:27 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 17 Jul 2017 15:23:27 +0000 Subject: [vtkusers] Widgets not working in a renderer In-Reply-To: References: Message-ID: Could you share more details about the renderer setup, which widgets are you using, VTK version, etc.? ? On Sun, Jul 16, 2017 at 2:48 AM abcd efgh wrote: > Hello, > > I have 4 renderers in a window, in 3 of them widgets work. However in one > of them widgets dont work. I havent done any specific changes for that > renderer. > > Thanks all. > _______________________________________________ > 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 > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Jul 17 11:48:56 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 17 Jul 2017 10:48:56 -0500 Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <1784503810.2268640.1500304873791@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> Message-ID: There shouldn't be any geometry smoothing going on in this filter. Can you verify that the geometry has changed in the smoothed version? This is speculation, but one possibility is that the surface normals in your original surface come from a gradient computation in the volume from which the surface was extracted and noise in the volume result in the bumpy appearance. You can check this by applying the vtkPolyDataNormals filter to your original surface and looking at the result. HTH, Cory On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi < majid.msadeghi at yahoo.com> wrote: > Dear Cory, > > Thanks for the reply, I set the actors property to SetInterpolationToFlat > (); as you said, but the result is the same I put a picture before and > after boolean operation here. Any suggestion? Are you familier with any > other library? Current boolean operation takes about 150 seconds on my > system, do you think this is normal? > > [image: Inline image] > > > > > On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What do you mean by smooth? The lighting is smooth? I think the filter > may be adding surface normals, in which case any actor for the data > will turn on Gouraud shading (or maybe Phong) by default, which will > make your surface look smooth. You can turn off smooth lighting as > shown in this example: > > http://www.vtk.org/Wiki/VTK/Examples/Cxx/Visualization/FlatShading > > On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers > wrote: > > Hi everyone, > > > > I am using vtkBooleanOperationPolyDataFilter, and it works fine except > after > > the operation it smoothes the polydata, which I dont want. Is there a > way to > > stop that? Or is there another library for boolean operations on > polydata? > > > > Thanks. > > > > > > _______________________________________________ > > 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 > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From majid.msadeghi at yahoo.com Mon Jul 17 12:22:05 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Mon, 17 Jul 2017 16:22:05 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> Message-ID: <923607396.2192921.1500308525188@mail.yahoo.com> Dear Cory, As I applied vtkPolyDataNormals to the polydata before the boolean operation I got the smoothed object, so you were right. But I dont understand exactly what is happening here? Since the geometry dimentions are very important for my application, Can I have the noisy version? Is there any way I do not get it smoothed? Thanks, On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen wrote: There shouldn't be any geometry smoothing going on in this filter. Can you verify that the geometry has changed in the smoothed version? This is speculation, but one possibility is that the surface normals in your original surface come from a gradient computation in the volume from which the surface was extracted and noise in the volume result in the bumpy appearance. You can check this by applying the vtkPolyDataNormals filter to your original surface and looking at the result. HTH,Cory On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi wrote: Dear Cory, Thanks for the reply, I set the actors property to? SetInterpolationToFlat(); as you said, but the result is the same I put a picture before and after boolean operation here. Any suggestion? Are you familier with any other library? Current boolean operation takes about 150 seconds on my system, do you think this is normal? On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen wrote: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > ______________________________ _________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From cory.quammen at kitware.com Mon Jul 17 12:33:16 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 17 Jul 2017 11:33:16 -0500 Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <923607396.2192921.1500308525188@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> Message-ID: What I think you are seeing with the rough surface is surface normals generated from an image volume. I am assuming a lot here, so please correct me if I am wrong. It looks like you have a geometry of a bone extracted from a CT scan. The extraction algorithm was probably a variant of marching cubes or a similar algorithm. The surface normals estimated from the surface extraction algorithm were probably computed from the intensity gradient of the CT scan. This is a reasonable approach, but noise in the CT scan will affect the gradient calculation and may perturb the surface normals in the geometry a little. When this happens, you can get a rough appearing surface from the surface lighting calculation. Google "bump mapping" for how this can be used for a nice graphics effect - I think roughly the same thing is happening with your original data. When you use vtkPolyDataNormals, the normals are computed from the surface data, which was smooth to begin with. Hence, the normals are not perturbed, so you don't get a bumpy appearance. In any case, the measurements you want to take are not dependent on the surface normals. As long as the points on the surface are not smooth, which they should not be, your measurement procedure should be fine. To convince yourself the geometry is the same, you can display both the original "bumpy" surface and the smoothed surface at the same time with different colors. You should see just one surface or the other, probably the one you added to the vtkRenderer last. If the geometry is different, you will see some of one surface color and some of the other depending on which geometry is closer to the camera. I suspect you will see just one surface. HTH, Cory On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi < majid.msadeghi at yahoo.com> wrote: > Dear Cory, > > As I applied vtkPolyDataNormals to the polydata before the boolean > operation I got the smoothed object, so you were right. But I dont > understand exactly what is happening here? Since the geometry dimentions > are very important for my application, Can I have the noisy version? Is > there any way I do not get it smoothed? > > Thanks, > > > > > On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > There shouldn't be any geometry smoothing going on in this filter. Can you > verify that the geometry has changed in the smoothed version? > > This is speculation, but one possibility is that the surface normals in > your original surface come from a gradient computation in the volume from > which the surface was extracted and noise in the volume result in the bumpy > appearance. You can check this by applying the vtkPolyDataNormals filter to > your original surface and looking at the result. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > Thanks for the reply, I set the actors property to SetInterpolationToFlat > (); as you said, but the result is the same I put a picture before and > after boolean operation here. Any suggestion? Are you familier with any > other library? Current boolean operation takes about 150 seconds on my > system, do you think this is normal? > > [image: Inline image] > > > > > On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What do you mean by smooth? The lighting is smooth? I think the filter > may be adding surface normals, in which case any actor for the data > will turn on Gouraud shading (or maybe Phong) by default, which will > make your surface look smooth. You can turn off smooth lighting as > shown in this example: > > http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading > > > On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers > wrote: > > Hi everyone, > > > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except > after > > the operation it smoothes the polydata, which I dont want. Is there a > way to > > stop that? Or is there another library for boolean operations on > polydata? > > > > Thanks. > > > > > > ______________________________ _________________ > > 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 > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From majid.msadeghi at yahoo.com Mon Jul 17 12:47:30 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Mon, 17 Jul 2017 16:47:30 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> Message-ID: <1236928608.2359425.1500310050954@mail.yahoo.com> Dear Cory, All you said was exactly what I have done. I tested your method to check the data and I could see only one of the objects. So If I understand right, during the boolean operation the vtkPolyDataNormals are recalculated and that is the reason the polydata is shown smoothed. Is there a way not to let boolean recalculate it? Or more generally is there a way to keep the bumps. That kind of is the norm in the medical field and some doctors might not feel very good about the smooth data. Thanks. On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen wrote: What I think you are seeing with the rough surface is surface normals generated from an image volume. I am assuming a lot here, so please correct me if I am wrong. It looks like you have a geometry of a bone extracted from a CT scan. The extraction algorithm was probably a variant of marching cubes or a similar algorithm. The surface normals estimated from the surface extraction algorithm were probably computed from the intensity gradient of the CT scan. This is a reasonable approach, but noise in the CT scan will affect the gradient calculation and may perturb the surface normals in the geometry a little. When this happens, you can get a rough appearing surface from the surface lighting calculation. Google "bump mapping" for how this can be used for a nice graphics effect - I think roughly the same thing is happening with your original data. When you use vtkPolyDataNormals, the normals are computed from the surface data, which was smooth to begin with. Hence, the normals are not perturbed, so you don't get a bumpy appearance. In any case, the measurements you want to take are not dependent on the surface normals. As long as the points on the surface are not smooth, which they should not be, your measurement procedure should be fine. To convince yourself the geometry is the same, you can display both the original "bumpy" surface and the smoothed surface at the same time with different colors. You should see just one surface or the other, probably the one you added to the vtkRenderer last. If the geometry is different, you will see some of one surface color and some of the other depending on which geometry is closer to the camera. I suspect you will see just one surface. HTH,Cory On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi wrote: Dear Cory, As I applied vtkPolyDataNormals to the polydata before the boolean operation I got the smoothed object, so you were right. But I dont understand exactly what is happening here? Since the geometry dimentions are very important for my application, Can I have the noisy version? Is there any way I do not get it smoothed? Thanks, On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen wrote: There shouldn't be any geometry smoothing going on in this filter. Can you verify that the geometry has changed in the smoothed version? This is speculation, but one possibility is that the surface normals in your original surface come from a gradient computation in the volume from which the surface was extracted and noise in the volume result in the bumpy appearance. You can check this by applying the vtkPolyDataNormals filter to your original surface and looking at the result. HTH,Cory On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi wrote: Dear Cory, Thanks for the reply, I set the actors property to? SetInterpolationToFlat(); as you said, but the result is the same I put a picture before and after boolean operation here. Any suggestion? Are you familier with any other library? Current boolean operation takes about 150 seconds on my system, do you think this is normal? On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen wrote: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > ______________________________ _________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From adarshdesai.dsp at gmail.com Mon Jul 17 14:25:44 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Mon, 17 Jul 2017 11:25:44 -0700 Subject: [vtkusers] Widgets not working in a renderer In-Reply-To: References: Message-ID: Hi, I am using VTK version 7.1. Set up: I have one render window, 4 tiles which correspond to 4 renderers, each of them have different actors. One renderer which has Actor2D (image) doesnt respond to any widgets. I am using slider widget, button widget. But they work on other renderers, there is no specific change that was done to this renderer alone. Thanks, On Mon, Jul 17, 2017 at 8:23 AM, Sankhesh Jhaveri < sankhesh.jhaveri at kitware.com> wrote: > Could you share more details about the renderer setup, which widgets are > you using, VTK version, etc.? > ? > > On Sun, Jul 16, 2017 at 2:48 AM abcd efgh > wrote: > >> Hello, >> >> I have 4 renderers in a window, in 3 of them widgets work. However in one >> of them widgets dont work. I havent done any specific changes for that >> renderer. >> >> Thanks all. >> _______________________________________________ >> 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 >> > -- > Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware > | (518) 881-4417 > ? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adarshdesai.dsp at gmail.com Mon Jul 17 14:31:11 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Mon, 17 Jul 2017 11:31:11 -0700 Subject: [vtkusers] Problem with shadows In-Reply-To: References: Message-ID: Thanks, if I turn off scalars then I see only white color, by the way even after that I see the shadow effects, how can I turn off the shadows in the scene completely. I think the problem is with respect to shadows. Thanks again. On Sun, Jul 16, 2017 at 5:21 AM, David Gobbi wrote: > Clipping a data set adds scalars to the data set. These scalars are > probably causing the strange coloring that you are seeing. You can tell the > mapper to ignore the scalars, and use the vtkProperty color instead: > > mapper->ScalarVisibilityOff(); > > - David > > On Sun, Jul 16, 2017 at 2:15 AM, abcd efgh > wrote: > >> Hello, >> >> I am new to vtk. I have a 3D polydata, I cut it using vtkClipPolydata. >> Now there are some shadow kind of thing, I have called functions to turn >> off shadows >> as well as backface culling as off. But still shadow kind of effect >> remains and the Poly data is sometimes dark due to this. >> >> Thanks >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Mon Jul 17 14:46:43 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Mon, 17 Jul 2017 18:46:43 +0000 Subject: [vtkusers] Widgets not working in a renderer In-Reply-To: References: Message-ID: I know that the button widget has issues when using with multiple viewports. Its possible that the slider widget has similar issues. I'll look into it. Hopefully, we?ll have a fix soon. Thanks, Sankhesh ? On Mon, Jul 17, 2017 at 2:25 PM abcd efgh wrote: > Hi, > > I am using VTK version 7.1. > Set up: > I have one render window, 4 tiles which correspond to 4 renderers, each of > them have different actors. > One renderer which has Actor2D (image) doesnt respond to any widgets. > I am using slider widget, button widget. > But they work on other renderers, there is no specific change that was > done to this renderer alone. > > Thanks, > > > On Mon, Jul 17, 2017 at 8:23 AM, Sankhesh Jhaveri < > sankhesh.jhaveri at kitware.com> wrote: > >> Could you share more details about the renderer setup, which widgets are >> you using, VTK version, etc.? >> ? >> >> On Sun, Jul 16, 2017 at 2:48 AM abcd efgh >> wrote: >> >>> Hello, >>> >>> I have 4 renderers in a window, in 3 of them widgets work. However in >>> one of them widgets dont work. I havent done any specific changes for that >>> renderer. >>> >>> Thanks all. >>> _______________________________________________ >>> 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 >>> >> -- >> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >> | (518) 881-4417 >> ? >> > > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From adarshdesai.dsp at gmail.com Mon Jul 17 14:49:46 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Mon, 17 Jul 2017 11:49:46 -0700 Subject: [vtkusers] Widgets not working in a renderer In-Reply-To: References: Message-ID: Hi, yes, slider also has same issues. Thanks, On Mon, Jul 17, 2017 at 11:46 AM, Sankhesh Jhaveri < sankhesh.jhaveri at kitware.com> wrote: > I know that the button widget has issues when using with multiple > viewports. Its possible that the slider widget has similar issues. > I'll look into it. Hopefully, we?ll have a fix soon. > > Thanks, > Sankhesh > ? > > On Mon, Jul 17, 2017 at 2:25 PM abcd efgh > wrote: > >> Hi, >> >> I am using VTK version 7.1. >> Set up: >> I have one render window, 4 tiles which correspond to 4 renderers, each >> of them have different actors. >> One renderer which has Actor2D (image) doesnt respond to any widgets. >> I am using slider widget, button widget. >> But they work on other renderers, there is no specific change that was >> done to this renderer alone. >> >> Thanks, >> >> >> On Mon, Jul 17, 2017 at 8:23 AM, Sankhesh Jhaveri < >> sankhesh.jhaveri at kitware.com> wrote: >> >>> Could you share more details about the renderer setup, which widgets are >>> you using, VTK version, etc.? >>> ? >>> >>> On Sun, Jul 16, 2017 at 2:48 AM abcd efgh >>> wrote: >>> >>>> Hello, >>>> >>>> I have 4 renderers in a window, in 3 of them widgets work. However in >>>> one of them widgets dont work. I havent done any specific changes for that >>>> renderer. >>>> >>>> Thanks all. >>>> _______________________________________________ >>>> 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 >>>> >>> -- >>> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >>> | (518) 881-4417 >>> ? >>> >> >> -- > Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware > | (518) 881-4417 > ? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Mon Jul 17 15:06:41 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Mon, 17 Jul 2017 13:06:41 -0600 Subject: [vtkusers] Problem with shadows In-Reply-To: References: Message-ID: If it isn't the scalars, then it is probably the normals. If the data has bad normals, then lighting of the data will be incorrect. You can try generating new normals for the data with vtkPolyDataNormals. Make sure that you read the documentation for this class, it has lots of options. - David On Mon, Jul 17, 2017 at 12:31 PM, abcd efgh wrote: > Thanks, > if I turn off scalars then I see only white color, by the way even after > that I see the shadow effects, how can I turn off the shadows in the scene > completely. > I think the problem is with respect to shadows. > > Thanks again. > > On Sun, Jul 16, 2017 at 5:21 AM, David Gobbi > wrote: > >> Clipping a data set adds scalars to the data set. These scalars are >> probably causing the strange coloring that you are seeing. You can tell the >> mapper to ignore the scalars, and use the vtkProperty color instead: >> >> mapper->ScalarVisibilityOff(); >> >> - David >> >> On Sun, Jul 16, 2017 at 2:15 AM, abcd efgh >> wrote: >> >>> Hello, >>> >>> I am new to vtk. I have a 3D polydata, I cut it using vtkClipPolydata. >>> Now there are some shadow kind of thing, I have called functions to turn >>> off shadows >>> as well as backface culling as off. But still shadow kind of effect >>> remains and the Poly data is sometimes dark due to this. >>> >>> Thanks >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Mon Jul 17 18:18:51 2017 From: jayavardhanravi at outlook.com (kay) Date: Mon, 17 Jul 2017 15:18:51 -0700 (MST) Subject: [vtkusers] How do we check weather my VTK application is using GPU/ Graphic card Message-ID: <1500329931056-5743997.post@n5.nabble.com> I am trying to measure the performance of the VTK application. I am trying find whether my application is using graphic card or not. Can anyone let me know how do I check this. I had the NVidia graphic card installed on my system and all the drivers are updated. Thanks for you time Regards, Kay -- View this message in context: http://vtk.1045678.n5.nabble.com/How-do-we-check-weather-my-VTK-application-is-using-GPU-Graphic-card-tp5743997.html Sent from the VTK - Users mailing list archive at Nabble.com. From kmorel at sandia.gov Mon Jul 17 18:19:56 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 17 Jul 2017 22:19:56 +0000 Subject: [vtkusers] **Deadline Extended** CFP: 3rd Annual Workshop on In Situ Infrastructures for Enabling Extreme-Scale Analysis and Visualization (ISAV 2017) Message-ID: <2108aaf3872140a281b84920cc9dc924@ES08AMSNLNT.srn.sandia.gov> Sorry for the spam, but some VTK users may be interested in this workshop. Update: paper submission due date extended to 15 Aug 2017 23:59 AoE ISAV 2017: In Situ Infrastructures for Enabling Extreme-Scale Analysis and Visualization In cooperation with SIGHPC and held in conjunction with SC17: The International Conference on High Performance Computing, Networking, Storage and Analysis, Denver, Colorado, U.S.A. ISAV 2017 - http://vis.lbl.gov/Events/ISAV-2017/ Full-day 9:00 AM - 5:30 PM Sunday November 12th, 2017 Workshop Theme The considerable interest in the HPC community regarding in situ analysis and visualization is due to several factors. First is an I/O cost savings, where data is analyzed/visualized while being generated, without first storing to a file system. Second is the potential for increased accuracy, where fine temporal sampling of transient analysis might expose some complex behavior missed in coarse temporal sampling. Third is the ability to use all available resources, CPUs and accelerators, in the computation of analysis products. The workshop brings together researchers, developers and practitioners from industry, academia, and government laboratories developing, applying, and deploying in situ methods in extreme-scale, high performance computing. The goal is to present research findings, lessons learned, and insights related to developing and applying in situ methods and infrastructure across a range of science and engineering applications in HPC environments; to discuss topics like opportunities presented by new architectures, existing infrastructure needs, requirements, and gaps, and experiences to foster and enable in situ analysis and visualization; to serve as a "center of gravity" for researchers, practitioners, and users/consumers of in situ methods and infrastructure in the HPC space. Participation/Call for Papers and Oral Presentations We invite two types of submissions to ISAV 2017: (1) short, 4-page papers that present research results, that identify opportunities or challenges, and that present case studies/best practices for in situ methods/infrastructure in the areas of data management, analysis and visualization; (2) lightning presentation submission, consisting of a 1- or 2-page submission, for a brief oral presentation at the workshop. Short papers will appear in the workshop proceedings and will be invited to give an oral presentation of 15 to 20 minutes; lightning round submissions that are invited to present at the workshop will have author names and titles included as part of the proceedings. Submissions of both types are welcome that fall within one or more areas of interest, as follows: Areas of interest for ISAV, include, but are not limited to: In situ infrastructures * Current Systems: production quality, research prototypes * Opportunities * Gaps System resources, hardware, and emerging architectures * Enabling Hardware * Hardware and architectures that provide opportunities for in situ processing, such as burst buffers, staging computations on I/O nodes, sharing cores within a node for both simulation and in situ processing Methods/algorithms/applications/Case studies * Best practices * Analysis: feature detection, statistical methods, temporal methods, geometric methods * Visualization: information visualization, scientific visualization, time-varying methods * Data reduction/compression * Examples/case studies of solving a specific science challenge with in situ methods/infrastructure. Simulation * Integration: data modeling, software-engineering * Resilience: error detection, fault recovery * Workflows for supporting complex in situ processing pipelines Requirements * Preserve important elements * Significantly reduce the data size * Flexibility for post-processing exploration Review Process All submissions will undergo a peer-review process consisting of three reviews by experts in the field, and evaluated according to relevance to the workshop theme, technical soundness, creativity, originality, and impactfulness of method/results. Lightning round submissions will be evaluated primarily for relevance to the workshop. Submission Process Authors are invited to submit papers of at most 4 pages in PDF format, excluding references, and lightning presentations of at most 2 pages in PDF format, excluding references. Papers must be submitted in PDF format (readable by Adobe Acrobat Reader 5.0 and higher) and formatted for 8.5" x 11" (U.S. Letter). Submissions are required in the ACM format (http://www.acm.org/sigs/publications/proceedings-templates) using the sample-sigconf template and submitted via EasyChair (https://easychair.org/conferences/?conf=isav17). No changes to the margins, spacing, or font sizes as specified by the style file are allowed. Papers must be self-contained and provide the technical substance required for the program committee to evaluate their contributions. Submitted papers must be original work that has not appeared in and is not under consideration for another conference or a journal. See the ACM Prior Publication Policy for more details (http://www.acm.org/publications/policies/). Papers can be submitted at https://easychair.org/conferences/?conf=isav17. Publication in proceedings, presentation at the workshop All paper submissions that receive favorable reviews will be included as part of the workshop proceedings, which will be published through SIGHPC along with other SC17 workshop proceedings in the ACM Digital Library and IEEE Xplore. Lightning round submissions will not be included as part of the proceedings. Subject to the constraints of workshop length, some subset of the accepted publications will be invited to give a brief oral presentation at the workshop. The exact number of such presentations and their length will be determined after the review process has been completed. Timeline/Important Dates 15 August 2017 Paper submission deadline 15 September 2017 Author notification 30 September 2017 Camera ready copy due 15 October 2017 Final program posted to ISAV web page 12 November 2017 ISAV 2017 workshop at SC17 From tjlp at netease.com Tue Jul 18 03:45:14 2017 From: tjlp at netease.com (Liu_tj) Date: Tue, 18 Jul 2017 15:45:14 +0800 (CST) Subject: [vtkusers] How to trigger an event programmatically instead of mouse click or move? Message-ID: <5f2ba86f.5.15d54a87c96.Coremail.tjlp@netease.com> Hi, I have 2 RenderWindows for DICOM axial plane and 3D model respectively. I want to measure distance on these 2 windows at the same time with vtkDistanceWidget. So, is possible that if an event, such as PlacePointEvent, is triggered by mouse on axial plane RenderWindow, the same event with the same world position values is triggered programmatically on the 3D model RenderWindow? Thanks Liu Peng -------------- next part -------------- An HTML attachment was scrubbed... URL: From taron2000 at gmx.de Tue Jul 18 06:32:56 2017 From: taron2000 at gmx.de (Taron) Date: Tue, 18 Jul 2017 03:32:56 -0700 (MST) Subject: [vtkusers] Delayloading VTK Message-ID: <1500373976551-5744000.post@n5.nabble.com> Hi everyone, I am trying to delay load some vtk DLLs in my application. I want to achieve to set different DLL directory for opengl32.dll to switch to a software renderer. Despite declaring the dlls with /DELAYLOAD: some DLLs are instantly loaded at startup of the application. I traced it down and it seems to be related with VTK_MODULE_INIT. This seems to initialize some stuff right at startup and therefore loading some vtk DLLS. Is there anyway to delay the initialization of the VTK modules, so that the delayloading actually works? Best Regards Klaus -- View this message in context: http://vtk.1045678.n5.nabble.com/Delayloading-VTK-tp5744000.html Sent from the VTK - Users mailing list archive at Nabble.com. From taron2000 at gmx.de Tue Jul 18 08:17:46 2017 From: taron2000 at gmx.de (Taron) Date: Tue, 18 Jul 2017 05:17:46 -0700 (MST) Subject: [vtkusers] Delayloading VTK In-Reply-To: <1500373976551-5744000.post@n5.nabble.com> References: <1500373976551-5744000.post@n5.nabble.com> Message-ID: <1500380266410-5744001.post@n5.nabble.com> After further fidling I found a solution that seems to work for me. I simply recompiled VTK with /DELAYLOAD:opengl32.dll and it seems to work fine. Lets see what further testing brings up. -- View this message in context: http://vtk.1045678.n5.nabble.com/Delayloading-VTK-tp5744000p5744001.html Sent from the VTK - Users mailing list archive at Nabble.com. From cory.quammen at kitware.com Tue Jul 18 09:21:42 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 18 Jul 2017 08:21:42 -0500 Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <1236928608.2359425.1500310050954@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> Message-ID: Hmm, now I wonder if the boolean operations filter is simply removing the normals filter. The code has changed from the original, which did preserve normals. It looks like the current code should preserve normals as well, but I'm not 100% sure if that is the case. In the output of the boolean operation filter, could you check that there is a normals array in the pointdata? vtkDataArray* normals = output->GetPointData()->GetNormals(); If "normals" is NULL, then the normals are not being copied to the output. Thanks, Cory On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi < majid.msadeghi at yahoo.com> wrote: > Dear Cory, > > All you said was exactly what I have done. I tested your method to check > the data and I could see only one of the objects. So If I understand right, > during the boolean operation the vtkPolyDataNormals are recalculated and > that is the reason the polydata is shown smoothed. Is there a way not to > let boolean recalculate it? Or more generally is there a way to keep the > bumps. That kind of is the norm in the medical field and some doctors might > not feel very good about the smooth data. > > Thanks. > > > > > > On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What I think you are seeing with the rough surface is surface normals > generated from an image volume. I am assuming a lot here, so please correct > me if I am wrong. It looks like you have a geometry of a bone extracted > from a CT scan. The extraction algorithm was probably a variant of marching > cubes or a similar algorithm. The surface normals estimated from the > surface extraction algorithm were probably computed from the intensity > gradient of the CT scan. This is a reasonable approach, but noise in the CT > scan will affect the gradient calculation and may perturb the surface > normals in the geometry a little. When this happens, you can get a rough > appearing surface from the surface lighting calculation. Google "bump > mapping" for how this can be used for a nice graphics effect - I think > roughly the same thing is happening with your original data. > > When you use vtkPolyDataNormals, the normals are computed from the surface > data, which was smooth to begin with. Hence, the normals are not perturbed, > so you don't get a bumpy appearance. > > In any case, the measurements you want to take are not dependent on the > surface normals. As long as the points on the surface are not smooth, which > they should not be, your measurement procedure should be fine. > > To convince yourself the geometry is the same, you can display both the > original "bumpy" surface and the smoothed surface at the same time with > different colors. You should see just one surface or the other, probably > the one you added to the vtkRenderer last. If the geometry is different, > you will see some of one surface color and some of the other depending on > which geometry is closer to the camera. I suspect you will see just one > surface. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > As I applied vtkPolyDataNormals to the polydata before the boolean > operation I got the smoothed object, so you were right. But I dont > understand exactly what is happening here? Since the geometry dimentions > are very important for my application, Can I have the noisy version? Is > there any way I do not get it smoothed? > > Thanks, > > > > > On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > There shouldn't be any geometry smoothing going on in this filter. Can you > verify that the geometry has changed in the smoothed version? > > This is speculation, but one possibility is that the surface normals in > your original surface come from a gradient computation in the volume from > which the surface was extracted and noise in the volume result in the bumpy > appearance. You can check this by applying the vtkPolyDataNormals filter to > your original surface and looking at the result. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > Thanks for the reply, I set the actors property to SetInterpolationToFlat > (); as you said, but the result is the same I put a picture before and > after boolean operation here. Any suggestion? Are you familier with any > other library? Current boolean operation takes about 150 seconds on my > system, do you think this is normal? > > [image: Inline image] > > > > > On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What do you mean by smooth? The lighting is smooth? I think the filter > may be adding surface normals, in which case any actor for the data > will turn on Gouraud shading (or maybe Phong) by default, which will > make your surface look smooth. You can turn off smooth lighting as > shown in this example: > > http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading > > > On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers > wrote: > > Hi everyone, > > > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except > after > > the operation it smoothes the polydata, which I dont want. Is there a > way to > > stop that? Or is there another library for boolean operations on > polydata? > > > > Thanks. > > > > > > ______________________________ _________________ > > 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 > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From majid.msadeghi at yahoo.com Tue Jul 18 10:03:33 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Tue, 18 Jul 2017 14:03:33 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> Message-ID: <1781957654.3072634.1500386613818@mail.yahoo.com> Dear Cory, !normals returns true, so as you said there is no normal array. Is there a way to copy that before the operation and apply it afterwards? But I think that wont work because part of the data is changed in the boolean operation. So how can we keep the normals? Thanks, On Tuesday, July 18, 2017, 4:21:45 PM GMT+3, Cory Quammen wrote: Hmm, now I wonder if the boolean operations filter is simply removing the normals filter. The code has changed from the original, which did preserve normals. It looks like the current code should preserve normals as well, but I'm not 100% sure if that is the case. In the output of the boolean operation filter, could you check that there is a normals array in the pointdata? vtkDataArray* normals = output->GetPointData()-> GetNormals(); If "normals" is NULL, then the normals are not being copied to the output. Thanks,Cory On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi wrote: Dear Cory, All you said was exactly what I have done. I tested your method to check the data and I could see only one of the objects. So If I understand right, during the boolean operation the vtkPolyDataNormals are recalculated and that is the reason the polydata is shown smoothed. Is there a way not to let boolean recalculate it? Or more generally is there a way to keep the bumps. That kind of is the norm in the medical field and some doctors might not feel very good about the smooth data. Thanks. On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen wrote: What I think you are seeing with the rough surface is surface normals generated from an image volume. I am assuming a lot here, so please correct me if I am wrong. It looks like you have a geometry of a bone extracted from a CT scan. The extraction algorithm was probably a variant of marching cubes or a similar algorithm. The surface normals estimated from the surface extraction algorithm were probably computed from the intensity gradient of the CT scan. This is a reasonable approach, but noise in the CT scan will affect the gradient calculation and may perturb the surface normals in the geometry a little. When this happens, you can get a rough appearing surface from the surface lighting calculation. Google "bump mapping" for how this can be used for a nice graphics effect - I think roughly the same thing is happening with your original data. When you use vtkPolyDataNormals, the normals are computed from the surface data, which was smooth to begin with. Hence, the normals are not perturbed, so you don't get a bumpy appearance. In any case, the measurements you want to take are not dependent on the surface normals. As long as the points on the surface are not smooth, which they should not be, your measurement procedure should be fine. To convince yourself the geometry is the same, you can display both the original "bumpy" surface and the smoothed surface at the same time with different colors. You should see just one surface or the other, probably the one you added to the vtkRenderer last. If the geometry is different, you will see some of one surface color and some of the other depending on which geometry is closer to the camera. I suspect you will see just one surface. HTH,Cory On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi wrote: Dear Cory, As I applied vtkPolyDataNormals to the polydata before the boolean operation I got the smoothed object, so you were right. But I dont understand exactly what is happening here? Since the geometry dimentions are very important for my application, Can I have the noisy version? Is there any way I do not get it smoothed? Thanks, On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen wrote: There shouldn't be any geometry smoothing going on in this filter. Can you verify that the geometry has changed in the smoothed version? This is speculation, but one possibility is that the surface normals in your original surface come from a gradient computation in the volume from which the surface was extracted and noise in the volume result in the bumpy appearance. You can check this by applying the vtkPolyDataNormals filter to your original surface and looking at the result. HTH,Cory On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi wrote: Dear Cory, Thanks for the reply, I set the actors property to? SetInterpolationToFlat(); as you said, but the result is the same I put a picture before and after boolean operation here. Any suggestion? Are you familier with any other library? Current boolean operation takes about 150 seconds on my system, do you think this is normal? On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen wrote: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > ______________________________ _________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Jul 18 10:26:02 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 18 Jul 2017 09:26:02 -0500 Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <1781957654.3072634.1500386613818@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> <1781957654.3072634.1500386613818@mail.yahoo.com> Message-ID: Okay, let's try one more thing. Does vtkDataArray* normals = output->GetPointData()->GetArray("Normals"); return NULL? Perhaps the normals array is being copied but not being set as the active normals. Thanks, Cory On Tue, Jul 18, 2017 at 9:03 AM, Majid Mohammad sadeghi < majid.msadeghi at yahoo.com> wrote: > Dear Cory, > > !normals returns true, so as you said there is no normal array. Is there a > way to copy that before the operation and apply it afterwards? But I think > that wont work because part of the data is changed in the boolean > operation. So how can we keep the normals? > > Thanks, > > > On Tuesday, July 18, 2017, 4:21:45 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > Hmm, now I wonder if the boolean operations filter is simply removing the > normals filter. The code has changed from the original, which did preserve > normals. It looks like the current code should preserve normals as well, > but I'm not 100% sure if that is the case. > > In the output of the boolean operation filter, could you check that there > is a normals array in the pointdata? > > vtkDataArray* normals = output->GetPointData()-> GetNormals(); > > If "normals" is NULL, then the normals are not being copied to the output. > > Thanks, > Cory > > > > On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > All you said was exactly what I have done. I tested your method to check > the data and I could see only one of the objects. So If I understand right, > during the boolean operation the vtkPolyDataNormals are recalculated and > that is the reason the polydata is shown smoothed. Is there a way not to > let boolean recalculate it? Or more generally is there a way to keep the > bumps. That kind of is the norm in the medical field and some doctors might > not feel very good about the smooth data. > > Thanks. > > > > > > On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What I think you are seeing with the rough surface is surface normals > generated from an image volume. I am assuming a lot here, so please correct > me if I am wrong. It looks like you have a geometry of a bone extracted > from a CT scan. The extraction algorithm was probably a variant of marching > cubes or a similar algorithm. The surface normals estimated from the > surface extraction algorithm were probably computed from the intensity > gradient of the CT scan. This is a reasonable approach, but noise in the CT > scan will affect the gradient calculation and may perturb the surface > normals in the geometry a little. When this happens, you can get a rough > appearing surface from the surface lighting calculation. Google "bump > mapping" for how this can be used for a nice graphics effect - I think > roughly the same thing is happening with your original data. > > When you use vtkPolyDataNormals, the normals are computed from the surface > data, which was smooth to begin with. Hence, the normals are not perturbed, > so you don't get a bumpy appearance. > > In any case, the measurements you want to take are not dependent on the > surface normals. As long as the points on the surface are not smooth, which > they should not be, your measurement procedure should be fine. > > To convince yourself the geometry is the same, you can display both the > original "bumpy" surface and the smoothed surface at the same time with > different colors. You should see just one surface or the other, probably > the one you added to the vtkRenderer last. If the geometry is different, > you will see some of one surface color and some of the other depending on > which geometry is closer to the camera. I suspect you will see just one > surface. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > As I applied vtkPolyDataNormals to the polydata before the boolean > operation I got the smoothed object, so you were right. But I dont > understand exactly what is happening here? Since the geometry dimentions > are very important for my application, Can I have the noisy version? Is > there any way I do not get it smoothed? > > Thanks, > > > > > On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > There shouldn't be any geometry smoothing going on in this filter. Can you > verify that the geometry has changed in the smoothed version? > > This is speculation, but one possibility is that the surface normals in > your original surface come from a gradient computation in the volume from > which the surface was extracted and noise in the volume result in the bumpy > appearance. You can check this by applying the vtkPolyDataNormals filter to > your original surface and looking at the result. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > Thanks for the reply, I set the actors property to SetInterpolationToFlat > (); as you said, but the result is the same I put a picture before and > after boolean operation here. Any suggestion? Are you familier with any > other library? Current boolean operation takes about 150 seconds on my > system, do you think this is normal? > > [image: Inline image] > > > > > On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What do you mean by smooth? The lighting is smooth? I think the filter > may be adding surface normals, in which case any actor for the data > will turn on Gouraud shading (or maybe Phong) by default, which will > make your surface look smooth. You can turn off smooth lighting as > shown in this example: > > http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading > > > On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers > wrote: > > Hi everyone, > > > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except > after > > the operation it smoothes the polydata, which I dont want. Is there a > way to > > stop that? Or is there another library for boolean operations on > polydata? > > > > Thanks. > > > > > > ______________________________ _________________ > > 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 > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From dan.lipsa at kitware.com Tue Jul 18 10:58:55 2017 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 18 Jul 2017 10:58:55 -0400 Subject: [vtkusers] How do we check weather my VTK application is using GPU/ Graphic card In-Reply-To: <1500329931056-5743997.post@n5.nabble.com> References: <1500329931056-5743997.post@n5.nabble.com> Message-ID: You'll have to cast your render window to vtkOpenGLRenderWindow. If w is your render window you have to: vtkOpenGLExtensionManager *extensions = w->GetExtensionManager(); std::cout << extensions->GetDriverGLVendor() << std::endl << extensions->GetDriverGLVersion() << std::endl << extensions->GetDriverGLRenderer() << std::endl; On Mon, Jul 17, 2017 at 6:18 PM, kay wrote: > I am trying to measure the performance of the VTK application. I am trying > find whether my application is using graphic card or not. Can anyone let me > know how do I check this. > > I had the NVidia graphic card installed on my system and all the drivers > are > updated. > > Thanks for you time > > Regards, > Kay > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/How-do-we-check-weather-my-VTK-application-is-using- > GPU-Graphic-card-tp5743997.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Tue Jul 18 11:32:39 2017 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 18 Jul 2017 11:32:39 -0400 Subject: [vtkusers] How do we check weather my VTK application is using GPU/ Graphic card In-Reply-To: References: <1500329931056-5743997.post@n5.nabble.com> Message-ID: You might try cout << yourRenderWindow->ReportCapabilities(); or something like that On Tue, Jul 18, 2017 at 10:58 AM, Dan Lipsa wrote: > You'll have to cast your render window to vtkOpenGLRenderWindow. > If w is your render window you have to: > > vtkOpenGLExtensionManager *extensions = w->GetExtensionManager(); > std::cout << extensions->GetDriverGLVendor() << std::endl > << extensions->GetDriverGLVersion() << std::endl > << extensions->GetDriverGLRenderer() << std::endl; > > > On Mon, Jul 17, 2017 at 6:18 PM, kay wrote: > >> I am trying to measure the performance of the VTK application. I am trying >> find whether my application is using graphic card or not. Can anyone let >> me >> know how do I check this. >> >> I had the NVidia graphic card installed on my system and all the drivers >> are >> updated. >> >> Thanks for you time >> >> Regards, >> Kay >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.c >> om/How-do-we-check-weather-my-VTK-application-is-using-GPU- >> Graphic-card-tp5743997.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> > > > _______________________________________________ > 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 > > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 robert.maynard at kitware.com Tue Jul 18 11:32:01 2017 From: robert.maynard at kitware.com (Robert Maynard) Date: Tue, 18 Jul 2017 11:32:01 -0400 Subject: [vtkusers] VTK Development Survey Message-ID: Hi Everybody, The VTK team is always looking to attract new developers and improve the experience of developing VTK. To further that, we are putting out an anonymous survey to collect data on people's thoughts about the current software development process for VTK. We would love to hear all your rants ( or raves ) on the development process. We will gather the results after August 1'st. https://goo.gl/forms/WlqyiF0sBTZT7klJ3 Thank you for your inputs. From jayavardhanravi at outlook.com Tue Jul 18 11:58:56 2017 From: jayavardhanravi at outlook.com (kay) Date: Tue, 18 Jul 2017 08:58:56 -0700 (MST) Subject: [vtkusers] How do we check weather my VTK application is using GPU/ Graphic card In-Reply-To: References: <1500329931056-5743997.post@n5.nabble.com> Message-ID: <1500393536324-5744008.post@n5.nabble.com> With this function "ReportCapabilities()" I was able to find whether my application is using gpu or not. I was wondering if there is any module in VTK for profiling VTK. Thanks for your time Regards, Kay -- View this message in context: http://vtk.1045678.n5.nabble.com/How-do-we-check-whether-my-VTK-application-is-using-GPU-Graphic-card-tp5743997p5744008.html Sent from the VTK - Users mailing list archive at Nabble.com. From sunxiasx at foxmail.com Wed Jul 19 00:54:11 2017 From: sunxiasx at foxmail.com (Summer Sun) Date: Tue, 18 Jul 2017 21:54:11 -0700 (MST) Subject: [vtkusers] How to update renderer when vtkImageData is updated Message-ID: <1500440051624-5744009.post@n5.nabble.com> I have a vtkImageData and a vtkImageViewer2, I use SetInputData() to set vtkImageData rendered by vtkImageViewer2. However, I have changed the pixel value of vtkImageData by changing the scalar pointer. Now I cannot update the viewer to see the new image, how can I do this? I have learned some past posts, they have metioned Update() method and Modified() method, but they didn't work for me. -- View this message in context: http://vtk.1045678.n5.nabble.com/How-to-update-renderer-when-vtkImageData-is-updated-tp5744009.html Sent from the VTK - Users mailing list archive at Nabble.com. From majid.msadeghi at yahoo.com Wed Jul 19 04:19:26 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Wed, 19 Jul 2017 08:19:26 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> <1781957654.3072634.1500386613818@mail.yahoo.com> Message-ID: <367832745.245417.1500452366892@mail.yahoo.com> Dear Cory, It is still Null. Can we recalculate normals on the output of boolean operation? Thanks, Majid Mohammad Sadeghi PhD Candidate Mechatronics Engineering Department Istanbul Technical University On Tuesday, July 18, 2017, 5:26:05 PM GMT+3, Cory Quammen wrote: Okay, let's try one more thing. Does vtkDataArray* normals = output->GetPointData()->GetArray("Normals"); return NULL? Perhaps the normals array is being copied but not being set as the active normals. Thanks,Cory On Tue, Jul 18, 2017 at 9:03 AM, Majid Mohammad sadeghi wrote: Dear Cory, !normals returns true, so as you said there is no normal array. Is there a way to copy that before the operation and apply it afterwards? But I think that wont work because part of the data is changed in the boolean operation. So how can we keep the normals? Thanks, On Tuesday, July 18, 2017, 4:21:45 PM GMT+3, Cory Quammen wrote: Hmm, now I wonder if the boolean operations filter is simply removing the normals filter. The code has changed from the original, which did preserve normals. It looks like the current code should preserve normals as well, but I'm not 100% sure if that is the case. In the output of the boolean operation filter, could you check that there is a normals array in the pointdata? vtkDataArray* normals = output->GetPointData()-> GetNormals(); If "normals" is NULL, then the normals are not being copied to the output. Thanks,Cory On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi wrote: Dear Cory, All you said was exactly what I have done. I tested your method to check the data and I could see only one of the objects. So If I understand right, during the boolean operation the vtkPolyDataNormals are recalculated and that is the reason the polydata is shown smoothed. Is there a way not to let boolean recalculate it? Or more generally is there a way to keep the bumps. That kind of is the norm in the medical field and some doctors might not feel very good about the smooth data. Thanks. On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen wrote: What I think you are seeing with the rough surface is surface normals generated from an image volume. I am assuming a lot here, so please correct me if I am wrong. It looks like you have a geometry of a bone extracted from a CT scan. The extraction algorithm was probably a variant of marching cubes or a similar algorithm. The surface normals estimated from the surface extraction algorithm were probably computed from the intensity gradient of the CT scan. This is a reasonable approach, but noise in the CT scan will affect the gradient calculation and may perturb the surface normals in the geometry a little. When this happens, you can get a rough appearing surface from the surface lighting calculation. Google "bump mapping" for how this can be used for a nice graphics effect - I think roughly the same thing is happening with your original data. When you use vtkPolyDataNormals, the normals are computed from the surface data, which was smooth to begin with. Hence, the normals are not perturbed, so you don't get a bumpy appearance. In any case, the measurements you want to take are not dependent on the surface normals. As long as the points on the surface are not smooth, which they should not be, your measurement procedure should be fine. To convince yourself the geometry is the same, you can display both the original "bumpy" surface and the smoothed surface at the same time with different colors. You should see just one surface or the other, probably the one you added to the vtkRenderer last. If the geometry is different, you will see some of one surface color and some of the other depending on which geometry is closer to the camera. I suspect you will see just one surface. HTH,Cory On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi wrote: Dear Cory, As I applied vtkPolyDataNormals to the polydata before the boolean operation I got the smoothed object, so you were right. But I dont understand exactly what is happening here? Since the geometry dimentions are very important for my application, Can I have the noisy version? Is there any way I do not get it smoothed? Thanks, On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen wrote: There shouldn't be any geometry smoothing going on in this filter. Can you verify that the geometry has changed in the smoothed version? This is speculation, but one possibility is that the surface normals in your original surface come from a gradient computation in the volume from which the surface was extracted and noise in the volume result in the bumpy appearance. You can check this by applying the vtkPolyDataNormals filter to your original surface and looking at the result. HTH,Cory On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi wrote: Dear Cory, Thanks for the reply, I set the actors property to? SetInterpolationToFlat(); as you said, but the result is the same I put a picture before and after boolean operation here. Any suggestion? Are you familier with any other library? Current boolean operation takes about 150 seconds on my system, do you think this is normal? On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen wrote: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > ______________________________ _________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From palfonso.01 at gmail.com Wed Jul 19 05:17:35 2017 From: palfonso.01 at gmail.com (PonXo86) Date: Wed, 19 Jul 2017 02:17:35 -0700 (MST) Subject: [vtkusers] How to update renderer when vtkImageData is updated In-Reply-To: <1500440051624-5744009.post@n5.nabble.com> References: <1500440051624-5744009.post@n5.nabble.com> Message-ID: <1500455855183-5744012.post@n5.nabble.com> Hi Summer, I had the same problem, and the solution that worked for me was: 1. Use the modified function, for example I was updating the pixel values of my pointer vtkSmartPointer vtk_Im, and after vtk_Im->Modified(). 2. Sure, with the Modified() function your vtkImageViewer2 isn't updated. So, you have to call the method Render() of your pointer vtkImageViewer2 every time after you update your vtkImageData pointer. I hope this works for you. -- View this message in context: http://vtk.1045678.n5.nabble.com/How-to-update-renderer-when-vtkImageData-is-updated-tp5744009p5744012.html Sent from the VTK - Users mailing list archive at Nabble.com. From dolhasqueander at outlook.com Wed Jul 19 06:23:38 2017 From: dolhasqueander at outlook.com (Ander) Date: Wed, 19 Jul 2017 03:23:38 -0700 (MST) Subject: [vtkusers] Operating VTK 7.1.1 on Java 8 on macOS Message-ID: <1500459818433-5744013.post@n5.nabble.com> Hello, I'm working at the moment with VTK 7.1.1 on Java 8, using AWT. VTK works fine on Linux and Windows but not on macOS. That is the reason why I would like to know if using JOGL could solve this problem. I would also like to know if JOGL is the new standard for VTK in Java, and if AWT will still be maintained. -- View this message in context: http://vtk.1045678.n5.nabble.com/Operating-VTK-7-1-1-on-Java-8-on-macOS-tp5744013.html Sent from the VTK - Users mailing list archive at Nabble.com. From satwik.k8 at gmail.com Wed Jul 19 07:58:24 2017 From: satwik.k8 at gmail.com (Satwik) Date: Wed, 19 Jul 2017 04:58:24 -0700 (MST) Subject: [vtkusers] vtk-7.1 openGL 2.0 crash Message-ID: <1500465504824-5744014.post@n5.nabble.com> Hi, I configured VTK-7.1 with *openGL2* as Rendering Backend. But, When i tried to run Volume Rendering or any VTK applications in the machine which is not having openGL2.0. *Application is getting crashed*. How well can i handle this..???? Regards, satwik k -- View this message in context: http://vtk.1045678.n5.nabble.com/vtk-7-1-openGL-2-0-crash-tp5744014.html Sent from the VTK - Users mailing list archive at Nabble.com. From elainejiang8 at gmail.com Wed Jul 19 09:59:00 2017 From: elainejiang8 at gmail.com (elainejiang8) Date: Wed, 19 Jul 2017 06:59:00 -0700 (MST) Subject: [vtkusers] Using vtkExternalOpenGLCamera Message-ID: <1500472740832-5744015.post@n5.nabble.com> Hi everyone! I'm building a program that uses the externalVTKWidget to volume render an object in an OpenGL context. Right now, I'm calling *ren->GetActiveCamera(); * (where ren is a vtkExternalOpenGLRenderWindow instance) in my render function so I can control the position and focal point of the camera. However, I'm unable to get the camera to actually have any effect on the scene. The documentation for vtkExternalOpenGLCamera is rather slim, and I can't find any similar examples, so I am a bit stuck on this issue. Does anyone have any insight into how I could approach this problem? Thanks in advance! Elaine -- View this message in context: http://vtk.1045678.n5.nabble.com/Using-vtkExternalOpenGLCamera-tp5744015.html Sent from the VTK - Users mailing list archive at Nabble.com. From bebe0705 at colorado.edu Wed Jul 19 10:47:35 2017 From: bebe0705 at colorado.edu (BBerco) Date: Wed, 19 Jul 2017 07:47:35 -0700 (MST) Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: Message-ID: <1500475655836-5744016.post@n5.nabble.com> Hello all, I have been working making an application cross platform between MacOS and Linux Ubuntu. This piece of software is built around Qt 5.9.1 and VTK 8 for the GUI side of things. After a lot of fiddling, I'm pleased to say I have no issue at all on MacOS. Here's a link to the Github Wiki of the project, with an illustration of what it looks like as of today when operating nominally (https://github.com/bbercovici/SBGAT/wiki) Unfortunately, I am not quite there yet on Linux/Ubuntu. Specifically, the QVTKWidget at the center of the QMainWindow constituting the GUI acts weird. Here's what's happening when I am running SBGAT on Linux: - Upon launch, the QVTKWidget 'separates' from the QMainWindow, so that I am left with two windows instead of one - The QMainWindow window works fine. All the buttons are responsive. - The QVTKWidget is not responsive. No interaction appears to take place between the mouse cursor upong clicking and the camera orientation. - There is a strange "ghosting" effect with portions of the QVTKWidget that do not get redrawn properly, but show neighboring desktop elements or windows when moved around - When loading in an .obj file using the QMainWindow actions, it gets displayed on the QVTKWidget (so there is "some" rendering going on, although no interaction is possible). My desktop has a NVIDIA 980 GTX GPU, and I am using the latest NVidia drivers I could find on apt-get (nvidia 384 I believe). I believe a more detailed error message is sometimes spitted out by SBGAT upon leaving, I will copy/paste it here later today. Is there anyone who was able to make QVTKWidgets work on a similar platform? Thanks, Ben -- View this message in context: http://vtk.1045678.n5.nabble.com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia-GPU-tp5744016.html Sent from the VTK - Users mailing list archive at Nabble.com. From utkarsh.ayachit at kitware.com Wed Jul 19 10:50:08 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 19 Jul 2017 10:50:08 -0400 Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: <1500475655836-5744016.post@n5.nabble.com> References: <1500475655836-5744016.post@n5.nabble.com> Message-ID: I recommend using the new QVTKOpenGLWidget with Qt 5 instead of QVTKWidget ( http://www.vtk.org/doc/nightly/html/classQVTKOpenGLWidget.html). On Wed, Jul 19, 2017 at 10:47 AM, BBerco wrote: > Hello all, > > I have been working making an application cross platform between MacOS and > Linux Ubuntu. This piece of software is built around Qt 5.9.1 and VTK 8 for > the GUI side of things. > > After a lot of fiddling, I'm pleased to say I have no issue at all on > MacOS. > Here's a link to the Github Wiki of the project, with an illustration of > what it looks like as of today when operating nominally > (https://github.com/bbercovici/SBGAT/wiki) > > Unfortunately, I am not quite there yet on Linux/Ubuntu. Specifically, the > QVTKWidget at the center of the QMainWindow constituting the GUI acts > weird. > > Here's what's happening when I am running SBGAT on Linux: > > - Upon launch, the QVTKWidget 'separates' from the QMainWindow, so that I > am > left with two windows instead of one > - The QMainWindow window works fine. All the buttons are responsive. > - The QVTKWidget is not responsive. No interaction appears to take place > between the mouse cursor upong clicking and the camera orientation. > - There is a strange "ghosting" effect with portions of the QVTKWidget that > do not get redrawn properly, but show neighboring desktop elements or > windows when moved around > - When loading in an .obj file using the QMainWindow actions, it gets > displayed on the QVTKWidget (so there is "some" rendering going on, > although > no interaction is possible). > > My desktop has a NVIDIA 980 GTX GPU, and I am using the latest NVidia > drivers I could find on apt-get (nvidia 384 I believe). > > I believe a more detailed error message is sometimes spitted out by SBGAT > upon leaving, I will copy/paste it here later today. > > Is there anyone who was able to make QVTKWidgets work on a similar > platform? > > Thanks, > Ben > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia-GPU-tp5744016.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bebe0705 at colorado.edu Wed Jul 19 11:30:15 2017 From: bebe0705 at colorado.edu (BBerco) Date: Wed, 19 Jul 2017 08:30:15 -0700 (MST) Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: References: <1500475655836-5744016.post@n5.nabble.com> Message-ID: <1500478215092-5744018.post@n5.nabble.com> Utkarsh, thanks for the suggestion. I'm trying to have this working on my Mac first. I have replaced the QVTKWidget by a QVTKOpenGLWidget, and set its render window to a vtkGenericOpenGLRenderWindow. * vtkSmartPointer< vtkGenericOpenGLRenderWindow> render_window = vtkSmartPointer< vtkGenericOpenGLRenderWindow>::New(); this -> qvtkWidget -> SetRenderWindow(render_window); this -> qvtkWidget -> GetRenderWindow() -> AddRenderer(this -> renderer); * Unfortunately it segfaults after returning the following error message: * Warning: In /Users/bbercovici/VTK/VTK_source/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 835 vtkGenericOpenGLRenderWindow (0x7f97260f8e00): VTK is designed to work with OpenGL version 3.2 but it appears it has been given a context that does not support 3.2. VTK will run in a compatibility mode designed to work with earlier versions of OpenGL but some features may not work. ERROR: In /Users/bbercovici/VTK/VTK_source/Rendering/OpenGL2/vtkOpenGLPolyDataMapper2D.cxx, line 902 vtkOpenGLPolyDataMapper2D (0x7f9727e15960): failed after RenderOverlay 1 OpenGL errors detected 0 : (1280) Invalid enum * I recompiled VTK beforehand with the -DVTK_RENDERING_BACKEND:STRING=OpenGL2 flag. Is OpenGL3 a thing? -- View this message in context: http://vtk.1045678.n5.nabble.com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia-GPU-tp5744016p5744018.html Sent from the VTK - Users mailing list archive at Nabble.com. From utkarsh.ayachit at kitware.com Wed Jul 19 11:43:09 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 19 Jul 2017 11:43:09 -0400 Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: <1500478215092-5744018.post@n5.nabble.com> References: <1500475655836-5744016.post@n5.nabble.com> <1500478215092-5744018.post@n5.nabble.com> Message-ID: > > I recompiled VTK beforehand with the -DVTK_RENDERING_BACKEND: > STRING=OpenGL2 > flag. Is OpenGL3 a thing? > No, VTK_RENDERING_BACKEND:STRING=OpenGL2 is indeed what you want. Also make sure before you create the QApp in your main, you're calling `QSurfaceFormat::setDefaultFormat(QVTKOpenGLWidget::defaultFormat())`. Is that the case? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bebe0705 at colorado.edu Wed Jul 19 11:48:04 2017 From: bebe0705 at colorado.edu (BBerco) Date: Wed, 19 Jul 2017 08:48:04 -0700 (MST) Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: References: <1500475655836-5744016.post@n5.nabble.com> <1500478215092-5744018.post@n5.nabble.com> Message-ID: <1500479284544-5744020.post@n5.nabble.com> `QSurfaceFormat::setDefaultFormat(QVTKOpenGLWidget::defaultFormat())` was the missing part. Thanks! It's now working on my mac. I'll try on my Ubuntu platform later today. -- View this message in context: http://vtk.1045678.n5.nabble.com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia-GPU-tp5744016p5744020.html Sent from the VTK - Users mailing list archive at Nabble.com. From mikewithascarf at yahoo.com Wed Jul 19 12:49:05 2017 From: mikewithascarf at yahoo.com (Mike Withascarf) Date: Wed, 19 Jul 2017 16:49:05 +0000 (UTC) Subject: [vtkusers] vtkImageBlend output alpha References: <1279142850.537349.1500482945623.ref@mail.yahoo.com> Message-ID: <1279142850.537349.1500482945623@mail.yahoo.com> Hi, I'm using vtkImageBlend to blend two?vtkImageMapToColors. Right now if I change the opacity map of the first vtkImageMapToColors (via lookup table), it adjusts the entire alpha of the output (so for example hiding the first one hides both of them). Is there a way to prevent vtkImageBlend from assigning the opacity of the first element to the output? I've tried using the "compound" blending mode in case that would help, but the screen is blank then. Any help would be great! This is a simplified version of the code I'm using: vtkSmartPointer imapper1 = vtkSmartPointer::New();imapper1->SetLookupTable(lut1);imapper1->PassAlphaToOutputOn();imapper1->SetInputData(image1);imapper1->Update(); vtkSmartPointer imapper2 = vtkSmartPointer::New();imapper2->SetLookupTable(lut2);imapper2->PassAlphaToOutputOn();imapper2->SetInputData(image2);imapper2->Update(); vtkSmartPointer blend = vtkSmartPointer::New();blend->AddInputConnection(imapper1->GetOutputPort());blend->SetOpacity(0, 1.0);blend->AddInputConnection(imapper2->GetOutputPort());blend->SetOpacity(1, 1.0); // If I now render and adjust lut1, it affects the output of blend so the imapper2 image gets affected Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From elvis.stansvik at orexplore.com Wed Jul 19 13:02:35 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Wed, 19 Jul 2017 19:02:35 +0200 Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: <1500478215092-5744018.post@n5.nabble.com> References: <1500475655836-5744016.post@n5.nabble.com> <1500478215092-5744018.post@n5.nabble.com> Message-ID: 2017-07-19 17:30 GMT+02:00 BBerco : > Utkarsh, > thanks for the suggestion. > > I'm trying to have this working on my Mac first. > > I have replaced the QVTKWidget by a QVTKOpenGLWidget, and set its render > window to a vtkGenericOpenGLRenderWindow. > > * > vtkSmartPointer< vtkGenericOpenGLRenderWindow> render_window = > vtkSmartPointer< vtkGenericOpenGLRenderWindow>::New(); > this -> qvtkWidget -> SetRenderWindow(render_window); > this -> qvtkWidget -> GetRenderWindow() -> AddRenderer(this -> renderer); > * > > Unfortunately it segfaults after returning the following error message: > * > Warning: In > /Users/bbercovici/VTK/VTK_source/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, > line 835 > vtkGenericOpenGLRenderWindow (0x7f97260f8e00): VTK is designed to work with > OpenGL version 3.2 but it appears it has been given a context that does not > support 3.2. VTK will run in a compatibility mode designed to work with > earlier versions of OpenGL but some features may not work. Did you follow the instructions in the docs for QVTKOpenGLWidget [1] ? Specifically, you need to set the default QSurfaceFormat to an appropriate one with QSurfaceFormat::setDefaultFormat(QVTKOpenGLWidget::defaultFormat()); Elvis [1] http://www.vtk.org/doc/nightly/html/classQVTKOpenGLWidget.html > > ERROR: In > /Users/bbercovici/VTK/VTK_source/Rendering/OpenGL2/vtkOpenGLPolyDataMapper2D.cxx, > line 902 > vtkOpenGLPolyDataMapper2D (0x7f9727e15960): failed after RenderOverlay 1 > OpenGL errors detected > 0 : (1280) Invalid enum > * > > > I recompiled VTK beforehand with the -DVTK_RENDERING_BACKEND:STRING=OpenGL2 > flag. Is OpenGL3 a thing? > > > > > > > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia-GPU-tp5744016p5744018.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 From ken.martin at kitware.com Wed Jul 19 14:38:24 2017 From: ken.martin at kitware.com (Ken Martin) Date: Wed, 19 Jul 2017 14:38:24 -0400 Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: <1500465504824-5744014.post@n5.nabble.com> References: <1500465504824-5744014.post@n5.nabble.com> Message-ID: Two options I know of 1) build your executable against Mesa so it will run everywhere 2) gracefully test if the hardware supports OpenGL2 and gracefully exit if not. In current VTK you can do this but I think in 7.1 it may not work. Basically call renWin->GetSupportsOpenGL() and handle accordingly. On Wed, Jul 19, 2017 at 7:58 AM, Satwik wrote: > Hi, > > I configured VTK-7.1 with *openGL2* as Rendering Backend. > > But, When i tried to run Volume Rendering or any VTK applications in the > machine which is not having openGL2.0. *Application is getting crashed*. > > How well can i handle this..???? > > > Regards, > satwik k > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtk-7-1-openGL-2-0-crash-tp5744014.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 shawn.waldon at kitware.com Wed Jul 19 14:54:59 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 19 Jul 2017 14:54:59 -0400 Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: <1500478215092-5744018.post@n5.nabble.com> References: <1500475655836-5744016.post@n5.nabble.com> <1500478215092-5744018.post@n5.nabble.com> Message-ID: To clarify on Utkarsh's answer, "OpenGL2" is just the name of the backend (as the second OpenGL backend to VTK). The required version of OpenGL to use the "OpenGL2" backend is OpenGL 3.2. HTH, Shawn On Wed, Jul 19, 2017 at 11:30 AM, BBerco wrote: > Utkarsh, > thanks for the suggestion. > > I'm trying to have this working on my Mac first. > > I have replaced the QVTKWidget by a QVTKOpenGLWidget, and set its render > window to a vtkGenericOpenGLRenderWindow. > > * > vtkSmartPointer< vtkGenericOpenGLRenderWindow> render_window = > vtkSmartPointer< vtkGenericOpenGLRenderWindow>::New(); > this -> qvtkWidget -> SetRenderWindow(render_window); > this -> qvtkWidget -> GetRenderWindow() -> AddRenderer(this -> renderer); > * > > Unfortunately it segfaults after returning the following error message: > * > Warning: In > /Users/bbercovici/VTK/VTK_source/Rendering/OpenGL2/ > vtkOpenGLRenderWindow.cxx, > line 835 > vtkGenericOpenGLRenderWindow (0x7f97260f8e00): VTK is designed to work with > OpenGL version 3.2 but it appears it has been given a context that does not > support 3.2. VTK will run in a compatibility mode designed to work with > earlier versions of OpenGL but some features may not work. > > ERROR: In > /Users/bbercovici/VTK/VTK_source/Rendering/OpenGL2/ > vtkOpenGLPolyDataMapper2D.cxx, > line 902 > vtkOpenGLPolyDataMapper2D (0x7f9727e15960): failed after RenderOverlay 1 > OpenGL errors detected > 0 : (1280) Invalid enum > * > > > I recompiled VTK beforehand with the -DVTK_RENDERING_BACKEND: > STRING=OpenGL2 > flag. Is OpenGL3 a thing? > > > > > > > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia- > GPU-tp5744016p5744018.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maxime.boissonneault at calculquebec.ca Wed Jul 19 18:07:34 2017 From: maxime.boissonneault at calculquebec.ca (Maxime Boissonneault) Date: Wed, 19 Jul 2017 18:07:34 -0400 Subject: [vtkusers] Missing python bindings with VTK 8.0 Message-ID: <16c05f52-6331-6d91-f9e6-6d7a17fd0590@calculquebec.ca> Hi, I am trying to compile VTK 8.0. I am passing the following flags to cmake : cmake . - DCMAKE_INSTALL_PREFIX=/home/mboisson/.local/easybuild/software/2017/avx2/MPI/intel2016.4/openmpi2.1/vtk/8.0.0 -DCMAKE_C_COMPILER='icc' -DCMAKE_Fortran_FLAGS='-O2 -xCore-AVX2 -ftz -fp-speculation=safe -fp-model source' -DCMAKE_CXX_FLAGS='-O2 -xCore-AVX2 -ftz -fp-speculation=safe -fp-model source' -DCMAKE_CXX_COMPILER='icpc' -DCMAKE_Fortran_COMPILER='ifort' -DCMAKE_C_FLAGS='-O2 -xCore-AVX2 -ftz -fp-speculation=safe -fp-model source' -DCMAKE_VERBOSE_MAKEFILE=ON -DPYTHON_LIBRARY=$EBROOTPYTHON/lib/libpython2.7.so -DPYTHON_INCLUDE_DIR=$EBROOTPYTHON/include/python2.7 Python is found, but the bindings are not created. Below is a grep of "python" from the CMakeCache.txt. Anyone got an idea on how to fix this ? Thanks [mboisson at build-node VTK-8.0.0]$ grep -i PYTHON CMakeCache.txt CMAKE_EXE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib CMAKE_MODULE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib CMAKE_SHARED_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib //Request building AutobahnPython Module_AutobahnPython:BOOL=OFF //Request building SixPython Module_SixPython:BOOL=OFF //Request building vtkPython Module_vtkPython:BOOL=OFF //Request building vtkPythonInterpreter Module_vtkPythonInterpreter:BOOL=OFF //Request building vtkWebPython Module_vtkWebPython:BOOL=OFF //Request building vtkWrappingPythonCore Module_vtkWrappingPythonCore:BOOL=OFF PYTHON_EXECUTABLE:FILEPATH=/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/bin/python2 PYTHON_INCLUDE_DIR:UNINITIALIZED=/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/include/python2.7 PYTHON_LIBRARY:UNINITIALIZED=/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib/libpython2.7.so //Directory where python modules will be put inside the build tree VTK_BUILD_PYTHON_MODULE_DIR:PATH=-NOTFOUND //Directory where python modules will be installed VTK_INSTALL_PYTHON_MODULE_DIR:PATH=-NOTFOUND //Python version to use: 2, 2.x, 3, 3.x, or empty VTK_PYTHON_VERSION:STRING=2 //Should VTK Python wrapping be built? VTK_WRAP_PYTHON:BOOL=OFF //ADVANCED property for variable: Module_AutobahnPython Module_AutobahnPython-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_SixPython Module_SixPython-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPython Module_vtkPython-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkPythonInterpreter Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWebPython Module_vtkWebPython-ADVANCED:INTERNAL=1 //ADVANCED property for variable: Module_vtkWrappingPythonCore Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_EXECUTABLE PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_BUILD_PYTHON_MODULE_DIR VTK_BUILD_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: VTK_INSTALL_PYTHON_MODULE_DIR VTK_INSTALL_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 -- --------------------------------- Maxime Boissonneault Analyste de calcul - Calcul Qu?bec, Universit? Laval Pr?sident - Comit? de coordination du soutien ? la recherche de Calcul Qu?bec Team lead - Research Support National Team, Compute Canada Instructeur Software Carpentry Ph. D. en physique From david.gobbi at gmail.com Wed Jul 19 18:23:44 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Wed, 19 Jul 2017 16:23:44 -0600 Subject: [vtkusers] Missing python bindings with VTK 8.0 In-Reply-To: <16c05f52-6331-6d91-f9e6-6d7a17fd0590@calculquebec.ca> References: <16c05f52-6331-6d91-f9e6-6d7a17fd0590@calculquebec.ca> Message-ID: "-DVTK_WRAP_PYTHON:BOOL=ON" On Wed, Jul 19, 2017 at 4:07 PM, Maxime Boissonneault < maxime.boissonneault at calculquebec.ca> wrote: > Hi, > I am trying to compile VTK 8.0. I am passing the following flags to cmake : > cmake . - DCMAKE_INSTALL_PREFIX=/home/mboisson/.local/easybuild/softwa > re/2017/avx2/MPI/intel2016.4/openmpi2.1/vtk/8.0.0 > -DCMAKE_C_COMPILER='icc' -DCMAKE_Fortran_FLAGS='-O2 -xCore-AVX2 -ftz > -fp-speculation=safe -fp-model source' -DCMAKE_CXX_FLAGS='-O2 -xCore-AVX2 > -ftz -fp-speculation=safe -fp-model source' -DCMAKE_CXX_COMPILER='icpc' > -DCMAKE_Fortran_COMPILER='ifort' -DCMAKE_C_FLAGS='-O2 -xCore-AVX2 -ftz > -fp-speculation=safe -fp-model source' -DCMAKE_VERBOSE_MAKEFILE=ON > -DPYTHON_LIBRARY=$EBROOTPYTHON/lib/libpython2.7.so > -DPYTHON_INCLUDE_DIR=$EBROOTPYTHON/include/python2.7 > > > Python is found, but the bindings are not created. > > Below is a grep of "python" from the CMakeCache.txt. > > Anyone got an idea on how to fix this ? Thanks > > [mboisson at build-node VTK-8.0.0]$ grep -i PYTHON CMakeCache.txt > CMAKE_EXE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca > /easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/ > soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib > -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/ > imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca > /easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/ > soft.computecanada.ca/easybuild/software/2017/avx2/ > Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca > /nix/var/nix/profiles/python-2.7.13/lib > CMAKE_MODULE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada > .ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/ > soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib > -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/ > imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca > /easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/ > soft.computecanada.ca/easybuild/software/2017/avx2/ > Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca > /nix/var/nix/profiles/python-2.7.13/lib > CMAKE_SHARED_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada > .ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/ > soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib > -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/ > imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca > /easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/ > soft.computecanada.ca/easybuild/software/2017/avx2/ > Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca > /nix/var/nix/profiles/python-2.7.13/lib > //Request building AutobahnPython > Module_AutobahnPython:BOOL=OFF > //Request building SixPython > Module_SixPython:BOOL=OFF > //Request building vtkPython > Module_vtkPython:BOOL=OFF > //Request building vtkPythonInterpreter > Module_vtkPythonInterpreter:BOOL=OFF > //Request building vtkWebPython > Module_vtkWebPython:BOOL=OFF > //Request building vtkWrappingPythonCore > Module_vtkWrappingPythonCore:BOOL=OFF > PYTHON_EXECUTABLE:FILEPATH=/cvmfs/soft.computecanada.ca/nix/ > var/nix/profiles/16.09/bin/python2 > PYTHON_INCLUDE_DIR:UNINITIALIZED=/cvmfs/soft.computecanada. > ca/nix/var/nix/profiles/python-2.7.13/include/python2.7 > PYTHON_LIBRARY:UNINITIALIZED=/cvmfs/soft.computecanada.ca/ni > x/var/nix/profiles/python-2.7.13/lib/libpython2.7.so > //Directory where python modules will be put inside the build tree > VTK_BUILD_PYTHON_MODULE_DIR:PATH=-NOTFOUND > //Directory where python modules will be installed > VTK_INSTALL_PYTHON_MODULE_DIR:PATH=-NOTFOUND > //Python version to use: 2, 2.x, 3, 3.x, or empty > VTK_PYTHON_VERSION:STRING=2 > //Should VTK Python wrapping be built? > VTK_WRAP_PYTHON:BOOL=OFF > //ADVANCED property for variable: Module_AutobahnPython > Module_AutobahnPython-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: Module_SixPython > Module_SixPython-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: Module_vtkPython > Module_vtkPython-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: Module_vtkPythonInterpreter > Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: Module_vtkWebPython > Module_vtkWebPython-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: Module_vtkWrappingPythonCore > Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: PYTHON_EXECUTABLE > PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: VTK_BUILD_PYTHON_MODULE_DIR > VTK_BUILD_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 > //ADVANCED property for variable: VTK_INSTALL_PYTHON_MODULE_DIR > VTK_INSTALL_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 > > > -- > --------------------------------- > Maxime Boissonneault > Analyste de calcul - Calcul Qu?bec, Universit? Laval > Pr?sident - Comit? de coordination du soutien ? la recherche de Calcul > Qu?bec > Team lead - Research Support National Team, Compute Canada > Instructeur Software Carpentry > Ph. D. en physique > -------------- next part -------------- An HTML attachment was scrubbed... URL: From satwik.k8 at gmail.com Wed Jul 19 22:03:38 2017 From: satwik.k8 at gmail.com (satwik k) Date: Thu, 20 Jul 2017 07:33:38 +0530 Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: References: <1500465504824-5744014.post@n5.nabble.com> Message-ID: Is thr any way to find out OpenGL version in VTK . So that system which supports OpenGL 2.0 can make use of VTK 7.0 OpenGL 2.0 as Rendering backed. System which won't support OpenGL 2.0 can make use of OpenGL as Rendering backend. Regards, Satwik k On 20-Jul-2017 00:08, "Ken Martin" wrote: > Two options I know of > > 1) build your executable against Mesa so it will run everywhere > > 2) gracefully test if the hardware supports OpenGL2 and gracefully exit if > not. In current VTK you can do this but I think in 7.1 it may not work. > Basically call renWin->GetSupportsOpenGL() and handle accordingly. > > > > On Wed, Jul 19, 2017 at 7:58 AM, Satwik wrote: > >> Hi, >> >> I configured VTK-7.1 with *openGL2* as Rendering Backend. >> >> But, When i tried to run Volume Rendering or any VTK applications in the >> machine which is not having openGL2.0. *Application is getting crashed*. >> >> How well can i handle this..???? >> >> >> Regards, >> satwik k >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.c >> om/vtk-7-1-openGL-2-0-crash-tp5744014.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> > > > > -- > Ken Martin PhD > Distinguished Engineer > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > > 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 bebe0705 at colorado.edu Thu Jul 20 00:47:08 2017 From: bebe0705 at colorado.edu (BBerco) Date: Wed, 19 Jul 2017 21:47:08 -0700 (MST) Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: References: <1500475655836-5744016.post@n5.nabble.com> <1500478215092-5744018.post@n5.nabble.com> Message-ID: <1500526028122-5744038.post@n5.nabble.com> Unfortunately, the program crashes on my Ubuntu platform upon rendering. That is, it segfaults at * this -> qvtkWidget -> GetRenderWindow() -> Render(); * Where the render window is an instance of vtkGenericOpenGLRenderWindow. Any thoughts? -- View this message in context: http://vtk.1045678.n5.nabble.com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia-GPU-tp5744016p5744038.html Sent from the VTK - Users mailing list archive at Nabble.com. From bakkari.abdelkhalek at hotmail.fr Thu Jul 20 02:20:54 2017 From: bakkari.abdelkhalek at hotmail.fr (Abdelkhalek Bakkari) Date: Thu, 20 Jul 2017 06:20:54 +0000 Subject: [vtkusers] Setting camera to view the rendered slice Message-ID: Dear VTK users, I have an issue related to the Setting camera to view the rendered slice to the whole viewport. For the axial plane, the formula which I am using is the following: float yd = (image_vtk->GetExtent()[3] - image_vtk->GetExtent()[2] + 1)*image_vtk->GetSpacing()[1]; float d = camera->GetDistance(); camera->SetParallelScale(0.5f*yd); I would like to change it in order to get the Coronal plane. Thank you in advance. Best regards, Abdelkhalek Bakkari -------------- next part -------------- An HTML attachment was scrubbed... URL: From elvis.stansvik at orexplore.com Thu Jul 20 02:28:51 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Thu, 20 Jul 2017 08:28:51 +0200 Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: References: <1500465504824-5744014.post@n5.nabble.com> Message-ID: 2017-07-20 4:03 GMT+02:00 satwik k : > Is thr any way to find out OpenGL version in VTK . > So that system which supports OpenGL 2.0 can make use of VTK 7.0 OpenGL 2.0 > as Rendering backed. > > System which won't support OpenGL 2.0 can make use of OpenGL as Rendering > backend. Just some clarification: The current rendering backend in VTK is called "OpenGL2", because it's the second version of the OpenGL backend. It requires OpenGL 3.2. The old backend is called just "OpenGL". I'm not sure which version of OpenGL it requires. It's easy to confuse the name of the backend "OpenGL2" and think that the 2 means OpenGL version 2. But it's just a name. Perhaps it would have been better to call it OpenGLNG or something for that reason. It's not possible to build a VTK that has both the OpenGL and OpenGL2 backend built, and I'm not sure if it would be possible to deliver an application with two versions of VTK (one with OpenGL2 and one with OpenGL) and choose which one to use at runtime. Maybe.. but it would be rather complicated. Like Ken said, if you want something that runs everywhere, I think the only option is to build against Mesa. Elvis > > > > Regards, > Satwik k > > On 20-Jul-2017 00:08, "Ken Martin" wrote: >> >> Two options I know of >> >> 1) build your executable against Mesa so it will run everywhere >> >> 2) gracefully test if the hardware supports OpenGL2 and gracefully exit if >> not. In current VTK you can do this but I think in 7.1 it may not work. >> Basically call renWin->GetSupportsOpenGL() and handle accordingly. >> >> >> >> On Wed, Jul 19, 2017 at 7:58 AM, Satwik wrote: >>> >>> Hi, >>> >>> I configured VTK-7.1 with *openGL2* as Rendering Backend. >>> >>> But, When i tried to run Volume Rendering or any VTK applications in the >>> machine which is not having openGL2.0. *Application is getting crashed*. >>> >>> How well can i handle this..???? >>> >>> >>> Regards, >>> satwik k >>> >>> >>> >>> -- >>> View this message in context: >>> http://vtk.1045678.n5.nabble.com/vtk-7-1-openGL-2-0-crash-tp5744014.html >>> Sent from the VTK - Users mailing list archive at Nabble.com. >>> _______________________________________________ >>> 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 >> >> >> >> >> -- >> Ken Martin PhD >> Distinguished Engineer >> Kitware Inc. >> 28 Corporate Drive >> Clifton Park NY 12065 >> >> 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 > > 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 > From xoviat at tamu.edu Thu Jul 20 02:34:34 2017 From: xoviat at tamu.edu (Geoffrey Garner) Date: Thu, 20 Jul 2017 01:34:34 -0500 Subject: [vtkusers] (no subject) Message-ID: <59704efa.482cca0a.52c69.00b4@mx.google.com> All: After multiple attempts, I have not been able to compile VTK with OpenVR. With the project directory set to the OpenVR directory, I receive the following output. This is expected because vtkObjectFactory is part of the main project. Found OpenVR: C:/Users/Geoffrey/vcpkg/installed/x64-windows/include CMake Error at CMakeLists.txt:42 (include): include could not find load file: vtkObjectFactory CMake Error at CMakeLists.txt:43 (vtk_add_override): Unknown CMake command "vtk_add_override". CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.9) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. Configuring incomplete, errors occurred! See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/CMakeFiles/CMakeOutput.log". See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/CMakeFiles/CMakeError.log". However, what is not expected is the following when configuring the main project. There is no OpenVR folder in the build directory and no explanation of why. Yes, I have SDL2 and OpenVR from vcpkg. Group StandAlone modules: vtkChartsCore;vtkCommonComputationalGeometry;vtkCommonCore;vtkCommonDataModel;vtkCommonExecutionModel;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkDomainsChemistry;vtkFiltersAMR;vtkFiltersCore;vtkFiltersExtraction;vtkFiltersFlowPaths;vtkFiltersGeneral;vtkFiltersGeneric;vtkFiltersGeometry;vtkFiltersHybrid;vtkFiltersHyperTree;vtkFiltersImaging;vtkFiltersModeling;vtkFiltersParallel;vtkFiltersParallelImaging;vtkFiltersPoints;vtkFiltersProgrammable;vtkFiltersSMP;vtkFiltersSelection;vtkFiltersSources;vtkFiltersStatistics;vtkFiltersTexture;vtkFiltersTopology;vtkFiltersVerdict;vtkIOAMR;vtkIOCore;vtkIOEnSight;vtkIOExodus;vtkIOGeometry;vtkIOImage;vtkIOImport;vtkIOInfovis;vtkIOLSDyna;vtkIOLegacy;vtkIOMINC;vtkIOMovie;vtkIONetCDF;vtkIOPLY;vtkIOParallel;vtkIOParallelXML;vtkIOSQL;vtkIOTecplotTable;vtkIOVideo;vtkIOXML;vtkIOXMLParser;vtkImagingColor;vtkImagingCore;vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInfovisCore;vtkInfovisLayout;vtkParallelCore Group Imaging modules: vtkFiltersImaging;vtkImagingColor;vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInteractionImage;vtkRenderingImage Group MPI modules: vtkFiltersParallelGeometry;vtkFiltersParallelMPI;vtkIOMPIImage;vtkIOMPIParallel;vtkIOParallelNetCDF;vtkParallelMPI Group Qt modules: vtkGUISupportQt;vtkGUISupportQtSQL;vtkRenderingQt;vtkViewsQt Group Rendering modules: vtkGeovisCore;vtkIOExport;vtkInteractionImage;vtkInteractionStyle;vtkInteractionWidgets;vtkRenderingAnnotation;vtkRenderingContext2D;vtkRenderingCore;vtkRenderingFreeType;vtkRenderingImage;vtkRenderingLOD;vtkRenderingLabel;vtkRenderingVolume;vtkViewsContext2D;vtkViewsCore;vtkViewsInfovis Group Tk modules: vtkRenderingTk Group Views modules: vtkViewsContext2D;vtkViewsGeovis Group Web modules: vtkWebCore;vtkWebPython;vtkWebGLExporter Backend OpenGL2 modules: vtkDomainsChemistryOpenGL2;vtkIOExportOpenGL2;vtkImagingOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingGL2PSOpenGL2;vtkRenderingLICOpenGL2;vtkRenderingOculus;vtkRenderingOpenGL2;vtkRenderingOpenVR;vtkRenderingVolumeOpenGL2 Enabling modules for OpenGL2. Backend OpenGL modules: vtkIOExportOpenGL;vtkRenderingContextOpenGL;vtkRenderingGL2PS;vtkRenderingLIC;vtkRenderingOpenGL;vtkRenderingVolumeOpenGL Disable test module vtkFiltersParallel-Test-Cxx since required modules are not enabled: vtkFiltersParallelMPI;vtkParallelMPI;vtkRenderingParallel Disable test module vtkGeovisCore-Test-Cxx since required modules are not enabled: vtkViewsGeovis Disable test module vtkIOParallel-Test-Cxx since required modules are not enabled: vtkParallelMPI;vtkRenderingParallel Enabled 185 modules: * vtkChartsCore, needed by 6 modules: VTK_Group_StandAlone vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkViewsInfovis * vtkCommonColor, needed by 6 modules: vtkChartsCore vtkCommonColor-Test-Cxx vtkFiltersModeling-Test-Cxx vtkIOExport-Test-Cxx vtkRenderingCore vtkViewsInfovis * vtkCommonComputationalGeometry, needed by 8 modules: VTK_Group_StandAlone vtkCommonComputationalGeometry-Test-Cxx vtkFiltersGeneral vtkFiltersSources vtkImagingStencil vtkInfovisLayout vtkInteractionWidgets vtkRenderingCore * vtkCommonCore, needed by 94 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor vtkCommonComputationalGeometry vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonExecutionModel vtkCommonMath vtkCommonMisc vtkCommonSystem vtkCommonTransforms vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOExport vtkIOExportOpenGL2 vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingHybrid-Test-Cxx vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionStyle vtkInteractionWidgets vtkParallelCore vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingCore vtkTestingGenericBridge vtkTestingRendering vtkViewsContext2D vtkViewsCore vtkViewsInfovis * vtkCommonDataModel, needed by 86 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor vtkCommonComputationalGeometry vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOExport vtkIOExportOpenGL2 vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingHybrid-Test-Cxx vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionStyle vtkInteractionWidgets vtkParallelCore vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingGenericBridge vtkTestingRendering vtkViewsCore vtkViewsInfovis * vtkCommonExecutionModel, needed by 76 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIONetCDF-Test-Cxx vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingCore vtkRenderingFreeType vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkTestingRendering vtkViewsCore vtkViewsInfovis * vtkCommonMath, needed by 29 modules: vtkCommonDataModel vtkCommonMath-Test-Cxx vtkCommonMisc vtkCommonTransforms vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersSMP vtkIOExport vtkIOImage vtkIOMINC vtkImagingCore vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 * vtkCommonMisc, needed by 27 modules: VTK_Group_StandAlone vtkCommonDataModel vtkCommonExecutionModel vtkCommonExecutionModel vtkCommonMisc-Test-Cxx vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersSMP vtkFiltersStatistics vtkIOCore vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLegacy vtkIOMINC vtkIOMovie vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOXML vtkRenderingVolume vtkTestingGenericBridge * vtkCommonSystem, needed by 34 modules: VTK_Group_StandAlone vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonExecutionModel vtkCommonMath-Test-Cxx vtkCommonSystem-Test-Cxx vtkFiltersAMR vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHyperTree vtkFiltersImaging vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersSMP vtkGeovisCore vtkIOAMR vtkIOGeometry vtkIOImage vtkIOMovie vtkIOParallel vtkIOVideo vtkIOXML vtkImagingColor vtkInfovisLayout vtkInteractionWidgets vtkParallelCore vtkRenderingCore vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering * vtkCommonTransforms, needed by 37 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonMath-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersModeling vtkFiltersParallel vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSources vtkFiltersTexture vtkGeovisCore vtkIOExport vtkIOGeometry vtkIOImage vtkIOImport vtkIOMINC vtkImagingCore vtkInfovisLayout vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingImage vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkDICOMParser, needed by vtkIOImage. * vtkDomainsChemistry, needed by 4 modules: VTK_Group_StandAlone vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2 vtkDomainsChemistryOpenGL2 * vtkDomainsChemistryOpenGL2, needed by 4 modules: vtkDomainsChemistry vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx * vtkFiltersAMR, needed by 6 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkIOAMR vtkIOLegacy-Test-Cxx vtkIOXML-Test-Cxx * vtkFiltersCore, needed by 28 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkFiltersAMR vtkFiltersCore-Test-Cxx vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersParallel vtkFiltersSMP vtkFiltersSources vtkGeovisCore vtkIOExodus vtkIOImport vtkIOParallel vtkIOXML-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingCore vtkRenderingLOD vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkFiltersExtraction, needed by 9 modules: VTK_Group_StandAlone vtkFiltersExtraction-Test-Cxx vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersSelection-Test-Cxx vtkIOParallel vtkInfovisCore vtkInteractionStyle vtkViewsInfovis * vtkFiltersFlowPaths, needed by 4 modules: VTK_Group_StandAlone vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkFiltersGeneral, needed by 27 modules: VTK_Group_StandAlone vtkChartsCore vtkDomainsChemistry vtkFiltersCore-Test-Cxx vtkFiltersExtraction vtkFiltersGeneral-Test-Cxx vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersParallel vtkFiltersPoints-Test-Cxx vtkFiltersSMP vtkFiltersSources vtkFiltersTexture vtkGeovisCore vtkImagingCore-Test-Cxx vtkInfovisCore vtkInfovisLayout vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingCore vtkRenderingFreeType vtkRenderingLabel vtkRenderingVolumeOpenGL2 vtkViewsCore vtkViewsInfovis * vtkFiltersGeneric, needed by 3 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersGeneric-Test-Cxx * vtkFiltersGeometry, needed by 8 modules: VTK_Group_StandAlone vtkFiltersFlowPaths vtkFiltersGeometry-Test-Cxx vtkFiltersParallel vtkIOExport vtkIOGeometry-Test-Cxx vtkRenderingCore vtkViewsInfovis * vtkFiltersHybrid, needed by 5 modules: VTK_Group_StandAlone vtkFiltersHybrid-Test-Cxx vtkIOMINC vtkImagingCore-Test-Cxx vtkInteractionWidgets * vtkFiltersHyperTree, needed by 3 modules: VTK_Group_StandAlone vtkFiltersHyperTree-Test-Cxx vtkIOXML-Test-Cxx * vtkFiltersImaging, needed by 4 modules: VTK_Group_StandAlone vtkFiltersFlowPaths-Test-Cxx vtkFiltersParallelImaging vtkViewsInfovis * vtkFiltersModeling, needed by 16 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersParallel vtkFiltersSources-Test-Cxx vtkImagingCore-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkInteractionWidgets-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkFiltersParallel, needed by 3 modules: VTK_Group_StandAlone vtkFiltersParallelImaging vtkIOParallel * vtkFiltersParallelImaging, needed by VTK_Group_StandAlone. * vtkFiltersPoints, needed by 2 modules: VTK_Group_StandAlone vtkFiltersPoints-Test-Cxx * vtkFiltersProgrammable, needed by 4 modules: VTK_Group_StandAlone vtkFiltersProgrammable-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingCore-Test-Cxx * vtkFiltersSMP, needed by 2 modules: VTK_Group_StandAlone vtkFiltersSMP-Test-Cxx * vtkFiltersSelection, needed by 3 modules: VTK_Group_StandAlone vtkFiltersSelection-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkFiltersSources, needed by 18 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkFiltersFlowPaths vtkFiltersGeneric vtkFiltersModeling vtkFiltersParallel vtkFiltersSources-Test-Cxx vtkIOImport vtkIOXML-Test-Cxx vtkInfovisLayout vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingCore vtkRenderingCore-Test-Cxx vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkFiltersStatistics, needed by 6 modules: VTK_Group_StandAlone vtkFiltersExtraction vtkFiltersImaging vtkFiltersParallelImaging vtkFiltersStatistics-Test-Cxx vtkViewsInfovis * vtkFiltersTexture, needed by VTK_Group_StandAlone. * vtkFiltersTopology, needed by 2 modules: VTK_Group_StandAlone vtkFiltersTopology-Test-Cxx * vtkFiltersVerdict, needed by 3 modules: VTK_Group_StandAlone vtkFiltersSources-Test-Cxx vtkFiltersVerdict-Test-Cxx * vtkGeovisCore, needed by VTK_Group_Rendering. * vtkIOAMR, needed by 4 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkIOAMR-Test-Cxx vtkIOGeometry-Test-Cxx * vtkIOCore, needed by 16 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkFiltersFlowPaths vtkIOCore-Test-Cxx vtkIOExodus vtkIOExport vtkIOGeometry vtkIOInfovis vtkIOLegacy vtkIOMINC vtkIOPLY vtkIOParallel vtkIOSQL vtkIOTecplotTable vtkIOXML vtkIOXMLParser * vtkIOEnSight, needed by VTK_Group_StandAlone. * vtkIOExodus, needed by 6 modules: VTK_Group_StandAlone vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkIOExodus-Test-Cxx vtkRenderingCore-Test-Cxx * vtkIOExport, needed by 4 modules: VTK_Group_Rendering vtkIOExport-Test-Cxx vtkIOExportOpenGL2 vtkIOExportOpenGL2 * vtkIOExportOpenGL2, needed by 3 modules: vtkIOExport vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx * vtkIOGeometry, needed by 8 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOParallel vtkRenderingAnnotation-Test-Cxx * vtkIOImage, needed by 13 modules: VTK_Group_StandAlone vtkCommonColor-Test-Cxx vtkGeovisCore vtkIOExport vtkIOExport vtkIOImage-Test-Cxx vtkIOImport vtkIOMINC vtkIOPLY-Test-Cxx vtkIOParallel vtkImagingHybrid vtkRenderingVolume-Test-Cxx vtkTestingRendering * vtkIOImport, needed by 2 modules: VTK_Group_StandAlone vtkIOImport-Test-Cxx * vtkIOInfovis, needed by 6 modules: VTK_Group_StandAlone vtkChartsCore-Test-Cxx vtkIOInfovis-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkIOLSDyna, needed by 2 modules: VTK_Group_StandAlone vtkIOLSDyna-Test-Cxx * vtkIOLegacy, needed by 30 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkDomainsChemistry-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersParallel vtkFiltersPoints-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersTopology-Test-Cxx vtkFiltersVerdict-Test-Cxx vtkIOGeometry vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOInfovis vtkIOLegacy-Test-Cxx vtkIOParallel vtkIOSQL-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkParallelCore vtkRenderingCore-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkIOMINC, needed by VTK_Group_StandAlone. * vtkIOMovie, needed by 2 modules: VTK_Group_StandAlone vtkIOMovie-Test-Cxx * vtkIONetCDF, needed by 3 modules: VTK_Group_StandAlone vtkIONetCDF-Test-Cxx vtkIOParallel * vtkIOPLY, needed by 3 modules: VTK_Group_StandAlone vtkIOPLY-Test-Cxx vtkRenderingOpenGL2-Test-Cxx * vtkIOParallel, needed by 6 modules: VTK_Group_StandAlone vtkFiltersSources-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx * vtkIOParallelXML, needed by 2 modules: VTK_Group_StandAlone vtkIOXML-Test-Cxx * vtkIOSQL, needed by 4 modules: VTK_Group_StandAlone vtkIOSQL-Test-Cxx vtkTestingIOSQL vtkViewsInfovis-Test-Cxx * vtkIOTecplotTable, needed by 2 modules: VTK_Group_StandAlone vtkIOTecplotTable-Test-Cxx * vtkIOVideo, needed by VTK_Group_StandAlone. * vtkIOXML, needed by 26 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersAMR vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersSMP-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkGeovisCore vtkIOAMR-Test-Cxx vtkIOImport-Test-Cxx vtkIOInfovis vtkIOParallelXML vtkIOXML-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingVolume vtkRenderingVolume-Test-Cxx * vtkIOXMLParser, needed by 6 modules: VTK_Group_StandAlone vtkDomainsChemistry vtkIOExodus vtkIOInfovis vtkIOLSDyna vtkIOXML * vtkImagingColor, needed by 4 modules: VTK_Group_StandAlone vtkInteractionImage vtkInteractionWidgets vtkRenderingAnnotation * vtkImagingCore, needed by 28 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersHybrid vtkFiltersHybrid-Test-Cxx vtkFiltersParallelImaging vtkFiltersPoints-Test-Cxx vtkFiltersSMP-Test-Cxx vtkGeovisCore vtkIOExport vtkIOExportOpenGL2 vtkIOMovie-Test-Cxx vtkImagingColor vtkImagingCore-Test-Cxx vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInteractionImage vtkInteractionWidgets vtkRenderingContextOpenGL2 vtkRenderingImage vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering * vtkImagingFourier, needed by 2 modules: VTK_Group_StandAlone vtkFiltersStatistics * vtkImagingGeneral, needed by 9 modules: VTK_Group_StandAlone vtkFiltersImaging vtkFiltersParallelImaging vtkImagingCore-Test-Cxx vtkImagingMorphological vtkInteractionWidgets vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkImagingHybrid, needed by 5 modules: VTK_Group_StandAlone vtkImagingHybrid-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkRenderingVolume-Test-Cxx * vtkImagingMath, needed by 5 modules: VTK_Group_StandAlone vtkFiltersGeneral-Test-Cxx vtkIOImage-Test-Cxx vtkImagingCore-Test-Cxx vtkRenderingVolumeOpenGL2 * vtkImagingMorphological, needed by 2 modules: VTK_Group_StandAlone vtkImagingMorphological-Test-Cxx * vtkImagingSources, needed by 15 modules: VTK_Group_StandAlone vtkFiltersHybrid vtkGeovisCore vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOMovie-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingGeneral vtkImagingMorphological vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkImagingStatistics, needed by 2 modules: VTK_Group_StandAlone vtkImagingCore-Test-Cxx * vtkImagingStencil, needed by 5 modules: VTK_Group_StandAlone vtkFiltersHybrid-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkInfovisCore, needed by 8 modules: VTK_Group_StandAlone vtkChartsCore vtkGeovisCore vtkIOInfovis vtkIOXML-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout vtkViewsInfovis * vtkInfovisLayout, needed by 6 modules: VTK_Group_StandAlone vtkGeovisCore vtkIOInfovis-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkViewsInfovis * vtkInteractionImage, needed by 6 modules: VTK_Group_Rendering vtkIOExport-Test-Cxx vtkIOImage-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkInteractionStyle, needed by 46 modules: VTK_Group_Rendering vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkGeovisCore vtkIOExodus-Test-Cxx vtkIOExport-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkInteractionImage vtkInteractionWidgets vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingGL2PSOpenGL2-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkInteractionWidgets, needed by 6 modules: VTK_Group_Rendering vtkGeovisCore vtkInteractionImage vtkInteractionWidgets-Test-Cxx vtkViewsCore vtkViewsInfovis * vtkMetaIO, needed by vtkIOImage. * vtkParallelCore, needed by 8 modules: VTK_Group_StandAlone vtkFiltersAMR vtkFiltersParallel vtkFiltersParallelImaging vtkIOAMR vtkIOParallel vtkIOParallelXML vtkParallelCore-Test-Cxx * vtkRenderingAnnotation, needed by 9 modules: VTK_Group_Rendering vtkFiltersGeneral-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersSelection-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkViewsInfovis * vtkRenderingContext2D, needed by 9 modules: VTK_Group_Rendering vtkChartsCore vtkFiltersPoints-Test-Cxx vtkIOExport vtkRenderingContext2D-Test-Cxx vtkRenderingContextOpenGL2 vtkRenderingContextOpenGL2 vtkViewsContext2D vtkViewsInfovis * vtkRenderingContextOpenGL2, needed by 9 modules: vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkIOImage-Test-Cxx vtkRenderingContext2D vtkRenderingContext2D-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkRenderingCore, needed by 34 modules: VTK_Group_Rendering vtkChartsCore vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersHybrid vtkFiltersParallel vtkGeovisCore vtkIOExport vtkIOExportOpenGL2 vtkIOImport vtkIOInfovis-Test-Cxx vtkIOMINC vtkInteractionImage vtkInteractionStyle vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore-Test-Cxx vtkRenderingFreeType vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering vtkViewsContext2D vtkViewsCore vtkViewsInfovis * vtkRenderingFreeType, needed by 11 modules: VTK_Group_Rendering vtkIOExport vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingLabel vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkRenderingGL2PSOpenGL2, needed by 3 modules: vtkIOExport vtkIOExportOpenGL2 vtkRenderingGL2PSOpenGL2-Test-Cxx * vtkRenderingImage, needed by 4 modules: VTK_Group_Rendering vtkImagingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingOpenGL2-Test-Cxx * vtkRenderingLOD, needed by 4 modules: VTK_Group_Rendering vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingLOD-Test-Cxx * vtkRenderingLabel, needed by 7 modules: VTK_Group_Rendering vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkIOExport-Test-Cxx vtkInfovisLayout-Test-Cxx vtkRenderingLabel-Test-Cxx vtkViewsInfovis * vtkRenderingOpenGL2, needed by 47 modules: vtkCommonColor-Test-Cxx vtkCommonComputationalGeometry-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2 vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkIOExodus-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImport-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkParallelCore-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingGL2PSOpenGL2 vtkRenderingGL2PSOpenGL2 vtkRenderingGL2PSOpenGL2 vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolumeOpenGL2 * vtkRenderingVolume, needed by 5 modules: VTK_Group_Rendering vtkInteractionWidgets vtkRenderingVolume-Test-Cxx vtkRenderingVolumeOpenGL2 vtkRenderingVolumeOpenGL2 * vtkRenderingVolumeOpenGL2, needed by 6 modules: vtkFiltersCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingVolume vtkRenderingVolume-Test-Cxx * vtkTestingCore, needed by 33 modules: vtkChartsCore-Test-Cxx vtkCommonColor-Test-Cxx vtkCommonComputationalGeometry-Test-Cxx vtkCommonCore-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkCommonMath-Test-Cxx vtkCommonMisc-Test-Cxx vtkCommonSystem-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersAMR-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersSMP-Test-Cxx vtkFiltersSources-Test-Cxx vtkFiltersStatistics-Test-Cxx vtkFiltersVerdict-Test-Cxx vtkIOAMR-Test-Cxx vtkIOCore-Test-Cxx vtkIOImage-Test-Cxx vtkIOImage-Test-Cxx vtkIOMovie-Test-Cxx vtkIOSQL-Test-Cxx vtkIOTecplotTable-Test-Cxx vtkIOXML-Test-Cxx vtkImagingHybrid-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkTestingRendering * vtkTestingGenericBridge, needed by 2 modules: vtkCommonDataModel-Test-Cxx vtkFiltersGeneric-Test-Cxx * vtkTestingIOSQL, needed by vtkIOSQL-Test-Cxx. * vtkTestingRendering, needed by 51 modules: vtkChartsCore-Test-Cxx vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersAMR-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkFiltersTopology-Test-Cxx vtkIOAMR-Test-Cxx vtkIOExodus-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOInfovis-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkParallelCore-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingGL2PSOpenGL2-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkUtilitiesEncodeString, needed by vtkRenderingOpenGL2. * vtkUtilitiesHashSource, needed by vtkParallelCore. * vtkViewsContext2D, needed by 8 modules: VTK_Group_Rendering vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkViewsCore, needed by 4 modules: VTK_Group_Rendering vtkGeovisCore vtkViewsContext2D vtkViewsInfovis * vtkViewsInfovis, needed by 2 modules: VTK_Group_Rendering vtkViewsInfovis-Test-Cxx * vtkalglib, needed by vtkFiltersStatistics. * vtkexodusII, needed by 2 modules: vtkIOExodus vtkIOParallel * vtkexpat, needed by vtkIOXMLParser. * vtkfreetype, needed by vtkRenderingFreeType. * vtkgl2ps, needed by 2 modules: vtkIOExportOpenGL2 vtkRenderingGL2PSOpenGL2 * vtkglew, needed by 4 modules: vtkDomainsChemistryOpenGL2 vtkRenderingContextOpenGL2 vtkRenderingOpenGL2 vtkRenderingVolumeOpenGL2 * vtkhdf5, needed by 2 modules: vtkIOAMR vtknetcdf * vtkjpeg, needed by 2 modules: vtkIOImage vtktiff * vtkjsoncpp, needed by vtkIOParallel. * vtkkwiml, needed by 2 modules: vtkCommonCore vtkfreetype * vtklibharu, needed by vtkIOExport. * vtklibproj4, needed by vtkGeovisCore. * vtklibxml2, needed by vtkIOInfovis. * vtklz4, needed by vtkIOCore. * vtknetcdf, needed by 5 modules: vtkIOMINC vtkIONetCDF vtkIOParallel vtkexodusII vtknetcdfcpp * vtknetcdfcpp, needed by vtkIONetCDF. * vtkoggtheora, needed by vtkIOMovie. * vtkpng, needed by 3 modules: vtkIOImage vtkgl2ps vtklibharu * vtksqlite, needed by vtkIOSQL. * vtksys, needed by 33 modules: vtkChartsCore vtkCommonCore vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonSystem vtkDICOMParser vtkDomainsChemistry vtkFiltersHybrid vtkIOAMR vtkIOCore vtkIOExodus vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIONetCDF vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingFourier vtkParallelCore vtkRenderingCore vtkRenderingOpenGL2 vtkRenderingVolumeOpenGL2 vtkTestingRendering vtkUtilitiesHashSource * vtktiff, needed by vtkIOImage. * vtkverdict, needed by vtkFiltersVerdict. * vtkzlib, needed by 11 modules: vtkIOCore vtkIOGeometry vtkIOImage vtkMetaIO vtkfreetype vtkgl2ps vtkhdf5 vtklibharu vtklibxml2 vtkpng vtktiff 64 bit architecture detected size of void * is 8 Building tiff version 4.0.6 libtiff library version 5.2.4 CMAKE_HOST_SYSTEM_PROCESSOR set to AMD64 HOST_FILLORDER set to FILLORDER_MSB2LSB HOST_BIG_ENDIAN set to 0 HAVE_IEEEFP set to 1 HDF5: SOVERSION: 8.0.2 HDF5: Performing Other Test STDC_HEADERS - Success HDF5: Performing CXX Test OLD_HEADER_FILENAME - Failed HDF5: Performing CXX Test H5_NO_NAMESPACE - Failed HDF5: Performing CXX Test H5_NO_STD - Failed HDF5: Performing CXX Test BOOL_NOTDEFINED - Failed HDF5: Performing CXX Test NO_STATIC_CAST - Failed HDF5: Checking for InitOnceExecuteOnce: HDF5: Performing Test InitOnceExecuteOnce - Success HDF5: Performing Other Test INLINE_TEST_inline - Success HDF5: Performing Other Test INLINE_TEST___inline__ - Failed HDF5: Performing Other Test INLINE_TEST___inline - Success HDF5: checking IF converting from long double to integers is accurate... yes HDF5: checking IF accurately converting from integers to long double... yes HDF5: Checking IF accurately converting unsigned long to float values... yes HDF5: Checking IF accurately roundup converting floating-point to unsigned long long values... yes HDF5: Checking IF right maximum converting floating-point to unsigned long long values... yes HDF5: Checking IF correctly converting long double to unsigned int values... yes HDF5: Checking IF overflows normally converting floating-point to integer values... yes HDF5: Checking IF correctly converting long double to (unsigned) long long values... yes HDF5: Checking IF correctly converting (unsigned) long long to long double values... yes HDF5: Checking IF alignment restrictions are strictly enforced... yes HDF5: Filter ZLIB is ON Configuring PROJ: PROJ_VERSION = 4.9.2 PROJ_ABI_VERSION = 4_9 CMake Deprecation Warning at ThirdParty/libproj4/vtklibproj4/cmake/policies.cmake:2 (cmake_policy): The OLD behavior for policy CMP0022 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. Call Stack (most recent call first): ThirdParty/libproj4/vtklibproj4/CMakeLists.txt:43 (include) Configuring proj library: PROJ_CORE_TARGET = vtkproj4 PROJ_CORE_TARGET_OUTPUT_NAME = vtkproj4_4_9 PROJ_LIBRARIES = vtkproj4 Configuring done -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonid_dulman at yahoo.co.uk Thu Jul 20 06:29:10 2017 From: leonid_dulman at yahoo.co.uk (Leonid Dulman) Date: Thu, 20 Jul 2017 10:29:10 +0000 (UTC) Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: References: <1500465504824-5744014.post@n5.nabble.com> Message-ID: <773932223.1637030.1500546550358@mail.yahoo.com> But you can build two VTK different ?versions one ?with OpenGL and second with OpenGL2 ?and to use platform supported on current machine.? From: Elvis Stansvik To: satwik k Cc: vtk Sent: Thursday, July 20, 2017 9:29 AM Subject: Re: [vtkusers] vtk-7.1 openGL 2.0 crash 2017-07-20 4:03 GMT+02:00 satwik k : > Is thr any way to find out OpenGL version in VTK . >? So that system which supports OpenGL 2.0 can make use of VTK 7.0 OpenGL 2.0 > as Rendering backed. > > System which won't support OpenGL 2.0 can make use of OpenGL as Rendering > backend. Just some clarification: The current rendering backend in VTK is called "OpenGL2", because it's the second version of the OpenGL backend. It requires OpenGL 3.2. The old backend is called just "OpenGL". I'm not sure which version of OpenGL it requires. It's easy to confuse the name of the backend "OpenGL2" and think that the 2 means OpenGL version 2. But it's just a name. Perhaps it would have been better to call it OpenGLNG or something for that reason. It's not possible to build a VTK that has both the OpenGL and OpenGL2 backend built, and I'm not sure if it would be possible to deliver an application with two versions of VTK (one with OpenGL2 and one with OpenGL) and choose which one to use at runtime. Maybe.. but it would be rather complicated. Like Ken said, if you want something that runs everywhere, I think the only option is to build against Mesa. Elvis > > > > Regards, > Satwik k > > On 20-Jul-2017 00:08, "Ken Martin" wrote: >> >> Two options I know of >> >> 1) build your executable against Mesa so it will run everywhere >> >> 2) gracefully test if the hardware supports OpenGL2 and gracefully exit if >> not. In current VTK you can do this but I think in 7.1 it may not work. >> Basically call renWin->GetSupportsOpenGL() and handle accordingly. >> >> >> >> On Wed, Jul 19, 2017 at 7:58 AM, Satwik wrote: >>> >>> Hi, >>> >>> I configured VTK-7.1 with *openGL2* as Rendering Backend. >>> >>> But, When i tried to run Volume Rendering or any VTK applications in the >>> machine which is not having openGL2.0. *Application is getting crashed*. >>> >>> How well can i handle this..???? >>> >>> >>> Regards, >>> satwik k >>> >>> >>> >>> -- >>> View this message in context: >>> http://vtk.1045678.n5.nabble.com/vtk-7-1-openGL-2-0-crash-tp5744014.html >>> Sent from the VTK - Users mailing list archive at Nabble.com. >>> _______________________________________________ >>> 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 >> >> >> >> >> -- >> Ken Martin PhD >> Distinguished Engineer >> Kitware Inc. >> 28 Corporate Drive >> Clifton Park NY 12065 >> >> 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 > > 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 > _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maxime.boissonneault at calculquebec.ca Thu Jul 20 07:02:20 2017 From: maxime.boissonneault at calculquebec.ca (Maxime Boissonneault) Date: Thu, 20 Jul 2017 07:02:20 -0400 Subject: [vtkusers] Missing python bindings with VTK 8.0 Message-ID: <72a2ca87-f424-4fc7-b197-099a78c85a43@iPad> Thanks. That worked. Is this something that changed with version 8.0 ? I don't see this option in my install notes for version 7.x and the python bindings were installed. Maxime > > On juil. 19, 2017 at 6:23 PM, wrote: > > > > "-DVTK_WRAP_PYTHON:BOOL=ON" > > > > > On Wed, Jul 19, 2017 at 4:07 PM, Maxime Boissonneault wrote: > > > Hi, > > I am trying to compile VTK 8.0. I am passing the following flags to cmake : > > cmake . - DCMAKE_INSTALL_PREFIX=/home/mboisson/.local/easybuild/software/2017/avx2/MPI/intel2016.4/openmpi2.1/vtk/8.0.0 -DCMAKE_C_COMPILER='icc' -DCMAKE_Fortran_FLAGS='-O2 -xCore-AVX2 -ftz -fp-speculation=safe -fp-model source' -DCMAKE_CXX_FLAGS='-O2 -xCore-AVX2 -ftz -fp-speculation=safe -fp-model source' -DCMAKE_CXX_COMPILER='icpc' -DCMAKE_Fortran_COMPILER='ifort' -DCMAKE_C_FLAGS='-O2 -xCore-AVX2 -ftz -fp-speculation=safe -fp-model source' -DCMAKE_VERBOSE_MAKEFILE=ON -DPYTHON_LIBRARY=$EBROOTPYTHON/lib/libpython2.7.so (http://libpython2.7.so) -DPYTHON_INCLUDE_DIR=$EBROOTPYTHON/include/python2.7 > > > > > > Python is found, but the bindings are not created. > > > > Below is a grep of "python" from the CMakeCache.txt. > > > > Anyone got an idea on how to fix this ? Thanks > > > > [mboisson at build-node VTK-8.0.0]$ grep -i PYTHON CMakeCache.txt > > CMAKE_EXE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 (http://soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64 (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib (http://soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib) -L/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib (http://soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib) > > CMAKE_MODULE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 (http://soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64 (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib (http://soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib) -L/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib (http://soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib) > > CMAKE_SHARED_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 (http://soft.computecanada.ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64 (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/mkl/lib/intel64) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib (http://soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib) -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib (http://soft.computecanada.ca/easybuild/software/2017/avx2/Compiler/intel2016.4/hdf5/1.8.18/lib) -L/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib (http://soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib) > > //Request building AutobahnPython > > Module_AutobahnPython:BOOL=OFF > > //Request building SixPython > > Module_SixPython:BOOL=OFF > > //Request building vtkPython > > Module_vtkPython:BOOL=OFF > > //Request building vtkPythonInterpreter > > Module_vtkPythonInterpreter:BOOL=OFF > > //Request building vtkWebPython > > Module_vtkWebPython:BOOL=OFF > > //Request building vtkWrappingPythonCore > > Module_vtkWrappingPythonCore:BOOL=OFF > > PYTHON_EXECUTABLE:FILEPATH=/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/bin/python2 (http://soft.computecanada.ca/nix/var/nix/profiles/16.09/bin/python2) > > PYTHON_INCLUDE_DIR:UNINITIALIZED=/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/include/python2.7 (http://soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/include/python2.7) > > PYTHON_LIBRARY:UNINITIALIZED=/cvmfs/soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib/libpython2.7.so (http://soft.computecanada.ca/nix/var/nix/profiles/python-2.7.13/lib/libpython2.7.so) > > //Directory where python modules will be put inside the build tree > > VTK_BUILD_PYTHON_MODULE_DIR:PATH=-NOTFOUND > > //Directory where python modules will be installed > > VTK_INSTALL_PYTHON_MODULE_DIR:PATH=-NOTFOUND > > //Python version to use: 2, 2.x, 3, 3.x, or empty > > VTK_PYTHON_VERSION:STRING=2 > > //Should VTK Python wrapping be built? > > VTK_WRAP_PYTHON:BOOL=OFF > > //ADVANCED property for variable: Module_AutobahnPython > > Module_AutobahnPython-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: Module_SixPython > > Module_SixPython-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: Module_vtkPython > > Module_vtkPython-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: Module_vtkPythonInterpreter > > Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: Module_vtkWebPython > > Module_vtkWebPython-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: Module_vtkWrappingPythonCore > > Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: PYTHON_EXECUTABLE > > PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: VTK_BUILD_PYTHON_MODULE_DIR > > VTK_BUILD_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 > > //ADVANCED property for variable: VTK_INSTALL_PYTHON_MODULE_DIR > > VTK_INSTALL_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 > > > > > > -- > > --------------------------------- > > Maxime Boissonneault > > Analyste de calcul - Calcul Qu?bec, Universit? Laval > > Pr?sident - Comit? de coordination du soutien ? la recherche de Calcul Qu?bec > > Team lead - Research Support National Team, Compute Canada > > Instructeur Software Carpentry > > Ph. D. en physique > -------------- next part -------------- An HTML attachment was scrubbed... URL: From satwik.k8 at gmail.com Thu Jul 20 07:46:57 2017 From: satwik.k8 at gmail.com (Satwik) Date: Thu, 20 Jul 2017 04:46:57 -0700 (MST) Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: <773932223.1637030.1500546550358@mail.yahoo.com> References: <1500465504824-5744014.post@n5.nabble.com> <773932223.1637030.1500546550358@mail.yahoo.com> Message-ID: <1500551217979-5744045.post@n5.nabble.com> Yup, I didn't find any other option and We are thinking same to build application with two separate OpenGL compatibility. Thanks for ur time Elvin , Ken Regards, Satwik -- View this message in context: http://vtk.1045678.n5.nabble.com/vtk-7-1-openGL-2-0-crash-tp5744014p5744045.html Sent from the VTK - Users mailing list archive at Nabble.com. From david.gobbi at gmail.com Thu Jul 20 08:16:19 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 20 Jul 2017 06:16:19 -0600 Subject: [vtkusers] Missing python bindings with VTK 8.0 In-Reply-To: <72a2ca87-f424-4fc7-b197-099a78c85a43@iPad> References: <72a2ca87-f424-4fc7-b197-099a78c85a43@iPad> Message-ID: That's strange, because this option has always been necessary for enabling the python wrappers. - David On Thu, Jul 20, 2017 at 5:02 AM, Maxime Boissonneault < maxime.boissonneault at calculquebec.ca> wrote: > Thanks. That worked. > > Is this something that changed with version 8.0 ? I don't see this option > in my install notes for version 7.x and the python bindings were installed. > > Maxime > > > On juil. 19, 2017 at 6:23 PM, > wrote: > > "-DVTK_WRAP_PYTHON:BOOL=ON" > > > On Wed, Jul 19, 2017 at 4:07 PM, Maxime Boissonneault < > maxime.boissonneault at calculquebec.ca> wrote: > >> Hi, >> I am trying to compile VTK 8.0. I am passing the following flags to cmake >> : >> cmake . - DCMAKE_INSTALL_PREFIX=/home/mboisson/.local/easybuild/softwa >> re/2017/avx2/MPI/intel2016.4/openmpi2.1/vtk/8.0.0 >> -DCMAKE_C_COMPILER='icc' -DCMAKE_Fortran_FLAGS='-O2 -xCore-AVX2 -ftz >> -fp-speculation=safe -fp-model source' -DCMAKE_CXX_FLAGS='-O2 -xCore-AVX2 >> -ftz -fp-speculation=safe -fp-model source' -DCMAKE_CXX_COMPILER='icpc' >> -DCMAKE_Fortran_COMPILER='ifort' -DCMAKE_C_FLAGS='-O2 -xCore-AVX2 -ftz >> -fp-speculation=safe -fp-model source' -DCMAKE_VERBOSE_MAKEFILE=ON >> -DPYTHON_LIBRARY=$EBROOTPYTHON/lib/libpython2.7.so >> -DPYTHON_INCLUDE_DIR=$EBROOTPYTHON/include/python2.7 >> >> >> Python is found, but the bindings are not created. >> >> Below is a grep of "python" from the CMakeCache.txt. >> >> Anyone got an idea on how to fix this ? Thanks >> >> [mboisson at build-node VTK-8.0.0]$ grep -i PYTHON CMakeCache.txt >> CMAKE_EXE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada.ca >> /easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/ >> soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib >> -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/ >> imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca >> /easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/ >> soft.computecanada.ca/easybuild/software/2017/avx2/ >> Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca >> /nix/var/nix/profiles/python-2.7.13/lib >> CMAKE_MODULE_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada >> .ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/ >> soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib >> -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/ >> imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca >> /easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/ >> soft.computecanada.ca/easybuild/software/2017/avx2/ >> Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca >> /nix/var/nix/profiles/python-2.7.13/lib >> CMAKE_SHARED_LINKER_FLAGS:STRING=-L/cvmfs/soft.computecanada >> .ca/easybuild/software/2017/Core/icc/2016.4.258/lib/intel64 -L/cvmfs/ >> soft.computecanada.ca/easybuild/software/2017/Core/imkl/11.3.4.258/lib >> -L/cvmfs/soft.computecanada.ca/easybuild/software/2017/Core/ >> imkl/11.3.4.258/mkl/lib/intel64 -L/cvmfs/soft.computecanada.ca >> /easybuild/software/2017/Core/imkl/11.3.4.258/lib -L/cvmfs/ >> soft.computecanada.ca/easybuild/software/2017/avx2/ >> Compiler/intel2016.4/hdf5/1.8.18/lib -L/cvmfs/soft.computecanada.ca >> /nix/var/nix/profiles/python-2.7.13/lib >> //Request building AutobahnPython >> Module_AutobahnPython:BOOL=OFF >> //Request building SixPython >> Module_SixPython:BOOL=OFF >> //Request building vtkPython >> Module_vtkPython:BOOL=OFF >> //Request building vtkPythonInterpreter >> Module_vtkPythonInterpreter:BOOL=OFF >> //Request building vtkWebPython >> Module_vtkWebPython:BOOL=OFF >> //Request building vtkWrappingPythonCore >> Module_vtkWrappingPythonCore:BOOL=OFF >> PYTHON_EXECUTABLE:FILEPATH=/cvmfs/soft.computecanada.ca/nix/ >> var/nix/profiles/16.09/bin/python2 >> PYTHON_INCLUDE_DIR:UNINITIALIZED=/cvmfs/soft.computecanada.c >> a/nix/var/nix/profiles/python-2.7.13/include/python2.7 >> PYTHON_LIBRARY:UNINITIALIZED=/cvmfs/soft.computecanada.ca/ni >> x/var/nix/profiles/python-2.7.13/lib/libpython2.7.so >> //Directory where python modules will be put inside the build tree >> VTK_BUILD_PYTHON_MODULE_DIR:PATH=-NOTFOUND >> //Directory where python modules will be installed >> VTK_INSTALL_PYTHON_MODULE_DIR:PATH=-NOTFOUND >> //Python version to use: 2, 2.x, 3, 3.x, or empty >> VTK_PYTHON_VERSION:STRING=2 >> //Should VTK Python wrapping be built? >> VTK_WRAP_PYTHON:BOOL=OFF >> //ADVANCED property for variable: Module_AutobahnPython >> Module_AutobahnPython-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: Module_SixPython >> Module_SixPython-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: Module_vtkPython >> Module_vtkPython-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: Module_vtkPythonInterpreter >> Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: Module_vtkWebPython >> Module_vtkWebPython-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: Module_vtkWrappingPythonCore >> Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: PYTHON_EXECUTABLE >> PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: VTK_BUILD_PYTHON_MODULE_DIR >> VTK_BUILD_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 >> //ADVANCED property for variable: VTK_INSTALL_PYTHON_MODULE_DIR >> VTK_INSTALL_PYTHON_MODULE_DIR-ADVANCED:INTERNAL=1 >> >> >> -- >> --------------------------------- >> Maxime Boissonneault >> Analyste de calcul - Calcul Qu?bec, Universit? Laval >> Pr?sident - Comit? de coordination du soutien ? la recherche de Calcul >> Qu?bec >> Team lead - Research Support National Team, Compute Canada >> Instructeur Software Carpentry >> Ph. D. en physique >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From spir.robert at gmail.com Thu Jul 20 08:17:08 2017 From: spir.robert at gmail.com (=?iso-8859-2?B?UvNiZXJ0IKlwaXI=?=) Date: Thu, 20 Jul 2017 14:17:08 +0200 Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: <1500526028122-5744038.post@n5.nabble.com> References: <1500475655836-5744016.post@n5.nabble.com> <1500478215092-5744018.post@n5.nabble.com> <1500526028122-5744038.post@n5.nabble.com> Message-ID: <000001d30152$1bd6bbc0$53843340$@gmail.com> Hi, I have a small Qt+VTK project here for my students: https://bitbucket.org/spir_robert/qt-vtk-widgets Master branch has QVTKOpenGLWidget and QVTKWidget branch has QVTKWidget. Both of them works fine in linux, windows and MacOS with Qt 5.9 and VTK 8. Robert -----Original Message----- From: vtkusers [mailto:vtkusers-bounces at vtk.org] On Behalf Of BBerco Sent: Thursday, July 20, 2017 6:47 AM To: vtkusers at vtk.org Subject: Re: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: Unfortunately, the program crashes on my Ubuntu platform upon rendering. That is, it segfaults at * this -> qvtkWidget -> GetRenderWindow() -> Render(); * Where the render window is an instance of vtkGenericOpenGLRenderWindow. Any thoughts? -- View this message in context: http://vtk.1045678.n5.nabble.com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-an d-NVidia-GPU-tp5744016p5744038.html Sent from the VTK - Users mailing list archive at Nabble.com. _______________________________________________ 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 From majid.msadeghi at yahoo.com Thu Jul 20 08:20:02 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Thu, 20 Jul 2017 12:20:02 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <367832745.245417.1500452366892@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> <1781957654.3072634.1500386613818@mail.yahoo.com> <367832745.245417.1500452366892@mail.yahoo.com> Message-ID: <977366772.1174706.1500553202546@mail.yahoo.com> Any solution or idea for this yet? Thanks, On Wednesday, July 19, 2017, 11:19:51 AM GMT+3, Majid Mohammad sadeghi via vtkusers wrote: Dear Cory, It is still Null. Can we recalculate normals on the output of boolean operation? Thanks, Majid Mohammad Sadeghi PhD Candidate Mechatronics Engineering Department Istanbul Technical University On Tuesday, July 18, 2017, 5:26:05 PM GMT+3, Cory Quammen wrote: Okay, let's try one more thing. Does vtkDataArray* normals = output->GetPointData()->GetArray("Normals"); return NULL? Perhaps the normals array is being copied but not being set as the active normals. Thanks,Cory On Tue, Jul 18, 2017 at 9:03 AM, Majid Mohammad sadeghi wrote: Dear Cory, !normals returns true, so as you said there is no normal array. Is there a way to copy that before the operation and apply it afterwards? But I think that wont work because part of the data is changed in the boolean operation. So how can we keep the normals? Thanks, On Tuesday, July 18, 2017, 4:21:45 PM GMT+3, Cory Quammen wrote: Hmm, now I wonder if the boolean operations filter is simply removing the normals filter. The code has changed from the original, which did preserve normals. It looks like the current code should preserve normals as well, but I'm not 100% sure if that is the case. In the output of the boolean operation filter, could you check that there is a normals array in the pointdata? vtkDataArray* normals = output->GetPointData()-> GetNormals(); If "normals" is NULL, then the normals are not being copied to the output. Thanks,Cory On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi wrote: Dear Cory, All you said was exactly what I have done. I tested your method to check the data and I could see only one of the objects. So If I understand right, during the boolean operation the vtkPolyDataNormals are recalculated and that is the reason the polydata is shown smoothed. Is there a way not to let boolean recalculate it? Or more generally is there a way to keep the bumps. That kind of is the norm in the medical field and some doctors might not feel very good about the smooth data. Thanks. On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen wrote: What I think you are seeing with the rough surface is surface normals generated from an image volume. I am assuming a lot here, so please correct me if I am wrong. It looks like you have a geometry of a bone extracted from a CT scan. The extraction algorithm was probably a variant of marching cubes or a similar algorithm. The surface normals estimated from the surface extraction algorithm were probably computed from the intensity gradient of the CT scan. This is a reasonable approach, but noise in the CT scan will affect the gradient calculation and may perturb the surface normals in the geometry a little. When this happens, you can get a rough appearing surface from the surface lighting calculation. Google "bump mapping" for how this can be used for a nice graphics effect - I think roughly the same thing is happening with your original data. When you use vtkPolyDataNormals, the normals are computed from the surface data, which was smooth to begin with. Hence, the normals are not perturbed, so you don't get a bumpy appearance. In any case, the measurements you want to take are not dependent on the surface normals. As long as the points on the surface are not smooth, which they should not be, your measurement procedure should be fine. To convince yourself the geometry is the same, you can display both the original "bumpy" surface and the smoothed surface at the same time with different colors. You should see just one surface or the other, probably the one you added to the vtkRenderer last. If the geometry is different, you will see some of one surface color and some of the other depending on which geometry is closer to the camera. I suspect you will see just one surface. HTH,Cory On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi wrote: Dear Cory, As I applied vtkPolyDataNormals to the polydata before the boolean operation I got the smoothed object, so you were right. But I dont understand exactly what is happening here? Since the geometry dimentions are very important for my application, Can I have the noisy version? Is there any way I do not get it smoothed? Thanks, On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen wrote: There shouldn't be any geometry smoothing going on in this filter. Can you verify that the geometry has changed in the smoothed version? This is speculation, but one possibility is that the surface normals in your original surface come from a gradient computation in the volume from which the surface was extracted and noise in the volume result in the bumpy appearance. You can check this by applying the vtkPolyDataNormals filter to your original surface and looking at the result. HTH,Cory On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi wrote: Dear Cory, Thanks for the reply, I set the actors property to? SetInterpolationToFlat(); as you said, but the result is the same I put a picture before and after boolean operation here. Any suggestion? Are you familier with any other library? Current boolean operation takes about 150 seconds on my system, do you think this is normal? On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen wrote: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > ______________________________ _________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc._______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From satwik.k8 at gmail.com Thu Jul 20 08:20:35 2017 From: satwik.k8 at gmail.com (Satwik) Date: Thu, 20 Jul 2017 05:20:35 -0700 (MST) Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: References: <1500465504824-5744014.post@n5.nabble.com> Message-ID: <1500553235143-5744049.post@n5.nabble.com> Is there anyway to increase the performance for VTK-7.1 configured OpenGL. Regards, Satwik -- View this message in context: http://vtk.1045678.n5.nabble.com/vtk-7-1-openGL-2-0-crash-tp5744014p5744049.html Sent from the VTK - Users mailing list archive at Nabble.com. From david.gobbi at gmail.com Thu Jul 20 08:32:59 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Thu, 20 Jul 2017 06:32:59 -0600 Subject: [vtkusers] vtkImageBlend output alpha In-Reply-To: <1279142850.537349.1500482945623@mail.yahoo.com> References: <1279142850.537349.1500482945623.ref@mail.yahoo.com> <1279142850.537349.1500482945623@mail.yahoo.com> Message-ID: Hi Mike, There is no way to change this behavior for vtkImageBlend. One solution is to use a dummy image as input 0 (same dimensions as your first image, but with RGBA set to 0,0,0,1 for all pixels), and then add your two images as inputs 1 and 2. - David On Wed, Jul 19, 2017 at 10:49 AM, Mike Withascarf via vtkusers < vtkusers at vtk.org> wrote: > Hi, I'm using vtkImageBlend to blend two vtkImageMapToColors. Right now if > I change the opacity map of the first vtkImageMapToColors (via lookup > table), it adjusts the entire alpha of the output (so for example hiding > the first one hides both of them). Is there a way to prevent vtkImageBlend > from assigning the opacity of the first element to the output? I've tried > using the "compound" blending mode in case that would help, but the screen > is blank then. Any help would be great! > > This is a simplified version of the code I'm using: > > vtkSmartPointer imapper1 = > vtkSmartPointer::New(); > imapper1->SetLookupTable(lut1); > imapper1->PassAlphaToOutputOn(); > imapper1->SetInputData(image1); > imapper1->Update(); > > vtkSmartPointer imapper2 = > vtkSmartPointer::New(); > imapper2->SetLookupTable(lut2); > imapper2->PassAlphaToOutputOn(); > imapper2->SetInputData(image2); > imapper2->Update(); > > vtkSmartPointer blend = vtkSmartPointer > ::New(); > blend->AddInputConnection(imapper1->GetOutputPort()); > blend->SetOpacity(0, 1.0); > blend->AddInputConnection(imapper2->GetOutputPort()); > blend->SetOpacity(1, 1.0); > > // If I now render and adjust lut1, it affects the output of blend so the > imapper2 image gets affected > > Mike > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Jul 20 09:26:51 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 20 Jul 2017 08:26:51 -0500 Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <977366772.1174706.1500553202546@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> <1781957654.3072634.1500386613818@mail.yahoo.com> <367832745.245417.1500452366892@mail.yahoo.com> <977366772.1174706.1500553202546@mail.yahoo.com> Message-ID: You should be able to use vtkResampleWithDataSet [1] to sample the Normals array from the input bone data to the boolean operation output. You will get invalid normals for the indented region, though. That's all I've got for suggestions other than someone figuring out in the boolean operations code why the normals aren't getting copied. Thanks, Cory [1] http://www.vtk.org/doc/nightly/html/classvtkResampleWithDataSet.html On Thu, Jul 20, 2017 at 7:20 AM, Majid Mohammad sadeghi < majid.msadeghi at yahoo.com> wrote: > Any solution or idea for this yet? > > Thanks, > > > > On Wednesday, July 19, 2017, 11:19:51 AM GMT+3, Majid Mohammad sadeghi via > vtkusers wrote: > > > Dear Cory, > > It is still Null. Can we recalculate normals on the output of boolean > operation? > > Thanks, > > > Majid Mohammad Sadeghi > PhD Candidate > Mechatronics Engineering Department > Istanbul Technical University > > > > On Tuesday, July 18, 2017, 5:26:05 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > Okay, let's try one more thing. Does > > vtkDataArray* normals = output->GetPointData()->GetArray("Normals"); > > return NULL? Perhaps the normals array is being copied but not being set > as the active normals. > > Thanks, > Cory > > On Tue, Jul 18, 2017 at 9:03 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > !normals returns true, so as you said there is no normal array. Is there a > way to copy that before the operation and apply it afterwards? But I think > that wont work because part of the data is changed in the boolean > operation. So how can we keep the normals? > > Thanks, > > > On Tuesday, July 18, 2017, 4:21:45 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > Hmm, now I wonder if the boolean operations filter is simply removing the > normals filter. The code has changed from the original, which did preserve > normals. It looks like the current code should preserve normals as well, > but I'm not 100% sure if that is the case. > > In the output of the boolean operation filter, could you check that there > is a normals array in the pointdata? > > vtkDataArray* normals = output->GetPointData()-> GetNormals(); > > If "normals" is NULL, then the normals are not being copied to the output. > > Thanks, > Cory > > > > On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > All you said was exactly what I have done. I tested your method to check > the data and I could see only one of the objects. So If I understand right, > during the boolean operation the vtkPolyDataNormals are recalculated and > that is the reason the polydata is shown smoothed. Is there a way not to > let boolean recalculate it? Or more generally is there a way to keep the > bumps. That kind of is the norm in the medical field and some doctors might > not feel very good about the smooth data. > > Thanks. > > > > > > On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What I think you are seeing with the rough surface is surface normals > generated from an image volume. I am assuming a lot here, so please correct > me if I am wrong. It looks like you have a geometry of a bone extracted > from a CT scan. The extraction algorithm was probably a variant of marching > cubes or a similar algorithm. The surface normals estimated from the > surface extraction algorithm were probably computed from the intensity > gradient of the CT scan. This is a reasonable approach, but noise in the CT > scan will affect the gradient calculation and may perturb the surface > normals in the geometry a little. When this happens, you can get a rough > appearing surface from the surface lighting calculation. Google "bump > mapping" for how this can be used for a nice graphics effect - I think > roughly the same thing is happening with your original data. > > When you use vtkPolyDataNormals, the normals are computed from the surface > data, which was smooth to begin with. Hence, the normals are not perturbed, > so you don't get a bumpy appearance. > > In any case, the measurements you want to take are not dependent on the > surface normals. As long as the points on the surface are not smooth, which > they should not be, your measurement procedure should be fine. > > To convince yourself the geometry is the same, you can display both the > original "bumpy" surface and the smoothed surface at the same time with > different colors. You should see just one surface or the other, probably > the one you added to the vtkRenderer last. If the geometry is different, > you will see some of one surface color and some of the other depending on > which geometry is closer to the camera. I suspect you will see just one > surface. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > As I applied vtkPolyDataNormals to the polydata before the boolean > operation I got the smoothed object, so you were right. But I dont > understand exactly what is happening here? Since the geometry dimentions > are very important for my application, Can I have the noisy version? Is > there any way I do not get it smoothed? > > Thanks, > > > > > On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > There shouldn't be any geometry smoothing going on in this filter. Can you > verify that the geometry has changed in the smoothed version? > > This is speculation, but one possibility is that the surface normals in > your original surface come from a gradient computation in the volume from > which the surface was extracted and noise in the volume result in the bumpy > appearance. You can check this by applying the vtkPolyDataNormals filter to > your original surface and looking at the result. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > Thanks for the reply, I set the actors property to SetInterpolationToFlat > (); as you said, but the result is the same I put a picture before and > after boolean operation here. Any suggestion? Are you familier with any > other library? Current boolean operation takes about 150 seconds on my > system, do you think this is normal? > > [image: Inline image] > > > > > On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What do you mean by smooth? The lighting is smooth? I think the filter > may be adding surface normals, in which case any actor for the data > will turn on Gouraud shading (or maybe Phong) by default, which will > make your surface look smooth. You can turn off smooth lighting as > shown in this example: > > http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading > > > On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers > wrote: > > Hi everyone, > > > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except > after > > the operation it smoothes the polydata, which I dont want. Is there a > way to > > stop that? Or is there another library for boolean operations on > polydata? > > > > Thanks. > > > > > > ______________________________ _________________ > > 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 > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From majid.msadeghi at yahoo.com Thu Jul 20 09:33:12 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Thu, 20 Jul 2017 13:33:12 +0000 (UTC) Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> <1781957654.3072634.1500386613818@mail.yahoo.com> <367832745.245417.1500452366892@mail.yahoo.com> <977366772.1174706.1500553202546@mail.yahoo.com> Message-ID: <2076005416.1202992.1500557592702@mail.yahoo.com> Thank you so much Cory for the time and effort. Can I submit this as a bug, or do you know to whom should I ask this directly? Majid Mohammad Sadeghi PhD Candidate Mechatronics Engineering Department Istanbul Technical University On Thursday, July 20, 2017, 4:26:53 PM GMT+3, Cory Quammen wrote: You should be able to use vtkResampleWithDataSet [1] to sample the Normals array from the input bone data to the boolean operation output. You will get invalid normals for the indented region, though. That's all I've got for suggestions other than someone figuring out in the boolean operations code why the normals aren't getting copied. Thanks,Cory [1] http://www.vtk.org/doc/nightly/html/classvtkResampleWithDataSet.html On Thu, Jul 20, 2017 at 7:20 AM, Majid Mohammad sadeghi wrote: Any solution or idea for this yet? Thanks, On Wednesday, July 19, 2017, 11:19:51 AM GMT+3, Majid Mohammad sadeghi via vtkusers wrote: Dear Cory, It is still Null. Can we recalculate normals on the output of boolean operation? Thanks, Majid Mohammad Sadeghi PhD Candidate Mechatronics Engineering Department Istanbul Technical University On Tuesday, July 18, 2017, 5:26:05 PM GMT+3, Cory Quammen wrote: Okay, let's try one more thing. Does vtkDataArray* normals = output->GetPointData()-> GetArray("Normals"); return NULL? Perhaps the normals array is being copied but not being set as the active normals. Thanks,Cory On Tue, Jul 18, 2017 at 9:03 AM, Majid Mohammad sadeghi wrote: Dear Cory, !normals returns true, so as you said there is no normal array. Is there a way to copy that before the operation and apply it afterwards? But I think that wont work because part of the data is changed in the boolean operation. So how can we keep the normals? Thanks, On Tuesday, July 18, 2017, 4:21:45 PM GMT+3, Cory Quammen wrote: Hmm, now I wonder if the boolean operations filter is simply removing the normals filter. The code has changed from the original, which did preserve normals. It looks like the current code should preserve normals as well, but I'm not 100% sure if that is the case. In the output of the boolean operation filter, could you check that there is a normals array in the pointdata? vtkDataArray* normals = output->GetPointData()-> GetNormals(); If "normals" is NULL, then the normals are not being copied to the output. Thanks,Cory On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi wrote: Dear Cory, All you said was exactly what I have done. I tested your method to check the data and I could see only one of the objects. So If I understand right, during the boolean operation the vtkPolyDataNormals are recalculated and that is the reason the polydata is shown smoothed. Is there a way not to let boolean recalculate it? Or more generally is there a way to keep the bumps. That kind of is the norm in the medical field and some doctors might not feel very good about the smooth data. Thanks. On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen wrote: What I think you are seeing with the rough surface is surface normals generated from an image volume. I am assuming a lot here, so please correct me if I am wrong. It looks like you have a geometry of a bone extracted from a CT scan. The extraction algorithm was probably a variant of marching cubes or a similar algorithm. The surface normals estimated from the surface extraction algorithm were probably computed from the intensity gradient of the CT scan. This is a reasonable approach, but noise in the CT scan will affect the gradient calculation and may perturb the surface normals in the geometry a little. When this happens, you can get a rough appearing surface from the surface lighting calculation. Google "bump mapping" for how this can be used for a nice graphics effect - I think roughly the same thing is happening with your original data. When you use vtkPolyDataNormals, the normals are computed from the surface data, which was smooth to begin with. Hence, the normals are not perturbed, so you don't get a bumpy appearance. In any case, the measurements you want to take are not dependent on the surface normals. As long as the points on the surface are not smooth, which they should not be, your measurement procedure should be fine. To convince yourself the geometry is the same, you can display both the original "bumpy" surface and the smoothed surface at the same time with different colors. You should see just one surface or the other, probably the one you added to the vtkRenderer last. If the geometry is different, you will see some of one surface color and some of the other depending on which geometry is closer to the camera. I suspect you will see just one surface. HTH,Cory On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi wrote: Dear Cory, As I applied vtkPolyDataNormals to the polydata before the boolean operation I got the smoothed object, so you were right. But I dont understand exactly what is happening here? Since the geometry dimentions are very important for my application, Can I have the noisy version? Is there any way I do not get it smoothed? Thanks, On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen wrote: There shouldn't be any geometry smoothing going on in this filter. Can you verify that the geometry has changed in the smoothed version? This is speculation, but one possibility is that the surface normals in your original surface come from a gradient computation in the volume from which the surface was extracted and noise in the volume result in the bumpy appearance. You can check this by applying the vtkPolyDataNormals filter to your original surface and looking at the result. HTH,Cory On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi wrote: Dear Cory, Thanks for the reply, I set the actors property to? SetInterpolationToFlat(); as you said, but the result is the same I put a picture before and after boolean operation here. Any suggestion? Are you familier with any other library? Current boolean operation takes about 150 seconds on my system, do you think this is normal? On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen wrote: What do you mean by smooth? The lighting is smooth? I think the filter may be adding surface normals, in which case any actor for the data will turn on Gouraud shading (or maybe Phong) by default, which will make your surface look smooth. You can turn off smooth lighting as shown in this example: http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi everyone, > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except after > the operation it smoothes the polydata, which I dont want. Is there a way to > stop that? Or is there another library for boolean operations on polydata? > > Thanks. > > > ______________________________ _________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc.______________________________ _________________ 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 -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From cory.quammen at kitware.com Thu Jul 20 09:35:36 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 20 Jul 2017 08:35:36 -0500 Subject: [vtkusers] VTKboolean smoothes the results! Any other libraries for boolean operation on polydata? In-Reply-To: <2076005416.1202992.1500557592702@mail.yahoo.com> References: <1078907182.2222362.1500302988072.ref@mail.yahoo.com> <1078907182.2222362.1500302988072@mail.yahoo.com> <1784503810.2268640.1500304873791@mail.yahoo.com> <923607396.2192921.1500308525188@mail.yahoo.com> <1236928608.2359425.1500310050954@mail.yahoo.com> <1781957654.3072634.1500386613818@mail.yahoo.com> <367832745.245417.1500452366892@mail.yahoo.com> <977366772.1174706.1500553202546@mail.yahoo.com> <2076005416.1202992.1500557592702@mail.yahoo.com> Message-ID: Sure, feel free to submit a bug (https://gitlab.kitware.com/vtk/vtk). If you can include a self-contained code sample with either VTK source objects (e.g., vtkSphereSource) or small data files, that would greatly aid whoever takes on the bug in the future. On Thu, Jul 20, 2017 at 8:33 AM, Majid Mohammad sadeghi < majid.msadeghi at yahoo.com> wrote: > Thank you so much Cory for the time and effort. Can I submit this as a > bug, or do you know to whom should I ask this directly? > > > Majid Mohammad Sadeghi > PhD Candidate > Mechatronics Engineering Department > Istanbul Technical University > > > > On Thursday, July 20, 2017, 4:26:53 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > You should be able to use vtkResampleWithDataSet [1] to sample the Normals > array from the input bone data to the boolean operation output. You will > get invalid normals for the indented region, though. > > That's all I've got for suggestions other than someone figuring out in the > boolean operations code why the normals aren't getting copied. > > Thanks, > Cory > > [1] http://www.vtk.org/doc/nightly/html/classvtkResampleWithDataSet.html > > On Thu, Jul 20, 2017 at 7:20 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Any solution or idea for this yet? > > Thanks, > > > > On Wednesday, July 19, 2017, 11:19:51 AM GMT+3, Majid Mohammad sadeghi via > vtkusers wrote: > > > Dear Cory, > > It is still Null. Can we recalculate normals on the output of boolean > operation? > > Thanks, > > > Majid Mohammad Sadeghi > PhD Candidate > Mechatronics Engineering Department > Istanbul Technical University > > > > On Tuesday, July 18, 2017, 5:26:05 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > Okay, let's try one more thing. Does > > vtkDataArray* normals = output->GetPointData()-> GetArray("Normals"); > > return NULL? Perhaps the normals array is being copied but not being set > as the active normals. > > Thanks, > Cory > > On Tue, Jul 18, 2017 at 9:03 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > !normals returns true, so as you said there is no normal array. Is there a > way to copy that before the operation and apply it afterwards? But I think > that wont work because part of the data is changed in the boolean > operation. So how can we keep the normals? > > Thanks, > > > On Tuesday, July 18, 2017, 4:21:45 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > Hmm, now I wonder if the boolean operations filter is simply removing the > normals filter. The code has changed from the original, which did preserve > normals. It looks like the current code should preserve normals as well, > but I'm not 100% sure if that is the case. > > In the output of the boolean operation filter, could you check that there > is a normals array in the pointdata? > > vtkDataArray* normals = output->GetPointData()-> GetNormals(); > > If "normals" is NULL, then the normals are not being copied to the output. > > Thanks, > Cory > > > > On Mon, Jul 17, 2017 at 11:47 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > All you said was exactly what I have done. I tested your method to check > the data and I could see only one of the objects. So If I understand right, > during the boolean operation the vtkPolyDataNormals are recalculated and > that is the reason the polydata is shown smoothed. Is there a way not to > let boolean recalculate it? Or more generally is there a way to keep the > bumps. That kind of is the norm in the medical field and some doctors might > not feel very good about the smooth data. > > Thanks. > > > > > > On Monday, July 17, 2017, 7:33:19 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What I think you are seeing with the rough surface is surface normals > generated from an image volume. I am assuming a lot here, so please correct > me if I am wrong. It looks like you have a geometry of a bone extracted > from a CT scan. The extraction algorithm was probably a variant of marching > cubes or a similar algorithm. The surface normals estimated from the > surface extraction algorithm were probably computed from the intensity > gradient of the CT scan. This is a reasonable approach, but noise in the CT > scan will affect the gradient calculation and may perturb the surface > normals in the geometry a little. When this happens, you can get a rough > appearing surface from the surface lighting calculation. Google "bump > mapping" for how this can be used for a nice graphics effect - I think > roughly the same thing is happening with your original data. > > When you use vtkPolyDataNormals, the normals are computed from the surface > data, which was smooth to begin with. Hence, the normals are not perturbed, > so you don't get a bumpy appearance. > > In any case, the measurements you want to take are not dependent on the > surface normals. As long as the points on the surface are not smooth, which > they should not be, your measurement procedure should be fine. > > To convince yourself the geometry is the same, you can display both the > original "bumpy" surface and the smoothed surface at the same time with > different colors. You should see just one surface or the other, probably > the one you added to the vtkRenderer last. If the geometry is different, > you will see some of one surface color and some of the other depending on > which geometry is closer to the camera. I suspect you will see just one > surface. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 11:22 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > As I applied vtkPolyDataNormals to the polydata before the boolean > operation I got the smoothed object, so you were right. But I dont > understand exactly what is happening here? Since the geometry dimentions > are very important for my application, Can I have the noisy version? Is > there any way I do not get it smoothed? > > Thanks, > > > > > On Monday, July 17, 2017, 6:48:58 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > There shouldn't be any geometry smoothing going on in this filter. Can you > verify that the geometry has changed in the smoothed version? > > This is speculation, but one possibility is that the surface normals in > your original surface come from a gradient computation in the volume from > which the surface was extracted and noise in the volume result in the bumpy > appearance. You can check this by applying the vtkPolyDataNormals filter to > your original surface and looking at the result. > > HTH, > Cory > > On Mon, Jul 17, 2017 at 10:21 AM, Majid Mohammad sadeghi < > majid.msadeghi at yahoo.com> wrote: > > Dear Cory, > > Thanks for the reply, I set the actors property to SetInterpolationToFlat > (); as you said, but the result is the same I put a picture before and > after boolean operation here. Any suggestion? Are you familier with any > other library? Current boolean operation takes about 150 seconds on my > system, do you think this is normal? > > [image: Inline image] > > > > > On Monday, July 17, 2017, 6:00:50 PM GMT+3, Cory Quammen < > cory.quammen at kitware.com> wrote: > > > What do you mean by smooth? The lighting is smooth? I think the filter > may be adding surface normals, in which case any actor for the data > will turn on Gouraud shading (or maybe Phong) by default, which will > make your surface look smooth. You can turn off smooth lighting as > shown in this example: > > http://www.vtk.org/Wiki/VTK/ Examples/Cxx/Visualization/ FlatShading > > > On Mon, Jul 17, 2017 at 9:49 AM, Majid Mohammad sadeghi via vtkusers > wrote: > > Hi everyone, > > > > I am using vtkBooleanOperationPolyDataFil ter, and it works fine except > after > > the operation it smoothes the polydata, which I dont want. Is there a > way to > > stop that? Or is there another library for boolean operations on > polydata? > > > > Thanks. > > > > > > ______________________________ _________________ > > 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 > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > ______________________________ _________________ > 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 > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled-8.jpg Type: image/jpeg Size: 261587 bytes Desc: not available URL: From ken.martin at kitware.com Thu Jul 20 09:48:52 2017 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 20 Jul 2017 09:48:52 -0400 Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: <1500553235143-5744049.post@n5.nabble.com> References: <1500465504824-5744014.post@n5.nabble.com> <1500553235143-5744049.post@n5.nabble.com> Message-ID: Not really which is why there is OpenGL2. The old OpenGL backend supports all the way back to OpenGL 1.0. The problem is that most modern rendering techniques will not work on OpenGL 1.0. Keeping OpenGL (or extending it) was resulting more and more in a situation where we had to say things like "Well LIC works, but only on these graphics cards" As more modern features were added it was getting to the point where what worked on your computer was in no way assured to work on another computer. OpenGL2 moves the baseline to OpenGL version 3.2 which is about six or seven years old but has a lot of features that support modern graphics programming. Now we can say if it runs at all, every feature should work. This creates a different problem which we have been working on to make sure all platforms have an option to support OpenGL 3.2. For OSX it is easy as Apple already guarantees OpenGL 3.2 on any OS from the past many years. For linux and windows it is trickier. Often updating your driver or Mesa version solves the issue. Sometimes not. Mesa will work on both platforms but currently we (and the operating systems) do not have a good approach to try for hardware OpenGL 3.2 and if not available, fall back to Mesa. It is something we think about regularly though and we have some hopes that in the near future a more general virtual dispatch mechanism will be implemented to solve this issue. Thanks Ken On Thu, Jul 20, 2017 at 8:20 AM, Satwik wrote: > Is there anyway to increase the performance for VTK-7.1 configured OpenGL. > > Regards, > Satwik > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtk-7-1-openGL-2-0-crash-tp5744014p5744049.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 ken.martin at kitware.com Thu Jul 20 09:54:35 2017 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 20 Jul 2017 09:54:35 -0400 Subject: [vtkusers] (no subject) In-Reply-To: <59704efa.482cca0a.52c69.00b4@mx.google.com> References: <59704efa.482cca0a.52c69.00b4@mx.google.com> Message-ID: "Yes, I have SDL2 and OpenVR from vcpkg." Maybe that is the issue? I am building off of a git clone of OpenVR, maybe the directory structure is different and the CMake code is only handing the source code structure. Could be a similar issue for SDL2. On Thu, Jul 20, 2017 at 2:34 AM, Geoffrey Garner wrote: > All: > > > > After multiple attempts, I have not been able to compile VTK with OpenVR. > With the project directory set to the OpenVR directory, I receive the > following output. This is expected because vtkObjectFactory is part of the > main project. > > > > > > Found OpenVR: C:/Users/Geoffrey/vcpkg/installed/x64-windows/include > > CMake Error at CMakeLists.txt:42 (include): > include could not find load file: > > vtkObjectFactory > > CMake Error at CMakeLists.txt:43 (vtk_add_override): > Unknown CMake command "vtk_add_override". > > CMake Warning (dev) in CMakeLists.txt: > No cmake_minimum_required command is present. A line of code such as > > cmake_minimum_required(VERSION 3.9) > > should be added at the top of the file. The version specified may be lower > if you wish to support older CMake versions for this project. For more > information run "cmake --help-policy CMP0000". > This warning is for project developers. Use -Wno-dev to suppress it. > > Configuring incomplete, errors occurred! > > See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/ > CMakeFiles/CMakeOutput.log". > > See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/ > CMakeFiles/CMakeError.log". > > > > > > However, what is not expected is the following when configuring the main > project. There is no OpenVR folder in the build directory and no > explanation of why. Yes, I have SDL2 and OpenVR from vcpkg. > > > > Group StandAlone modules: vtkChartsCore;vtkCommonComputationalGeometry > ;vtkCommonCore;vtkCommonDataModel;vtkCommonExecutionModel; > vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkDomainsChemistry; > vtkFiltersAMR;vtkFiltersCore;vtkFiltersExtraction;vtkFiltersFlowPaths; > vtkFiltersGeneral;vtkFiltersGeneric;vtkFiltersGeometry;vtkFiltersHybrid; > vtkFiltersHyperTree;vtkFiltersImaging;vtkFiltersModeling; > vtkFiltersParallel;vtkFiltersParallelImaging;vtkFiltersPoints; > vtkFiltersProgrammable;vtkFiltersSMP;vtkFiltersSelection; > vtkFiltersSources;vtkFiltersStatistics;vtkFiltersTexture; > vtkFiltersTopology;vtkFiltersVerdict;vtkIOAMR;vtkIOCore;vtkIOEnSight; > vtkIOExodus;vtkIOGeometry;vtkIOImage;vtkIOImport;vtkIOInfovis;vtkIOLSDyna; > vtkIOLegacy;vtkIOMINC;vtkIOMovie;vtkIONetCDF;vtkIOPLY;vtkIOParallel; > vtkIOParallelXML;vtkIOSQL;vtkIOTecplotTable;vtkIOVideo; > vtkIOXML;vtkIOXMLParser;vtkImagingColor;vtkImagingCore;vtkImagingFourier; > vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological; > vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInfovisCore; > vtkInfovisLayout;vtkParallelCore > > Group Imaging modules: vtkFiltersImaging;vtkImagingColor; > vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath; > vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics; > vtkImagingStencil;vtkInteractionImage;vtkRenderingImage > > Group MPI modules: vtkFiltersParallelGeometry;vtkFiltersParallelMPI; > vtkIOMPIImage;vtkIOMPIParallel;vtkIOParallelNetCDF;vtkParallelMPI > > Group Qt modules: vtkGUISupportQt;vtkGUISupportQtSQL; > vtkRenderingQt;vtkViewsQt > > Group Rendering modules: vtkGeovisCore;vtkIOExport;vtkInteractionImage; > vtkInteractionStyle;vtkInteractionWidgets;vtkRenderingAnnotation; > vtkRenderingContext2D;vtkRenderingCore;vtkRenderingFreeType; > vtkRenderingImage;vtkRenderingLOD;vtkRenderingLabel;vtkRenderingVolume; > vtkViewsContext2D;vtkViewsCore;vtkViewsInfovis > > Group Tk modules: vtkRenderingTk > > Group Views modules: vtkViewsContext2D;vtkViewsGeovis > > Group Web modules: vtkWebCore;vtkWebPython;vtkWebGLExporter > > Backend OpenGL2 modules: vtkDomainsChemistryOpenGL2;vtkIOExportOpenGL2; > vtkImagingOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingGL2PSOpenGL2; > vtkRenderingLICOpenGL2;vtkRenderingOculus;vtkRenderingOpenGL2; > vtkRenderingOpenVR;vtkRenderingVolumeOpenGL2 > > Enabling modules for OpenGL2. > > Backend OpenGL modules: vtkIOExportOpenGL;vtkRenderingContextOpenGL; > vtkRenderingGL2PS;vtkRenderingLIC;vtkRenderingOpenGL; > vtkRenderingVolumeOpenGL > > Disable test module vtkFiltersParallel-Test-Cxx since required modules are > not enabled: vtkFiltersParallelMPI;vtkParallelMPI;vtkRenderingParallel > > Disable test module vtkGeovisCore-Test-Cxx since required modules are not > enabled: vtkViewsGeovis > > Disable test module vtkIOParallel-Test-Cxx since required modules are not > enabled: vtkParallelMPI;vtkRenderingParallel > > Enabled 185 modules: > > * vtkChartsCore, needed by 6 modules: > > VTK_Group_StandAlone > > vtkChartsCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkRenderingContext2D-Test-Cxx > > vtkViewsInfovis > > * vtkCommonColor, needed by 6 modules: > > vtkChartsCore > > vtkCommonColor-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkRenderingCore > > vtkViewsInfovis > > * vtkCommonComputationalGeometry, needed by 8 modules: > > VTK_Group_StandAlone > > vtkCommonComputationalGeometry-Test-Cxx > > vtkFiltersGeneral > > vtkFiltersSources > > vtkImagingStencil > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingCore > > * vtkCommonCore, needed by 94 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonColor > > vtkCommonComputationalGeometry > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonExecutionModel > > vtkCommonMath > > vtkCommonMisc > > vtkCommonSystem > > vtkCommonTransforms > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersPoints > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSelection > > vtkFiltersSources > > vtkFiltersStatistics > > vtkFiltersTexture > > vtkFiltersTopology > > vtkFiltersVerdict > > vtkGeovisCore > > vtkIOAMR > > vtkIOCore > > vtkIOEnSight > > vtkIOExodus > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIONetCDF > > vtkIOPLY > > vtkIOParallel > > vtkIOParallelXML > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkIOXMLParser > > vtkImagingColor > > vtkImagingCore > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingHybrid-Test-Cxx > > vtkImagingMath > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionImage > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkParallelCore > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingCore > > vtkTestingGenericBridge > > vtkTestingRendering > > vtkViewsContext2D > > vtkViewsCore > > vtkViewsInfovis > > * vtkCommonDataModel, needed by 86 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonColor > > vtkCommonComputationalGeometry > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersPoints > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSelection > > vtkFiltersSources > > vtkFiltersStatistics > > vtkFiltersTexture > > vtkFiltersTopology > > vtkFiltersVerdict > > vtkGeovisCore > > vtkIOAMR > > vtkIOCore > > vtkIOEnSight > > vtkIOExodus > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIONetCDF > > vtkIOPLY > > vtkIOParallel > > vtkIOParallelXML > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkIOXMLParser > > vtkImagingColor > > vtkImagingCore > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingHybrid-Test-Cxx > > vtkImagingMath > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionImage > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkParallelCore > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingGenericBridge > > vtkTestingRendering > > vtkViewsCore > > vtkViewsInfovis > > * vtkCommonExecutionModel, needed by 76 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonColor-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersPoints > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSelection > > vtkFiltersSources > > vtkFiltersStatistics > > vtkFiltersTexture > > vtkFiltersTopology > > vtkFiltersVerdict > > vtkGeovisCore > > vtkIOAMR > > vtkIOCore > > vtkIOEnSight > > vtkIOExodus > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIONetCDF > > vtkIONetCDF-Test-Cxx > > vtkIOParallel > > vtkIOParallelXML > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkImagingColor > > vtkImagingCore > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingMath > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionImage > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkTestingRendering > > vtkViewsCore > > vtkViewsInfovis > > * vtkCommonMath, needed by 29 modules: > > vtkCommonDataModel > > vtkCommonMath-Test-Cxx > > vtkCommonMisc > > vtkCommonTransforms > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHybrid > > vtkFiltersSMP > > vtkIOExport > > vtkIOImage > > vtkIOMINC > > vtkImagingCore > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > * vtkCommonMisc, needed by 27 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel > > vtkCommonExecutionModel > > vtkCommonExecutionModel > > vtkCommonMisc-Test-Cxx > > vtkFiltersCore > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersModeling > > vtkFiltersSMP > > vtkFiltersStatistics > > vtkIOCore > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIOPLY > > vtkIOParallel > > vtkIOParallelXML > > vtkIOXML > > vtkRenderingVolume > > vtkTestingGenericBridge > > * vtkCommonSystem, needed by 34 modules: > > VTK_Group_StandAlone > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonExecutionModel > > vtkCommonMath-Test-Cxx > > vtkCommonSystem-Test-Cxx > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersSMP > > vtkGeovisCore > > vtkIOAMR > > vtkIOGeometry > > vtkIOImage > > vtkIOMovie > > vtkIOParallel > > vtkIOVideo > > vtkIOXML > > vtkImagingColor > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkParallelCore > > vtkRenderingCore > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > * vtkCommonTransforms, needed by 37 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonMath-Test-Cxx > > vtkCommonTransforms-Test-Cxx > > vtkDomainsChemistry > > vtkFiltersCore > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHybrid > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSources > > vtkFiltersTexture > > vtkGeovisCore > > vtkIOExport > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOMINC > > vtkImagingCore > > vtkInfovisLayout > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingImage > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkViewsInfovis > > * vtkDICOMParser, needed by vtkIOImage. > > * vtkDomainsChemistry, needed by 4 modules: > > VTK_Group_StandAlone > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2 > > vtkDomainsChemistryOpenGL2 > > * vtkDomainsChemistryOpenGL2, needed by 4 modules: > > vtkDomainsChemistry > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > * vtkFiltersAMR, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkIOAMR > > vtkIOLegacy-Test-Cxx > > vtkIOXML-Test-Cxx > > * vtkFiltersCore, needed by 28 modules: > > VTK_Group_StandAlone > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkFiltersAMR > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersSMP > > vtkFiltersSources > > vtkGeovisCore > > vtkIOExodus > > vtkIOImport > > vtkIOParallel > > vtkIOXML-Test-Cxx > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingCore > > vtkRenderingLOD > > vtkRenderingVolumeOpenGL2 > > vtkViewsInfovis > > * vtkFiltersExtraction, needed by 9 modules: > > VTK_Group_StandAlone > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersSelection-Test-Cxx > > vtkIOParallel > > vtkInfovisCore > > vtkInteractionStyle > > vtkViewsInfovis > > * vtkFiltersFlowPaths, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkFiltersGeneral, needed by 27 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkDomainsChemistry > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSMP > > vtkFiltersSources > > vtkFiltersTexture > > vtkGeovisCore > > vtkImagingCore-Test-Cxx > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingLabel > > vtkRenderingVolumeOpenGL2 > > vtkViewsCore > > vtkViewsInfovis > > * vtkFiltersGeneric, needed by 3 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > * vtkFiltersGeometry, needed by 8 modules: > > VTK_Group_StandAlone > > vtkFiltersFlowPaths > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersParallel > > vtkIOExport > > vtkIOGeometry-Test-Cxx > > vtkRenderingCore > > vtkViewsInfovis > > * vtkFiltersHybrid, needed by 5 modules: > > VTK_Group_StandAlone > > vtkFiltersHybrid-Test-Cxx > > vtkIOMINC > > vtkImagingCore-Test-Cxx > > vtkInteractionWidgets > > * vtkFiltersHyperTree, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersHyperTree-Test-Cxx > > vtkIOXML-Test-Cxx > > * vtkFiltersImaging, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersParallelImaging > > vtkViewsInfovis > > * vtkFiltersModeling, needed by 16 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersParallel > > vtkFiltersSources-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis > > * vtkFiltersParallel, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersParallelImaging > > vtkIOParallel > > * vtkFiltersParallelImaging, needed by VTK_Group_StandAlone. > > * vtkFiltersPoints, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersPoints-Test-Cxx > > * vtkFiltersProgrammable, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersProgrammable-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingCore-Test-Cxx > > * vtkFiltersSMP, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersSMP-Test-Cxx > > * vtkFiltersSelection, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersSelection-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkFiltersSources, needed by 18 modules: > > VTK_Group_StandAlone > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkFiltersFlowPaths > > vtkFiltersGeneric > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersSources-Test-Cxx > > vtkIOImport > > vtkIOXML-Test-Cxx > > vtkInfovisLayout > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingCore > > vtkRenderingCore-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > vtkViewsInfovis > > * vtkFiltersStatistics, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersExtraction > > vtkFiltersImaging > > vtkFiltersParallelImaging > > vtkFiltersStatistics-Test-Cxx > > vtkViewsInfovis > > * vtkFiltersTexture, needed by VTK_Group_StandAlone. > > * vtkFiltersTopology, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersTopology-Test-Cxx > > * vtkFiltersVerdict, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersSources-Test-Cxx > > vtkFiltersVerdict-Test-Cxx > > * vtkGeovisCore, needed by VTK_Group_Rendering. > > * vtkIOAMR, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR-Test-Cxx > > vtkIOAMR-Test-Cxx > > vtkIOGeometry-Test-Cxx > > * vtkIOCore, needed by 16 modules: > > VTK_Group_StandAlone > > vtkCommonExecutionModel-Test-Cxx > > vtkFiltersFlowPaths > > vtkIOCore-Test-Cxx > > vtkIOExodus > > vtkIOExport > > vtkIOGeometry > > vtkIOInfovis > > vtkIOLegacy > > vtkIOMINC > > vtkIOPLY > > vtkIOParallel > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOXML > > vtkIOXMLParser > > * vtkIOEnSight, needed by VTK_Group_StandAlone. > > * vtkIOExodus, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkIOExodus-Test-Cxx > > vtkRenderingCore-Test-Cxx > > * vtkIOExport, needed by 4 modules: > > VTK_Group_Rendering > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2 > > vtkIOExportOpenGL2 > > * vtkIOExportOpenGL2, needed by 3 modules: > > vtkIOExport > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > * vtkIOGeometry, needed by 8 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOParallel > > vtkRenderingAnnotation-Test-Cxx > > * vtkIOImage, needed by 13 modules: > > VTK_Group_StandAlone > > vtkCommonColor-Test-Cxx > > vtkGeovisCore > > vtkIOExport > > vtkIOExport > > vtkIOImage-Test-Cxx > > vtkIOImport > > vtkIOMINC > > vtkIOPLY-Test-Cxx > > vtkIOParallel > > vtkImagingHybrid > > vtkRenderingVolume-Test-Cxx > > vtkTestingRendering > > * vtkIOImport, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOImport-Test-Cxx > > * vtkIOInfovis, needed by 6 modules: > > VTK_Group_StandAlone > > vtkChartsCore-Test-Cxx > > vtkIOInfovis-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkIOLSDyna, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOLSDyna-Test-Cxx > > * vtkIOLegacy, needed by 30 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkDomainsChemistry-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersParallel > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersTopology-Test-Cxx > > vtkFiltersVerdict-Test-Cxx > > vtkIOGeometry > > vtkIOGeometry-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOInfovis > > vtkIOLegacy-Test-Cxx > > vtkIOParallel > > vtkIOSQL-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkParallelCore > > vtkRenderingCore-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > * vtkIOMINC, needed by VTK_Group_StandAlone. > > * vtkIOMovie, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOMovie-Test-Cxx > > * vtkIONetCDF, needed by 3 modules: > > VTK_Group_StandAlone > > vtkIONetCDF-Test-Cxx > > vtkIOParallel > > * vtkIOPLY, needed by 3 modules: > > VTK_Group_StandAlone > > vtkIOPLY-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > * vtkIOParallel, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersSources-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > * vtkIOParallelXML, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOXML-Test-Cxx > > * vtkIOSQL, needed by 4 modules: > > VTK_Group_StandAlone > > vtkIOSQL-Test-Cxx > > vtkTestingIOSQL > > vtkViewsInfovis-Test-Cxx > > * vtkIOTecplotTable, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOTecplotTable-Test-Cxx > > * vtkIOVideo, needed by VTK_Group_StandAlone. > > * vtkIOXML, needed by 26 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkFiltersAMR > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSMP-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkGeovisCore > > vtkIOAMR-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOInfovis > > vtkIOParallelXML > > vtkIOXML-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingVolume > > vtkRenderingVolume-Test-Cxx > > * vtkIOXMLParser, needed by 6 modules: > > VTK_Group_StandAlone > > vtkDomainsChemistry > > vtkIOExodus > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOXML > > * vtkImagingColor, needed by 4 modules: > > VTK_Group_StandAlone > > vtkInteractionImage > > vtkInteractionWidgets > > vtkRenderingAnnotation > > * vtkImagingCore, needed by 28 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersHybrid > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersParallelImaging > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSMP-Test-Cxx > > vtkGeovisCore > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOMovie-Test-Cxx > > vtkImagingColor > > vtkImagingCore-Test-Cxx > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInteractionImage > > vtkInteractionWidgets > > vtkRenderingContextOpenGL2 > > vtkRenderingImage > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > * vtkImagingFourier, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersStatistics > > * vtkImagingGeneral, needed by 9 modules: > > VTK_Group_StandAlone > > vtkFiltersImaging > > vtkFiltersParallelImaging > > vtkImagingCore-Test-Cxx > > vtkImagingMorphological > > vtkInteractionWidgets > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis > > * vtkImagingHybrid, needed by 5 modules: > > VTK_Group_StandAlone > > vtkImagingHybrid-Test-Cxx > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingVolume-Test-Cxx > > * vtkImagingMath, needed by 5 modules: > > VTK_Group_StandAlone > > vtkFiltersGeneral-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > * vtkImagingMorphological, needed by 2 modules: > > VTK_Group_StandAlone > > vtkImagingMorphological-Test-Cxx > > * vtkImagingSources, needed by 15 modules: > > VTK_Group_StandAlone > > vtkFiltersHybrid > > vtkGeovisCore > > vtkIOImage-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOMovie-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingGeneral > > vtkImagingMorphological > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > * vtkImagingStatistics, needed by 2 modules: > > VTK_Group_StandAlone > > vtkImagingCore-Test-Cxx > > * vtkImagingStencil, needed by 5 modules: > > VTK_Group_StandAlone > > vtkFiltersHybrid-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkInfovisCore, needed by 8 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkGeovisCore > > vtkIOInfovis > > vtkIOXML-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout > > vtkViewsInfovis > > * vtkInfovisLayout, needed by 6 modules: > > VTK_Group_StandAlone > > vtkGeovisCore > > vtkIOInfovis-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkViewsInfovis > > * vtkInteractionImage, needed by 6 modules: > > VTK_Group_Rendering > > vtkIOExport-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkInteractionStyle, needed by 46 modules: > > VTK_Group_Rendering > > vtkCommonColor-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersProgrammable-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkGeovisCore > > vtkIOExodus-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOLSDyna-Test-Cxx > > vtkIOLegacy-Test-Cxx > > vtkIONetCDF-Test-Cxx > > vtkIOPLY-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkInteractionImage > > vtkInteractionWidgets > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingGL2PSOpenGL2-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis > > * vtkInteractionWidgets, needed by 6 modules: > > VTK_Group_Rendering > > vtkGeovisCore > > vtkInteractionImage > > vtkInteractionWidgets-Test-Cxx > > vtkViewsCore > > vtkViewsInfovis > > * vtkMetaIO, needed by vtkIOImage. > > * vtkParallelCore, needed by 8 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkIOAMR > > vtkIOParallel > > vtkIOParallelXML > > vtkParallelCore-Test-Cxx > > * vtkRenderingAnnotation, needed by 9 modules: > > VTK_Group_Rendering > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInteractionWidgets > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkViewsInfovis > > * vtkRenderingContext2D, needed by 9 modules: > > VTK_Group_Rendering > > vtkChartsCore > > vtkFiltersPoints-Test-Cxx > > vtkIOExport > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingContextOpenGL2 > > vtkRenderingContextOpenGL2 > > vtkViewsContext2D > > vtkViewsInfovis > > * vtkRenderingContextOpenGL2, needed by 9 modules: > > vtkChartsCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkRenderingContext2D > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkRenderingCore, needed by 34 modules: > > VTK_Group_Rendering > > vtkChartsCore > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersHybrid > > vtkFiltersParallel > > vtkGeovisCore > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOImport > > vtkIOInfovis-Test-Cxx > > vtkIOMINC > > vtkInteractionImage > > vtkInteractionStyle > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType > > vtkRenderingFreeType > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > vtkViewsContext2D > > vtkViewsCore > > vtkViewsInfovis > > * vtkRenderingFreeType, needed by 11 modules: > > VTK_Group_Rendering > > vtkIOExport > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkRenderingLabel > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > * vtkRenderingGL2PSOpenGL2, needed by 3 modules: > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkRenderingGL2PSOpenGL2-Test-Cxx > > * vtkRenderingImage, needed by 4 modules: > > VTK_Group_Rendering > > vtkImagingCore-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > * vtkRenderingLOD, needed by 4 modules: > > VTK_Group_Rendering > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > * vtkRenderingLabel, needed by 7 modules: > > VTK_Group_Rendering > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkViewsInfovis > > * vtkRenderingOpenGL2, needed by 47 modules: > > vtkCommonColor-Test-Cxx > > vtkCommonComputationalGeometry-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkCommonTransforms-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2 > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersProgrammable-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkIOExodus-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOLSDyna-Test-Cxx > > vtkIOLegacy-Test-Cxx > > vtkIONetCDF-Test-Cxx > > vtkIOPLY-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkParallelCore-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > * vtkRenderingVolume, needed by 5 modules: > > VTK_Group_Rendering > > vtkInteractionWidgets > > vtkRenderingVolume-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > vtkRenderingVolumeOpenGL2 > > * vtkRenderingVolumeOpenGL2, needed by 6 modules: > > vtkFiltersCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingVolume > > vtkRenderingVolume-Test-Cxx > > * vtkTestingCore, needed by 33 modules: > > vtkChartsCore-Test-Cxx > > vtkCommonColor-Test-Cxx > > vtkCommonComputationalGeometry-Test-Cxx > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel-Test-Cxx > > vtkCommonMath-Test-Cxx > > vtkCommonMisc-Test-Cxx > > vtkCommonSystem-Test-Cxx > > vtkCommonTransforms-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersAMR-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersSMP-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkFiltersStatistics-Test-Cxx > > vtkFiltersVerdict-Test-Cxx > > vtkIOAMR-Test-Cxx > > vtkIOCore-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOMovie-Test-Cxx > > vtkIOSQL-Test-Cxx > > vtkIOTecplotTable-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkTestingRendering > > * vtkTestingGenericBridge, needed by 2 modules: > > vtkCommonDataModel-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > * vtkTestingIOSQL, needed by vtkIOSQL-Test-Cxx. > > * vtkTestingRendering, needed by 51 modules: > > vtkChartsCore-Test-Cxx > > vtkCommonColor-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersAMR-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersProgrammable-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkFiltersTopology-Test-Cxx > > vtkIOAMR-Test-Cxx > > vtkIOExodus-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOInfovis-Test-Cxx > > vtkIOLSDyna-Test-Cxx > > vtkIOLegacy-Test-Cxx > > vtkIONetCDF-Test-Cxx > > vtkIOPLY-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkParallelCore-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkRenderingGL2PSOpenGL2-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkUtilitiesEncodeString, needed by vtkRenderingOpenGL2. > > * vtkUtilitiesHashSource, needed by vtkParallelCore. > > * vtkViewsContext2D, needed by 8 modules: > > VTK_Group_Rendering > > vtkChartsCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkViewsCore, needed by 4 modules: > > VTK_Group_Rendering > > vtkGeovisCore > > vtkViewsContext2D > > vtkViewsInfovis > > * vtkViewsInfovis, needed by 2 modules: > > VTK_Group_Rendering > > vtkViewsInfovis-Test-Cxx > > * vtkalglib, needed by vtkFiltersStatistics. > > * vtkexodusII, needed by 2 modules: > > vtkIOExodus > > vtkIOParallel > > * vtkexpat, needed by vtkIOXMLParser. > > * vtkfreetype, needed by vtkRenderingFreeType. > > * vtkgl2ps, needed by 2 modules: > > vtkIOExportOpenGL2 > > vtkRenderingGL2PSOpenGL2 > > * vtkglew, needed by 4 modules: > > vtkDomainsChemistryOpenGL2 > > vtkRenderingContextOpenGL2 > > vtkRenderingOpenGL2 > > vtkRenderingVolumeOpenGL2 > > * vtkhdf5, needed by 2 modules: > > vtkIOAMR > > vtknetcdf > > * vtkjpeg, needed by 2 modules: > > vtkIOImage > > vtktiff > > * vtkjsoncpp, needed by vtkIOParallel. > > * vtkkwiml, needed by 2 modules: > > vtkCommonCore > > vtkfreetype > > * vtklibharu, needed by vtkIOExport. > > * vtklibproj4, needed by vtkGeovisCore. > > * vtklibxml2, needed by vtkIOInfovis. > > * vtklz4, needed by vtkIOCore. > > * vtknetcdf, needed by 5 modules: > > vtkIOMINC > > vtkIONetCDF > > vtkIOParallel > > vtkexodusII > > vtknetcdfcpp > > * vtknetcdfcpp, needed by vtkIONetCDF. > > * vtkoggtheora, needed by vtkIOMovie. > > * vtkpng, needed by 3 modules: > > vtkIOImage > > vtkgl2ps > > vtklibharu > > * vtksqlite, needed by vtkIOSQL. > > * vtksys, needed by 33 modules: > > vtkChartsCore > > vtkCommonCore > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonSystem > > vtkDICOMParser > > vtkDomainsChemistry > > vtkFiltersHybrid > > vtkIOAMR > > vtkIOCore > > vtkIOExodus > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIONetCDF > > vtkIOParallel > > vtkIOParallelXML > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkIOXMLParser > > vtkImagingFourier > > vtkParallelCore > > vtkRenderingCore > > vtkRenderingOpenGL2 > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > vtkUtilitiesHashSource > > * vtktiff, needed by vtkIOImage. > > * vtkverdict, needed by vtkFiltersVerdict. > > * vtkzlib, needed by 11 modules: > > vtkIOCore > > vtkIOGeometry > > vtkIOImage > > vtkMetaIO > > vtkfreetype > > vtkgl2ps > > vtkhdf5 > > vtklibharu > > vtklibxml2 > > vtkpng > > vtktiff > > 64 bit architecture detected size of void * is 8 > > Building tiff version 4.0.6 > > libtiff library version 5.2.4 > > CMAKE_HOST_SYSTEM_PROCESSOR set to AMD64 > > HOST_FILLORDER set to FILLORDER_MSB2LSB > > HOST_BIG_ENDIAN set to 0 > > HAVE_IEEEFP set to 1 > > HDF5: SOVERSION: 8.0.2 > > HDF5: Performing Other Test STDC_HEADERS - Success > > HDF5: Performing CXX Test OLD_HEADER_FILENAME - Failed > > HDF5: Performing CXX Test H5_NO_NAMESPACE - Failed > > HDF5: Performing CXX Test H5_NO_STD - Failed > > HDF5: Performing CXX Test BOOL_NOTDEFINED - Failed > > HDF5: Performing CXX Test NO_STATIC_CAST - Failed > > HDF5: Checking for InitOnceExecuteOnce: > > HDF5: Performing Test InitOnceExecuteOnce - Success > > HDF5: Performing Other Test INLINE_TEST_inline - Success > > HDF5: Performing Other Test INLINE_TEST___inline__ - Failed > > HDF5: Performing Other Test INLINE_TEST___inline - Success > > HDF5: checking IF converting from long double to integers is accurate... > yes > > HDF5: checking IF accurately converting from integers to long double... yes > > HDF5: Checking IF accurately converting unsigned long to float values... > yes > > HDF5: Checking IF accurately roundup converting floating-point to unsigned > long long values... yes > > HDF5: Checking IF right maximum converting floating-point to unsigned long > long values... yes > > HDF5: Checking IF correctly converting long double to unsigned int > values... yes > > HDF5: Checking IF overflows normally converting floating-point to integer > values... yes > > HDF5: Checking IF correctly converting long double to (unsigned) long long > values... yes > > HDF5: Checking IF correctly converting (unsigned) long long to long double > values... yes > > HDF5: Checking IF alignment restrictions are strictly enforced... yes > > HDF5: Filter ZLIB is ON > > > > Configuring PROJ: > > > > PROJ_VERSION = 4.9.2 > > PROJ_ABI_VERSION = 4_9 > > CMake Deprecation Warning at ThirdParty/libproj4/ > vtklibproj4/cmake/policies.cmake:2 (cmake_policy): > The OLD behavior for policy CMP0022 will be removed from a future version > of CMake. > > The cmake-policies(7) manual explains that the OLD behaviors of all > policies are deprecated and that a policy should be set to OLD only under > specific short-term circumstances. Projects should be ported to the NEW > behavior and not rely on setting a policy to OLD. > Call Stack (most recent call first): > ThirdParty/libproj4/vtklibproj4/CMakeLists.txt:43 (include) > > > > Configuring proj library: > > > > PROJ_CORE_TARGET = vtkproj4 > > PROJ_CORE_TARGET_OUTPUT_NAME = vtkproj4_4_9 > > PROJ_LIBRARIES = vtkproj4 > > Configuring done > > > > _______________________________________________ > 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 > > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 sankhesh.jhaveri at kitware.com Thu Jul 20 11:12:34 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 20 Jul 2017 15:12:34 +0000 Subject: [vtkusers] Using vtkExternalOpenGLCamera In-Reply-To: <1500472740832-5744015.post@n5.nabble.com> References: <1500472740832-5744015.post@n5.nabble.com> Message-ID: Hi, Could you please provide more details on how you?re trying to set the camera parameters? The way the external camera works is that it ignores the camera position and focal point parameters if the projection and model view matrices are set explicitly using vtkExternalOpenGLCamera::SetProjectionMatrix() and vtkExternalOpenGLCamera::SetModelViewTransformMatrix() Thanks, Sankhesh ? On Wed, Jul 19, 2017 at 9:59 AM elainejiang8 wrote: > Hi everyone! > > I'm building a program that uses the externalVTKWidget to volume render an > object in an OpenGL context. Right now, I'm calling > > *ren->GetActiveCamera(); > * > > (where ren is a vtkExternalOpenGLRenderWindow instance) in my render > function so I can control the position and focal point of the camera. > However, I'm unable to get the camera to actually have any effect on the > scene. The documentation for vtkExternalOpenGLCamera is rather slim, and I > can't find any similar examples, so I am a bit stuck on this issue. > > Does anyone have any insight into how I could approach this problem? Thanks > in advance! > > Elaine > > > > -- > View this message in context: > http://vtk.1045678.n5.nabble.com/Using-vtkExternalOpenGLCamera-tp5744015.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From majid.msadeghi at yahoo.com Thu Jul 20 11:24:49 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Thu, 20 Jul 2017 15:24:49 +0000 (UTC) Subject: [vtkusers] 2 polydata overlapping area calculation References: <2088967382.1284255.1500564289739.ref@mail.yahoo.com> Message-ID: <2088967382.1284255.1500564289739@mail.yahoo.com> Hi everyone, Does anybody know of a mthod to find how out how much surface area two polydata shares or are overlapping. Basically I have 2 objects and I want to find out what percentage they are properly touching each other. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From xoviat at tamu.edu Thu Jul 20 11:25:27 2017 From: xoviat at tamu.edu (Geoffrey Garner) Date: Thu, 20 Jul 2017 10:25:27 -0500 Subject: [vtkusers] (no subject) In-Reply-To: References: <59704efa.482cca0a.52c69.00b4@mx.google.com> Message-ID: <5970cb67.8fcfca0a.18289.313f@mx.google.com> Is there any way that I could get some message out about why it is skipping OpenVR rather than silently skipping it? Thanks Geoffrey From: Ken Martin Sent: Thursday, July 20, 2017 8:54 AM To: Geoffrey Garner Cc: vtkusers at vtk.org Subject: Re: [vtkusers] (no subject) "Yes, I have SDL2 and OpenVR from vcpkg." Maybe that is the issue?? I am building off of a git clone of OpenVR, maybe the directory structure is different and the CMake code is only handing the source code structure. Could be a similar issue for SDL2. On Thu, Jul 20, 2017 at 2:34 AM, Geoffrey Garner wrote: All: ? After multiple attempts, I have not been able to compile VTK with OpenVR. With the project directory set to the OpenVR directory, I receive the following output. This is expected because vtkObjectFactory is part of the main project. ? ? Found OpenVR: C:/Users/Geoffrey/vcpkg/installed/x64-windows/include CMake Error at CMakeLists.txt:42 (include): include could not find load file: vtkObjectFactory CMake Error at CMakeLists.txt:43 (vtk_add_override): Unknown CMake command "vtk_add_override". CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.9) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. Configuring incomplete, errors occurred! See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/CMakeFiles/CMakeOutput.log". See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/CMakeFiles/CMakeError.log". ? ? However, what is not expected is the following when configuring the main project. There is no OpenVR folder in the build directory and no explanation of why. Yes, I have SDL2 and OpenVR from vcpkg. ? Group StandAlone modules: vtkChartsCore;vtkCommonComputationalGeometry;vtkCommonCore;vtkCommonDataModel;vtkCommonExecutionModel;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkDomainsChemistry;vtkFiltersAMR;vtkFiltersCore;vtkFiltersExtraction;vtkFiltersFlowPaths;vtkFiltersGeneral;vtkFiltersGeneric;vtkFiltersGeometry;vtkFiltersHybrid;vtkFiltersHyperTree;vtkFiltersImaging;vtkFiltersModeling;vtkFiltersParallel;vtkFiltersParallelImaging;vtkFiltersPoints;vtkFiltersProgrammable;vtkFiltersSMP;vtkFiltersSelection;vtkFiltersSources;vtkFiltersStatistics;vtkFiltersTexture;vtkFiltersTopology;vtkFiltersVerdict;vtkIOAMR;vtkIOCore;vtkIOEnSight;vtkIOExodus;vtkIOGeometry;vtkIOImage;vtkIOImport;vtkIOInfovis;vtkIOLSDyna;vtkIOLegacy;vtkIOMINC;vtkIOMovie;vtkIONetCDF;vtkIOPLY;vtkIOParallel;vtkIOParallelXML;vtkIOSQL;vtkIOTecplotTable;vtkIOVideo;vtkIOXML;vtkIOXMLParser;vtkImagingColor;vtkImagingCore;vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInfovisCore;vtkInfovisLayout;vtkParallelCore Group Imaging modules: vtkFiltersImaging;vtkImagingColor;vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInteractionImage;vtkRenderingImage Group MPI modules: vtkFiltersParallelGeometry;vtkFiltersParallelMPI;vtkIOMPIImage;vtkIOMPIParallel;vtkIOParallelNetCDF;vtkParallelMPI Group Qt modules: vtkGUISupportQt;vtkGUISupportQtSQL;vtkRenderingQt;vtkViewsQt Group Rendering modules: vtkGeovisCore;vtkIOExport;vtkInteractionImage;vtkInteractionStyle;vtkInteractionWidgets;vtkRenderingAnnotation;vtkRenderingContext2D;vtkRenderingCore;vtkRenderingFreeType;vtkRenderingImage;vtkRenderingLOD;vtkRenderingLabel;vtkRenderingVolume;vtkViewsContext2D;vtkViewsCore;vtkViewsInfovis Group Tk modules: vtkRenderingTk Group Views modules: vtkViewsContext2D;vtkViewsGeovis Group Web modules: vtkWebCore;vtkWebPython;vtkWebGLExporter Backend OpenGL2 modules: vtkDomainsChemistryOpenGL2;vtkIOExportOpenGL2;vtkImagingOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingGL2PSOpenGL2;vtkRenderingLICOpenGL2;vtkRenderingOculus;vtkRenderingOpenGL2;vtkRenderingOpenVR;vtkRenderingVolumeOpenGL2 Enabling modules for OpenGL2. Backend OpenGL modules: vtkIOExportOpenGL;vtkRenderingContextOpenGL;vtkRenderingGL2PS;vtkRenderingLIC;vtkRenderingOpenGL;vtkRenderingVolumeOpenGL Disable test module vtkFiltersParallel-Test-Cxx since required modules are not enabled: vtkFiltersParallelMPI;vtkParallelMPI;vtkRenderingParallel Disable test module vtkGeovisCore-Test-Cxx since required modules are not enabled: vtkViewsGeovis Disable test module vtkIOParallel-Test-Cxx since required modules are not enabled: vtkParallelMPI;vtkRenderingParallel Enabled 185 modules: * vtkChartsCore, needed by 6 modules: VTK_Group_StandAlone vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkViewsInfovis * vtkCommonColor, needed by 6 modules: vtkChartsCore vtkCommonColor-Test-Cxx vtkFiltersModeling-Test-Cxx vtkIOExport-Test-Cxx vtkRenderingCore vtkViewsInfovis * vtkCommonComputationalGeometry, needed by 8 modules: VTK_Group_StandAlone vtkCommonComputationalGeometry-Test-Cxx vtkFiltersGeneral vtkFiltersSources vtkImagingStencil vtkInfovisLayout vtkInteractionWidgets vtkRenderingCore * vtkCommonCore, needed by 94 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor vtkCommonComputationalGeometry vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonExecutionModel vtkCommonMath vtkCommonMisc vtkCommonSystem vtkCommonTransforms vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOExport vtkIOExportOpenGL2 vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingHybrid-Test-Cxx vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionStyle vtkInteractionWidgets vtkParallelCore vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingCore vtkTestingGenericBridge vtkTestingRendering vtkViewsContext2D vtkViewsCore vtkViewsInfovis * vtkCommonDataModel, needed by 86 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor vtkCommonComputationalGeometry vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOExport vtkIOExportOpenGL2 vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingHybrid-Test-Cxx vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionStyle vtkInteractionWidgets vtkParallelCore vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingGenericBridge vtkTestingRendering vtkViewsCore vtkViewsInfovis * vtkCommonExecutionModel, needed by 76 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIONetCDF-Test-Cxx vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingCore vtkRenderingFreeType vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkTestingRendering vtkViewsCore vtkViewsInfovis * vtkCommonMath, needed by 29 modules: vtkCommonDataModel vtkCommonMath-Test-Cxx vtkCommonMisc vtkCommonTransforms vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersSMP vtkIOExport vtkIOImage vtkIOMINC vtkImagingCore vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 * vtkCommonMisc, needed by 27 modules: VTK_Group_StandAlone vtkCommonDataModel vtkCommonExecutionModel vtkCommonExecutionModel vtkCommonMisc-Test-Cxx vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersSMP vtkFiltersStatistics vtkIOCore vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLegacy vtkIOMINC vtkIOMovie vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOXML vtkRenderingVolume vtkTestingGenericBridge * vtkCommonSystem, needed by 34 modules: VTK_Group_StandAlone vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonExecutionModel vtkCommonMath-Test-Cxx vtkCommonSystem-Test-Cxx vtkFiltersAMR vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHyperTree vtkFiltersImaging vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersSMP vtkGeovisCore vtkIOAMR vtkIOGeometry vtkIOImage vtkIOMovie vtkIOParallel vtkIOVideo vtkIOXML vtkImagingColor vtkInfovisLayout vtkInteractionWidgets vtkParallelCore vtkRenderingCore vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering * vtkCommonTransforms, needed by 37 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonMath-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersModeling vtkFiltersParallel vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSources vtkFiltersTexture vtkGeovisCore vtkIOExport vtkIOGeometry vtkIOImage vtkIOImport vtkIOMINC vtkImagingCore vtkInfovisLayout vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingImage vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkDICOMParser, needed by vtkIOImage. * vtkDomainsChemistry, needed by 4 modules: VTK_Group_StandAlone vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2 vtkDomainsChemistryOpenGL2 * vtkDomainsChemistryOpenGL2, needed by 4 modules: vtkDomainsChemistry vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx * vtkFiltersAMR, needed by 6 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkIOAMR vtkIOLegacy-Test-Cxx vtkIOXML-Test-Cxx * vtkFiltersCore, needed by 28 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkFiltersAMR vtkFiltersCore-Test-Cxx vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersParallel vtkFiltersSMP vtkFiltersSources vtkGeovisCore vtkIOExodus vtkIOImport vtkIOParallel vtkIOXML-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingCore vtkRenderingLOD vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkFiltersExtraction, needed by 9 modules: VTK_Group_StandAlone vtkFiltersExtraction-Test-Cxx vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersSelection-Test-Cxx vtkIOParallel vtkInfovisCore vtkInteractionStyle vtkViewsInfovis * vtkFiltersFlowPaths, needed by 4 modules: VTK_Group_StandAlone vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkFiltersGeneral, needed by 27 modules: VTK_Group_StandAlone vtkChartsCore vtkDomainsChemistry vtkFiltersCore-Test-Cxx vtkFiltersExtraction vtkFiltersGeneral-Test-Cxx vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersParallel vtkFiltersPoints-Test-Cxx vtkFiltersSMP vtkFiltersSources vtkFiltersTexture vtkGeovisCore vtkImagingCore-Test-Cxx vtkInfovisCore vtkInfovisLayout vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingCore vtkRenderingFreeType vtkRenderingLabel vtkRenderingVolumeOpenGL2 vtkViewsCore vtkViewsInfovis * vtkFiltersGeneric, needed by 3 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersGeneric-Test-Cxx * vtkFiltersGeometry, needed by 8 modules: VTK_Group_StandAlone vtkFiltersFlowPaths vtkFiltersGeometry-Test-Cxx vtkFiltersParallel vtkIOExport vtkIOGeometry-Test-Cxx vtkRenderingCore vtkViewsInfovis * vtkFiltersHybrid, needed by 5 modules: VTK_Group_StandAlone vtkFiltersHybrid-Test-Cxx vtkIOMINC vtkImagingCore-Test-Cxx vtkInteractionWidgets * vtkFiltersHyperTree, needed by 3 modules: VTK_Group_StandAlone vtkFiltersHyperTree-Test-Cxx vtkIOXML-Test-Cxx * vtkFiltersImaging, needed by 4 modules: VTK_Group_StandAlone vtkFiltersFlowPaths-Test-Cxx vtkFiltersParallelImaging vtkViewsInfovis * vtkFiltersModeling, needed by 16 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersParallel vtkFiltersSources-Test-Cxx vtkImagingCore-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkInteractionWidgets-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkFiltersParallel, needed by 3 modules: VTK_Group_StandAlone vtkFiltersParallelImaging vtkIOParallel * vtkFiltersParallelImaging, needed by VTK_Group_StandAlone. * vtkFiltersPoints, needed by 2 modules: VTK_Group_StandAlone vtkFiltersPoints-Test-Cxx * vtkFiltersProgrammable, needed by 4 modules: VTK_Group_StandAlone vtkFiltersProgrammable-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingCore-Test-Cxx * vtkFiltersSMP, needed by 2 modules: VTK_Group_StandAlone vtkFiltersSMP-Test-Cxx * vtkFiltersSelection, needed by 3 modules: VTK_Group_StandAlone vtkFiltersSelection-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkFiltersSources, needed by 18 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkFiltersFlowPaths vtkFiltersGeneric vtkFiltersModeling vtkFiltersParallel vtkFiltersSources-Test-Cxx vtkIOImport vtkIOXML-Test-Cxx vtkInfovisLayout vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingCore vtkRenderingCore-Test-Cxx vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkFiltersStatistics, needed by 6 modules: VTK_Group_StandAlone vtkFiltersExtraction vtkFiltersImaging vtkFiltersParallelImaging vtkFiltersStatistics-Test-Cxx vtkViewsInfovis * vtkFiltersTexture, needed by VTK_Group_StandAlone. * vtkFiltersTopology, needed by 2 modules: VTK_Group_StandAlone vtkFiltersTopology-Test-Cxx * vtkFiltersVerdict, needed by 3 modules: VTK_Group_StandAlone vtkFiltersSources-Test-Cxx vtkFiltersVerdict-Test-Cxx * vtkGeovisCore, needed by VTK_Group_Rendering. * vtkIOAMR, needed by 4 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkIOAMR-Test-Cxx vtkIOGeometry-Test-Cxx * vtkIOCore, needed by 16 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkFiltersFlowPaths vtkIOCore-Test-Cxx vtkIOExodus vtkIOExport vtkIOGeometry vtkIOInfovis vtkIOLegacy vtkIOMINC vtkIOPLY vtkIOParallel vtkIOSQL vtkIOTecplotTable vtkIOXML vtkIOXMLParser * vtkIOEnSight, needed by VTK_Group_StandAlone. * vtkIOExodus, needed by 6 modules: VTK_Group_StandAlone vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkIOExodus-Test-Cxx vtkRenderingCore-Test-Cxx * vtkIOExport, needed by 4 modules: VTK_Group_Rendering vtkIOExport-Test-Cxx vtkIOExportOpenGL2 vtkIOExportOpenGL2 * vtkIOExportOpenGL2, needed by 3 modules: vtkIOExport vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx * vtkIOGeometry, needed by 8 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOParallel vtkRenderingAnnotation-Test-Cxx * vtkIOImage, needed by 13 modules: VTK_Group_StandAlone vtkCommonColor-Test-Cxx vtkGeovisCore vtkIOExport vtkIOExport vtkIOImage-Test-Cxx vtkIOImport vtkIOMINC vtkIOPLY-Test-Cxx vtkIOParallel vtkImagingHybrid vtkRenderingVolume-Test-Cxx vtkTestingRendering * vtkIOImport, needed by 2 modules: VTK_Group_StandAlone vtkIOImport-Test-Cxx * vtkIOInfovis, needed by 6 modules: VTK_Group_StandAlone vtkChartsCore-Test-Cxx vtkIOInfovis-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkIOLSDyna, needed by 2 modules: VTK_Group_StandAlone vtkIOLSDyna-Test-Cxx * vtkIOLegacy, needed by 30 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkDomainsChemistry-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersParallel vtkFiltersPoints-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersTopology-Test-Cxx vtkFiltersVerdict-Test-Cxx vtkIOGeometry vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOInfovis vtkIOLegacy-Test-Cxx vtkIOParallel vtkIOSQL-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkParallelCore vtkRenderingCore-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkIOMINC, needed by VTK_Group_StandAlone. * vtkIOMovie, needed by 2 modules: VTK_Group_StandAlone vtkIOMovie-Test-Cxx * vtkIONetCDF, needed by 3 modules: VTK_Group_StandAlone vtkIONetCDF-Test-Cxx vtkIOParallel * vtkIOPLY, needed by 3 modules: VTK_Group_StandAlone vtkIOPLY-Test-Cxx vtkRenderingOpenGL2-Test-Cxx * vtkIOParallel, needed by 6 modules: VTK_Group_StandAlone vtkFiltersSources-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx * vtkIOParallelXML, needed by 2 modules: VTK_Group_StandAlone vtkIOXML-Test-Cxx * vtkIOSQL, needed by 4 modules: VTK_Group_StandAlone vtkIOSQL-Test-Cxx vtkTestingIOSQL vtkViewsInfovis-Test-Cxx * vtkIOTecplotTable, needed by 2 modules: VTK_Group_StandAlone vtkIOTecplotTable-Test-Cxx * vtkIOVideo, needed by VTK_Group_StandAlone. * vtkIOXML, needed by 26 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersAMR vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersSMP-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkGeovisCore vtkIOAMR-Test-Cxx vtkIOImport-Test-Cxx vtkIOInfovis vtkIOParallelXML vtkIOXML-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingVolume vtkRenderingVolume-Test-Cxx * vtkIOXMLParser, needed by 6 modules: VTK_Group_StandAlone vtkDomainsChemistry vtkIOExodus vtkIOInfovis vtkIOLSDyna vtkIOXML * vtkImagingColor, needed by 4 modules: VTK_Group_StandAlone vtkInteractionImage vtkInteractionWidgets vtkRenderingAnnotation * vtkImagingCore, needed by 28 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersHybrid vtkFiltersHybrid-Test-Cxx vtkFiltersParallelImaging vtkFiltersPoints-Test-Cxx vtkFiltersSMP-Test-Cxx vtkGeovisCore vtkIOExport vtkIOExportOpenGL2 vtkIOMovie-Test-Cxx vtkImagingColor vtkImagingCore-Test-Cxx vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInteractionImage vtkInteractionWidgets vtkRenderingContextOpenGL2 vtkRenderingImage vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering * vtkImagingFourier, needed by 2 modules: VTK_Group_StandAlone vtkFiltersStatistics * vtkImagingGeneral, needed by 9 modules: VTK_Group_StandAlone vtkFiltersImaging vtkFiltersParallelImaging vtkImagingCore-Test-Cxx vtkImagingMorphological vtkInteractionWidgets vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkImagingHybrid, needed by 5 modules: VTK_Group_StandAlone vtkImagingHybrid-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkRenderingVolume-Test-Cxx * vtkImagingMath, needed by 5 modules: VTK_Group_StandAlone vtkFiltersGeneral-Test-Cxx vtkIOImage-Test-Cxx vtkImagingCore-Test-Cxx vtkRenderingVolumeOpenGL2 * vtkImagingMorphological, needed by 2 modules: VTK_Group_StandAlone vtkImagingMorphological-Test-Cxx * vtkImagingSources, needed by 15 modules: VTK_Group_StandAlone vtkFiltersHybrid vtkGeovisCore vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOMovie-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingGeneral vtkImagingMorphological vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkImagingStatistics, needed by 2 modules: VTK_Group_StandAlone vtkImagingCore-Test-Cxx * vtkImagingStencil, needed by 5 modules: VTK_Group_StandAlone vtkFiltersHybrid-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkInfovisCore, needed by 8 modules: VTK_Group_StandAlone vtkChartsCore vtkGeovisCore vtkIOInfovis vtkIOXML-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout vtkViewsInfovis * vtkInfovisLayout, needed by 6 modules: VTK_Group_StandAlone vtkGeovisCore vtkIOInfovis-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkViewsInfovis * vtkInteractionImage, needed by 6 modules: VTK_Group_Rendering vtkIOExport-Test-Cxx vtkIOImage-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkInteractionStyle, needed by 46 modules: VTK_Group_Rendering vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkGeovisCore vtkIOExodus-Test-Cxx vtkIOExport-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkInteractionImage vtkInteractionWidgets vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingGL2PSOpenGL2-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkInteractionWidgets, needed by 6 modules: VTK_Group_Rendering vtkGeovisCore vtkInteractionImage vtkInteractionWidgets-Test-Cxx vtkViewsCore vtkViewsInfovis * vtkMetaIO, needed by vtkIOImage. * vtkParallelCore, needed by 8 modules: VTK_Group_StandAlone vtkFiltersAMR vtkFiltersParallel vtkFiltersParallelImaging vtkIOAMR vtkIOParallel vtkIOParallelXML vtkParallelCore-Test-Cxx * vtkRenderingAnnotation, needed by 9 modules: VTK_Group_Rendering vtkFiltersGeneral-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersSelection-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkViewsInfovis * vtkRenderingContext2D, needed by 9 modules: VTK_Group_Rendering vtkChartsCore vtkFiltersPoints-Test-Cxx vtkIOExport vtkRenderingContext2D-Test-Cxx vtkRenderingContextOpenGL2 vtkRenderingContextOpenGL2 vtkViewsContext2D vtkViewsInfovis * vtkRenderingContextOpenGL2, needed by 9 modules: vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkIOImage-Test-Cxx vtkRenderingContext2D vtkRenderingContext2D-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkRenderingCore, needed by 34 modules: VTK_Group_Rendering vtkChartsCore vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersHybrid vtkFiltersParallel vtkGeovisCore vtkIOExport vtkIOExportOpenGL2 vtkIOImport vtkIOInfovis-Test-Cxx vtkIOMINC vtkInteractionImage vtkInteractionStyle vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore-Test-Cxx vtkRenderingFreeType vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering vtkViewsContext2D vtkViewsCore vtkViewsInfovis * vtkRenderingFreeType, needed by 11 modules: VTK_Group_Rendering vtkIOExport vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingLabel vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkRenderingGL2PSOpenGL2, needed by 3 modules: vtkIOExport vtkIOExportOpenGL2 vtkRenderingGL2PSOpenGL2-Test-Cxx * vtkRenderingImage, needed by 4 modules: VTK_Group_Rendering vtkImagingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingOpenGL2-Test-Cxx * vtkRenderingLOD, needed by 4 modules: VTK_Group_Rendering vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingLOD-Test-Cxx * vtkRenderingLabel, needed by 7 modules: VTK_Group_Rendering vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkIOExport-Test-Cxx vtkInfovisLayout-Test-Cxx vtkRenderingLabel-Test-Cxx vtkViewsInfovis * vtkRenderingOpenGL2, needed by 47 modules: vtkCommonColor-Test-Cxx vtkCommonComputationalGeometry-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2 vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkIOExodus-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImport-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkParallelCore-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingGL2PSOpenGL2 vtkRenderingGL2PSOpenGL2 vtkRenderingGL2PSOpenGL2 vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolumeOpenGL2 * vtkRenderingVolume, needed by 5 modules: VTK_Group_Rendering vtkInteractionWidgets vtkRenderingVolume-Test-Cxx vtkRenderingVolumeOpenGL2 vtkRenderingVolumeOpenGL2 * vtkRenderingVolumeOpenGL2, needed by 6 modules: vtkFiltersCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingVolume vtkRenderingVolume-Test-Cxx * vtkTestingCore, needed by 33 modules: vtkChartsCore-Test-Cxx vtkCommonColor-Test-Cxx vtkCommonComputationalGeometry-Test-Cxx vtkCommonCore-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkCommonMath-Test-Cxx vtkCommonMisc-Test-Cxx vtkCommonSystem-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersAMR-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersSMP-Test-Cxx vtkFiltersSources-Test-Cxx vtkFiltersStatistics-Test-Cxx vtkFiltersVerdict-Test-Cxx vtkIOAMR-Test-Cxx vtkIOCore-Test-Cxx vtkIOImage-Test-Cxx vtkIOImage-Test-Cxx vtkIOMovie-Test-Cxx vtkIOSQL-Test-Cxx vtkIOTecplotTable-Test-Cxx vtkIOXML-Test-Cxx vtkImagingHybrid-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkTestingRendering * vtkTestingGenericBridge, needed by 2 modules: vtkCommonDataModel-Test-Cxx vtkFiltersGeneric-Test-Cxx * vtkTestingIOSQL, needed by vtkIOSQL-Test-Cxx. * vtkTestingRendering, needed by 51 modules: vtkChartsCore-Test-Cxx vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersAMR-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkFiltersTopology-Test-Cxx vtkIOAMR-Test-Cxx vtkIOExodus-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOInfovis-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkParallelCore-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingGL2PSOpenGL2-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkUtilitiesEncodeString, needed by vtkRenderingOpenGL2. * vtkUtilitiesHashSource, needed by vtkParallelCore. * vtkViewsContext2D, needed by 8 modules: VTK_Group_Rendering vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkViewsCore, needed by 4 modules: VTK_Group_Rendering vtkGeovisCore vtkViewsContext2D vtkViewsInfovis * vtkViewsInfovis, needed by 2 modules: VTK_Group_Rendering vtkViewsInfovis-Test-Cxx * vtkalglib, needed by vtkFiltersStatistics. * vtkexodusII, needed by 2 modules: vtkIOExodus vtkIOParallel * vtkexpat, needed by vtkIOXMLParser. * vtkfreetype, needed by vtkRenderingFreeType. * vtkgl2ps, needed by 2 modules: vtkIOExportOpenGL2 vtkRenderingGL2PSOpenGL2 * vtkglew, needed by 4 modules: vtkDomainsChemistryOpenGL2 vtkRenderingContextOpenGL2 vtkRenderingOpenGL2 vtkRenderingVolumeOpenGL2 * vtkhdf5, needed by 2 modules: vtkIOAMR vtknetcdf * vtkjpeg, needed by 2 modules: vtkIOImage vtktiff * vtkjsoncpp, needed by vtkIOParallel. * vtkkwiml, needed by 2 modules: vtkCommonCore vtkfreetype * vtklibharu, needed by vtkIOExport. * vtklibproj4, needed by vtkGeovisCore. * vtklibxml2, needed by vtkIOInfovis. * vtklz4, needed by vtkIOCore. * vtknetcdf, needed by 5 modules: vtkIOMINC vtkIONetCDF vtkIOParallel vtkexodusII vtknetcdfcpp * vtknetcdfcpp, needed by vtkIONetCDF. * vtkoggtheora, needed by vtkIOMovie. * vtkpng, needed by 3 modules: vtkIOImage vtkgl2ps vtklibharu * vtksqlite, needed by vtkIOSQL. * vtksys, needed by 33 modules: vtkChartsCore vtkCommonCore vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonSystem vtkDICOMParser vtkDomainsChemistry vtkFiltersHybrid vtkIOAMR vtkIOCore vtkIOExodus vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIONetCDF vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingFourier vtkParallelCore vtkRenderingCore vtkRenderingOpenGL2 vtkRenderingVolumeOpenGL2 vtkTestingRendering vtkUtilitiesHashSource * vtktiff, needed by vtkIOImage. * vtkverdict, needed by vtkFiltersVerdict. * vtkzlib, needed by 11 modules: vtkIOCore vtkIOGeometry vtkIOImage vtkMetaIO vtkfreetype vtkgl2ps vtkhdf5 vtklibharu vtklibxml2 vtkpng vtktiff 64 bit architecture detected size of void * is 8 Building tiff version 4.0.6 libtiff library version 5.2.4 CMAKE_HOST_SYSTEM_PROCESSOR set to AMD64 HOST_FILLORDER set to FILLORDER_MSB2LSB HOST_BIG_ENDIAN set to 0 HAVE_IEEEFP set to 1 HDF5: SOVERSION: 8.0.2 HDF5: Performing Other Test STDC_HEADERS - Success HDF5: Performing CXX Test OLD_HEADER_FILENAME - Failed HDF5: Performing CXX Test H5_NO_NAMESPACE - Failed HDF5: Performing CXX Test H5_NO_STD - Failed HDF5: Performing CXX Test BOOL_NOTDEFINED - Failed HDF5: Performing CXX Test NO_STATIC_CAST - Failed HDF5: Checking for InitOnceExecuteOnce: HDF5: Performing Test InitOnceExecuteOnce - Success HDF5: Performing Other Test INLINE_TEST_inline - Success HDF5: Performing Other Test INLINE_TEST___inline__ - Failed HDF5: Performing Other Test INLINE_TEST___inline - Success HDF5: checking IF converting from long double to integers is accurate... yes HDF5: checking IF accurately converting from integers to long double... yes HDF5: Checking IF accurately converting unsigned long to float values... yes HDF5: Checking IF accurately roundup converting floating-point to unsigned long long values... yes HDF5: Checking IF right maximum converting floating-point to unsigned long long values... yes HDF5: Checking IF correctly converting long double to unsigned int values... yes HDF5: Checking IF overflows normally converting floating-point to integer values... yes HDF5: Checking IF correctly converting long double to (unsigned) long long values... yes HDF5: Checking IF correctly converting (unsigned) long long to long double values... yes HDF5: Checking IF alignment restrictions are strictly enforced... yes HDF5: Filter ZLIB is ON ? Configuring PROJ: ? PROJ_VERSION = 4.9.2 PROJ_ABI_VERSION = 4_9 CMake Deprecation Warning at ThirdParty/libproj4/vtklibproj4/cmake/policies.cmake:2 (cmake_policy): The OLD behavior for policy CMP0022 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. Call Stack (most recent call first): ThirdParty/libproj4/vtklibproj4/CMakeLists.txt:43 (include) ? Configuring proj library: ? PROJ_CORE_TARGET = vtkproj4 PROJ_CORE_TARGET_OUTPUT_NAME = vtkproj4_4_9 PROJ_LIBRARIES = vtkproj4 Configuring done ? _______________________________________________ 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 -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 elainejiang8 at gmail.com Thu Jul 20 11:38:04 2017 From: elainejiang8 at gmail.com (Elaine Jiang) Date: Thu, 20 Jul 2017 11:38:04 -0400 Subject: [vtkusers] Using vtkExternalOpenGLCamera In-Reply-To: References: <1500472740832-5744015.post@n5.nabble.com> Message-ID: Hi Sankhesh, I've tried setting the camera and focal point parameters without using SetProjectionMatrix() and SetModelViewTransformMatrix(), and I've also tried just calling SetProjectionMatrix() and SetModelViewTransformMatrix() by themselves. Neither approach seemed to have an effect on the scene. I was looking through the documentation and was wondering if I need to use the function vtkCamera::vtkSetUseExplicitProjectionTransformMatrix(bool) to solve the problem? Thanks, Elaine On Thu, Jul 20, 2017 at 11:12 AM, Sankhesh Jhaveri < sankhesh.jhaveri at kitware.com> wrote: > Hi, > > Could you please provide more details on how you?re trying to set the > camera parameters? > The way the external camera works is that it ignores the camera position > and focal point parameters if the projection and model view matrices are > set explicitly using vtkExternalOpenGLCamera::SetProjectionMatrix() and > vtkExternalOpenGLCamera::SetModelViewTransformMatrix() > > Thanks, > Sankhesh > ? > > On Wed, Jul 19, 2017 at 9:59 AM elainejiang8 > wrote: > >> Hi everyone! >> >> I'm building a program that uses the externalVTKWidget to volume render an >> object in an OpenGL context. Right now, I'm calling >> >> *ren->GetActiveCamera(); >> * >> >> (where ren is a vtkExternalOpenGLRenderWindow instance) in my render >> function so I can control the position and focal point of the camera. >> However, I'm unable to get the camera to actually have any effect on the >> scene. The documentation for vtkExternalOpenGLCamera is rather slim, and I >> can't find any similar examples, so I am a bit stuck on this issue. >> >> Does anyone have any insight into how I could approach this problem? >> Thanks >> in advance! >> >> Elaine >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.com/Using- >> vtkExternalOpenGLCamera-tp5744015.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> > -- > Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware > | (518) 881-4417 > ? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rick at pile.com Thu Jul 20 12:45:02 2017 From: rick at pile.com (Rick Dailey) Date: Thu, 20 Jul 2017 09:45:02 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error Message-ID: <1500569102114-5744068.post@n5.nabble.com> This is an ongoing issue I have had since starting my project with VTK 6.3 until today when I am using 7.1.1. I have seen it mentioned many times by other users and no one has been able to help. I even had VTK paid support for over a year and even working directly with a Kitware engineer failed to the problem. There are many times when I will display a 3D object and numerous errors related to vtkTextureObject will be generated. The result is that I get notified of these errors and my object does not display. The first problem occurs here, on the second line, assert(this->Handle). Note that nowhere in my code do I explicitly use a vtkTextureObject. It is my understanding that VTK must use this object for displaying text, even when the text is a solid color, so if I don't specify a texture then a default is created. void vtkTextureObject::Bind() { assert(this->Context); assert(this->Handle); ... } The next error occurs here: void vtkTextureObject::SendParameters() { assert("pre: is_bound" && this->IsBound()); ... } Unfortunately, I am unable to provide sample code that reliably demonstrates this issue. The software it is used in is a commercial release which is quite large and not open-source. Out of the hundreds of users of this software, approximately one half report the bug. Many attempts at creating a demo had varying results. I was able to create one demo that failed on half the computers I tried it on but no one at Kitware could duplicate them. There are many things I tried at the suggestion of Kitware and I will try to organize a list at some time in the future. -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068.html Sent from the VTK - Users mailing list archive at Nabble.com. From sankhesh.jhaveri at kitware.com Thu Jul 20 13:11:03 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 20 Jul 2017 17:11:03 +0000 Subject: [vtkusers] Using vtkExternalOpenGLCamera In-Reply-To: References: <1500472740832-5744015.post@n5.nabble.com> Message-ID: Hi Elaine, You shouldn?t have to set that flag for using the matrices set on the external camera. Could you share some sample code that doesn?t work? Thanks, Sankhesh ? On Thu, Jul 20, 2017 at 11:38 AM Elaine Jiang wrote: > Hi Sankhesh, > > I've tried setting the camera and focal point parameters without using > SetProjectionMatrix() and SetModelViewTransformMatrix(), and I've also > tried just calling SetProjectionMatrix() and SetModelViewTransformMatrix() > by themselves. Neither approach seemed to have an effect on the scene. I > was looking through the documentation and was wondering if I need to use > the function vtkCamera::vtkSetUseExplicitProjectionTransformMatrix(bool) to > solve the problem? > > Thanks, > Elaine > > On Thu, Jul 20, 2017 at 11:12 AM, Sankhesh Jhaveri < > sankhesh.jhaveri at kitware.com> wrote: > >> Hi, >> >> Could you please provide more details on how you?re trying to set the >> camera parameters? >> The way the external camera works is that it ignores the camera position >> and focal point parameters if the projection and model view matrices are >> set explicitly using vtkExternalOpenGLCamera::SetProjectionMatrix() and >> vtkExternalOpenGLCamera::SetModelViewTransformMatrix() >> >> Thanks, >> Sankhesh >> ? >> >> On Wed, Jul 19, 2017 at 9:59 AM elainejiang8 >> wrote: >> >>> Hi everyone! >>> >>> I'm building a program that uses the externalVTKWidget to volume render >>> an >>> object in an OpenGL context. Right now, I'm calling >>> >>> *ren->GetActiveCamera(); >>> * >>> >>> (where ren is a vtkExternalOpenGLRenderWindow instance) in my render >>> function so I can control the position and focal point of the camera. >>> However, I'm unable to get the camera to actually have any effect on the >>> scene. The documentation for vtkExternalOpenGLCamera is rather slim, and >>> I >>> can't find any similar examples, so I am a bit stuck on this issue. >>> >>> Does anyone have any insight into how I could approach this problem? >>> Thanks >>> in advance! >>> >>> Elaine >>> >>> >>> >>> -- >>> View this message in context: >>> http://vtk.1045678.n5.nabble.com/Using-vtkExternalOpenGLCamera-tp5744015.html >>> Sent from the VTK - Users mailing list archive at Nabble.com. >>> _______________________________________________ >>> 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 >>> >> -- >> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >> | (518) 881-4417 >> ? >> > > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From elainejiang8 at gmail.com Thu Jul 20 13:31:17 2017 From: elainejiang8 at gmail.com (Elaine Jiang) Date: Thu, 20 Jul 2017 13:31:17 -0400 Subject: [vtkusers] Using vtkExternalOpenGLCamera In-Reply-To: References: <1500472740832-5744015.post@n5.nabble.com> Message-ID: Hi Sankhesh, Here's my initialization function and my render function. The external camera set up is highlighted. *vtkNew externalVTKWidget;* *vtkSmartPointer ren = externalVTKWidget->AddRenderer();* *static int windowId = -1;* *static int windowH = 800;* *static int windowW = 800;* *vtkSmartPointer actors[7];* *vtkNew transform;* *int press_x, press_y;* *int release_x, release_y;* *float x_angle = 0.0;* *float y_angle = 0.0;* *float scale_size = 1;* *int xform_mode = 0;* *#define XFORM_NONE 0* *#define XFORM_ROTATE 1* *#define XFORM_SCALE 2* *void initialize() {* *vtkNew renWin;* * externalVTKWidget->SetRenderWindow(renWin.GetPointer());* *std::string files[7] = {"../data/newsi-ascii.vtk", "../data/newjets-ascii.vtk", "../data/fekcorr-ascii.vtk", "../data/newar-ascii.vtk", "../data/newhetg-ascii.vtk", "../data/newopt-ascii.vtk", "../data/newsi-ascii.vtk"};* * for(int i = 0; i < 7; i++) {* * vtkSmartPointer reader =* * vtkSmartPointer::New();* * reader->SetFileName(files[i].c_str());* * reader->Update();* * vtkSmartPointer inputPolyData = reader->GetOutput();* * vtkSmartPointer clean =* * vtkSmartPointer::New();* * clean->SetInputData(inputPolyData);* // Generate normals *vtkSmartPointer normals =* * vtkSmartPointer::New();* * normals->SetInputConnection(clean->GetOutputPort());* * normals->SplittingOff();* *vtkSmartPointer mapper =* * vtkSmartPointer::New();* * mapper->SetInputConnection(normals->GetOutputPort());* *vtkSmartPointer actor =* * vtkSmartPointer::New();* * actor->SetMapper(mapper);* * actor->GetProperty()->SetInterpolationToFlat();* * ren->AddActor(actor);* * actors[i] = actor;* * }* *ren->SetBackground(0, 0, 0);* * ren->MakeCamera();* * ren->ResetCamera();* * renWin->AddRenderer(ren);* *}* // Render function *void display() {* // Enable depth testing. Demonstrates OpenGL context being managed by external // application i.e. GLUT in this case. *glEnable(GL_DEPTH_TEST);* // Buffers being managed by external application i.e. GLUT in this case. *glClearColor(0.0f, 0.0f, 0.0f, 1.0f);* // Set background color to black and opaque *glClearDepth(1.0f);* *glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);* // Clear the color buffer *glFlush();* // Render now *glEnable(GL_LIGHTING);* * glEnable(GL_LIGHT0);* *GLfloat diffuse[] = {1.0f, 1.0f, 1.0f, 1.0f};* * glLightfv(GL_LIGHT0, GL_DIFFUSE, diffuse);* * GLfloat specular[] = {0.5f, 0.0f, 0.0f, 1.0f};* * glLightfv(GL_LIGHT0, GL_SPECULAR, specular);* * GLfloat ambient[] = {1.0f, 1.0f, 0.2f, 1.0f};* * glLightfv(GL_LIGHT0, GL_AMBIENT, ambient);* *vtkExternalOpenGLCamera *camera = (vtkExternalOpenGLCamera *)ren->GetActiveCamera();* * camera->SetPosition(0,0,-100);* * camera->SetFocalPoint(0,0,0); * * camera->SetViewUp(0,1,0); * *for(int i = 0; i < 7; i++) {* * // transpose - vtk* * actors[i]->SetOrientation(0,0,0);* * actors[i]->RotateX(y_angle);* * actors[i]->RotateY(x_angle);* * actors[i]->SetScale(scale_size);* * // transpose - opengl* * double f[16];* * actors[i]->GetMatrix(f);* * // transpose* * double g[16];* * g[0] = f[0]; g[1] = f[4]; g[2] = f[8]; g[3] = f[12];* * g[4] = f[1]; g[5] = f[5]; g[6] = f[9]; g[7] = f[13];* * g[8] = f[2]; g[9] = f[6]; g[10]= f[10];g[11]= f[14];* * g[12]= f[3]; g[13]= f[7]; g[14]= f[11];g[15]= f[15];* * glMultMatrixd(g); // multiply current matrix with specified matrix* * }* *externalVTKWidget->GetRenderWindow()->Render();* * glutSwapBuffers();* *}* Thanks, Elaine On Thu, Jul 20, 2017 at 1:11 PM, Sankhesh Jhaveri < sankhesh.jhaveri at kitware.com> wrote: > Hi Elaine, > > You shouldn?t have to set that flag for using the matrices set on the > external camera. Could you share some sample code that doesn?t work? > > Thanks, > Sankhesh > ? > > On Thu, Jul 20, 2017 at 11:38 AM Elaine Jiang > wrote: > >> Hi Sankhesh, >> >> I've tried setting the camera and focal point parameters without using >> SetProjectionMatrix() and SetModelViewTransformMatrix(), and I've also >> tried just calling SetProjectionMatrix() and SetModelViewTransformMatrix() >> by themselves. Neither approach seemed to have an effect on the scene. I >> was looking through the documentation and was wondering if I need to use >> the function vtkCamera::vtkSetUseExplicitProjectionTransformMatrix(bool) >> to solve the problem? >> >> Thanks, >> Elaine >> >> On Thu, Jul 20, 2017 at 11:12 AM, Sankhesh Jhaveri < >> sankhesh.jhaveri at kitware.com> wrote: >> >>> Hi, >>> >>> Could you please provide more details on how you?re trying to set the >>> camera parameters? >>> The way the external camera works is that it ignores the camera position >>> and focal point parameters if the projection and model view matrices are >>> set explicitly using vtkExternalOpenGLCamera::SetProjectionMatrix() and >>> vtkExternalOpenGLCamera::SetModelViewTransformMatrix() >>> >>> Thanks, >>> Sankhesh >>> ? >>> >>> On Wed, Jul 19, 2017 at 9:59 AM elainejiang8 >>> wrote: >>> >>>> Hi everyone! >>>> >>>> I'm building a program that uses the externalVTKWidget to volume render >>>> an >>>> object in an OpenGL context. Right now, I'm calling >>>> >>>> *ren->GetActiveCamera(); >>>> * >>>> >>>> (where ren is a vtkExternalOpenGLRenderWindow instance) in my render >>>> function so I can control the position and focal point of the camera. >>>> However, I'm unable to get the camera to actually have any effect on the >>>> scene. The documentation for vtkExternalOpenGLCamera is rather slim, >>>> and I >>>> can't find any similar examples, so I am a bit stuck on this issue. >>>> >>>> Does anyone have any insight into how I could approach this problem? >>>> Thanks >>>> in advance! >>>> >>>> Elaine >>>> >>>> >>>> >>>> -- >>>> View this message in context: http://vtk.1045678.n5.nabble.com/Using- >>>> vtkExternalOpenGLCamera-tp5744015.html >>>> Sent from the VTK - Users mailing list archive at Nabble.com. >>>> _______________________________________________ >>>> 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 >>>> >>> -- >>> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >>> | (518) 881-4417 >>> ? >>> >> >> -- > Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware > | (518) 881-4417 > ? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankhesh.jhaveri at kitware.com Thu Jul 20 14:00:51 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 20 Jul 2017 18:00:51 +0000 Subject: [vtkusers] Using vtkExternalOpenGLCamera In-Reply-To: References: <1500472740832-5744015.post@n5.nabble.com> Message-ID: Hi Elaine, I didn?t see anything obvious in your sample code so decided to look more closely at the external renderer implementation. Its been a while since I looked at that code and my memory was rusty. You don?t need the external renderer if you are driving the OpenGL scene via VTK. Think of the external renderer as glue code that synchronizes the external OpenGL scene with VTK. It makes sure that the camera used is an external camera and overrides the camera parameters with what it finds in the external OpenGL scene. You need it in cases where something else is controlling the OpenGL camera and you?d like the VTK scene to be up-to-date as well; e.g. virtual reality systems where the main application updates OpenGL camera parameters. In your case, you can simply instantiate a vtkRenderer and set it on the vtkExternalOpenGLRenderWindow via vtkRenderWindow::AddRenderer(vtkRenderer* ren). The rest of the code should work as expected - except that the active camera would be of type vtkOpenGLCamera instead of vtkExternalOpenGLCamera. Hope that helps. Sankhesh ? On Thu, Jul 20, 2017 at 1:31 PM Elaine Jiang wrote: > Hi Sankhesh, > > Here's my initialization function and my render function. The external > camera set up is highlighted. > > *vtkNew externalVTKWidget;* > *vtkSmartPointer ren = externalVTKWidget->AddRenderer();* > *static int windowId = -1;* > *static int windowH = 800;* > *static int windowW = 800;* > *vtkSmartPointer actors[7];* > > *vtkNew transform;* > *int press_x, press_y;* > *int release_x, release_y;* > *float x_angle = 0.0;* > *float y_angle = 0.0;* > *float scale_size = 1;* > *int xform_mode = 0;* > *#define XFORM_NONE 0* > *#define XFORM_ROTATE 1* > *#define XFORM_SCALE 2* > > > *void initialize() {* > *vtkNew renWin;* > * externalVTKWidget->SetRenderWindow(renWin.GetPointer());* > > *std::string files[7] = {"../data/newsi-ascii.vtk", > "../data/newjets-ascii.vtk", "../data/fekcorr-ascii.vtk", > "../data/newar-ascii.vtk", "../data/newhetg-ascii.vtk", > "../data/newopt-ascii.vtk", "../data/newsi-ascii.vtk"};* > > * for(int i = 0; i < 7; i++) {* > * vtkSmartPointer reader =* > * vtkSmartPointer::New();* > * reader->SetFileName(files[i].c_str());* > * reader->Update();* > * vtkSmartPointer inputPolyData = reader->GetOutput();* > > * vtkSmartPointer clean =* > * vtkSmartPointer::New();* > * clean->SetInputData(inputPolyData);* > > // Generate normals > *vtkSmartPointer normals =* > * vtkSmartPointer::New();* > * normals->SetInputConnection(clean->GetOutputPort());* > * normals->SplittingOff();* > > > *vtkSmartPointer mapper =* > * vtkSmartPointer::New();* > * mapper->SetInputConnection(normals->GetOutputPort());* > > *vtkSmartPointer actor =* > * vtkSmartPointer::New();* > * actor->SetMapper(mapper);* > * actor->GetProperty()->SetInterpolationToFlat();* > > * ren->AddActor(actor);* > * actors[i] = actor;* > * }* > > *ren->SetBackground(0, 0, 0);* > * ren->MakeCamera();* > * ren->ResetCamera();* > * renWin->AddRenderer(ren);* > *}* > > // Render function > *void display() {* > // Enable depth testing. Demonstrates OpenGL context being managed by > external > // application i.e. GLUT in this case. > *glEnable(GL_DEPTH_TEST);* > > // Buffers being managed by external application i.e. GLUT in this > case. > *glClearColor(0.0f, 0.0f, 0.0f, 1.0f);* // Set background color to > black and opaque > *glClearDepth(1.0f);* > *glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);* // Clear the > color buffer > > *glFlush();* // Render now > > *glEnable(GL_LIGHTING);* > * glEnable(GL_LIGHT0);* > > *GLfloat diffuse[] = {1.0f, 1.0f, 1.0f, 1.0f};* > * glLightfv(GL_LIGHT0, GL_DIFFUSE, diffuse);* > * GLfloat specular[] = {0.5f, 0.0f, 0.0f, 1.0f};* > * glLightfv(GL_LIGHT0, GL_SPECULAR, specular);* > * GLfloat ambient[] = {1.0f, 1.0f, 0.2f, 1.0f};* > * glLightfv(GL_LIGHT0, GL_AMBIENT, ambient);* > > > *vtkExternalOpenGLCamera *camera = (vtkExternalOpenGLCamera > *)ren->GetActiveCamera();* > * camera->SetPosition(0,0,-100);* > * camera->SetFocalPoint(0,0,0); * > * camera->SetViewUp(0,1,0); * > > > *for(int i = 0; i < 7; i++) {* > * // transpose - vtk* > * actors[i]->SetOrientation(0,0,0);* > * actors[i]->RotateX(y_angle);* > * actors[i]->RotateY(x_angle);* > * actors[i]->SetScale(scale_size);* > > * // transpose - opengl* > * double f[16];* > * actors[i]->GetMatrix(f);* > > * // transpose* > * double g[16];* > * g[0] = f[0]; g[1] = f[4]; g[2] = f[8]; g[3] = f[12];* > * g[4] = f[1]; g[5] = f[5]; g[6] = f[9]; g[7] = f[13];* > * g[8] = f[2]; g[9] = f[6]; g[10]= f[10];g[11]= f[14];* > * g[12]= f[3]; g[13]= f[7]; g[14]= f[11];g[15]= f[15];* > * glMultMatrixd(g); // multiply current matrix with specified > matrix* > * }* > > *externalVTKWidget->GetRenderWindow()->Render();* > * glutSwapBuffers();* > *}* > > Thanks, > Elaine > > On Thu, Jul 20, 2017 at 1:11 PM, Sankhesh Jhaveri < > sankhesh.jhaveri at kitware.com> wrote: > >> Hi Elaine, >> >> You shouldn?t have to set that flag for using the matrices set on the >> external camera. Could you share some sample code that doesn?t work? >> >> Thanks, >> Sankhesh >> ? >> >> On Thu, Jul 20, 2017 at 11:38 AM Elaine Jiang >> wrote: >> >>> Hi Sankhesh, >>> >>> I've tried setting the camera and focal point parameters without using >>> SetProjectionMatrix() and SetModelViewTransformMatrix(), and I've also >>> tried just calling SetProjectionMatrix() and SetModelViewTransformMatrix() >>> by themselves. Neither approach seemed to have an effect on the scene. I >>> was looking through the documentation and was wondering if I need to use >>> the function vtkCamera::vtkSetUseExplicitProjectionTransformMatrix(bool) to >>> solve the problem? >>> >>> Thanks, >>> Elaine >>> >>> On Thu, Jul 20, 2017 at 11:12 AM, Sankhesh Jhaveri < >>> sankhesh.jhaveri at kitware.com> wrote: >>> >>>> Hi, >>>> >>>> Could you please provide more details on how you?re trying to set the >>>> camera parameters? >>>> The way the external camera works is that it ignores the camera >>>> position and focal point parameters if the projection and model view >>>> matrices are set explicitly using >>>> vtkExternalOpenGLCamera::SetProjectionMatrix() and >>>> vtkExternalOpenGLCamera::SetModelViewTransformMatrix() >>>> >>>> Thanks, >>>> Sankhesh >>>> ? >>>> >>>> On Wed, Jul 19, 2017 at 9:59 AM elainejiang8 >>>> wrote: >>>> >>>>> Hi everyone! >>>>> >>>>> I'm building a program that uses the externalVTKWidget to volume >>>>> render an >>>>> object in an OpenGL context. Right now, I'm calling >>>>> >>>>> *ren->GetActiveCamera(); >>>>> * >>>>> >>>>> (where ren is a vtkExternalOpenGLRenderWindow instance) in my render >>>>> function so I can control the position and focal point of the camera. >>>>> However, I'm unable to get the camera to actually have any effect on >>>>> the >>>>> scene. The documentation for vtkExternalOpenGLCamera is rather slim, >>>>> and I >>>>> can't find any similar examples, so I am a bit stuck on this issue. >>>>> >>>>> Does anyone have any insight into how I could approach this problem? >>>>> Thanks >>>>> in advance! >>>>> >>>>> Elaine >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://vtk.1045678.n5.nabble.com/Using-vtkExternalOpenGLCamera-tp5744015.html >>>>> Sent from the VTK - Users mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> 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 >>>>> >>>> -- >>>> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >>>> | (518) 881-4417 >>>> ? >>>> >>> >>> -- >> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >> | (518) 881-4417 >> ? >> > > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikewithascarf at yahoo.com Thu Jul 20 14:00:34 2017 From: mikewithascarf at yahoo.com (Mike Withascarf) Date: Thu, 20 Jul 2017 18:00:34 +0000 (UTC) Subject: [vtkusers] vtkImageBlend output alpha In-Reply-To: References: <1279142850.537349.1500482945623.ref@mail.yahoo.com> <1279142850.537349.1500482945623@mail.yahoo.com> Message-ID: <1035267085.1434878.1500573634428@mail.yahoo.com> Thanks, that's the workaround I'm using for the moment. Mike From: David Gobbi To: Mike Withascarf Cc: "vtkusers at vtk.org" Sent: Thursday, July 20, 2017 8:33 AM Subject: Re: [vtkusers] vtkImageBlend output alpha Hi Mike, There is no way to change this behavior for vtkImageBlend.? One solution is to use a dummy image as input 0 (same dimensions as your first image, but with RGBA set to 0,0,0,1 for all pixels), and then add your two images as inputs 1 and 2. ?- David? On Wed, Jul 19, 2017 at 10:49 AM, Mike Withascarf via vtkusers wrote: Hi, I'm using vtkImageBlend to blend two?vtkImageMapToColors. Right now if I change the opacity map of the first vtkImageMapToColors (via lookup table), it adjusts the entire alpha of the output (so for example hiding the first one hides both of them). Is there a way to prevent vtkImageBlend from assigning the opacity of the first element to the output? I've tried using the "compound" blending mode in case that would help, but the screen is blank then. Any help would be great! This is a simplified version of the code I'm using: vtkSmartPointer imapper1 = vtkSmartPointer::New();imapper1->SetLookupTable(lut1) ;imapper1->PassAlphaToOutputOn( );imapper1->SetInputData(image1) ;imapper1->Update(); vtkSmartPointer imapper2 = vtkSmartPointer::New();imapper2->SetLookupTable(lut2) ;imapper2->PassAlphaToOutputOn( );imapper2->SetInputData(image2) ;imapper2->Update(); vtkSmartPointer blend = vtkSmartPointer ::New();blend->AddInputConnection(imap per1->GetOutputPort());blend->SetOpacity(0, 1.0);blend->AddInputConnection(imap per2->GetOutputPort());blend->SetOpacity(1, 1.0); // If I now render and adjust lut1, it affects the output of blend so the imapper2 image gets affected Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From xoviat at tamu.edu Thu Jul 20 14:15:53 2017 From: xoviat at tamu.edu (Geoffrey Garner) Date: Thu, 20 Jul 2017 13:15:53 -0500 Subject: [vtkusers] (no subject) In-Reply-To: <5970cb67.8fcfca0a.18289.313f@mx.google.com> References: <59704efa.482cca0a.52c69.00b4@mx.google.com> <5970cb67.8fcfca0a.18289.313f@mx.google.com> Message-ID: <5970f359.54e2ca0a.1d73c.135e@mx.google.com> After some additional configuration, I now receive the following. However, the OpenVR directory is still not included in the build. Regards, Geoffrey From: Geoffrey Garner Sent: Thursday, July 20, 2017 10:25 AM To: Ken Martin Cc: vtkusers at vtk.org Subject: RE: [vtkusers] (no subject) Is there any way that I could get some message out about why it is skipping OpenVR rather than silently skipping it? Thanks Geoffrey From: Ken Martin Sent: Thursday, July 20, 2017 8:54 AM To: Geoffrey Garner Cc: vtkusers at vtk.org Subject: Re: [vtkusers] (no subject) "Yes, I have SDL2 and OpenVR from vcpkg." Maybe that is the issue?? I am building off of a git clone of OpenVR, maybe the directory structure is different and the CMake code is only handing the source code structure. Could be a similar issue for SDL2. On Thu, Jul 20, 2017 at 2:34 AM, Geoffrey Garner wrote: All: ? After multiple attempts, I have not been able to compile VTK with OpenVR. With the project directory set to the OpenVR directory, I receive the following output. This is expected because vtkObjectFactory is part of the main project. ? ? Found OpenVR: C:/Users/Geoffrey/vcpkg/installed/x64-windows/include CMake Error at CMakeLists.txt:42 (include): include could not find load file: vtkObjectFactory CMake Error at CMakeLists.txt:43 (vtk_add_override): Unknown CMake command "vtk_add_override". CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.9) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. Configuring incomplete, errors occurred! See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/CMakeFiles/CMakeOutput.log". See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/CMakeFiles/CMakeError.log". ? ? However, what is not expected is the following when configuring the main project. There is no OpenVR folder in the build directory and no explanation of why. Yes, I have SDL2 and OpenVR from vcpkg. ? Group StandAlone modules: vtkChartsCore;vtkCommonComputationalGeometry;vtkCommonCore;vtkCommonDataModel;vtkCommonExecutionModel;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkDomainsChemistry;vtkFiltersAMR;vtkFiltersCore;vtkFiltersExtraction;vtkFiltersFlowPaths;vtkFiltersGeneral;vtkFiltersGeneric;vtkFiltersGeometry;vtkFiltersHybrid;vtkFiltersHyperTree;vtkFiltersImaging;vtkFiltersModeling;vtkFiltersParallel;vtkFiltersParallelImaging;vtkFiltersPoints;vtkFiltersProgrammable;vtkFiltersSMP;vtkFiltersSelection;vtkFiltersSources;vtkFiltersStatistics;vtkFiltersTexture;vtkFiltersTopology;vtkFiltersVerdict;vtkIOAMR;vtkIOCore;vtkIOEnSight;vtkIOExodus;vtkIOGeometry;vtkIOImage;vtkIOImport;vtkIOInfovis;vtkIOLSDyna;vtkIOLegacy;vtkIOMINC;vtkIOMovie;vtkIONetCDF;vtkIOPLY;vtkIOParallel;vtkIOParallelXML;vtkIOSQL;vtkIOTecplotTable;vtkIOVideo;vtkIOXML;vtkIOXMLParser;vtkImagingColor;vtkImagingCore;vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInfovisCore;vtkInfovisLayout;vtkParallelCore Group Imaging modules: vtkFiltersImaging;vtkImagingColor;vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInteractionImage;vtkRenderingImage Group MPI modules: vtkFiltersParallelGeometry;vtkFiltersParallelMPI;vtkIOMPIImage;vtkIOMPIParallel;vtkIOParallelNetCDF;vtkParallelMPI Group Qt modules: vtkGUISupportQt;vtkGUISupportQtSQL;vtkRenderingQt;vtkViewsQt Group Rendering modules: vtkGeovisCore;vtkIOExport;vtkInteractionImage;vtkInteractionStyle;vtkInteractionWidgets;vtkRenderingAnnotation;vtkRenderingContext2D;vtkRenderingCore;vtkRenderingFreeType;vtkRenderingImage;vtkRenderingLOD;vtkRenderingLabel;vtkRenderingVolume;vtkViewsContext2D;vtkViewsCore;vtkViewsInfovis Group Tk modules: vtkRenderingTk Group Views modules: vtkViewsContext2D;vtkViewsGeovis Group Web modules: vtkWebCore;vtkWebPython;vtkWebGLExporter Backend OpenGL2 modules: vtkDomainsChemistryOpenGL2;vtkIOExportOpenGL2;vtkImagingOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingGL2PSOpenGL2;vtkRenderingLICOpenGL2;vtkRenderingOculus;vtkRenderingOpenGL2;vtkRenderingOpenVR;vtkRenderingVolumeOpenGL2 Enabling modules for OpenGL2. Backend OpenGL modules: vtkIOExportOpenGL;vtkRenderingContextOpenGL;vtkRenderingGL2PS;vtkRenderingLIC;vtkRenderingOpenGL;vtkRenderingVolumeOpenGL Disable test module vtkFiltersParallel-Test-Cxx since required modules are not enabled: vtkFiltersParallelMPI;vtkParallelMPI;vtkRenderingParallel Disable test module vtkGeovisCore-Test-Cxx since required modules are not enabled: vtkViewsGeovis Disable test module vtkIOParallel-Test-Cxx since required modules are not enabled: vtkParallelMPI;vtkRenderingParallel Enabled 185 modules: * vtkChartsCore, needed by 6 modules: VTK_Group_StandAlone vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkViewsInfovis * vtkCommonColor, needed by 6 modules: vtkChartsCore vtkCommonColor-Test-Cxx vtkFiltersModeling-Test-Cxx vtkIOExport-Test-Cxx vtkRenderingCore vtkViewsInfovis * vtkCommonComputationalGeometry, needed by 8 modules: VTK_Group_StandAlone vtkCommonComputationalGeometry-Test-Cxx vtkFiltersGeneral vtkFiltersSources vtkImagingStencil vtkInfovisLayout vtkInteractionWidgets vtkRenderingCore * vtkCommonCore, needed by 94 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor vtkCommonComputationalGeometry vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonExecutionModel vtkCommonMath vtkCommonMisc vtkCommonSystem vtkCommonTransforms vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOExport vtkIOExportOpenGL2 vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingHybrid-Test-Cxx vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionStyle vtkInteractionWidgets vtkParallelCore vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingCore vtkTestingGenericBridge vtkTestingRendering vtkViewsContext2D vtkViewsCore vtkViewsInfovis * vtkCommonDataModel, needed by 86 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor vtkCommonComputationalGeometry vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOExport vtkIOExportOpenGL2 vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingHybrid-Test-Cxx vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionStyle vtkInteractionWidgets vtkParallelCore vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingGenericBridge vtkTestingRendering vtkViewsCore vtkViewsInfovis * vtkCommonExecutionModel, needed by 76 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersImaging vtkFiltersModeling vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersPoints vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSelection vtkFiltersSources vtkFiltersStatistics vtkFiltersTexture vtkFiltersTopology vtkFiltersVerdict vtkGeovisCore vtkIOAMR vtkIOCore vtkIOEnSight vtkIOExodus vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIOMovie vtkIONetCDF vtkIONetCDF-Test-Cxx vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkImagingColor vtkImagingCore vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingMath vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInfovisCore vtkInfovisLayout vtkInteractionImage vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingCore vtkRenderingFreeType vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkTestingRendering vtkViewsCore vtkViewsInfovis * vtkCommonMath, needed by 29 modules: vtkCommonDataModel vtkCommonMath-Test-Cxx vtkCommonMisc vtkCommonTransforms vtkDomainsChemistryOpenGL2 vtkFiltersAMR vtkFiltersCore vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersSMP vtkIOExport vtkIOImage vtkIOMINC vtkImagingCore vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 * vtkCommonMisc, needed by 27 modules: VTK_Group_StandAlone vtkCommonDataModel vtkCommonExecutionModel vtkCommonExecutionModel vtkCommonMisc-Test-Cxx vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersSMP vtkFiltersStatistics vtkIOCore vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLegacy vtkIOMINC vtkIOMovie vtkIOPLY vtkIOParallel vtkIOParallelXML vtkIOXML vtkRenderingVolume vtkTestingGenericBridge * vtkCommonSystem, needed by 34 modules: VTK_Group_StandAlone vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonExecutionModel vtkCommonMath-Test-Cxx vtkCommonSystem-Test-Cxx vtkFiltersAMR vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHyperTree vtkFiltersImaging vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersSMP vtkGeovisCore vtkIOAMR vtkIOGeometry vtkIOImage vtkIOMovie vtkIOParallel vtkIOVideo vtkIOXML vtkImagingColor vtkInfovisLayout vtkInteractionWidgets vtkParallelCore vtkRenderingCore vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering * vtkCommonTransforms, needed by 37 modules: VTK_Group_StandAlone vtkChartsCore vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonMath-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry vtkFiltersCore vtkFiltersGeneral vtkFiltersGeneric vtkFiltersHybrid vtkFiltersModeling vtkFiltersParallel vtkFiltersProgrammable vtkFiltersSMP vtkFiltersSources vtkFiltersTexture vtkGeovisCore vtkIOExport vtkIOGeometry vtkIOImage vtkIOImport vtkIOMINC vtkImagingCore vtkInfovisLayout vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingImage vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkDICOMParser, needed by vtkIOImage. * vtkDomainsChemistry, needed by 4 modules: VTK_Group_StandAlone vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2 vtkDomainsChemistryOpenGL2 * vtkDomainsChemistryOpenGL2, needed by 4 modules: vtkDomainsChemistry vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx * vtkFiltersAMR, needed by 6 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkIOAMR vtkIOLegacy-Test-Cxx vtkIOXML-Test-Cxx * vtkFiltersCore, needed by 28 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkFiltersAMR vtkFiltersCore-Test-Cxx vtkFiltersExtraction vtkFiltersFlowPaths vtkFiltersGeneral vtkFiltersGeneric vtkFiltersGeometry vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersParallel vtkFiltersSMP vtkFiltersSources vtkGeovisCore vtkIOExodus vtkIOImport vtkIOParallel vtkIOXML-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingCore vtkRenderingLOD vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkFiltersExtraction, needed by 9 modules: VTK_Group_StandAlone vtkFiltersExtraction-Test-Cxx vtkFiltersParallel vtkFiltersParallelImaging vtkFiltersSelection-Test-Cxx vtkIOParallel vtkInfovisCore vtkInteractionStyle vtkViewsInfovis * vtkFiltersFlowPaths, needed by 4 modules: VTK_Group_StandAlone vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkFiltersGeneral, needed by 27 modules: VTK_Group_StandAlone vtkChartsCore vtkDomainsChemistry vtkFiltersCore-Test-Cxx vtkFiltersExtraction vtkFiltersGeneral-Test-Cxx vtkFiltersHybrid vtkFiltersHyperTree vtkFiltersModeling vtkFiltersParallel vtkFiltersPoints-Test-Cxx vtkFiltersSMP vtkFiltersSources vtkFiltersTexture vtkGeovisCore vtkImagingCore-Test-Cxx vtkInfovisCore vtkInfovisLayout vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingCore vtkRenderingFreeType vtkRenderingLabel vtkRenderingVolumeOpenGL2 vtkViewsCore vtkViewsInfovis * vtkFiltersGeneric, needed by 3 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersGeneric-Test-Cxx * vtkFiltersGeometry, needed by 8 modules: VTK_Group_StandAlone vtkFiltersFlowPaths vtkFiltersGeometry-Test-Cxx vtkFiltersParallel vtkIOExport vtkIOGeometry-Test-Cxx vtkRenderingCore vtkViewsInfovis * vtkFiltersHybrid, needed by 5 modules: VTK_Group_StandAlone vtkFiltersHybrid-Test-Cxx vtkIOMINC vtkImagingCore-Test-Cxx vtkInteractionWidgets * vtkFiltersHyperTree, needed by 3 modules: VTK_Group_StandAlone vtkFiltersHyperTree-Test-Cxx vtkIOXML-Test-Cxx * vtkFiltersImaging, needed by 4 modules: VTK_Group_StandAlone vtkFiltersFlowPaths-Test-Cxx vtkFiltersParallelImaging vtkViewsInfovis * vtkFiltersModeling, needed by 16 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersParallel vtkFiltersSources-Test-Cxx vtkImagingCore-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkInteractionWidgets-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkFiltersParallel, needed by 3 modules: VTK_Group_StandAlone vtkFiltersParallelImaging vtkIOParallel * vtkFiltersParallelImaging, needed by VTK_Group_StandAlone. * vtkFiltersPoints, needed by 2 modules: VTK_Group_StandAlone vtkFiltersPoints-Test-Cxx * vtkFiltersProgrammable, needed by 4 modules: VTK_Group_StandAlone vtkFiltersProgrammable-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingCore-Test-Cxx * vtkFiltersSMP, needed by 2 modules: VTK_Group_StandAlone vtkFiltersSMP-Test-Cxx * vtkFiltersSelection, needed by 3 modules: VTK_Group_StandAlone vtkFiltersSelection-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkFiltersSources, needed by 18 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkFiltersFlowPaths vtkFiltersGeneric vtkFiltersModeling vtkFiltersParallel vtkFiltersSources-Test-Cxx vtkIOImport vtkIOXML-Test-Cxx vtkInfovisLayout vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingCore vtkRenderingCore-Test-Cxx vtkRenderingVolumeOpenGL2 vtkViewsInfovis * vtkFiltersStatistics, needed by 6 modules: VTK_Group_StandAlone vtkFiltersExtraction vtkFiltersImaging vtkFiltersParallelImaging vtkFiltersStatistics-Test-Cxx vtkViewsInfovis * vtkFiltersTexture, needed by VTK_Group_StandAlone. * vtkFiltersTopology, needed by 2 modules: VTK_Group_StandAlone vtkFiltersTopology-Test-Cxx * vtkFiltersVerdict, needed by 3 modules: VTK_Group_StandAlone vtkFiltersSources-Test-Cxx vtkFiltersVerdict-Test-Cxx * vtkGeovisCore, needed by VTK_Group_Rendering. * vtkIOAMR, needed by 4 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkIOAMR-Test-Cxx vtkIOGeometry-Test-Cxx * vtkIOCore, needed by 16 modules: VTK_Group_StandAlone vtkCommonExecutionModel-Test-Cxx vtkFiltersFlowPaths vtkIOCore-Test-Cxx vtkIOExodus vtkIOExport vtkIOGeometry vtkIOInfovis vtkIOLegacy vtkIOMINC vtkIOPLY vtkIOParallel vtkIOSQL vtkIOTecplotTable vtkIOXML vtkIOXMLParser * vtkIOEnSight, needed by VTK_Group_StandAlone. * vtkIOExodus, needed by 6 modules: VTK_Group_StandAlone vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkIOExodus-Test-Cxx vtkRenderingCore-Test-Cxx * vtkIOExport, needed by 4 modules: VTK_Group_Rendering vtkIOExport-Test-Cxx vtkIOExportOpenGL2 vtkIOExportOpenGL2 * vtkIOExportOpenGL2, needed by 3 modules: vtkIOExport vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx * vtkIOGeometry, needed by 8 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOParallel vtkRenderingAnnotation-Test-Cxx * vtkIOImage, needed by 13 modules: VTK_Group_StandAlone vtkCommonColor-Test-Cxx vtkGeovisCore vtkIOExport vtkIOExport vtkIOImage-Test-Cxx vtkIOImport vtkIOMINC vtkIOPLY-Test-Cxx vtkIOParallel vtkImagingHybrid vtkRenderingVolume-Test-Cxx vtkTestingRendering * vtkIOImport, needed by 2 modules: VTK_Group_StandAlone vtkIOImport-Test-Cxx * vtkIOInfovis, needed by 6 modules: VTK_Group_StandAlone vtkChartsCore-Test-Cxx vtkIOInfovis-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkIOLSDyna, needed by 2 modules: VTK_Group_StandAlone vtkIOLSDyna-Test-Cxx * vtkIOLegacy, needed by 30 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkDomainsChemistry vtkDomainsChemistry-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersParallel vtkFiltersPoints-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersTopology-Test-Cxx vtkFiltersVerdict-Test-Cxx vtkIOGeometry vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOInfovis vtkIOLegacy-Test-Cxx vtkIOParallel vtkIOSQL-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkParallelCore vtkRenderingCore-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkIOMINC, needed by VTK_Group_StandAlone. * vtkIOMovie, needed by 2 modules: VTK_Group_StandAlone vtkIOMovie-Test-Cxx * vtkIONetCDF, needed by 3 modules: VTK_Group_StandAlone vtkIONetCDF-Test-Cxx vtkIOParallel * vtkIOPLY, needed by 3 modules: VTK_Group_StandAlone vtkIOPLY-Test-Cxx vtkRenderingOpenGL2-Test-Cxx * vtkIOParallel, needed by 6 modules: VTK_Group_StandAlone vtkFiltersSources-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx * vtkIOParallelXML, needed by 2 modules: VTK_Group_StandAlone vtkIOXML-Test-Cxx * vtkIOSQL, needed by 4 modules: VTK_Group_StandAlone vtkIOSQL-Test-Cxx vtkTestingIOSQL vtkViewsInfovis-Test-Cxx * vtkIOTecplotTable, needed by 2 modules: VTK_Group_StandAlone vtkIOTecplotTable-Test-Cxx * vtkIOVideo, needed by VTK_Group_StandAlone. * vtkIOXML, needed by 26 modules: VTK_Group_StandAlone vtkCommonDataModel-Test-Cxx vtkFiltersAMR vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersSMP-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkGeovisCore vtkIOAMR-Test-Cxx vtkIOImport-Test-Cxx vtkIOInfovis vtkIOParallelXML vtkIOXML-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingVolume vtkRenderingVolume-Test-Cxx * vtkIOXMLParser, needed by 6 modules: VTK_Group_StandAlone vtkDomainsChemistry vtkIOExodus vtkIOInfovis vtkIOLSDyna vtkIOXML * vtkImagingColor, needed by 4 modules: VTK_Group_StandAlone vtkInteractionImage vtkInteractionWidgets vtkRenderingAnnotation * vtkImagingCore, needed by 28 modules: VTK_Group_StandAlone vtkFiltersAMR-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersHybrid vtkFiltersHybrid-Test-Cxx vtkFiltersParallelImaging vtkFiltersPoints-Test-Cxx vtkFiltersSMP-Test-Cxx vtkGeovisCore vtkIOExport vtkIOExportOpenGL2 vtkIOMovie-Test-Cxx vtkImagingColor vtkImagingCore-Test-Cxx vtkImagingFourier vtkImagingGeneral vtkImagingHybrid vtkImagingMorphological vtkImagingSources vtkImagingStatistics vtkImagingStencil vtkInteractionImage vtkInteractionWidgets vtkRenderingContextOpenGL2 vtkRenderingImage vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering * vtkImagingFourier, needed by 2 modules: VTK_Group_StandAlone vtkFiltersStatistics * vtkImagingGeneral, needed by 9 modules: VTK_Group_StandAlone vtkFiltersImaging vtkFiltersParallelImaging vtkImagingCore-Test-Cxx vtkImagingMorphological vtkInteractionWidgets vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkImagingHybrid, needed by 5 modules: VTK_Group_StandAlone vtkImagingHybrid-Test-Cxx vtkInfovisLayout vtkInteractionWidgets vtkRenderingVolume-Test-Cxx * vtkImagingMath, needed by 5 modules: VTK_Group_StandAlone vtkFiltersGeneral-Test-Cxx vtkIOImage-Test-Cxx vtkImagingCore-Test-Cxx vtkRenderingVolumeOpenGL2 * vtkImagingMorphological, needed by 2 modules: VTK_Group_StandAlone vtkImagingMorphological-Test-Cxx * vtkImagingSources, needed by 15 modules: VTK_Group_StandAlone vtkFiltersHybrid vtkGeovisCore vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOMovie-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingGeneral vtkImagingMorphological vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkImagingStatistics, needed by 2 modules: VTK_Group_StandAlone vtkImagingCore-Test-Cxx * vtkImagingStencil, needed by 5 modules: VTK_Group_StandAlone vtkFiltersHybrid-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkInfovisCore, needed by 8 modules: VTK_Group_StandAlone vtkChartsCore vtkGeovisCore vtkIOInfovis vtkIOXML-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout vtkViewsInfovis * vtkInfovisLayout, needed by 6 modules: VTK_Group_StandAlone vtkGeovisCore vtkIOInfovis-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkViewsInfovis * vtkInteractionImage, needed by 6 modules: VTK_Group_Rendering vtkIOExport-Test-Cxx vtkIOImage-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInteractionWidgets-Test-Cxx * vtkInteractionStyle, needed by 46 modules: VTK_Group_Rendering vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkGeovisCore vtkIOExodus-Test-Cxx vtkIOExport-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkInteractionImage vtkInteractionWidgets vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingGL2PSOpenGL2-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis * vtkInteractionWidgets, needed by 6 modules: VTK_Group_Rendering vtkGeovisCore vtkInteractionImage vtkInteractionWidgets-Test-Cxx vtkViewsCore vtkViewsInfovis * vtkMetaIO, needed by vtkIOImage. * vtkParallelCore, needed by 8 modules: VTK_Group_StandAlone vtkFiltersAMR vtkFiltersParallel vtkFiltersParallelImaging vtkIOAMR vtkIOParallel vtkIOParallelXML vtkParallelCore-Test-Cxx * vtkRenderingAnnotation, needed by 9 modules: VTK_Group_Rendering vtkFiltersGeneral-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersSelection-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets vtkRenderingAnnotation-Test-Cxx vtkRenderingCore-Test-Cxx vtkViewsInfovis * vtkRenderingContext2D, needed by 9 modules: VTK_Group_Rendering vtkChartsCore vtkFiltersPoints-Test-Cxx vtkIOExport vtkRenderingContext2D-Test-Cxx vtkRenderingContextOpenGL2 vtkRenderingContextOpenGL2 vtkViewsContext2D vtkViewsInfovis * vtkRenderingContextOpenGL2, needed by 9 modules: vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkIOImage-Test-Cxx vtkRenderingContext2D vtkRenderingContext2D-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkRenderingCore, needed by 34 modules: VTK_Group_Rendering vtkChartsCore vtkDomainsChemistry vtkDomainsChemistryOpenGL2 vtkFiltersHybrid vtkFiltersParallel vtkGeovisCore vtkIOExport vtkIOExportOpenGL2 vtkIOImport vtkIOInfovis-Test-Cxx vtkIOMINC vtkInteractionImage vtkInteractionStyle vtkInteractionStyle vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore-Test-Cxx vtkRenderingFreeType vtkRenderingFreeType vtkRenderingGL2PSOpenGL2 vtkRenderingImage vtkRenderingLOD vtkRenderingLabel vtkRenderingOpenGL2 vtkRenderingOpenGL2 vtkRenderingVolume vtkRenderingVolumeOpenGL2 vtkTestingRendering vtkViewsContext2D vtkViewsCore vtkViewsInfovis * vtkRenderingFreeType, needed by 11 modules: VTK_Group_Rendering vtkIOExport vtkInteractionWidgets vtkRenderingAnnotation vtkRenderingContext2D vtkRenderingContextOpenGL2 vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingLabel vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx * vtkRenderingGL2PSOpenGL2, needed by 3 modules: vtkIOExport vtkIOExportOpenGL2 vtkRenderingGL2PSOpenGL2-Test-Cxx * vtkRenderingImage, needed by 4 modules: VTK_Group_Rendering vtkImagingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingOpenGL2-Test-Cxx * vtkRenderingLOD, needed by 4 modules: VTK_Group_Rendering vtkInteractionWidgets-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingLOD-Test-Cxx * vtkRenderingLabel, needed by 7 modules: VTK_Group_Rendering vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkIOExport-Test-Cxx vtkInfovisLayout-Test-Cxx vtkRenderingLabel-Test-Cxx vtkViewsInfovis * vtkRenderingOpenGL2, needed by 47 modules: vtkCommonColor-Test-Cxx vtkCommonComputationalGeometry-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2 vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkIOExodus-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImport-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkParallelCore-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingContextOpenGL2 vtkRenderingCore vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingGL2PSOpenGL2 vtkRenderingGL2PSOpenGL2 vtkRenderingGL2PSOpenGL2 vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolumeOpenGL2 * vtkRenderingVolume, needed by 5 modules: VTK_Group_Rendering vtkInteractionWidgets vtkRenderingVolume-Test-Cxx vtkRenderingVolumeOpenGL2 vtkRenderingVolumeOpenGL2 * vtkRenderingVolumeOpenGL2, needed by 6 modules: vtkFiltersCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkRenderingVolume vtkRenderingVolume-Test-Cxx * vtkTestingCore, needed by 33 modules: vtkChartsCore-Test-Cxx vtkCommonColor-Test-Cxx vtkCommonComputationalGeometry-Test-Cxx vtkCommonCore-Test-Cxx vtkCommonDataModel-Test-Cxx vtkCommonExecutionModel-Test-Cxx vtkCommonMath-Test-Cxx vtkCommonMisc-Test-Cxx vtkCommonSystem-Test-Cxx vtkCommonTransforms-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersAMR-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersSMP-Test-Cxx vtkFiltersSources-Test-Cxx vtkFiltersStatistics-Test-Cxx vtkFiltersVerdict-Test-Cxx vtkIOAMR-Test-Cxx vtkIOCore-Test-Cxx vtkIOImage-Test-Cxx vtkIOImage-Test-Cxx vtkIOMovie-Test-Cxx vtkIOSQL-Test-Cxx vtkIOTecplotTable-Test-Cxx vtkIOXML-Test-Cxx vtkImagingHybrid-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkTestingRendering * vtkTestingGenericBridge, needed by 2 modules: vtkCommonDataModel-Test-Cxx vtkFiltersGeneric-Test-Cxx * vtkTestingIOSQL, needed by vtkIOSQL-Test-Cxx. * vtkTestingRendering, needed by 51 modules: vtkChartsCore-Test-Cxx vtkCommonColor-Test-Cxx vtkCommonDataModel-Test-Cxx vtkDomainsChemistry-Test-Cxx vtkDomainsChemistryOpenGL2-Test-Cxx vtkFiltersAMR-Test-Cxx vtkFiltersCore-Test-Cxx vtkFiltersExtraction-Test-Cxx vtkFiltersFlowPaths-Test-Cxx vtkFiltersGeneral-Test-Cxx vtkFiltersGeneric-Test-Cxx vtkFiltersGeometry-Test-Cxx vtkFiltersHybrid-Test-Cxx vtkFiltersHyperTree-Test-Cxx vtkFiltersModeling-Test-Cxx vtkFiltersPoints-Test-Cxx vtkFiltersProgrammable-Test-Cxx vtkFiltersSelection-Test-Cxx vtkFiltersSources-Test-Cxx vtkFiltersTopology-Test-Cxx vtkIOAMR-Test-Cxx vtkIOExodus-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkIOGeometry-Test-Cxx vtkIOImage-Test-Cxx vtkIOImport-Test-Cxx vtkIOInfovis-Test-Cxx vtkIOLSDyna-Test-Cxx vtkIOLegacy-Test-Cxx vtkIONetCDF-Test-Cxx vtkIOPLY-Test-Cxx vtkIOXML-Test-Cxx vtkImagingCore-Test-Cxx vtkImagingHybrid-Test-Cxx vtkImagingMorphological-Test-Cxx vtkInfovisCore-Test-Cxx vtkInfovisLayout-Test-Cxx vtkInteractionWidgets-Test-Cxx vtkParallelCore-Test-Cxx vtkRenderingAnnotation-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkRenderingCore-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkRenderingGL2PSOpenGL2-Test-Cxx vtkRenderingImage-Test-Cxx vtkRenderingLOD-Test-Cxx vtkRenderingLabel-Test-Cxx vtkRenderingOpenGL2-Test-Cxx vtkRenderingVolume-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkUtilitiesEncodeString, needed by vtkRenderingOpenGL2. * vtkUtilitiesHashSource, needed by vtkParallelCore. * vtkViewsContext2D, needed by 8 modules: VTK_Group_Rendering vtkChartsCore-Test-Cxx vtkFiltersPoints-Test-Cxx vtkIOExport-Test-Cxx vtkIOExportOpenGL2-Test-Cxx vtkRenderingContext2D-Test-Cxx vtkRenderingFreeType-Test-Cxx vtkViewsInfovis-Test-Cxx * vtkViewsCore, needed by 4 modules: VTK_Group_Rendering vtkGeovisCore vtkViewsContext2D vtkViewsInfovis * vtkViewsInfovis, needed by 2 modules: VTK_Group_Rendering vtkViewsInfovis-Test-Cxx * vtkalglib, needed by vtkFiltersStatistics. * vtkexodusII, needed by 2 modules: vtkIOExodus vtkIOParallel * vtkexpat, needed by vtkIOXMLParser. * vtkfreetype, needed by vtkRenderingFreeType. * vtkgl2ps, needed by 2 modules: vtkIOExportOpenGL2 vtkRenderingGL2PSOpenGL2 * vtkglew, needed by 4 modules: vtkDomainsChemistryOpenGL2 vtkRenderingContextOpenGL2 vtkRenderingOpenGL2 vtkRenderingVolumeOpenGL2 * vtkhdf5, needed by 2 modules: vtkIOAMR vtknetcdf * vtkjpeg, needed by 2 modules: vtkIOImage vtktiff * vtkjsoncpp, needed by vtkIOParallel. * vtkkwiml, needed by 2 modules: vtkCommonCore vtkfreetype * vtklibharu, needed by vtkIOExport. * vtklibproj4, needed by vtkGeovisCore. * vtklibxml2, needed by vtkIOInfovis. * vtklz4, needed by vtkIOCore. * vtknetcdf, needed by 5 modules: vtkIOMINC vtkIONetCDF vtkIOParallel vtkexodusII vtknetcdfcpp * vtknetcdfcpp, needed by vtkIONetCDF. * vtkoggtheora, needed by vtkIOMovie. * vtkpng, needed by 3 modules: vtkIOImage vtkgl2ps vtklibharu * vtksqlite, needed by vtkIOSQL. * vtksys, needed by 33 modules: vtkChartsCore vtkCommonCore vtkCommonCore-Test-Cxx vtkCommonDataModel vtkCommonSystem vtkDICOMParser vtkDomainsChemistry vtkFiltersHybrid vtkIOAMR vtkIOCore vtkIOExodus vtkIOGeometry vtkIOImage vtkIOImport vtkIOInfovis vtkIOLSDyna vtkIOLegacy vtkIOMINC vtkIONetCDF vtkIOParallel vtkIOParallelXML vtkIOSQL vtkIOTecplotTable vtkIOVideo vtkIOXML vtkIOXMLParser vtkImagingFourier vtkParallelCore vtkRenderingCore vtkRenderingOpenGL2 vtkRenderingVolumeOpenGL2 vtkTestingRendering vtkUtilitiesHashSource * vtktiff, needed by vtkIOImage. * vtkverdict, needed by vtkFiltersVerdict. * vtkzlib, needed by 11 modules: vtkIOCore vtkIOGeometry vtkIOImage vtkMetaIO vtkfreetype vtkgl2ps vtkhdf5 vtklibharu vtklibxml2 vtkpng vtktiff 64 bit architecture detected size of void * is 8 Building tiff version 4.0.6 libtiff library version 5.2.4 CMAKE_HOST_SYSTEM_PROCESSOR set to AMD64 HOST_FILLORDER set to FILLORDER_MSB2LSB HOST_BIG_ENDIAN set to 0 HAVE_IEEEFP set to 1 HDF5: SOVERSION: 8.0.2 HDF5: Performing Other Test STDC_HEADERS - Success HDF5: Performing CXX Test OLD_HEADER_FILENAME - Failed HDF5: Performing CXX Test H5_NO_NAMESPACE - Failed HDF5: Performing CXX Test H5_NO_STD - Failed HDF5: Performing CXX Test BOOL_NOTDEFINED - Failed HDF5: Performing CXX Test NO_STATIC_CAST - Failed HDF5: Checking for InitOnceExecuteOnce: HDF5: Performing Test InitOnceExecuteOnce - Success HDF5: Performing Other Test INLINE_TEST_inline - Success HDF5: Performing Other Test INLINE_TEST___inline__ - Failed HDF5: Performing Other Test INLINE_TEST___inline - Success HDF5: checking IF converting from long double to integers is accurate... yes HDF5: checking IF accurately converting from integers to long double... yes HDF5: Checking IF accurately converting unsigned long to float values... yes HDF5: Checking IF accurately roundup converting floating-point to unsigned long long values... yes HDF5: Checking IF right maximum converting floating-point to unsigned long long values... yes HDF5: Checking IF correctly converting long double to unsigned int values... yes HDF5: Checking IF overflows normally converting floating-point to integer values... yes HDF5: Checking IF correctly converting long double to (unsigned) long long values... yes HDF5: Checking IF correctly converting (unsigned) long long to long double values... yes HDF5: Checking IF alignment restrictions are strictly enforced... yes HDF5: Filter ZLIB is ON ? Configuring PROJ: ? PROJ_VERSION = 4.9.2 PROJ_ABI_VERSION = 4_9 CMake Deprecation Warning at ThirdParty/libproj4/vtklibproj4/cmake/policies.cmake:2 (cmake_policy): The OLD behavior for policy CMP0022 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. Call Stack (most recent call first): ThirdParty/libproj4/vtklibproj4/CMakeLists.txt:43 (include) ? Configuring proj library: ? PROJ_CORE_TARGET = vtkproj4 PROJ_CORE_TARGET_OUTPUT_NAME = vtkproj4_4_9 PROJ_LIBRARIES = vtkproj4 Configuring done ? _______________________________________________ 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 -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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: 73671AD9C3BD48BFA91651495F5078E2.png Type: image/png Size: 98803 bytes Desc: not available URL: From ken.martin at kitware.com Thu Jul 20 14:19:54 2017 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 20 Jul 2017 14:19:54 -0400 Subject: [vtkusers] (no subject) In-Reply-To: <5970f359.54e2ca0a.1d73c.135e@mx.google.com> References: <59704efa.482cca0a.52c69.00b4@mx.google.com> <5970cb67.8fcfca0a.18289.313f@mx.google.com> <5970f359.54e2ca0a.1d73c.135e@mx.google.com> Message-ID: Here is what I have [image: Inline image 1] On Thu, Jul 20, 2017 at 2:15 PM, Geoffrey Garner wrote: > > > After some additional configuration, I now receive the following. However, > the OpenVR directory is still not included in the build. > > > > Regards, > > > > Geoffrey > > > > > > *From: *Geoffrey Garner > *Sent: *Thursday, July 20, 2017 10:25 AM > *To: *Ken Martin > *Cc: *vtkusers at vtk.org > *Subject: *RE: [vtkusers] (no subject) > > > > Is there any way that I could get some message out about why it is > skipping OpenVR rather than silently skipping it? > > > > Thanks > > > > > > Geoffrey > > > > *From: *Ken Martin > *Sent: *Thursday, July 20, 2017 8:54 AM > *To: *Geoffrey Garner > *Cc: *vtkusers at vtk.org > *Subject: *Re: [vtkusers] (no subject) > > > > "Yes, I have SDL2 and OpenVR from vcpkg." > > > > Maybe that is the issue? I am building off of a git clone of OpenVR, > maybe the directory structure is different and the CMake code is only > handing the source code structure. Could be a similar issue for SDL2. > > > > On Thu, Jul 20, 2017 at 2:34 AM, Geoffrey Garner wrote: > > All: > > > > After multiple attempts, I have not been able to compile VTK with OpenVR. > With the project directory set to the OpenVR directory, I receive the > following output. This is expected because vtkObjectFactory is part of the > main project. > > > > > > Found OpenVR: C:/Users/Geoffrey/vcpkg/installed/x64-windows/include > > CMake Error at CMakeLists.txt:42 (include): > include could not find load file: > > vtkObjectFactory > > CMake Error at CMakeLists.txt:43 (vtk_add_override): > Unknown CMake command "vtk_add_override". > > CMake Warning (dev) in CMakeLists.txt: > No cmake_minimum_required command is present. A line of code such as > > cmake_minimum_required(VERSION 3.9) > > should be added at the top of the file. The version specified may be lower > if you wish to support older CMake versions for this project. For more > information run "cmake --help-policy CMP0000". > This warning is for project developers. Use -Wno-dev to suppress it. > > Configuring incomplete, errors occurred! > > See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/ > CMakeFiles/CMakeOutput.log". > > See also "C:/Users/Geoffrey/workspace/VTK/Rendering/OpenVR/build/ > CMakeFiles/CMakeError.log". > > > > > > However, what is not expected is the following when configuring the main > project. There is no OpenVR folder in the build directory and no > explanation of why. Yes, I have SDL2 and OpenVR from vcpkg. > > > > Group StandAlone modules: vtkChartsCore;vtkCommonComputationalGeometry > ;vtkCommonCore;vtkCommonDataModel;vtkCommonExecutionModel; > vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkDomainsChemistry; > vtkFiltersAMR;vtkFiltersCore;vtkFiltersExtraction;vtkFiltersFlowPaths; > vtkFiltersGeneral;vtkFiltersGeneric;vtkFiltersGeometry;vtkFiltersHybrid; > vtkFiltersHyperTree;vtkFiltersImaging;vtkFiltersModeling; > vtkFiltersParallel;vtkFiltersParallelImaging;vtkFiltersPoints; > vtkFiltersProgrammable;vtkFiltersSMP;vtkFiltersSelection; > vtkFiltersSources;vtkFiltersStatistics;vtkFiltersTexture; > vtkFiltersTopology;vtkFiltersVerdict;vtkIOAMR;vtkIOCore;vtkIOEnSight; > vtkIOExodus;vtkIOGeometry;vtkIOImage;vtkIOImport;vtkIOInfovis;vtkIOLSDyna; > vtkIOLegacy;vtkIOMINC;vtkIOMovie;vtkIONetCDF;vtkIOPLY;vtkIOParallel; > vtkIOParallelXML;vtkIOSQL;vtkIOTecplotTable;vtkIOVideo; > vtkIOXML;vtkIOXMLParser;vtkImagingColor;vtkImagingCore;vtkImagingFourier; > vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath;vtkImagingMorphological; > vtkImagingSources;vtkImagingStatistics;vtkImagingStencil;vtkInfovisCore; > vtkInfovisLayout;vtkParallelCore > > Group Imaging modules: vtkFiltersImaging;vtkImagingColor; > vtkImagingFourier;vtkImagingGeneral;vtkImagingHybrid;vtkImagingMath; > vtkImagingMorphological;vtkImagingSources;vtkImagingStatistics; > vtkImagingStencil;vtkInteractionImage;vtkRenderingImage > > Group MPI modules: vtkFiltersParallelGeometry;vtkFiltersParallelMPI; > vtkIOMPIImage;vtkIOMPIParallel;vtkIOParallelNetCDF;vtkParallelMPI > > Group Qt modules: vtkGUISupportQt;vtkGUISupportQtSQL; > vtkRenderingQt;vtkViewsQt > > Group Rendering modules: vtkGeovisCore;vtkIOExport;vtkInteractionImage; > vtkInteractionStyle;vtkInteractionWidgets;vtkRenderingAnnotation; > vtkRenderingContext2D;vtkRenderingCore;vtkRenderingFreeType; > vtkRenderingImage;vtkRenderingLOD;vtkRenderingLabel;vtkRenderingVolume; > vtkViewsContext2D;vtkViewsCore;vtkViewsInfovis > > Group Tk modules: vtkRenderingTk > > Group Views modules: vtkViewsContext2D;vtkViewsGeovis > > Group Web modules: vtkWebCore;vtkWebPython;vtkWebGLExporter > > Backend OpenGL2 modules: vtkDomainsChemistryOpenGL2;vtkIOExportOpenGL2; > vtkImagingOpenGL2;vtkRenderingContextOpenGL2;vtkRenderingGL2PSOpenGL2; > vtkRenderingLICOpenGL2;vtkRenderingOculus;vtkRenderingOpenGL2; > vtkRenderingOpenVR;vtkRenderingVolumeOpenGL2 > > Enabling modules for OpenGL2. > > Backend OpenGL modules: vtkIOExportOpenGL;vtkRenderingContextOpenGL; > vtkRenderingGL2PS;vtkRenderingLIC;vtkRenderingOpenGL; > vtkRenderingVolumeOpenGL > > Disable test module vtkFiltersParallel-Test-Cxx since required modules are > not enabled: vtkFiltersParallelMPI;vtkParallelMPI;vtkRenderingParallel > > Disable test module vtkGeovisCore-Test-Cxx since required modules are not > enabled: vtkViewsGeovis > > Disable test module vtkIOParallel-Test-Cxx since required modules are not > enabled: vtkParallelMPI;vtkRenderingParallel > > Enabled 185 modules: > > * vtkChartsCore, needed by 6 modules: > > VTK_Group_StandAlone > > vtkChartsCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkRenderingContext2D-Test-Cxx > > vtkViewsInfovis > > * vtkCommonColor, needed by 6 modules: > > vtkChartsCore > > vtkCommonColor-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkRenderingCore > > vtkViewsInfovis > > * vtkCommonComputationalGeometry, needed by 8 modules: > > VTK_Group_StandAlone > > vtkCommonComputationalGeometry-Test-Cxx > > vtkFiltersGeneral > > vtkFiltersSources > > vtkImagingStencil > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingCore > > * vtkCommonCore, needed by 94 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonColor > > vtkCommonComputationalGeometry > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonExecutionModel > > vtkCommonMath > > vtkCommonMisc > > vtkCommonSystem > > vtkCommonTransforms > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersPoints > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSelection > > vtkFiltersSources > > vtkFiltersStatistics > > vtkFiltersTexture > > vtkFiltersTopology > > vtkFiltersVerdict > > vtkGeovisCore > > vtkIOAMR > > vtkIOCore > > vtkIOEnSight > > vtkIOExodus > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIONetCDF > > vtkIOPLY > > vtkIOParallel > > vtkIOParallelXML > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkIOXMLParser > > vtkImagingColor > > vtkImagingCore > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingHybrid-Test-Cxx > > vtkImagingMath > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionImage > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkParallelCore > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingCore > > vtkTestingGenericBridge > > vtkTestingRendering > > vtkViewsContext2D > > vtkViewsCore > > vtkViewsInfovis > > * vtkCommonDataModel, needed by 86 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonColor > > vtkCommonComputationalGeometry > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersPoints > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSelection > > vtkFiltersSources > > vtkFiltersStatistics > > vtkFiltersTexture > > vtkFiltersTopology > > vtkFiltersVerdict > > vtkGeovisCore > > vtkIOAMR > > vtkIOCore > > vtkIOEnSight > > vtkIOExodus > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIONetCDF > > vtkIOPLY > > vtkIOParallel > > vtkIOParallelXML > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkIOXMLParser > > vtkImagingColor > > vtkImagingCore > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingHybrid-Test-Cxx > > vtkImagingMath > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionImage > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkParallelCore > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingGenericBridge > > vtkTestingRendering > > vtkViewsCore > > vtkViewsInfovis > > * vtkCommonExecutionModel, needed by 76 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonColor-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersPoints > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSelection > > vtkFiltersSources > > vtkFiltersStatistics > > vtkFiltersTexture > > vtkFiltersTopology > > vtkFiltersVerdict > > vtkGeovisCore > > vtkIOAMR > > vtkIOCore > > vtkIOEnSight > > vtkIOExodus > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIONetCDF > > vtkIONetCDF-Test-Cxx > > vtkIOParallel > > vtkIOParallelXML > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkImagingColor > > vtkImagingCore > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingMath > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionImage > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkTestingRendering > > vtkViewsCore > > vtkViewsInfovis > > * vtkCommonMath, needed by 29 modules: > > vtkCommonDataModel > > vtkCommonMath-Test-Cxx > > vtkCommonMisc > > vtkCommonTransforms > > vtkDomainsChemistryOpenGL2 > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHybrid > > vtkFiltersSMP > > vtkIOExport > > vtkIOImage > > vtkIOMINC > > vtkImagingCore > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > * vtkCommonMisc, needed by 27 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel > > vtkCommonExecutionModel > > vtkCommonExecutionModel > > vtkCommonMisc-Test-Cxx > > vtkFiltersCore > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersModeling > > vtkFiltersSMP > > vtkFiltersStatistics > > vtkIOCore > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLegacy > > vtkIOMINC > > vtkIOMovie > > vtkIOPLY > > vtkIOParallel > > vtkIOParallelXML > > vtkIOXML > > vtkRenderingVolume > > vtkTestingGenericBridge > > * vtkCommonSystem, needed by 34 modules: > > VTK_Group_StandAlone > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonExecutionModel > > vtkCommonMath-Test-Cxx > > vtkCommonSystem-Test-Cxx > > vtkFiltersAMR > > vtkFiltersCore > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHyperTree > > vtkFiltersImaging > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersSMP > > vtkGeovisCore > > vtkIOAMR > > vtkIOGeometry > > vtkIOImage > > vtkIOMovie > > vtkIOParallel > > vtkIOVideo > > vtkIOXML > > vtkImagingColor > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkParallelCore > > vtkRenderingCore > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > * vtkCommonTransforms, needed by 37 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonMath-Test-Cxx > > vtkCommonTransforms-Test-Cxx > > vtkDomainsChemistry > > vtkFiltersCore > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersHybrid > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersProgrammable > > vtkFiltersSMP > > vtkFiltersSources > > vtkFiltersTexture > > vtkGeovisCore > > vtkIOExport > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOMINC > > vtkImagingCore > > vtkInfovisLayout > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingImage > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkViewsInfovis > > * vtkDICOMParser, needed by vtkIOImage. > > * vtkDomainsChemistry, needed by 4 modules: > > VTK_Group_StandAlone > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2 > > vtkDomainsChemistryOpenGL2 > > * vtkDomainsChemistryOpenGL2, needed by 4 modules: > > vtkDomainsChemistry > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > * vtkFiltersAMR, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkIOAMR > > vtkIOLegacy-Test-Cxx > > vtkIOXML-Test-Cxx > > * vtkFiltersCore, needed by 28 modules: > > VTK_Group_StandAlone > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkFiltersAMR > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction > > vtkFiltersFlowPaths > > vtkFiltersGeneral > > vtkFiltersGeneric > > vtkFiltersGeometry > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersSMP > > vtkFiltersSources > > vtkGeovisCore > > vtkIOExodus > > vtkIOImport > > vtkIOParallel > > vtkIOXML-Test-Cxx > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingCore > > vtkRenderingLOD > > vtkRenderingVolumeOpenGL2 > > vtkViewsInfovis > > * vtkFiltersExtraction, needed by 9 modules: > > VTK_Group_StandAlone > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkFiltersSelection-Test-Cxx > > vtkIOParallel > > vtkInfovisCore > > vtkInteractionStyle > > vtkViewsInfovis > > * vtkFiltersFlowPaths, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkFiltersGeneral, needed by 27 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkDomainsChemistry > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersHybrid > > vtkFiltersHyperTree > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSMP > > vtkFiltersSources > > vtkFiltersTexture > > vtkGeovisCore > > vtkImagingCore-Test-Cxx > > vtkInfovisCore > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingCore > > vtkRenderingFreeType > > vtkRenderingLabel > > vtkRenderingVolumeOpenGL2 > > vtkViewsCore > > vtkViewsInfovis > > * vtkFiltersGeneric, needed by 3 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > * vtkFiltersGeometry, needed by 8 modules: > > VTK_Group_StandAlone > > vtkFiltersFlowPaths > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersParallel > > vtkIOExport > > vtkIOGeometry-Test-Cxx > > vtkRenderingCore > > vtkViewsInfovis > > * vtkFiltersHybrid, needed by 5 modules: > > VTK_Group_StandAlone > > vtkFiltersHybrid-Test-Cxx > > vtkIOMINC > > vtkImagingCore-Test-Cxx > > vtkInteractionWidgets > > * vtkFiltersHyperTree, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersHyperTree-Test-Cxx > > vtkIOXML-Test-Cxx > > * vtkFiltersImaging, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersParallelImaging > > vtkViewsInfovis > > * vtkFiltersModeling, needed by 16 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersParallel > > vtkFiltersSources-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis > > * vtkFiltersParallel, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersParallelImaging > > vtkIOParallel > > * vtkFiltersParallelImaging, needed by VTK_Group_StandAlone. > > * vtkFiltersPoints, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersPoints-Test-Cxx > > * vtkFiltersProgrammable, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersProgrammable-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingCore-Test-Cxx > > * vtkFiltersSMP, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersSMP-Test-Cxx > > * vtkFiltersSelection, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersSelection-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkFiltersSources, needed by 18 modules: > > VTK_Group_StandAlone > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkFiltersFlowPaths > > vtkFiltersGeneric > > vtkFiltersModeling > > vtkFiltersParallel > > vtkFiltersSources-Test-Cxx > > vtkIOImport > > vtkIOXML-Test-Cxx > > vtkInfovisLayout > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingCore > > vtkRenderingCore-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > vtkViewsInfovis > > * vtkFiltersStatistics, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersExtraction > > vtkFiltersImaging > > vtkFiltersParallelImaging > > vtkFiltersStatistics-Test-Cxx > > vtkViewsInfovis > > * vtkFiltersTexture, needed by VTK_Group_StandAlone. > > * vtkFiltersTopology, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersTopology-Test-Cxx > > * vtkFiltersVerdict, needed by 3 modules: > > VTK_Group_StandAlone > > vtkFiltersSources-Test-Cxx > > vtkFiltersVerdict-Test-Cxx > > * vtkGeovisCore, needed by VTK_Group_Rendering. > > * vtkIOAMR, needed by 4 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR-Test-Cxx > > vtkIOAMR-Test-Cxx > > vtkIOGeometry-Test-Cxx > > * vtkIOCore, needed by 16 modules: > > VTK_Group_StandAlone > > vtkCommonExecutionModel-Test-Cxx > > vtkFiltersFlowPaths > > vtkIOCore-Test-Cxx > > vtkIOExodus > > vtkIOExport > > vtkIOGeometry > > vtkIOInfovis > > vtkIOLegacy > > vtkIOMINC > > vtkIOPLY > > vtkIOParallel > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOXML > > vtkIOXMLParser > > * vtkIOEnSight, needed by VTK_Group_StandAlone. > > * vtkIOExodus, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkIOExodus-Test-Cxx > > vtkRenderingCore-Test-Cxx > > * vtkIOExport, needed by 4 modules: > > VTK_Group_Rendering > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2 > > vtkIOExportOpenGL2 > > * vtkIOExportOpenGL2, needed by 3 modules: > > vtkIOExport > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > * vtkIOGeometry, needed by 8 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOParallel > > vtkRenderingAnnotation-Test-Cxx > > * vtkIOImage, needed by 13 modules: > > VTK_Group_StandAlone > > vtkCommonColor-Test-Cxx > > vtkGeovisCore > > vtkIOExport > > vtkIOExport > > vtkIOImage-Test-Cxx > > vtkIOImport > > vtkIOMINC > > vtkIOPLY-Test-Cxx > > vtkIOParallel > > vtkImagingHybrid > > vtkRenderingVolume-Test-Cxx > > vtkTestingRendering > > * vtkIOImport, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOImport-Test-Cxx > > * vtkIOInfovis, needed by 6 modules: > > VTK_Group_StandAlone > > vtkChartsCore-Test-Cxx > > vtkIOInfovis-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkIOLSDyna, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOLSDyna-Test-Cxx > > * vtkIOLegacy, needed by 30 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel-Test-Cxx > > vtkDomainsChemistry > > vtkDomainsChemistry-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersParallel > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersTopology-Test-Cxx > > vtkFiltersVerdict-Test-Cxx > > vtkIOGeometry > > vtkIOGeometry-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOInfovis > > vtkIOLegacy-Test-Cxx > > vtkIOParallel > > vtkIOSQL-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkParallelCore > > vtkRenderingCore-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > * vtkIOMINC, needed by VTK_Group_StandAlone. > > * vtkIOMovie, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOMovie-Test-Cxx > > * vtkIONetCDF, needed by 3 modules: > > VTK_Group_StandAlone > > vtkIONetCDF-Test-Cxx > > vtkIOParallel > > * vtkIOPLY, needed by 3 modules: > > VTK_Group_StandAlone > > vtkIOPLY-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > * vtkIOParallel, needed by 6 modules: > > VTK_Group_StandAlone > > vtkFiltersSources-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > * vtkIOParallelXML, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOXML-Test-Cxx > > * vtkIOSQL, needed by 4 modules: > > VTK_Group_StandAlone > > vtkIOSQL-Test-Cxx > > vtkTestingIOSQL > > vtkViewsInfovis-Test-Cxx > > * vtkIOTecplotTable, needed by 2 modules: > > VTK_Group_StandAlone > > vtkIOTecplotTable-Test-Cxx > > * vtkIOVideo, needed by VTK_Group_StandAlone. > > * vtkIOXML, needed by 26 modules: > > VTK_Group_StandAlone > > vtkCommonDataModel-Test-Cxx > > vtkFiltersAMR > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSMP-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkGeovisCore > > vtkIOAMR-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOInfovis > > vtkIOParallelXML > > vtkIOXML-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingVolume > > vtkRenderingVolume-Test-Cxx > > * vtkIOXMLParser, needed by 6 modules: > > VTK_Group_StandAlone > > vtkDomainsChemistry > > vtkIOExodus > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOXML > > * vtkImagingColor, needed by 4 modules: > > VTK_Group_StandAlone > > vtkInteractionImage > > vtkInteractionWidgets > > vtkRenderingAnnotation > > * vtkImagingCore, needed by 28 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersHybrid > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersParallelImaging > > vtkFiltersPoints-Test-Cxx > > vtkFiltersSMP-Test-Cxx > > vtkGeovisCore > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOMovie-Test-Cxx > > vtkImagingColor > > vtkImagingCore-Test-Cxx > > vtkImagingFourier > > vtkImagingGeneral > > vtkImagingHybrid > > vtkImagingMorphological > > vtkImagingSources > > vtkImagingStatistics > > vtkImagingStencil > > vtkInteractionImage > > vtkInteractionWidgets > > vtkRenderingContextOpenGL2 > > vtkRenderingImage > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > * vtkImagingFourier, needed by 2 modules: > > VTK_Group_StandAlone > > vtkFiltersStatistics > > * vtkImagingGeneral, needed by 9 modules: > > VTK_Group_StandAlone > > vtkFiltersImaging > > vtkFiltersParallelImaging > > vtkImagingCore-Test-Cxx > > vtkImagingMorphological > > vtkInteractionWidgets > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis > > * vtkImagingHybrid, needed by 5 modules: > > VTK_Group_StandAlone > > vtkImagingHybrid-Test-Cxx > > vtkInfovisLayout > > vtkInteractionWidgets > > vtkRenderingVolume-Test-Cxx > > * vtkImagingMath, needed by 5 modules: > > VTK_Group_StandAlone > > vtkFiltersGeneral-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > * vtkImagingMorphological, needed by 2 modules: > > VTK_Group_StandAlone > > vtkImagingMorphological-Test-Cxx > > * vtkImagingSources, needed by 15 modules: > > VTK_Group_StandAlone > > vtkFiltersHybrid > > vtkGeovisCore > > vtkIOImage-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOMovie-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingGeneral > > vtkImagingMorphological > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > * vtkImagingStatistics, needed by 2 modules: > > VTK_Group_StandAlone > > vtkImagingCore-Test-Cxx > > * vtkImagingStencil, needed by 5 modules: > > VTK_Group_StandAlone > > vtkFiltersHybrid-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkInfovisCore, needed by 8 modules: > > VTK_Group_StandAlone > > vtkChartsCore > > vtkGeovisCore > > vtkIOInfovis > > vtkIOXML-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout > > vtkViewsInfovis > > * vtkInfovisLayout, needed by 6 modules: > > VTK_Group_StandAlone > > vtkGeovisCore > > vtkIOInfovis-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkViewsInfovis > > * vtkInteractionImage, needed by 6 modules: > > VTK_Group_Rendering > > vtkIOExport-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > * vtkInteractionStyle, needed by 46 modules: > > VTK_Group_Rendering > > vtkCommonColor-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersProgrammable-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkGeovisCore > > vtkIOExodus-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOLSDyna-Test-Cxx > > vtkIOLegacy-Test-Cxx > > vtkIONetCDF-Test-Cxx > > vtkIOPLY-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkInteractionImage > > vtkInteractionWidgets > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingGL2PSOpenGL2-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis > > * vtkInteractionWidgets, needed by 6 modules: > > VTK_Group_Rendering > > vtkGeovisCore > > vtkInteractionImage > > vtkInteractionWidgets-Test-Cxx > > vtkViewsCore > > vtkViewsInfovis > > * vtkMetaIO, needed by vtkIOImage. > > * vtkParallelCore, needed by 8 modules: > > VTK_Group_StandAlone > > vtkFiltersAMR > > vtkFiltersParallel > > vtkFiltersParallelImaging > > vtkIOAMR > > vtkIOParallel > > vtkIOParallelXML > > vtkParallelCore-Test-Cxx > > * vtkRenderingAnnotation, needed by 9 modules: > > VTK_Group_Rendering > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInteractionWidgets > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkViewsInfovis > > * vtkRenderingContext2D, needed by 9 modules: > > VTK_Group_Rendering > > vtkChartsCore > > vtkFiltersPoints-Test-Cxx > > vtkIOExport > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingContextOpenGL2 > > vtkRenderingContextOpenGL2 > > vtkViewsContext2D > > vtkViewsInfovis > > * vtkRenderingContextOpenGL2, needed by 9 modules: > > vtkChartsCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkRenderingContext2D > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkRenderingCore, needed by 34 modules: > > VTK_Group_Rendering > > vtkChartsCore > > vtkDomainsChemistry > > vtkDomainsChemistryOpenGL2 > > vtkFiltersHybrid > > vtkFiltersParallel > > vtkGeovisCore > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkIOImport > > vtkIOInfovis-Test-Cxx > > vtkIOMINC > > vtkInteractionImage > > vtkInteractionStyle > > vtkInteractionStyle > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType > > vtkRenderingFreeType > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage > > vtkRenderingLOD > > vtkRenderingLabel > > vtkRenderingOpenGL2 > > vtkRenderingOpenGL2 > > vtkRenderingVolume > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > vtkViewsContext2D > > vtkViewsCore > > vtkViewsInfovis > > * vtkRenderingFreeType, needed by 11 modules: > > VTK_Group_Rendering > > vtkIOExport > > vtkInteractionWidgets > > vtkRenderingAnnotation > > vtkRenderingContext2D > > vtkRenderingContextOpenGL2 > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkRenderingLabel > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > * vtkRenderingGL2PSOpenGL2, needed by 3 modules: > > vtkIOExport > > vtkIOExportOpenGL2 > > vtkRenderingGL2PSOpenGL2-Test-Cxx > > * vtkRenderingImage, needed by 4 modules: > > VTK_Group_Rendering > > vtkImagingCore-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > * vtkRenderingLOD, needed by 4 modules: > > VTK_Group_Rendering > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > * vtkRenderingLabel, needed by 7 modules: > > VTK_Group_Rendering > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkViewsInfovis > > * vtkRenderingOpenGL2, needed by 47 modules: > > vtkCommonColor-Test-Cxx > > vtkCommonComputationalGeometry-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkCommonTransforms-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2 > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersProgrammable-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkIOExodus-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOLSDyna-Test-Cxx > > vtkIOLegacy-Test-Cxx > > vtkIONetCDF-Test-Cxx > > vtkIOPLY-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkParallelCore-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingContextOpenGL2 > > vtkRenderingCore > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingGL2PSOpenGL2 > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > * vtkRenderingVolume, needed by 5 modules: > > VTK_Group_Rendering > > vtkInteractionWidgets > > vtkRenderingVolume-Test-Cxx > > vtkRenderingVolumeOpenGL2 > > vtkRenderingVolumeOpenGL2 > > * vtkRenderingVolumeOpenGL2, needed by 6 modules: > > vtkFiltersCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkRenderingVolume > > vtkRenderingVolume-Test-Cxx > > * vtkTestingCore, needed by 33 modules: > > vtkChartsCore-Test-Cxx > > vtkCommonColor-Test-Cxx > > vtkCommonComputationalGeometry-Test-Cxx > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkCommonExecutionModel-Test-Cxx > > vtkCommonMath-Test-Cxx > > vtkCommonMisc-Test-Cxx > > vtkCommonSystem-Test-Cxx > > vtkCommonTransforms-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersAMR-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersSMP-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkFiltersStatistics-Test-Cxx > > vtkFiltersVerdict-Test-Cxx > > vtkIOAMR-Test-Cxx > > vtkIOCore-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOMovie-Test-Cxx > > vtkIOSQL-Test-Cxx > > vtkIOTecplotTable-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkTestingRendering > > * vtkTestingGenericBridge, needed by 2 modules: > > vtkCommonDataModel-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > * vtkTestingIOSQL, needed by vtkIOSQL-Test-Cxx. > > * vtkTestingRendering, needed by 51 modules: > > vtkChartsCore-Test-Cxx > > vtkCommonColor-Test-Cxx > > vtkCommonDataModel-Test-Cxx > > vtkDomainsChemistry-Test-Cxx > > vtkDomainsChemistryOpenGL2-Test-Cxx > > vtkFiltersAMR-Test-Cxx > > vtkFiltersCore-Test-Cxx > > vtkFiltersExtraction-Test-Cxx > > vtkFiltersFlowPaths-Test-Cxx > > vtkFiltersGeneral-Test-Cxx > > vtkFiltersGeneric-Test-Cxx > > vtkFiltersGeometry-Test-Cxx > > vtkFiltersHybrid-Test-Cxx > > vtkFiltersHyperTree-Test-Cxx > > vtkFiltersModeling-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkFiltersProgrammable-Test-Cxx > > vtkFiltersSelection-Test-Cxx > > vtkFiltersSources-Test-Cxx > > vtkFiltersTopology-Test-Cxx > > vtkIOAMR-Test-Cxx > > vtkIOExodus-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > vtkIOGeometry-Test-Cxx > > vtkIOImage-Test-Cxx > > vtkIOImport-Test-Cxx > > vtkIOInfovis-Test-Cxx > > vtkIOLSDyna-Test-Cxx > > vtkIOLegacy-Test-Cxx > > vtkIONetCDF-Test-Cxx > > vtkIOPLY-Test-Cxx > > vtkIOXML-Test-Cxx > > vtkImagingCore-Test-Cxx > > vtkImagingHybrid-Test-Cxx > > vtkImagingMorphological-Test-Cxx > > vtkInfovisCore-Test-Cxx > > vtkInfovisLayout-Test-Cxx > > vtkInteractionWidgets-Test-Cxx > > vtkParallelCore-Test-Cxx > > vtkRenderingAnnotation-Test-Cxx > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingCore-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkRenderingGL2PSOpenGL2-Test-Cxx > > vtkRenderingImage-Test-Cxx > > vtkRenderingLOD-Test-Cxx > > vtkRenderingLabel-Test-Cxx > > vtkRenderingOpenGL2-Test-Cxx > > vtkRenderingVolume-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkUtilitiesEncodeString, needed by vtkRenderingOpenGL2. > > * vtkUtilitiesHashSource, needed by vtkParallelCore. > > * vtkViewsContext2D, needed by 8 modules: > > VTK_Group_Rendering > > vtkChartsCore-Test-Cxx > > vtkFiltersPoints-Test-Cxx > > vtkIOExport-Test-Cxx > > vtkIOExportOpenGL2-Test-Cxx > > vtkRenderingContext2D-Test-Cxx > > vtkRenderingFreeType-Test-Cxx > > vtkViewsInfovis-Test-Cxx > > * vtkViewsCore, needed by 4 modules: > > VTK_Group_Rendering > > vtkGeovisCore > > vtkViewsContext2D > > vtkViewsInfovis > > * vtkViewsInfovis, needed by 2 modules: > > VTK_Group_Rendering > > vtkViewsInfovis-Test-Cxx > > * vtkalglib, needed by vtkFiltersStatistics. > > * vtkexodusII, needed by 2 modules: > > vtkIOExodus > > vtkIOParallel > > * vtkexpat, needed by vtkIOXMLParser. > > * vtkfreetype, needed by vtkRenderingFreeType. > > * vtkgl2ps, needed by 2 modules: > > vtkIOExportOpenGL2 > > vtkRenderingGL2PSOpenGL2 > > * vtkglew, needed by 4 modules: > > vtkDomainsChemistryOpenGL2 > > vtkRenderingContextOpenGL2 > > vtkRenderingOpenGL2 > > vtkRenderingVolumeOpenGL2 > > * vtkhdf5, needed by 2 modules: > > vtkIOAMR > > vtknetcdf > > * vtkjpeg, needed by 2 modules: > > vtkIOImage > > vtktiff > > * vtkjsoncpp, needed by vtkIOParallel. > > * vtkkwiml, needed by 2 modules: > > vtkCommonCore > > vtkfreetype > > * vtklibharu, needed by vtkIOExport. > > * vtklibproj4, needed by vtkGeovisCore. > > * vtklibxml2, needed by vtkIOInfovis. > > * vtklz4, needed by vtkIOCore. > > * vtknetcdf, needed by 5 modules: > > vtkIOMINC > > vtkIONetCDF > > vtkIOParallel > > vtkexodusII > > vtknetcdfcpp > > * vtknetcdfcpp, needed by vtkIONetCDF. > > * vtkoggtheora, needed by vtkIOMovie. > > * vtkpng, needed by 3 modules: > > vtkIOImage > > vtkgl2ps > > vtklibharu > > * vtksqlite, needed by vtkIOSQL. > > * vtksys, needed by 33 modules: > > vtkChartsCore > > vtkCommonCore > > vtkCommonCore-Test-Cxx > > vtkCommonDataModel > > vtkCommonSystem > > vtkDICOMParser > > vtkDomainsChemistry > > vtkFiltersHybrid > > vtkIOAMR > > vtkIOCore > > vtkIOExodus > > vtkIOGeometry > > vtkIOImage > > vtkIOImport > > vtkIOInfovis > > vtkIOLSDyna > > vtkIOLegacy > > vtkIOMINC > > vtkIONetCDF > > vtkIOParallel > > vtkIOParallelXML > > vtkIOSQL > > vtkIOTecplotTable > > vtkIOVideo > > vtkIOXML > > vtkIOXMLParser > > vtkImagingFourier > > vtkParallelCore > > vtkRenderingCore > > vtkRenderingOpenGL2 > > vtkRenderingVolumeOpenGL2 > > vtkTestingRendering > > vtkUtilitiesHashSource > > * vtktiff, needed by vtkIOImage. > > * vtkverdict, needed by vtkFiltersVerdict. > > * vtkzlib, needed by 11 modules: > > vtkIOCore > > vtkIOGeometry > > vtkIOImage > > vtkMetaIO > > vtkfreetype > > vtkgl2ps > > vtkhdf5 > > vtklibharu > > vtklibxml2 > > vtkpng > > vtktiff > > 64 bit architecture detected size of void * is 8 > > Building tiff version 4.0.6 > > libtiff library version 5.2.4 > > CMAKE_HOST_SYSTEM_PROCESSOR set to AMD64 > > HOST_FILLORDER set to FILLORDER_MSB2LSB > > HOST_BIG_ENDIAN set to 0 > > HAVE_IEEEFP set to 1 > > HDF5: SOVERSION: 8.0.2 > > HDF5: Performing Other Test STDC_HEADERS - Success > > HDF5: Performing CXX Test OLD_HEADER_FILENAME - Failed > > HDF5: Performing CXX Test H5_NO_NAMESPACE - Failed > > HDF5: Performing CXX Test H5_NO_STD - Failed > > HDF5: Performing CXX Test BOOL_NOTDEFINED - Failed > > HDF5: Performing CXX Test NO_STATIC_CAST - Failed > > HDF5: Checking for InitOnceExecuteOnce: > > HDF5: Performing Test InitOnceExecuteOnce - Success > > HDF5: Performing Other Test INLINE_TEST_inline - Success > > HDF5: Performing Other Test INLINE_TEST___inline__ - Failed > > HDF5: Performing Other Test INLINE_TEST___inline - Success > > HDF5: checking IF converting from long double to integers is accurate... > yes > > HDF5: checking IF accurately converting from integers to long double... yes > > HDF5: Checking IF accurately converting unsigned long to float values... > yes > > HDF5: Checking IF accurately roundup converting floating-point to unsigned > long long values... yes > > HDF5: Checking IF right maximum converting floating-point to unsigned long > long values... yes > > HDF5: Checking IF correctly converting long double to unsigned int > values... yes > > HDF5: Checking IF overflows normally converting floating-point to integer > values... yes > > HDF5: Checking IF correctly converting long double to (unsigned) long long > values... yes > > HDF5: Checking IF correctly converting (unsigned) long long to long double > values... yes > > HDF5: Checking IF alignment restrictions are strictly enforced... yes > > HDF5: Filter ZLIB is ON > > > > Configuring PROJ: > > > > PROJ_VERSION = 4.9.2 > > PROJ_ABI_VERSION = 4_9 > > CMake Deprecation Warning at ThirdParty/libproj4/ > vtklibproj4/cmake/policies.cmake:2 (cmake_policy): > The OLD behavior for policy CMP0022 will be removed from a future version > of CMake. > > The cmake-policies(7) manual explains that the OLD behaviors of all > policies are deprecated and that a policy should be set to OLD only under > specific short-term circumstances. Projects should be ported to the NEW > behavior and not rely on setting a policy to OLD. > Call Stack (most recent call first): > ThirdParty/libproj4/vtklibproj4/CMakeLists.txt:43 (include) > > > > Configuring proj library: > > > > PROJ_CORE_TARGET = vtkproj4 > > PROJ_CORE_TARGET_OUTPUT_NAME = vtkproj4_4_9 > > PROJ_LIBRARIES = vtkproj4 > > Configuring done > > > > > _______________________________________________ > 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 > > > > > > > -- > > Ken Martin PhD > > Distinguished Engineer > Kitware Inc. > > 28 Corporate Drive > Clifton Park NY 12065 > > > > 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. > > > > > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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: image.png Type: image/png Size: 44008 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 73671AD9C3BD48BFA91651495F5078E2.png Type: image/png Size: 98803 bytes Desc: not available URL: From pbisbal at pppl.gov Thu Jul 20 14:37:47 2017 From: pbisbal at pppl.gov (Prentice Bisbal) Date: Thu, 20 Jul 2017 14:37:47 -0400 Subject: [vtkusers] Trying to build VTK 7.1.1 on CentOS 6 - 'make test' fails Message-ID: <2ca80f0e-c73e-0dd7-b4bd-5cbcfac7e448@pppl.gov> I'm a system administrator trying to build VTK 7.1.1 on CentOS 6.9 for my users. When I do 'make test', I get a lot of failures. Here's what I do to build: My cmake command: cmake \ -D CMAKE_INSTALL_PREFIX:PATH=/usr/pppl/vtk/7.1.1 \ -D CMAKE_BUILD_TYPE:STRING=Release \ -D CMAKE_C_COMPILER:PATH=/usr/bin/gcc \ -D CMAKE_CXX_COMPILER:PATH=/usr/bin/g++ \ -D BUILD_SHARED_LIBS:BOOL=OFF \ -D BUILD_TESTING=ON \ -D VTK_Group_Imaging=ON \ -D VTK_Group_Qt=ON \ -D VTK_Group_Tk=ON \ -D VTK_WRAP_JAVA=ON \ -D VTK_WRAP_PYTHON=ON \ -D VTK_WRAP_TCL=ON \ ../ \ 2>&1 | tee cmake.log After make completes, I do a 'make test', and get a bunch of segfault and 'other fault' errors: make test 2>&1 | tee test.log $ grep -i fault test.log | head -n 20 208/2232 Test #208: vtkCommonComputationalGeometryTcl-TestParametricFunctions ....................***Exception: SegFault 0.85 sec 209/2232 Test #209: vtkCommonComputationalGeometryTcl-CSpline ....................................***Exception: SegFault 0.45 sec 210/2232 Test #210: vtkCommonComputationalGeometryTcl-KSpline ....................................***Exception: SegFault 0.45 sec 211/2232 Test #211: vtkCommonComputationalGeometryTcl-closedSplines ..............................***Exception: SegFault 0.35 sec Start 312: vtkCommonCorePython-TestDefaultArgs 312/2232 Test #312: vtkCommonCorePython-TestDefaultArgs .......................................... Passed 0.19 sec 434/2232 Test #434: vtkCommonDataModelTcl-headBone ...............................................***Exception: SegFault 0.33 sec 435/2232 Test #435: vtkCommonDataModelTcl-ImplicitSum ............................................***Exception: SegFault 0.32 sec 436/2232 Test #436: vtkCommonDataModelTcl-PerlinNoise ............................................***Exception: SegFault 0.31 sec 437/2232 Test #437: vtkCommonDataModelTcl-SelectionLoop ..........................................***Exception: SegFault 0.21 sec 438/2232 Test #438: vtkCommonDataModelTcl-LineIntersectQuadraticCells ............................***Exception: SegFault 0.26 sec 439/2232 Test #439: vtkCommonDataModelTcl-quadricCut .............................................***Exception: SegFault 0.28 sec 440/2232 Test #440: vtkCommonDataModelTcl-scalarColors ...........................................***Exception: SegFault 0.35 sec 441/2232 Test #441: vtkCommonDataModelTcl-scalarConn .............................................***Exception: SegFault 0.34 sec 442/2232 Test #442: vtkCommonDataModelTcl-TestConvexPointSet .....................................***Exception: SegFault 0.31 sec 443/2232 Test #443: vtkCommonDataModelTcl-TestQuadricClustering ..................................***Exception: SegFault 0.37 sec 444/2232 Test #444: vtkCommonDataModelTcl-TestStructuredGrid .....................................***Exception: SegFault 0.34 sec 445/2232 Test #445: vtkCommonDataModelTcl-TestICPTransform .......................................***Exception: SegFault 0.39 sec 475/2232 Test #475: vtkCommonTransformsTcl-cylindrical ...........................................***Exception: SegFault 0.36 sec 476/2232 Test #476: vtkCommonTransformsTcl-spherical .............................................***Exception: SegFault 0.32 sec That's just some of the errors in total, I get ~1800 errors: $ grep -i fault test.log | wc -l 1830 When I run 'make test', I'm not doing it on my local server. I'm doing it on a remote system, that I ssh into with X11 forwarding enabled. I've noticed that, at least for the tests at the start, the tests segfault when they're drawing on my screen. Could the SSH/X11 forwarding be part of the problem? Could it be that I need to use the older OpenGL interface on CentOS 6.9? Should I link to Mesa instead? Thanks for all your help, from a complete newbie to this list. Prentice From pbisbal at pppl.gov Thu Jul 20 14:53:53 2017 From: pbisbal at pppl.gov (Prentice Bisbal) Date: Thu, 20 Jul 2017 14:53:53 -0400 Subject: [vtkusers] Building Python support for both Python 2 and Python 3 Message-ID: <090f2ad5-6db8-bc11-4947-cdebf16c3fa9@pppl.gov> I searched the mailing list archives and coudn't find an answer to this question, which I imagine must be quite common on this list: I support an environment where the users use both Python 2.7 and Python 3.6 from python.org, as well as the Anaconda2 and Anaconda3 python distributions from Continuum Analytics (continuum.io). I need to build vtk python modules for these different versions of Python. What is the best way to do this? Is it possible to build just the VTK python module? In a perfect world, I should be able to build VTK, install it, and then build the Python modules for that version of VTK for the various versions of python I support, but that doesn't seem possible. I imagine I could build VTK with Python2 in my path, and then rebuild it with Python3 in my path and have them install in the same location, so that the python2 and python3 libraries are both installed, in the VTK install directory, but I suspect this might lead to other issues elsewhere in the VTK environment. I imagine I only need to build one module for python 2.7 and both the python.org and anaconda2 installations can use the same module, ditto for Python 3.6 Any help/suggestions will be greatly appreciated. Prentice From sankhesh.jhaveri at kitware.com Thu Jul 20 15:28:31 2017 From: sankhesh.jhaveri at kitware.com (Sankhesh Jhaveri) Date: Thu, 20 Jul 2017 19:28:31 +0000 Subject: [vtkusers] Using vtkExternalOpenGLCamera In-Reply-To: References: <1500472740832-5744015.post@n5.nabble.com> Message-ID: Hi Elaine, I see. In that case, you can remove all the code where you?re explicitly setting the projection and view matrices on the external camera. The external renderer handles that internally (automatically). The external renderer is responsible for updating the VTK camera matrices based on the OpenGL state. Thanks, Sankhesh ? On Thu, Jul 20, 2017 at 2:13 PM Elaine Jiang wrote: > Hi Sankhesh, > > That makes sense! However, my end goal is indeed to integrate with a > virtual reality system that is controlling the OpenGL camera - I was just > trying to get the external camera to work before integrating with a VR > program. I can attach the render function that I'm working on that is part > of a VR program. Here, I'm using SetViewTransformMatrix() and > SetProjectionTransformMatrix(). Sorry for the confusion before, and thanks > for your quick replies! > > > /// This is called each time through the main graphics loop, and > /// re-draws the scene according to whatever has changed since the > /// last time it was drawn. > *void onVRRenderGraphics(const MinVR::VRGraphicsState &renderState) {* > // Only draw if the application is still running. > *if (isRunning()) {* > // Enable depth testing. Demonstrates OpenGL context being > managed by external > // application i.e. GLUT in this case. > *glEnable(GL_DEPTH_TEST);* > > // Buffers being managed by external application i.e. GLUT in > this case. > *glClearColor(1.0f, 1.0f, 1.0f, 0.0f);* > *glClearDepth(1.0f);* > *glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);* // > Clear the color buffer > > *glFlush(); * // Render now > > *glEnable(GL_LIGHTING);* > * glEnable(GL_LIGHT0);* > > // color > *GLfloat diffuse[] = {1.0f, 0.8f, 1.0f, 1.0f};* > * glLightfv(GL_LIGHT0, GL_DIFFUSE, diffuse);* > * GLfloat specular[] = {0.5f, 0.0f, 0.0f, 1.0f};* > * glLightfv(GL_LIGHT0, GL_SPECULAR, specular);* > * GLfloat ambient[] = {1.0f, 1.0f, 0.2f, 1.0f};* > * glLightfv(GL_LIGHT0, GL_AMBIENT, ambient);* > > > // Second the load() step. We let MinVR give us the projection > // matrix from the render state argument to this method. > *const float* pm = renderState.getProjectionMatrix();* > * glm::mat4 projMatrix = glm::mat4( pm[0], pm[1], pm[2], > pm[3],* > * pm[4], pm[5], pm[6], pm[7],* > * pm[8], pm[9],pm[10],pm[11],* > * pm[12],pm[13],pm[14],pm[15]);* > > // The draw step. We let MinVR give us the view matrix. > *const float* vm = renderState.getViewMatrix();* > * glm::mat4 viewMatrix = glm::mat4( vm[0], vm[1], vm[2], > vm[3],* > * vm[4], vm[5], vm[6], vm[7],* > * vm[8], vm[9],vm[10],vm[11],* > * vm[12],vm[13],vm[14],vm[15]);* > > > * camera = (vtkExternalOpenGLCamera *)ren->GetActiveCamera();* > > *double view[16];* > * for(int i = 0; i < 16; i++) {* > * view[i] = glm::value_ptr(viewMatrix)[i];* > * }* > > *camera->SetViewTransformMatrix(view);* > > * double proj[16];* > * for(int i = 0; i < 16; i++) {* > * proj[i] = glm::value_ptr(projMatrix)[i];* > * }* > > * camera->SetProjectionTransformMatrix(proj);* > > > * for(int i = 0; i < 7; i++) {* > * // transpose - vtk* > * //actors[i]->SetOrientation(0,0,0);* > * actors[i]->RotateX(y_angle);* > * actors[i]->RotateY(x_angle);* > * actors[i]->SetScale(scale_size);* > * }* > > * externalVTKWidget->GetRenderWindow()->Render();* > > // We let MinVR swap the graphics buffers. > // glutSwapBuffers(); > * }* > * }* > * };* > > > Thanks, > Elaine > > On Thu, Jul 20, 2017 at 2:00 PM, Sankhesh Jhaveri < > sankhesh.jhaveri at kitware.com> wrote: > >> Hi Elaine, >> >> I didn?t see anything obvious in your sample code so decided to look more >> closely at the external renderer implementation. Its been a while since I >> looked at that code and my memory was rusty. >> >> You don?t need the external renderer if you are driving the OpenGL scene >> via VTK. Think of the external renderer as glue code that synchronizes the >> external OpenGL scene with VTK. It makes sure that the camera used is an >> external camera and overrides the camera parameters with what it finds in >> the external OpenGL scene. You need it in cases where something else is >> controlling the OpenGL camera and you?d like the VTK scene to be up-to-date >> as well; e.g. virtual reality systems where the main application updates >> OpenGL camera parameters. >> >> In your case, you can simply instantiate a vtkRenderer and set it on the >> vtkExternalOpenGLRenderWindow via vtkRenderWindow::AddRenderer(vtkRenderer* >> ren). The rest of the code should work as expected - except that the >> active camera would be of type vtkOpenGLCamera instead of >> vtkExternalOpenGLCamera. >> >> Hope that helps. >> >> Sankhesh >> ? >> >> On Thu, Jul 20, 2017 at 1:31 PM Elaine Jiang >> wrote: >> >>> Hi Sankhesh, >>> >>> Here's my initialization function and my render function. The external >>> camera set up is highlighted. >>> >>> *vtkNew externalVTKWidget;* >>> *vtkSmartPointer ren = externalVTKWidget->AddRenderer();* >>> *static int windowId = -1;* >>> *static int windowH = 800;* >>> *static int windowW = 800;* >>> *vtkSmartPointer actors[7];* >>> >>> *vtkNew transform;* >>> *int press_x, press_y;* >>> *int release_x, release_y;* >>> *float x_angle = 0.0;* >>> *float y_angle = 0.0;* >>> *float scale_size = 1;* >>> *int xform_mode = 0;* >>> *#define XFORM_NONE 0* >>> *#define XFORM_ROTATE 1* >>> *#define XFORM_SCALE 2* >>> >>> >>> *void initialize() {* >>> *vtkNew renWin;* >>> * externalVTKWidget->SetRenderWindow(renWin.GetPointer());* >>> >>> *std::string files[7] = {"../data/newsi-ascii.vtk", >>> "../data/newjets-ascii.vtk", "../data/fekcorr-ascii.vtk", >>> "../data/newar-ascii.vtk", "../data/newhetg-ascii.vtk", >>> "../data/newopt-ascii.vtk", "../data/newsi-ascii.vtk"};* >>> >>> * for(int i = 0; i < 7; i++) {* >>> * vtkSmartPointer reader =* >>> * vtkSmartPointer::New();* >>> * reader->SetFileName(files[i].c_str());* >>> * reader->Update();* >>> * vtkSmartPointer inputPolyData = >>> reader->GetOutput();* >>> >>> * vtkSmartPointer clean =* >>> * vtkSmartPointer::New();* >>> * clean->SetInputData(inputPolyData);* >>> >>> // Generate normals >>> *vtkSmartPointer normals =* >>> * vtkSmartPointer::New();* >>> * normals->SetInputConnection(clean->GetOutputPort());* >>> * normals->SplittingOff();* >>> >>> >>> *vtkSmartPointer mapper =* >>> * vtkSmartPointer::New();* >>> * mapper->SetInputConnection(normals->GetOutputPort());* >>> >>> *vtkSmartPointer actor =* >>> * vtkSmartPointer::New();* >>> * actor->SetMapper(mapper);* >>> * actor->GetProperty()->SetInterpolationToFlat();* >>> >>> * ren->AddActor(actor);* >>> * actors[i] = actor;* >>> * }* >>> >>> *ren->SetBackground(0, 0, 0);* >>> * ren->MakeCamera();* >>> * ren->ResetCamera();* >>> * renWin->AddRenderer(ren);* >>> *}* >>> >>> // Render function >>> *void display() {* >>> // Enable depth testing. Demonstrates OpenGL context being managed >>> by external >>> // application i.e. GLUT in this case. >>> *glEnable(GL_DEPTH_TEST);* >>> >>> // Buffers being managed by external application i.e. GLUT in this >>> case. >>> *glClearColor(0.0f, 0.0f, 0.0f, 1.0f);* // Set background color to >>> black and opaque >>> *glClearDepth(1.0f);* >>> *glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);* // Clear the >>> color buffer >>> >>> *glFlush();* // Render now >>> >>> *glEnable(GL_LIGHTING);* >>> * glEnable(GL_LIGHT0);* >>> >>> *GLfloat diffuse[] = {1.0f, 1.0f, 1.0f, 1.0f};* >>> * glLightfv(GL_LIGHT0, GL_DIFFUSE, diffuse);* >>> * GLfloat specular[] = {0.5f, 0.0f, 0.0f, 1.0f};* >>> * glLightfv(GL_LIGHT0, GL_SPECULAR, specular);* >>> * GLfloat ambient[] = {1.0f, 1.0f, 0.2f, 1.0f};* >>> * glLightfv(GL_LIGHT0, GL_AMBIENT, ambient);* >>> >>> >>> *vtkExternalOpenGLCamera *camera = (vtkExternalOpenGLCamera >>> *)ren->GetActiveCamera();* >>> * camera->SetPosition(0,0,-100);* >>> * camera->SetFocalPoint(0,0,0); * >>> * camera->SetViewUp(0,1,0); * >>> >>> >>> *for(int i = 0; i < 7; i++) {* >>> * // transpose - vtk* >>> * actors[i]->SetOrientation(0,0,0);* >>> * actors[i]->RotateX(y_angle);* >>> * actors[i]->RotateY(x_angle);* >>> * actors[i]->SetScale(scale_size);* >>> >>> * // transpose - opengl* >>> * double f[16];* >>> * actors[i]->GetMatrix(f);* >>> >>> * // transpose* >>> * double g[16];* >>> * g[0] = f[0]; g[1] = f[4]; g[2] = f[8]; g[3] = f[12];* >>> * g[4] = f[1]; g[5] = f[5]; g[6] = f[9]; g[7] = f[13];* >>> * g[8] = f[2]; g[9] = f[6]; g[10]= f[10];g[11]= f[14];* >>> * g[12]= f[3]; g[13]= f[7]; g[14]= f[11];g[15]= f[15];* >>> * glMultMatrixd(g); // multiply current matrix with specified >>> matrix* >>> * }* >>> >>> *externalVTKWidget->GetRenderWindow()->Render();* >>> * glutSwapBuffers();* >>> *}* >>> >>> Thanks, >>> Elaine >>> >>> On Thu, Jul 20, 2017 at 1:11 PM, Sankhesh Jhaveri < >>> sankhesh.jhaveri at kitware.com> wrote: >>> >>>> Hi Elaine, >>>> >>>> You shouldn?t have to set that flag for using the matrices set on the >>>> external camera. Could you share some sample code that doesn?t work? >>>> >>>> Thanks, >>>> Sankhesh >>>> ? >>>> >>>> On Thu, Jul 20, 2017 at 11:38 AM Elaine Jiang >>>> wrote: >>>> >>>>> Hi Sankhesh, >>>>> >>>>> I've tried setting the camera and focal point parameters without using >>>>> SetProjectionMatrix() and SetModelViewTransformMatrix(), and I've also >>>>> tried just calling SetProjectionMatrix() and SetModelViewTransformMatrix() >>>>> by themselves. Neither approach seemed to have an effect on the scene. I >>>>> was looking through the documentation and was wondering if I need to use >>>>> the function vtkCamera::vtkSetUseExplicitProjectionTransformMatrix(bool) to >>>>> solve the problem? >>>>> >>>>> Thanks, >>>>> Elaine >>>>> >>>>> On Thu, Jul 20, 2017 at 11:12 AM, Sankhesh Jhaveri < >>>>> sankhesh.jhaveri at kitware.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Could you please provide more details on how you?re trying to set the >>>>>> camera parameters? >>>>>> The way the external camera works is that it ignores the camera >>>>>> position and focal point parameters if the projection and model view >>>>>> matrices are set explicitly using >>>>>> vtkExternalOpenGLCamera::SetProjectionMatrix() and >>>>>> vtkExternalOpenGLCamera::SetModelViewTransformMatrix() >>>>>> >>>>>> Thanks, >>>>>> Sankhesh >>>>>> ? >>>>>> >>>>>> On Wed, Jul 19, 2017 at 9:59 AM elainejiang8 >>>>>> wrote: >>>>>> >>>>>>> Hi everyone! >>>>>>> >>>>>>> I'm building a program that uses the externalVTKWidget to volume >>>>>>> render an >>>>>>> object in an OpenGL context. Right now, I'm calling >>>>>>> >>>>>>> *ren->GetActiveCamera(); >>>>>>> * >>>>>>> >>>>>>> (where ren is a vtkExternalOpenGLRenderWindow instance) in my render >>>>>>> function so I can control the position and focal point of the camera. >>>>>>> However, I'm unable to get the camera to actually have any effect on >>>>>>> the >>>>>>> scene. The documentation for vtkExternalOpenGLCamera is rather slim, >>>>>>> and I >>>>>>> can't find any similar examples, so I am a bit stuck on this issue. >>>>>>> >>>>>>> Does anyone have any insight into how I could approach this problem? >>>>>>> Thanks >>>>>>> in advance! >>>>>>> >>>>>>> Elaine >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> View this message in context: >>>>>>> http://vtk.1045678.n5.nabble.com/Using-vtkExternalOpenGLCamera-tp5744015.html >>>>>>> Sent from the VTK - Users mailing list archive at Nabble.com. >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>>> >>>>>> -- >>>>>> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >>>>>> | (518) 881-4417 >>>>>> ? >>>>>> >>>>> >>>>> -- >>>> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >>>> | (518) 881-4417 >>>> ? >>>> >>> >>> -- >> Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware >> | (518) 881-4417 >> ? >> > > -- Sankhesh Jhaveri *Sr. Research & Development Engineer* | Kitware | (518) 881-4417 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bebe0705 at colorado.edu Thu Jul 20 20:25:20 2017 From: bebe0705 at colorado.edu (BBerco) Date: Thu, 20 Jul 2017 17:25:20 -0700 (MST) Subject: [vtkusers] QVTK Widget odd behavior on Ubuntu 16.10 and NVidia GPU: In-Reply-To: <000001d30152$1bd6bbc0$53843340$@gmail.com> References: <1500475655836-5744016.post@n5.nabble.com> <1500478215092-5744018.post@n5.nabble.com> <1500526028122-5744038.post@n5.nabble.com> <000001d30152$1bd6bbc0$53843340$@gmail.com> Message-ID: <1500596720892-5744087.post@n5.nabble.com> Robert, thanks a lot! I found the culprit by comparing my code to yours (which was working fine on my system). The problem was that I was overwriting the vtkRenderWindowInteractor of the main window, instead of using the one already instantiated from render_window -> GetInterator(). Many thanks, Ben -- View this message in context: http://vtk.1045678.n5.nabble.com/QVTK-Widget-odd-behavior-on-Ubuntu-16-10-and-NVidia-GPU-tp5744016p5744087.html Sent from the VTK - Users mailing list archive at Nabble.com. From judith.schulte1191 at gmail.com Fri Jul 21 04:00:04 2017 From: judith.schulte1191 at gmail.com (Judith Schulte) Date: Fri, 21 Jul 2017 10:00:04 +0200 Subject: [vtkusers] vtkProcrustesAlignmentFilter Message-ID: Hi everyone, I am using the vtkProcrustesAlignmentFilter to align meshes. It works fine if the meshes have the same number of points. But the meshes that I use have different number of points and I know that the ProcrustesAlignmentFilter needs the same number of points. Therefore I tried to downsample the number of points of the meshes with the function cleanPolyData. The downsampling with this function is working but I cannot set the number of points, only the tolerance. So after this cleaning the meshes will still have a different number of points. Do you have any suggestions, how I can downsample the meshes to get the same number of points? Because I want to align a set of meshes and therefore the Procrustes Alignment will be very helpful. With ICP I can only align two point sets. Thanks in Advance! Judith -------------- next part -------------- An HTML attachment was scrubbed... URL: From coyarzunlaura at googlemail.com Fri Jul 21 04:43:09 2017 From: coyarzunlaura at googlemail.com (Cristina Oyarzun) Date: Fri, 21 Jul 2017 10:43:09 +0200 Subject: [vtkusers] VTK-js: how to read a .json file Message-ID: Dear all, I visualized several actors using VTK-js. Now I want to read a .json file and according to the information that it is included there assign different colors to the actors. Unfortunately as soon as I try to use the Build-in modules of Node.js I start getting errors. I didnt manage to find out how do I have to adapt the "webpack.config.js" (or the "package.json"?) so that it works. I found somewhere in a forum that it should work by adding " target: 'node' " to the webpack.config.js but it didnt. Any help would be great! Thank you! Cristina -------------- next part -------------- An HTML attachment was scrubbed... URL: From taron2000 at gmx.de Fri Jul 21 05:21:18 2017 From: taron2000 at gmx.de (Taron) Date: Fri, 21 Jul 2017 02:21:18 -0700 (MST) Subject: [vtkusers] VTK 8.0.0 OpenGL2 Invisible surfaces Message-ID: <1500628878599-5744093.post@n5.nabble.com> Hi there, I have found a strange thing switching to the new Backend OpenGL2. When I render surfaces it seems that only one side of a face is rendered and the other is not. Front & Backface-Culling is off for those Actors. This worked perfectly fine with the old Backend. Strangely enough when I turn on Depth-Peeling in the renderer the faces are rendered correctly, although none of the actors has any transparency set to it. It is not driver related because I can reproduce this behaviour with mesa drivers as well. Everything takes place under Windows 10. It is an x64 Qt (5.9) app and im using the QVTKWidget. I also tried the QVTKOpenGLWidget, but it has the same issues. Any hints what goes wrong here? -- View this message in context: http://vtk.1045678.n5.nabble.com/VTK-8-0-0-OpenGL2-Invisible-surfaces-tp5744093.html Sent from the VTK - Users mailing list archive at Nabble.com. From rick at pile.com Fri Jul 21 06:13:42 2017 From: rick at pile.com (Rick Dailey) Date: Fri, 21 Jul 2017 03:13:42 -0700 (MST) Subject: [vtkusers] Delayloading VTK In-Reply-To: <1500373976551-5744000.post@n5.nabble.com> References: <1500373976551-5744000.post@n5.nabble.com> Message-ID: <1500632022857-5744095.post@n5.nabble.com> I have done this successfully using C++ and Win32. For other languages and OS, I don't know. With Win32 you can provide dll loading hooks and redirect any path. See this page on MSDN for an overview: https://msdn.microsoft.com/en-us/library/z9h1h6ty.aspx If you need more detailed information about implementing with VTK, let me know and I'll post more. -- View this message in context: http://vtk.1045678.n5.nabble.com/Delayloading-VTK-tp5744000p5744095.html Sent from the VTK - Users mailing list archive at Nabble.com. From fgr at lordsofts.com Fri Jul 21 06:44:20 2017 From: fgr at lordsofts.com (nolvis) Date: Fri, 21 Jul 2017 03:44:20 -0700 (MST) Subject: [vtkusers] triangle - triangle intersection VTK C++ Message-ID: <1500633860968-5744096.post@n5.nabble.com> I am bit confused how Triangle - triangle intersection works in VTK. When im using points commented as Shares an edge z = 0 it shows that intersection doesn't exist, but when im using points commented as Shares an edge z = 5 , i am getting intersection. Why is that? //VTK includes #include #include #include #include //render #include #include #include #include #include //polydata #include #include #include //default includes #include using namespace std; void displayPoly(vtkSmartPointer &polyData); int main(int , char *[]) { // Creates a polydata object vtkSmartPointer polyData = vtkSmartPointer::New(); // creates a point object vtkSmartPointer points = vtkSmartPointer::New(); //Shares an edge z = 5 points->InsertNextPoint ( 0.0, 0.0, 0.0 ); points->InsertNextPoint ( 5.0, 0.0, 0.0 ); points->InsertNextPoint ( 0.0, 5.0, 0.0 ); points->InsertNextPoint ( 0.0, 5.0, 0.0 ); points->InsertNextPoint ( 5.0, 0.0, 0.0 ); points->InsertNextPoint ( 10.0, 10.0, 5.0 ); //Shares an edge z = 0 // points->InsertNextPoint ( 0.0, 0.0, 0.0 ); // points->InsertNextPoint ( 5.0, 0.0, 0.0 ); // points->InsertNextPoint ( 0.0, 5.0, 0.0 ); // points->InsertNextPoint ( 0.0, 5.0, 0.0 ); // points->InsertNextPoint ( 5.0, 0.0, 0.0 ); // points->InsertNextPoint ( 10.0, 10.0, 0.0 ); vtkSmartPointer triangles = vtkSmartPointer::New(); for(int i = 0; i < 2; i++){ vtkSmartPointer triangle = vtkSmartPointer::New(); triangle->GetPointIds()->SetId ( 0, i*3 ); triangle->GetPointIds()->SetId ( 1, i*3+1 ); triangle->GetPointIds()->SetId ( 2, i*3 + 2 ); //add the triangles to the list of triangles triangles->InsertNextCell ( triangle ); } polyData->SetPoints ( points ); polyData->SetPolys ( triangles ); vtkSmartPointer cells = vtkSmartPointer::New(); cells = polyData->GetPolys(); cells->InitTraversal(); vtkSmartPointer idList = vtkSmartPointer::New(); vtkSmartPointer filter = vtkSmartPointer::New(); while(cells->GetNextCell(idList)) { vtkIdType i = cells->GetTraversalLocation(); double a[3], b[3], c[3]; polyData->GetPoint(idList->GetId(0), a); polyData->GetPoint(idList->GetId(1), b); polyData->GetPoint(idList->GetId(2), c); while(cells->GetNextCell(idList)){ double e[3], f[3], g[3], pt1[3], pt2[3], surfaceid[2], tolerance; polyData->GetPoint(idList->GetId(0), e); polyData->GetPoint(idList->GetId(1), f); polyData->GetPoint(idList->GetId(2), g); int coplanar; int intersect = filter->TriangleTriangleIntersection(a, b, c, e, f, g, coplanar, pt1, pt2, surfaceid, tolerance); if(intersect == 1){ cout << "triangle to compare with" << endl; cout << a[0] << " " << a[1] << " " << a[2] << endl; cout << b[0] << " " << b[1] << " " << b[2] << endl; cout << c[0] << " " << c[1] << " " << c[2] << endl; cout << "comperable triangle" << endl; cout << e[0] << " " << e[1] << " " << e[2] << endl; cout << f[0] << " " << f[1] << " " << f[2] << endl; cout << g[0] << " " << g[1] << " " << g[2] << endl; cout << "Intersection of triangles" << endl << endl; cout << "coplanar: " << coplanar << endl; cout << "pt1: " << pt1[0] << " " << pt1[1] << " " << pt1[2] << endl; cout << "pt2: " << pt2[0] << " " << pt2[1] << " " << pt2[2] << endl; cout << "surfid: " << surfaceid[0] << " " << surfaceid[1] << endl; cout << "tolerance: " << tolerance << endl; cout << "Intersect: " << intersect << endl; } } cells->SetTraversalLocation(i); } displayPoly(polyData); } void displayPoly(vtkSmartPointer &polyData){ //mapper vtkSmartPointer mapper = vtkSmartPointer::New(); mapper->SetInputDataObject(polyData); //actor vtkSmartPointer actor = vtkSmartPointer::New(); actor->SetMapper(mapper); actor->GetProperty()->SetRepresentationToWireframe(); //render vtkSmartPointer renderer = vtkSmartPointer::New(); vtkSmartPointer renderWindow = vtkSmartPointer::New(); renderWindow->AddRenderer(renderer); //renderWindow vtkSmartPointer renderWindowInteractor = vtkSmartPointer::New(); renderWindowInteractor->SetRenderWindow(renderWindow); renderer->AddActor(actor); renderWindow->Render(); renderWindowInteractor->Start(); } -- View this message in context: http://vtk.1045678.n5.nabble.com/triangle-triangle-intersection-VTK-C-tp5744096.html Sent from the VTK - Users mailing list archive at Nabble.com. From tj.corona at kitware.com Fri Jul 21 07:48:47 2017 From: tj.corona at kitware.com (TJ Corona) Date: Fri, 21 Jul 2017 07:48:47 -0400 Subject: [vtkusers] triangle - triangle intersection VTK C++ In-Reply-To: <1500633860968-5744096.post@n5.nabble.com> References: <1500633860968-5744096.post@n5.nabble.com> Message-ID: <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> I agree, this is rather confusing. The method vtkIntersectionPolyDataFilter::TriangleTriangleIntersection() sets the isCoplanar flag if the triangles are coplanar, and does not continue with the intersection calculation. In your first example, the triangles are coplanar, whereas in your second example they are not. This is deliberate, as the algorithm employed in vtkIntersectionPolyDataFilter keys off of this isCoplanar flag to traverse a different code path. I will post a MR today to update the documentation to reflect this. The good news is that there is also a method called vtkTriangle::TrianglesIntersect(). It will not return where the intersection occurs, but should correctly identify both of your triangles as intersecting. Would anybody be opposed to me changing the method name vtkIntersectionPolyDataFilter::TriangleTriangleIntersection() to better reflect the fact that it is not entirely general? Thomas J. Corona, Ph.D. Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4443 > On Jul 21, 2017, at 6:44 AM, nolvis wrote: > > > > I am bit confused how Triangle - triangle intersection works in VTK. When im > using points commented as Shares an edge z = 0 it shows that intersection > doesn't exist, but when im using points commented as Shares an edge z = 5 , > i am getting intersection. Why is that? > > //VTK includes > #include > #include > #include > #include > //render > #include > #include > #include > #include > #include > //polydata > #include > #include > #include > > //default includes > #include > using namespace std; > > void displayPoly(vtkSmartPointer &polyData); > > int main(int , char *[]) > { > // Creates a polydata object > vtkSmartPointer polyData = > vtkSmartPointer::New(); > > // creates a point object > vtkSmartPointer points = vtkSmartPointer::New(); > //Shares an edge z = 5 > points->InsertNextPoint ( 0.0, 0.0, 0.0 ); > points->InsertNextPoint ( 5.0, 0.0, 0.0 ); > points->InsertNextPoint ( 0.0, 5.0, 0.0 ); > points->InsertNextPoint ( 0.0, 5.0, 0.0 ); > points->InsertNextPoint ( 5.0, 0.0, 0.0 ); > points->InsertNextPoint ( 10.0, 10.0, 5.0 ); > > //Shares an edge z = 0 > // points->InsertNextPoint ( 0.0, 0.0, 0.0 ); > // points->InsertNextPoint ( 5.0, 0.0, 0.0 ); > // points->InsertNextPoint ( 0.0, 5.0, 0.0 ); > // points->InsertNextPoint ( 0.0, 5.0, 0.0 ); > // points->InsertNextPoint ( 5.0, 0.0, 0.0 ); > // points->InsertNextPoint ( 10.0, 10.0, 0.0 ); > > vtkSmartPointer triangles = > vtkSmartPointer::New(); > for(int i = 0; i < 2; i++){ > vtkSmartPointer triangle = > vtkSmartPointer::New(); > triangle->GetPointIds()->SetId ( 0, i*3 ); > triangle->GetPointIds()->SetId ( 1, i*3+1 ); > triangle->GetPointIds()->SetId ( 2, i*3 + 2 ); > > //add the triangles to the list of triangles > triangles->InsertNextCell ( triangle ); > } > > polyData->SetPoints ( points ); > polyData->SetPolys ( triangles ); > vtkSmartPointer cells = > vtkSmartPointer::New(); > cells = polyData->GetPolys(); > cells->InitTraversal(); > vtkSmartPointer idList = vtkSmartPointer::New(); > vtkSmartPointer filter = > vtkSmartPointer::New(); > > while(cells->GetNextCell(idList)) > { > vtkIdType i = cells->GetTraversalLocation(); > double a[3], b[3], c[3]; > polyData->GetPoint(idList->GetId(0), a); > polyData->GetPoint(idList->GetId(1), b); > polyData->GetPoint(idList->GetId(2), c); > > while(cells->GetNextCell(idList)){ > double e[3], f[3], g[3], pt1[3], pt2[3], surfaceid[2], tolerance; > polyData->GetPoint(idList->GetId(0), e); > polyData->GetPoint(idList->GetId(1), f); > polyData->GetPoint(idList->GetId(2), g); > > int coplanar; > int intersect = filter->TriangleTriangleIntersection(a, b, c, e, f, g, > coplanar, pt1, pt2, surfaceid, tolerance); > if(intersect == 1){ > cout << "triangle to compare with" << endl; > cout << a[0] << " " << a[1] << " " << a[2] << endl; > cout << b[0] << " " << b[1] << " " << b[2] << endl; > cout << c[0] << " " << c[1] << " " << c[2] << endl; > > cout << "comperable triangle" << endl; > cout << e[0] << " " << e[1] << " " << e[2] << endl; > cout << f[0] << " " << f[1] << " " << f[2] << endl; > cout << g[0] << " " << g[1] << " " << g[2] << endl; > cout << "Intersection of triangles" << endl << endl; > cout << "coplanar: " << coplanar << endl; > cout << "pt1: " << pt1[0] << " " << pt1[1] << " " << pt1[2] << endl; > cout << "pt2: " << pt2[0] << " " << pt2[1] << " " << pt2[2] << endl; > cout << "surfid: " << surfaceid[0] << " " << surfaceid[1] << endl; > cout << "tolerance: " << tolerance << endl; > cout << "Intersect: " << intersect << endl; > } > } > cells->SetTraversalLocation(i); > } > displayPoly(polyData); > } > > void displayPoly(vtkSmartPointer &polyData){ > //mapper > vtkSmartPointer mapper = > vtkSmartPointer::New(); > mapper->SetInputDataObject(polyData); > > //actor > vtkSmartPointer actor = vtkSmartPointer::New(); > actor->SetMapper(mapper); > actor->GetProperty()->SetRepresentationToWireframe(); > > //render > vtkSmartPointer renderer = > vtkSmartPointer::New(); > vtkSmartPointer renderWindow = > vtkSmartPointer::New(); > renderWindow->AddRenderer(renderer); > > //renderWindow > vtkSmartPointer renderWindowInteractor = > vtkSmartPointer::New(); > renderWindowInteractor->SetRenderWindow(renderWindow); > renderer->AddActor(actor); > renderWindow->Render(); > renderWindowInteractor->Start(); > } > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/triangle-triangle-intersection-VTK-C-tp5744096.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Fri Jul 21 08:24:27 2017 From: david.thompson at kitware.com (David Thompson) Date: Fri, 21 Jul 2017 08:24:27 -0400 Subject: [vtkusers] triangle - triangle intersection VTK C++ In-Reply-To: <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> References: <1500633860968-5744096.post@n5.nabble.com> <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> Message-ID: <2D3C0A8C-B4F7-4E15-936D-AB5E800B623F@kitware.com> > ... > Would anybody be opposed to me changing the method name vtkIntersectionPolyDataFilter::TriangleTriangleIntersection() to better reflect the fact that it is not entirely general? +1 but only if you use the VTK_LEGACY macros so people maintaining external apps have a chance to update. David From fgr at lordsofts.com Fri Jul 21 08:34:54 2017 From: fgr at lordsofts.com (nolvis) Date: Fri, 21 Jul 2017 05:34:54 -0700 (MST) Subject: [vtkusers] triangle - triangle intersection VTK C++ In-Reply-To: <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> References: <1500633860968-5744096.post@n5.nabble.com> <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> Message-ID: <1500640494986-5744099.post@n5.nabble.com> Changing my code from TriangleTriangleIntersect() to TrianglesIntersect(), it seems to still give me some headache. I am still bit confused as why it returns 0, even if triangles go in to each other. Am i missing something? Picture: http://imgur.com/a/PMcRk //1st triangle coordinates 0.0, 0.0, 0.0 5.0, 0.0, 0.0 0.0, 5.0, 0.0 //2nd triangle coordinates 10.0, 5.0, 0.0 5.0, 10.0, 0.0 1.0, 1.0, 0.0 -- View this message in context: http://vtk.1045678.n5.nabble.com/triangle-triangle-intersection-VTK-C-tp5744096p5744099.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Fri Jul 21 09:36:15 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 21 Jul 2017 09:36:15 -0400 Subject: [vtkusers] VTK 8.0.0 OpenGL2 Invisible surfaces In-Reply-To: <1500628878599-5744093.post@n5.nabble.com> References: <1500628878599-5744093.post@n5.nabble.com> Message-ID: VTK thinks your surface is translucent. The logic changed in OpenGL2 and so something in your object indicates the possibility of transparency. The options include - opacity < 1.0 - a lookup table/ color transfer function with some opacity values < 1.0 - a texture map with (< 1.0?) alpha values You can force VTK to treat your object as Opaque using the ForceOpaqe option on Actor/Property one of those I think. On Fri, Jul 21, 2017 at 5:21 AM, Taron wrote: > Hi there, > > I have found a strange thing switching to the new Backend OpenGL2. When I > render surfaces it seems that only one side of a face is rendered and the > other is not. Front & Backface-Culling is off for those Actors. > This worked perfectly fine with the old Backend. Strangely enough when I > turn on Depth-Peeling in the renderer the faces are rendered correctly, > although none of the actors has any transparency set to it. > It is not driver related because I can reproduce this behaviour with mesa > drivers as well. > Everything takes place under Windows 10. It is an x64 Qt (5.9) app and im > using the QVTKWidget. > I also tried the QVTKOpenGLWidget, but it has the same issues. > > Any hints what goes wrong here? > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/VTK-8-0-0-OpenGL2-Invisible-surfaces-tp5744093.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 ken.martin at kitware.com Fri Jul 21 09:45:59 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 21 Jul 2017 09:45:59 -0400 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1500569102114-5744068.post@n5.nabble.com> References: <1500569102114-5744068.post@n5.nabble.com> Message-ID: My quick thoughts on this are (1) There have been some fixes in object destruction that may fix this issue in newer versions of VTK. (2) I believe vtkSystemTools includes support for printing stack traces. If this happens on a debug build adding some code there to print a stack trace prior to the assert (but when the assert will fail) could help narrow down who is trying to bind a freed (or never created) texture. If not in System tools I know windows has fairly lightweight stack printing code that could be pasted in. Even with a stack trace these can sometimes be tricky to track down as sometimes the issue revolves around not who is using the texture after deletion, but who deleted it. But even then the issue can be tracked down given time and some extra logging. If it only happens on release (and not reldebinfo) builds then it gets tougher. On Thu, Jul 20, 2017 at 12:45 PM, Rick Dailey wrote: > This is an ongoing issue I have had since starting my project with VTK 6.3 > until today when I am using 7.1.1. I have seen it mentioned many times by > other users and no one has been able to help. I even had VTK paid support > for over a year and even working directly with a Kitware engineer failed to > the problem. > > There are many times when I will display a 3D object and numerous errors > related to vtkTextureObject will be generated. The result is that I get > notified of these errors and my object does not display. > > The first problem occurs here, on the second line, assert(this->Handle). > Note that nowhere in my code do I explicitly use a vtkTextureObject. It is > my understanding that VTK must use this object for displaying text, even > when the text is a solid color, so if I don't specify a texture then a > default is created. > > void vtkTextureObject::Bind() > { > assert(this->Context); > assert(this->Handle); > ... > } > > The next error occurs here: > > void vtkTextureObject::SendParameters() > { > assert("pre: is_bound" && this->IsBound()); > ... > } > > Unfortunately, I am unable to provide sample code that reliably > demonstrates > this issue. The software it is used in is a commercial release which is > quite large and not open-source. Out of the hundreds of users of this > software, approximately one half report the bug. Many attempts at creating > a demo had varying results. I was able to create one demo that failed on > half the computers I tried it on but no one at Kitware could duplicate > them. > There are many things I tried at the suggestion of Kitware and I will try > to > organize a list at some time in the future. > > > > > > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 tj.corona at kitware.com Fri Jul 21 09:50:45 2017 From: tj.corona at kitware.com (TJ Corona) Date: Fri, 21 Jul 2017 09:50:45 -0400 Subject: [vtkusers] triangle - triangle intersection VTK C++ In-Reply-To: <1500640494986-5744099.post@n5.nabble.com> References: <1500633860968-5744096.post@n5.nabble.com> <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> <1500640494986-5744099.post@n5.nabble.com> Message-ID: <20CCE090-8B28-44E9-B9DC-7F312BA0F78B@kitware.com> > Changing my code from TriangleTriangleIntersect() to TrianglesIntersect(), it > seems to still give me some headache. > I am still bit confused as why it returns 0, even if triangles go in to each > other. Is ?it? the vtkIntersectionPolyDataFilter::TriangleTriangleIntersect() method or the vtkTriangle::TrianglesIntersect() method? If the former, then the triangles are again coplanar. Please see vtkIntersectionPolyDataFilter.cxx:2060, where the method exits without continuing the calculation. If the latter, then the method should return true for the triangles intersecting. If it doesn?t then this is a bug. Thomas J. Corona, Ph.D. Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4443 > On Jul 21, 2017, at 8:34 AM, nolvis wrote: > > Changing my code from TriangleTriangleIntersect() to TrianglesIntersect(), it > seems to still give me some headache. > I am still bit confused as why it returns 0, even if triangles go in to each > other. > Am i missing something? > > Picture: http://imgur.com/a/PMcRk > > //1st triangle coordinates > 0.0, 0.0, 0.0 > 5.0, 0.0, 0.0 > 0.0, 5.0, 0.0 > //2nd triangle coordinates > 10.0, 5.0, 0.0 > 5.0, 10.0, 0.0 > 1.0, 1.0, 0.0 > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/triangle-triangle-intersection-VTK-C-tp5744096p5744099.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fgr at lordsofts.com Fri Jul 21 10:06:57 2017 From: fgr at lordsofts.com (nolvis) Date: Fri, 21 Jul 2017 07:06:57 -0700 (MST) Subject: [vtkusers] triangle - triangle intersection VTK C++ In-Reply-To: <20CCE090-8B28-44E9-B9DC-7F312BA0F78B@kitware.com> References: <1500633860968-5744096.post@n5.nabble.com> <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> <1500640494986-5744099.post@n5.nabble.com> <20CCE090-8B28-44E9-B9DC-7F312BA0F78B@kitware.com> Message-ID: <1500646017410-5744104.post@n5.nabble.com> I am using now vtkTriangle::TrianglesIntersect() method. Link to the source code: https://pastebin.com/7bi1UHtN Maybe it's something wrong with my code. -- View this message in context: http://vtk.1045678.n5.nabble.com/triangle-triangle-intersection-VTK-C-tp5744096p5744104.html Sent from the VTK - Users mailing list archive at Nabble.com. From aron.helser at kitware.com Fri Jul 21 10:57:48 2017 From: aron.helser at kitware.com (Aron Helser) Date: Fri, 21 Jul 2017 10:57:48 -0400 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Hi Cristina, ParaViewWeb uses this webpack 1.x loader: { test: /\.json$/, loader: 'json-loader', }, That should allow you to 'include' a json file in your javascript, and then you might need to use the built-in JSON.parse() to turn it into an object. Regards, Aron On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < vtkusers at vtk.org> wrote: > Dear all, > > I visualized several actors using VTK-js. Now I want to read a .json file > and according to the information that it is included there assign different > colors to the actors. > > Unfortunately as soon as I try to use the Build-in modules of Node.js I > start getting errors. I didnt manage to find out how do I have to adapt the > "webpack.config.js" (or the "package.json"?) so that it works. > > I found somewhere in a forum that it should work by adding " target: > 'node' " to the webpack.config.js but it didnt. Any help would be great! > > Thank you! > Cristina > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Fri Jul 21 11:50:45 2017 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 21 Jul 2017 09:50:45 -0600 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Hi Cristina, In vtk.js we now use webpack2 (in master at least, you may have picked an older version though), and the webpack2 documentation states that you no longer need a loader for json: https://webpack.js.org/guides/migrating/#json-loader-is-not-required-anymore Is your project also using webpack2? In that case you shouldn't need the json loader. Also, when you refer to "Build-in modules of Node.js", does that refer specifically to this: https://github.com/sindresorhus/builtin-modules or do you mean something else? Cheers, Scott On Fri, Jul 21, 2017 at 8:57 AM, Aron Helser wrote: > Hi Cristina, > ParaViewWeb uses this webpack 1.x loader: > { > test: /\.json$/, > loader: 'json-loader', > }, > That should allow you to 'include' a json file in your javascript, and > then you might need to use the built-in JSON.parse() to turn it into an > object. > > Regards, > Aron > > On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < > vtkusers at vtk.org> wrote: > >> Dear all, >> >> I visualized several actors using VTK-js. Now I want to read a .json file >> and according to the information that it is included there assign different >> colors to the actors. >> >> Unfortunately as soon as I try to use the Build-in modules of Node.js I >> start getting errors. I didnt manage to find out how do I have to adapt the >> "webpack.config.js" (or the "package.json"?) so that it works. >> >> I found somewhere in a forum that it should work by adding " target: >> 'node' " to the webpack.config.js but it didnt. Any help would be great! >> >> Thank you! >> Cristina >> >> _______________________________________________ >> 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 >> >> > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tj.corona at kitware.com Fri Jul 21 11:53:31 2017 From: tj.corona at kitware.com (TJ Corona) Date: Fri, 21 Jul 2017 11:53:31 -0400 Subject: [vtkusers] triangle - triangle intersection VTK C++ In-Reply-To: <1500646017410-5744104.post@n5.nabble.com> References: <1500633860968-5744096.post@n5.nabble.com> <3BA86D89-268E-44AF-B0AC-97A12166FDFF@kitware.com> <1500640494986-5744099.post@n5.nabble.com> <20CCE090-8B28-44E9-B9DC-7F312BA0F78B@kitware.com> <1500646017410-5744104.post@n5.nabble.com> Message-ID: <8C3EAC3D-F9DE-45F8-9741-47886CA2F913@kitware.com> This is indeed a bug. Thank you for issuing a bug report. Thomas J. Corona, Ph.D. Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4443 > On Jul 21, 2017, at 10:06 AM, nolvis wrote: > > I am using now vtkTriangle::TrianglesIntersect() method. > > Link to the source code: https://pastebin.com/7bi1UHtN > > Maybe it's something wrong with my code. > > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/triangle-triangle-intersection-VTK-C-tp5744096p5744104.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vtk12af6bc42 at kant.sophonet.de Fri Jul 21 12:19:16 2017 From: vtk12af6bc42 at kant.sophonet.de (Sophonet) Date: Fri, 21 Jul 2017 18:19:16 +0200 Subject: [vtkusers] VTK 8.0.0 OpenGL2 Invisible surfaces In-Reply-To: <1500628878599-5744093.post@n5.nabble.com> References: <1500628878599-5744093.post@n5.nabble.com> Message-ID: I can confirm this and have seen the exact same effect here on OpenGL2. Likewise, I do not have any transparency set in my colors. Interestingly, it does not happen to all vtkPolyData objects that I have, but only to some of them. The platform is similar to mine and I can add that the problem also occurs when having openGL Mesa-library-dlls extracted in the executable folder, so it does not seem to be a driver problem. So it might actually be a bug in VTK? On 2017-07-21 11:21, Taron wrote: > Hi there, > > I have found a strange thing switching to the new Backend OpenGL2. When > I > render surfaces it seems that only one side of a face is rendered and > the > other is not. Front & Backface-Culling is off for those Actors. > This worked perfectly fine with the old Backend. Strangely enough when > I > turn on Depth-Peeling in the renderer the faces are rendered correctly, > although none of the actors has any transparency set to it. > It is not driver related because I can reproduce this behaviour with > mesa > drivers as well. > Everything takes place under Windows 10. It is an x64 Qt (5.9) app and > im > using the QVTKWidget. > I also tried the QVTKOpenGLWidget, but it has the same issues. > > Any hints what goes wrong here? > > > > > > -- > View this message in context: > http://vtk.1045678.n5.nabble.com/VTK-8-0-0-OpenGL2-Invisible-surfaces-tp5744093.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 From tapash1991 at gmail.com Fri Jul 21 12:34:12 2017 From: tapash1991 at gmail.com (Tapash Barman) Date: Fri, 21 Jul 2017 09:34:12 -0700 (MST) Subject: [vtkusers] Fetal error Message-ID: <1500654852272-5744112.post@n5.nabble.com> hiii..I am try to run a simple program of vtk downloaded from http://www.vtk.org/Wiki/VTK/Examples..but when I am trying to run the code it giving the linking error saying LINK : fatal error LNK1104: cannot open file 'Qt5::OpenGL.lib'..plz help -- View this message in context: http://vtk.1045678.n5.nabble.com/Fetal-error-tp5744112.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Fri Jul 21 12:46:33 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 21 Jul 2017 12:46:33 -0400 Subject: [vtkusers] VTK 8.0.0 OpenGL2 Invisible surfaces In-Reply-To: References: <1500628878599-5744093.post@n5.nabble.com> Message-ID: Show me an example and maybe I can show you what VTK thinks is translucent. Sometimes folks forget about LUTs and textures which can include transparency. Alternatively if you set ForceOpaque and the problem goes away, then that confirms it. On Fri, Jul 21, 2017 at 12:19 PM, Sophonet wrote: > I can confirm this and have seen the exact same effect here on OpenGL2. > Likewise, I do not have any transparency set in my colors. Interestingly, > it does not happen to all vtkPolyData objects that I have, but only to some > of them. > > The platform is similar to mine and I can add that the problem also occurs > when having openGL Mesa-library-dlls extracted in the executable folder, so > it does not seem to be a driver problem. > > So it might actually be a bug in VTK? > > > On 2017-07-21 11:21, Taron wrote: > >> Hi there, >> >> I have found a strange thing switching to the new Backend OpenGL2. When I >> render surfaces it seems that only one side of a face is rendered and the >> other is not. Front & Backface-Culling is off for those Actors. >> This worked perfectly fine with the old Backend. Strangely enough when I >> turn on Depth-Peeling in the renderer the faces are rendered correctly, >> although none of the actors has any transparency set to it. >> It is not driver related because I can reproduce this behaviour with mesa >> drivers as well. >> Everything takes place under Windows 10. It is an x64 Qt (5.9) app and im >> using the QVTKWidget. >> I also tried the QVTKOpenGLWidget, but it has the same issues. >> >> Any hints what goes wrong here? >> >> >> >> >> >> -- >> View this message in context: >> http://vtk.1045678.n5.nabble.com/VTK-8-0-0-OpenGL2-Invisible >> -surfaces-tp5744093.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 mikewithascarf at yahoo.com Fri Jul 21 14:16:44 2017 From: mikewithascarf at yahoo.com (mikewithascarf) Date: Fri, 21 Jul 2017 11:16:44 -0700 (MST) Subject: [vtkusers] image rendering speed Message-ID: <1500661004209-5744115.post@n5.nabble.com> Hi! I'm attempting to speed up some image rendering (lots of images in sequence). Right now rendering time varies a lot, anywhere between 0.001 and 0.059 seconds. Here is my pipeline: vtkImageData (3D) -> vtkImageReslice -> vtkImageMapToColors (using a lookup table with color/opacity) -> vtkImageActor -> vtkRenderer -> QVTKWidget I move the vtkImageReslice through the 3D volume, displaying images as I go. Is there any way to speed things up? I'm in release mode, using a NVidia GTX 1070. If I could get it to always be less than 0.012 seconds that would be great. Here are example timings for multiple frames in a row: 0.001 s 0.006 s 0.059 s 0.002 s 0.014 s 0.003 s 0.013 s 0.011 s 0.036 s 0.001 s 0.038 s 0.001 s 0.028 s 0.001 s It's not even consistent per image. If I run the same test multiple times, different frames will have very different render times. Any help would be awesome! Mike -- View this message in context: http://vtk.1045678.n5.nabble.com/image-rendering-speed-tp5744115.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Fri Jul 21 14:32:03 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 21 Jul 2017 14:32:03 -0400 Subject: [vtkusers] image rendering speed In-Reply-To: <1500661004209-5744115.post@n5.nabble.com> References: <1500661004209-5744115.post@n5.nabble.com> Message-ID: Be aware that in the new OpenGL2 backend rendering is asynchronous. That is VTK sends commands to the OpenGL hardware and continues processing. When the OpenGL hardware gets around to executing those commands is up to the hardware. Fortunately there is vtkRenderTimerLog which I believe works quite well as of a month or two ago. See TestGPURayCastDepthPeeling.cxx in VTK for an example of its usage. Below is some sample output - 100.0% 63.655 ms "vtkRenderWindow::Render" - 98.2% 62.535 ms "vtkRenderer::Render this=@0x2437a80 Layer=0" - 0.0% 0.001 ms "Culling props" - 100.0% 62.532 ms "DeviceRender" - 0.0% 0.025 ms "vtkRenderer::UpdateCamera" - 0.0% 0.001 ms "vtkRenderer::UpdateLightGeometry" - 0.0% 0.001 ms "vtkOpenGLRenderer::UpdateLights" - 100.0% 62.501 ms "vtkOpenGLRenderer::UpdateGeometry" - 0.0% 0.015 ms "Opaque Geometry" - 100.0% 62.481 ms "Translucent Geometry" - 100.0% 62.479 ms "vtkDualDepthPeelingPass::Render" - 0.0% 0.001 ms "vtkDualDepthPeelingPass::Initialize" - 4.1% 2.586 ms "vtkDualDepthPeelingPass::Prepare" - 95.0% 2.457 ms "vtkDualDepthPeelingPass::CopyOpaqueDepthBuffer" - 4.0% 0.103 ms "vtkDualDepthPeelingPass::InitializeDepth" - 98.4% 0.102 ms "vtkDualDepthPeelingPass::RenderTranslucentPass" - 51.2% 31.968 ms "vtkDualDepthPeelingPass::PeelVolumesOutsideTranslucentRange" - 100.0% 31.966 ms "vtkDualDepthPeelingPass::RenderVolumetricPass" - 30.4% 19.021 ms "vtkDualDepthPeelingPass::Peel" - 0.4% 0.074 ms "vtkDualDepthPeelingPass::InitializeTargetsForTranslucentPass" - 86.4% 0.064 ms "vtkDualDepthPeelingPass::CopyFrontSourceToFrontDestination" - 0.6% 0.123 ms "vtkDualDepthPeelingPass::PeelTranslucentGeometry" - 98.7% 0.122 ms "vtkDualDepthPeelingPass::RenderTranslucentPass" - 0.2% 0.044 ms "vtkDualDepthPeelingPass::BlendBackBuffer" - 2.5% 0.466 ms "vtkDualDepthPeelingPass::EndTranslucentOcclusionQuery" - 0.3% 0.049 ms "vtkDualDepthPeelingPass::InitializeTargetsForVolumetricPass" - 90.2% 0.045 ms "vtkDualDepthPeelingPass::CopyFrontSourceToFrontDestination" - 88.7% 16.878 ms "vtkDualDepthPeelingPass::PeelVolumeGeometry" - 100.0% 16.876 ms "vtkDualDepthPeelingPass::RenderVolumetricPass" - 0.2% 0.044 ms "vtkDualDepthPeelingPass::BlendBackBuffer" - 7.0% 1.330 ms "vtkDualDepthPeelingPass::EndVolumetricOcclusionQuery" - 10.2% 6.349 ms "vtkDualDepthPeelingPass::Peel" - 1.2% 0.075 ms "vtkDualDepthPeelingPass::InitializeTargetsForTranslucentPass" - 87.5% 0.065 ms "vtkDualDepthPeelingPass::CopyFrontSourceToFrontDestination" - 2.0% 0.124 ms "vtkDualDepthPeelingPass::PeelTranslucentGeometry" - 98.7% 0.123 ms "vtkDualDepthPeelingPass::RenderTranslucentPass" - 0.7% 0.044 ms "vtkDualDepthPeelingPass::BlendBackBuffer" - 8.9% 0.565 ms "vtkDualDepthPeelingPass::EndTranslucentOcclusionQuery" - 0.8% 0.049 ms "vtkDualDepthPeelingPass::InitializeTargetsForVolumetricPass" - 90.2% 0.045 ms "vtkDualDepthPeelingPass::CopyFrontSourceToFrontDestination" - 76.8% 4.878 ms "vtkDualDepthPeelingPass::PeelVolumeGeometry" - 100.0% 4.876 ms "vtkDualDepthPeelingPass::RenderVolumetricPass" - 0.7% 0.044 ms "vtkDualDepthPeelingPass::BlendBackBuffer" - 8.9% 0.563 ms "vtkDualDepthPeelingPass::EndVolumetricOcclusionQuery" - 4.0% 2.492 ms "vtkDualDepthPeelingPass::Peel" - 3.0% 0.074 ms "vtkDualDepthPeelingPass::InitializeTargetsForTranslucentPass" - 87.7% 0.065 ms "vtkDualDepthPeelingPass::CopyFrontSourceToFrontDestination" - 4.9% 0.123 ms "vtkDualDepthPeelingPass::PeelTranslucentGeometry" - 98.7% 0.121 ms "vtkDualDepthPeelingPass::RenderTranslucentPass" - 1.7% 0.043 ms "vtkDualDepthPeelingPass::BlendBackBuffer" - 12.7% 0.315 ms "vtkDualDepthPeelingPass::EndTranslucentOcclusionQuery" - 2.0% 0.049 ms "vtkDualDepthPeelingPass::InitializeTargetsForVolumetricPass" - 90.2% 0.044 ms "vtkDualDepthPeelingPass::CopyFrontSourceToFrontDestination" - 53.7% 1.338 ms "vtkDualDepthPeelingPass::PeelVolumeGeometry" - 99.9% 1.337 ms "vtkDualDepthPeelingPass::RenderVolumetricPass" - 1.8% 0.044 ms "vtkDualDepthPeelingPass::BlendBackBuffer" - 20.0% 0.498 ms "vtkDualDepthPeelingPass::EndVolumetricOcclusionQuery" - 0.1% 0.056 ms "vtkDualDepthPeelingPass::Finalize" - 94.8% 0.053 ms "vtkDualDepthPeelingPass::BlendFinalImage" - 0.0% 0.001 ms "Overlay" - 1.8% 1.118 ms "glXSwapBuffers (may stall for VSync)" On Fri, Jul 21, 2017 at 2:16 PM, mikewithascarf via vtkusers < vtkusers at vtk.org> wrote: > Hi! I'm attempting to speed up some image rendering (lots of images in > sequence). Right now rendering time varies a lot, anywhere between 0.001 > and > 0.059 seconds. Here is my pipeline: > > vtkImageData (3D) -> vtkImageReslice -> vtkImageMapToColors (using a lookup > table with color/opacity) -> vtkImageActor -> vtkRenderer -> QVTKWidget > > I move the vtkImageReslice through the 3D volume, displaying images as I > go. > Is there any way to speed things up? I'm in release mode, using a NVidia > GTX > 1070. If I could get it to always be less than 0.012 seconds that would be > great. Here are example timings for multiple frames in a row: > > 0.001 s > 0.006 s > 0.059 s > 0.002 s > 0.014 s > 0.003 s > 0.013 s > 0.011 s > 0.036 s > 0.001 s > 0.038 s > 0.001 s > 0.028 s > 0.001 s > > It's not even consistent per image. If I run the same test multiple times, > different frames will have very different render times. Any help would be > awesome! > > Mike > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/image-rendering-speed-tp5744115.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 adarshdesai.dsp at gmail.com Fri Jul 21 14:37:46 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Fri, 21 Jul 2017 11:37:46 -0700 Subject: [vtkusers] Problem with shadows In-Reply-To: References: Message-ID: previously forgot to add VTKusers list.. forwarding same mail. Hi, Thank you for the input. I have tried with new Normals, its the same. I dont think there is an issue with normals. When Poly data appears on screen, it will be in darkness(shadow). I need to turn off every shadow in the renderer. I am using Renderer->UseShadowsOff(), still no use. Please someone guide me to turn off all shadows in the scene. Just like how the Cube source appears in the renderer. Thanks On Thu, Jul 20, 2017 at 3:52 PM, abcd efgh wrote: > Hi, > > Thank you for the input. I have tried with new Normals, its the same. > I dont think there is an issue with normals. When Poly data appears on > screen, it will be in darkness(shadow). > I need to turn off every shadow in the renderer. I am using > Renderer->UseShadowsOff(), still no use. > > Please someone guide me to turn off all shadows in the scene. Just like > how the Cube source appears in the renderer. > > Thanks > > On Mon, Jul 17, 2017 at 12:06 PM, David Gobbi > wrote: > >> If it isn't the scalars, then it is probably the normals. If the data >> has bad normals, then lighting of the data will be incorrect. >> >> You can try generating new normals for the data with vtkPolyDataNormals. >> Make sure that you read the documentation for this class, it has lots of >> options. >> >> - David >> >> >> On Mon, Jul 17, 2017 at 12:31 PM, abcd efgh >> wrote: >> >>> Thanks, >>> if I turn off scalars then I see only white color, by the way even >>> after that I see the shadow effects, how can I turn off the shadows in the >>> scene completely. >>> I think the problem is with respect to shadows. >>> >>> Thanks again. >>> >>> On Sun, Jul 16, 2017 at 5:21 AM, David Gobbi >>> wrote: >>> >>>> Clipping a data set adds scalars to the data set. These scalars are >>>> probably causing the strange coloring that you are seeing. You can tell the >>>> mapper to ignore the scalars, and use the vtkProperty color instead: >>>> >>>> mapper->ScalarVisibilityOff(); >>>> >>>> - David >>>> >>>> On Sun, Jul 16, 2017 at 2:15 AM, abcd efgh >>>> wrote: >>>> >>>>> Hello, >>>>> >>>>> I am new to vtk. I have a 3D polydata, I cut it using vtkClipPolydata. >>>>> Now there are some shadow kind of thing, I have called functions to >>>>> turn off shadows >>>>> as well as backface culling as off. But still shadow kind of effect >>>>> remains and the Poly data is sometimes dark due to this. >>>>> >>>>> Thanks >>>>> >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lasso at queensu.ca Fri Jul 21 15:10:44 2017 From: lasso at queensu.ca (Andras Lasso) Date: Fri, 21 Jul 2017 19:10:44 +0000 Subject: [vtkusers] Delayloading VTK In-Reply-To: <1500632022857-5744095.post@n5.nabble.com> References: <1500373976551-5744000.post@n5.nabble.com> <1500632022857-5744095.post@n5.nabble.com> Message-ID: This functionality would be really useful. By having such a method, we could more confidently leave the old OpenGL backend and switch to OpenGL2. It would be great to have it as a built-in option in VTK, and for at least Windows, Linux, and Mac. I cannot offer much to help, just that if there is a solution available then I can test it on various Windows PCs. Andras -----Original Message----- From: vtkusers [mailto:vtkusers-bounces at vtk.org] On Behalf Of Rick Dailey Sent: Friday, July 21, 2017 6:14 AM To: vtkusers at vtk.org Subject: Re: [vtkusers] Delayloading VTK I have done this successfully using C++ and Win32. For other languages and OS, I don't know. With Win32 you can provide dll loading hooks and redirect any path. See this page on MSDN for an overview: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fz9h1h6ty.aspx&data=02%7C01%7Classo%40queensu.ca%7C2ba8435405b34fe8746308d4d0212cd2%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636362288275821443&sdata=NNkliP2hRa9AY8b0x8mXYe8I3d7jSC29OvvmAK888xc%3D&reserved=0 If you need more detailed information about implementing with VTK, let me know and I'll post more. -- View this message in context: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvtk.1045678.n5.nabble.com%2FDelayloading-VTK-tp5744000p5744095.html&data=02%7C01%7Classo%40queensu.ca%7C2ba8435405b34fe8746308d4d0212cd2%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636362288275821443&sdata=ZrvIyc7eTmcVSQwV3FLCK%2BNNuMeN0J1mt8QKRHDMeAY%3D&reserved=0 Sent from the VTK - Users mailing list archive at Nabble.com. _______________________________________________ Powered by https://na01.safelinks.protection.outlook.com/?url=www.kitware.com&data=02%7C01%7Classo%40queensu.ca%7C2ba8435405b34fe8746308d4d0212cd2%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636362288275821443&sdata=vOQpuRf75OVC4ecl6OO4wzk9%2F%2BhFaV1tuFj90EhtXVw%3D&reserved=0 Visit other Kitware open-source projects at https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kitware.com%2Fopensource%2Fopensource.html&data=02%7C01%7Classo%40queensu.ca%7C2ba8435405b34fe8746308d4d0212cd2%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636362288275821443&sdata=E86pGOZbOAgLar%2FRkUo0iZ7al0T9V1v3cupMZGnZGks%3D&reserved=0 Please keep messages on-topic and check the VTK FAQ at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vtk.org%2FWiki%2FVTK_FAQ&data=02%7C01%7Classo%40queensu.ca%7C2ba8435405b34fe8746308d4d0212cd2%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636362288275821443&sdata=2sAh0HDwK%2BhbYRMKDOTOfyQLw0lbmd%2BO%2BMc039il5dw%3D&reserved=0 Search the list archives at: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmarkmail.org%2Fsearch%2F%3Fq%3Dvtkusers&data=02%7C01%7Classo%40queensu.ca%7C2ba8435405b34fe8746308d4d0212cd2%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636362288275821443&sdata=RMSt7O0XY8sjOBH1hkpJ02QYYyLdT2IlY6chDaKNLJs%3D&reserved=0 Follow this link to subscribe/unsubscribe: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpublic.kitware.com%2Fmailman%2Flistinfo%2Fvtkusers&data=02%7C01%7Classo%40queensu.ca%7C2ba8435405b34fe8746308d4d0212cd2%7Cd61ecb3b38b142d582c4efb2838b925c%7C1%7C0%7C636362288275821443&sdata=vGzpzEJ4k3WIyqjlmcyunSh73uN0h%2BTRKOP7LftG5ZE%3D&reserved=0 From david.gobbi at gmail.com Fri Jul 21 15:12:03 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Fri, 21 Jul 2017 13:12:03 -0600 Subject: [vtkusers] Problem with shadows In-Reply-To: References: Message-ID: Can you attach a screenshot? My own experience with VTK tells me that it is very, very unlikely that you are seeing shadows. Whenever I see dark areas in VTK rendering, it is almost always due to the scalars, the normals, or the winding of the polydata. It could be that some of your polygons are wound incorrectly. On Fri, Jul 21, 2017 at 12:37 PM, abcd efgh wrote: > previously forgot to add VTKusers list.. forwarding same mail. > > Hi, > > Thank you for the input. I have tried with new Normals, its the same. > I dont think there is an issue with normals. When Poly data appears on > screen, it will be in darkness(shadow). > I need to turn off every shadow in the renderer. I am using > Renderer->UseShadowsOff(), still no use. > > Please someone guide me to turn off all shadows in the scene. Just like > how the Cube source appears in the renderer. > > Thanks > > On Thu, Jul 20, 2017 at 3:52 PM, abcd efgh > wrote: > >> Hi, >> >> Thank you for the input. I have tried with new Normals, its the same. >> I dont think there is an issue with normals. When Poly data appears on >> screen, it will be in darkness(shadow). >> I need to turn off every shadow in the renderer. I am using >> Renderer->UseShadowsOff(), still no use. >> >> Please someone guide me to turn off all shadows in the scene. Just like >> how the Cube source appears in the renderer. >> >> Thanks >> >> On Mon, Jul 17, 2017 at 12:06 PM, David Gobbi >> wrote: >> >>> If it isn't the scalars, then it is probably the normals. If the data >>> has bad normals, then lighting of the data will be incorrect. >>> >>> You can try generating new normals for the data with >>> vtkPolyDataNormals. Make sure that you read the documentation for this >>> class, it has lots of options. >>> >>> - David >>> >>> >>> On Mon, Jul 17, 2017 at 12:31 PM, abcd efgh >>> wrote: >>> >>>> Thanks, >>>> if I turn off scalars then I see only white color, by the way even >>>> after that I see the shadow effects, how can I turn off the shadows in the >>>> scene completely. >>>> I think the problem is with respect to shadows. >>>> >>>> Thanks again. >>>> >>>> On Sun, Jul 16, 2017 at 5:21 AM, David Gobbi >>>> wrote: >>>> >>>>> Clipping a data set adds scalars to the data set. These scalars are >>>>> probably causing the strange coloring that you are seeing. You can tell the >>>>> mapper to ignore the scalars, and use the vtkProperty color instead: >>>>> >>>>> mapper->ScalarVisibilityOff(); >>>>> >>>>> - David >>>>> >>>>> On Sun, Jul 16, 2017 at 2:15 AM, abcd efgh >>>>> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I am new to vtk. I have a 3D polydata, I cut it using vtkClipPolydata. >>>>>> Now there are some shadow kind of thing, I have called functions to >>>>>> turn off shadows >>>>>> as well as backface culling as off. But still shadow kind of effect >>>>>> remains and the Poly data is sometimes dark due to this. >>>>>> >>>>>> Thanks >>>>>> >>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From adarshdesai.dsp at gmail.com Fri Jul 21 15:20:37 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Fri, 21 Jul 2017 12:20:37 -0700 Subject: [vtkusers] Problem with shadows In-Reply-To: References: Message-ID: Hi, Due to some reason I am not able to attach screenshot. But if I rotate and change the angle for the Polydata by interacting with it, I can see colors correctly, only at certain angles the colors are dark the way you see for shadows. May be my understanding is wrong, meanwhile I will try to work with Normals ,Scalars. But if there is a way to turn off every shadow or add lights to all viewing angles it would be great. Thanks On Fri, Jul 21, 2017 at 12:12 PM, David Gobbi wrote: > Can you attach a screenshot? My own experience with VTK tells me that it > is very, very unlikely that you are seeing shadows. Whenever I see dark > areas in VTK rendering, it is almost always due to the scalars, the > normals, or the winding of the polydata. It could be that some of your > polygons are wound incorrectly. > > > On Fri, Jul 21, 2017 at 12:37 PM, abcd efgh > wrote: > >> previously forgot to add VTKusers list.. forwarding same mail. >> >> Hi, >> >> Thank you for the input. I have tried with new Normals, its the same. >> I dont think there is an issue with normals. When Poly data appears on >> screen, it will be in darkness(shadow). >> I need to turn off every shadow in the renderer. I am using >> Renderer->UseShadowsOff(), still no use. >> >> Please someone guide me to turn off all shadows in the scene. Just like >> how the Cube source appears in the renderer. >> >> Thanks >> >> On Thu, Jul 20, 2017 at 3:52 PM, abcd efgh >> wrote: >> >>> Hi, >>> >>> Thank you for the input. I have tried with new Normals, its the same. >>> I dont think there is an issue with normals. When Poly data appears on >>> screen, it will be in darkness(shadow). >>> I need to turn off every shadow in the renderer. I am using >>> Renderer->UseShadowsOff(), still no use. >>> >>> Please someone guide me to turn off all shadows in the scene. Just like >>> how the Cube source appears in the renderer. >>> >>> Thanks >>> >>> On Mon, Jul 17, 2017 at 12:06 PM, David Gobbi >>> wrote: >>> >>>> If it isn't the scalars, then it is probably the normals. If the data >>>> has bad normals, then lighting of the data will be incorrect. >>>> >>>> You can try generating new normals for the data with >>>> vtkPolyDataNormals. Make sure that you read the documentation for this >>>> class, it has lots of options. >>>> >>>> - David >>>> >>>> >>>> On Mon, Jul 17, 2017 at 12:31 PM, abcd efgh >>>> wrote: >>>> >>>>> Thanks, >>>>> if I turn off scalars then I see only white color, by the way even >>>>> after that I see the shadow effects, how can I turn off the shadows in the >>>>> scene completely. >>>>> I think the problem is with respect to shadows. >>>>> >>>>> Thanks again. >>>>> >>>>> On Sun, Jul 16, 2017 at 5:21 AM, David Gobbi >>>>> wrote: >>>>> >>>>>> Clipping a data set adds scalars to the data set. These scalars are >>>>>> probably causing the strange coloring that you are seeing. You can tell the >>>>>> mapper to ignore the scalars, and use the vtkProperty color instead: >>>>>> >>>>>> mapper->ScalarVisibilityOff(); >>>>>> >>>>>> - David >>>>>> >>>>>> On Sun, Jul 16, 2017 at 2:15 AM, abcd efgh >>>>> > wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I am new to vtk. I have a 3D polydata, I cut it using >>>>>>> vtkClipPolydata. >>>>>>> Now there are some shadow kind of thing, I have called functions to >>>>>>> turn off shadows >>>>>>> as well as backface culling as off. But still shadow kind of effect >>>>>>> remains and the Poly data is sometimes dark due to this. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhurkulis at gmail.com Sun Jul 23 13:22:11 2017 From: zhurkulis at gmail.com (nolvis) Date: Sun, 23 Jul 2017 10:22:11 -0700 (MST) Subject: [vtkusers] vtkTriangle::IntersectWithLine() question. Message-ID: <1500830531065-5744123.post@n5.nabble.com> Hello, does vtkTriangle::IntersectWithLine(), should return intersection between coplanar line and triangle, or it only returns intersection on non-conplanar triangles and lines? Thanks in advance! -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTriangle-IntersectWithLine-question-tp5744123.html Sent from the VTK - Users mailing list archive at Nabble.com. From elvis.stansvik at orexplore.com Sun Jul 23 20:45:51 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Mon, 24 Jul 2017 02:45:51 +0200 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra Message-ID: Hi all, I have a set of points describing multiple convex polyhedra. The polyhedra are for the most part disjoint in space, but they may intersect slightly in some places. I need to create an empty voxel volume (all scalars 0), and then "fill" the voxels that are inside one (or several) of the polyhedrons with some Perlin noise. I also have access to normals for the faces constituting the polyhedra, if necessary. Finally, I also have a single separate polyhedron (non-convex this time), and as a finishing step, I'd like to fill the voxels that are inside this polyhedron with a constant scalar value. Can VTK help me here? As this is new territory for me as far as VTK goes, any pointers/advice on how to go about it would be much appreciated. Cheers, Elvis From inglis.dl at gmail.com Sun Jul 23 23:09:22 2017 From: inglis.dl at gmail.com (Dean Inglis) Date: Sun, 23 Jul 2017 23:09:22 -0400 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra In-Reply-To: References: Message-ID: HI Elvis, ITK would probably handle the mesh to image problem solving space better, but I have had success with a pipeline composed of myPolyData => vtkPolyDataToImageStencil => vtkImageStencilToImage => write_your_own_myWorkOnMaskImageOfPolyDataContents There are some limits to what vtkPolyDataToImageStencil and do: you may need to transform your mesh to an x-y-z aligned image space with sufficient resolution and have it satisfy certain topological conditions. - Dean On Sun, Jul 23, 2017 at 8:45 PM, Elvis Stansvik < elvis.stansvik at orexplore.com> wrote: > Hi all, > > I have a set of points describing multiple convex polyhedra. The > polyhedra are for the most part disjoint in space, but they may > intersect slightly in some places. > > I need to create an empty voxel volume (all scalars 0), and then > "fill" the voxels that are inside one (or several) of the polyhedrons > with some Perlin noise. I also have access to normals for the faces > constituting the polyhedra, if necessary. > > Finally, I also have a single separate polyhedron (non-convex this > time), and as a finishing step, I'd like to fill the voxels that are > inside this polyhedron with a constant scalar value. > > Can VTK help me here? > > As this is new territory for me as far as VTK goes, any > pointers/advice on how to go about it would be much appreciated. > > Cheers, > Elvis > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.gobbi at gmail.com Sun Jul 23 23:21:43 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Sun, 23 Jul 2017 21:21:43 -0600 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra In-Reply-To: References: Message-ID: Hi Elvis, I'd recommend generating a stencil with vtkPolyDataToImageStencil, then iterating over over all the voxels inside the stencil with vtkImagePointDataIterator: http://www.vtk.org/doc/nightly/html/classvtkPolyDataToImageStencil.html http://www.vtk.org/doc/nightly/html/classvtkImagePointDataIterator.html The iterator can efficiently give you the pointId for every voxel enclosed by the polyhedral surface (works for concave as well as convex surfaces). Once you have the pointId, you can set that voxel to whatever you want. There's a brief and vaguely relevant description on gitlab: https://gitlab. kitware.com/vtk/vtk/merge_requests/1118 - David On Sun, Jul 23, 2017 at 6:45 PM, Elvis Stansvik < elvis.stansvik at orexplore.com> wrote: > Hi all, > > I have a set of points describing multiple convex polyhedra. The > polyhedra are for the most part disjoint in space, but they may > intersect slightly in some places. > > I need to create an empty voxel volume (all scalars 0), and then > "fill" the voxels that are inside one (or several) of the polyhedrons > with some Perlin noise. I also have access to normals for the faces > constituting the polyhedra, if necessary. > > Finally, I also have a single separate polyhedron (non-convex this > time), and as a finishing step, I'd like to fill the voxels that are > inside this polyhedron with a constant scalar value. > > Can VTK help me here? > > As this is new territory for me as far as VTK goes, any > pointers/advice on how to go about it would be much appreciated. > > Cheers, > Elvis > -------------- next part -------------- An HTML attachment was scrubbed... URL: From inglis.dl at gmail.com Sun Jul 23 23:25:23 2017 From: inglis.dl at gmail.com (Dean Inglis) Date: Sun, 23 Jul 2017 23:25:23 -0400 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra In-Reply-To: References: Message-ID: good to know David, thanks!!! - Dean On Sun, Jul 23, 2017 at 11:21 PM, David Gobbi wrote: > Hi Elvis, > > I'd recommend generating a stencil with vtkPolyDataToImageStencil, then > iterating over over all the voxels inside the stencil with > vtkImagePointDataIterator: > > http://www.vtk.org/doc/nightly/html/classvtkPolyDataToImageStencil.html > http://www.vtk.org/doc/nightly/html/classvtkImagePointDataIterator.html > > The iterator can efficiently give you the pointId for every voxel enclosed > by the polyhedral surface (works for concave as well as convex surfaces). > Once you have the pointId, you can set that voxel to whatever you want. > There's a brief and vaguely relevant description on gitlab: > https://gitlab.kitware.com/vtk/vtk/merge_requests/1118 > > - David > > > On Sun, Jul 23, 2017 at 6:45 PM, Elvis Stansvik < > elvis.stansvik at orexplore.com> wrote: > >> Hi all, >> >> I have a set of points describing multiple convex polyhedra. The >> polyhedra are for the most part disjoint in space, but they may >> intersect slightly in some places. >> >> I need to create an empty voxel volume (all scalars 0), and then >> "fill" the voxels that are inside one (or several) of the polyhedrons >> with some Perlin noise. I also have access to normals for the faces >> constituting the polyhedra, if necessary. >> >> Finally, I also have a single separate polyhedron (non-convex this >> time), and as a finishing step, I'd like to fill the voxels that are >> inside this polyhedron with a constant scalar value. >> >> Can VTK help me here? >> >> As this is new territory for me as far as VTK goes, any >> pointers/advice on how to go about it would be much appreciated. >> >> Cheers, >> Elvis >> > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From elvis.stansvik at orexplore.com Sun Jul 23 23:30:50 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Mon, 24 Jul 2017 05:30:50 +0200 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra In-Reply-To: References: Message-ID: 2017-07-24 5:25 GMT+02:00 Dean Inglis : > good to know David, thanks!!! Many thanks to both of you. I had not found vtkPolyDataToImageStencil yet, but was looking more towards the concept of implicit functions. But this sounds like a much better approach, so I think I was right in reaching out :) Elvis > > - Dean > > On Sun, Jul 23, 2017 at 11:21 PM, David Gobbi wrote: >> >> Hi Elvis, >> >> I'd recommend generating a stencil with vtkPolyDataToImageStencil, then >> iterating over over all the voxels inside the stencil with >> vtkImagePointDataIterator: >> >> http://www.vtk.org/doc/nightly/html/classvtkPolyDataToImageStencil.html >> http://www.vtk.org/doc/nightly/html/classvtkImagePointDataIterator.html >> >> The iterator can efficiently give you the pointId for every voxel enclosed >> by the polyhedral surface (works for concave as well as convex surfaces). >> Once you have the pointId, you can set that voxel to whatever you want. >> There's a brief and vaguely relevant description on gitlab: >> https://gitlab.kitware.com/vtk/vtk/merge_requests/1118 >> >> - David >> >> >> On Sun, Jul 23, 2017 at 6:45 PM, Elvis Stansvik >> wrote: >>> >>> Hi all, >>> >>> I have a set of points describing multiple convex polyhedra. The >>> polyhedra are for the most part disjoint in space, but they may >>> intersect slightly in some places. >>> >>> I need to create an empty voxel volume (all scalars 0), and then >>> "fill" the voxels that are inside one (or several) of the polyhedrons >>> with some Perlin noise. I also have access to normals for the faces >>> constituting the polyhedra, if necessary. >>> >>> Finally, I also have a single separate polyhedron (non-convex this >>> time), and as a finishing step, I'd like to fill the voxels that are >>> inside this polyhedron with a constant scalar value. >>> >>> Can VTK help me here? >>> >>> As this is new territory for me as far as VTK goes, any >>> pointers/advice on how to go about it would be much appreciated. >>> >>> Cheers, >>> Elvis >> >> >> _______________________________________________ >> 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 >> > From elvis.stansvik at orexplore.com Sun Jul 23 23:34:33 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Mon, 24 Jul 2017 05:34:33 +0200 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra In-Reply-To: References: Message-ID: 2017-07-24 5:30 GMT+02:00 Elvis Stansvik : > 2017-07-24 5:25 GMT+02:00 Dean Inglis : >> good to know David, thanks!!! > > Many thanks to both of you. I had not found vtkPolyDataToImageStencil > yet, but was looking more towards the concept of implicit functions. > But this sounds like a much better approach, so I think I was right in > reaching out :) Just one thing I saw in the docs for vtkPolyDataToImageStencil now: "The polydata can either be a closed surface mesh or a series of polyline contours (one contour per slice)." Does this mean that, since I have a set of closed surfaces (upwards a 100 or so), I'd have to repeat the process David described, once for each of my polyhedron? Or is there some way to generate a stencil from many closed surfaces in one go? Elvis > > Elvis > >> >> - Dean >> >> On Sun, Jul 23, 2017 at 11:21 PM, David Gobbi wrote: >>> >>> Hi Elvis, >>> >>> I'd recommend generating a stencil with vtkPolyDataToImageStencil, then >>> iterating over over all the voxels inside the stencil with >>> vtkImagePointDataIterator: >>> >>> http://www.vtk.org/doc/nightly/html/classvtkPolyDataToImageStencil.html >>> http://www.vtk.org/doc/nightly/html/classvtkImagePointDataIterator.html >>> >>> The iterator can efficiently give you the pointId for every voxel enclosed >>> by the polyhedral surface (works for concave as well as convex surfaces). >>> Once you have the pointId, you can set that voxel to whatever you want. >>> There's a brief and vaguely relevant description on gitlab: >>> https://gitlab.kitware.com/vtk/vtk/merge_requests/1118 >>> >>> - David >>> >>> >>> On Sun, Jul 23, 2017 at 6:45 PM, Elvis Stansvik >>> wrote: >>>> >>>> Hi all, >>>> >>>> I have a set of points describing multiple convex polyhedra. The >>>> polyhedra are for the most part disjoint in space, but they may >>>> intersect slightly in some places. >>>> >>>> I need to create an empty voxel volume (all scalars 0), and then >>>> "fill" the voxels that are inside one (or several) of the polyhedrons >>>> with some Perlin noise. I also have access to normals for the faces >>>> constituting the polyhedra, if necessary. >>>> >>>> Finally, I also have a single separate polyhedron (non-convex this >>>> time), and as a finishing step, I'd like to fill the voxels that are >>>> inside this polyhedron with a constant scalar value. >>>> >>>> Can VTK help me here? >>>> >>>> As this is new territory for me as far as VTK goes, any >>>> pointers/advice on how to go about it would be much appreciated. >>>> >>>> Cheers, >>>> Elvis >>> >>> >>> _______________________________________________ >>> 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 >>> >> From david.gobbi at gmail.com Sun Jul 23 23:43:03 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Sun, 23 Jul 2017 21:43:03 -0600 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra In-Reply-To: References: Message-ID: You can use as many closed surfaces as you want with vtkPolyDataToImageStencil, as long as the surfaces don't intersect. Intersection would break the topological constraints of the filter. But if you have each polyhedron as a separate vtkPolyData, then iterating over them all should still be fast, because for each polyhedron you can ignore all voxels except for the ones that are inside. - David On Sun, Jul 23, 2017 at 9:34 PM, Elvis Stansvik < elvis.stansvik at orexplore.com> wrote: > 2017-07-24 5:30 GMT+02:00 Elvis Stansvik : > > 2017-07-24 5:25 GMT+02:00 Dean Inglis : > >> good to know David, thanks!!! > > > > Many thanks to both of you. I had not found vtkPolyDataToImageStencil > > yet, but was looking more towards the concept of implicit functions. > > But this sounds like a much better approach, so I think I was right in > > reaching out :) > > Just one thing I saw in the docs for vtkPolyDataToImageStencil now: > > "The polydata can either be a closed surface mesh or a series of > polyline contours (one contour per slice)." > > Does this mean that, since I have a set of closed surfaces (upwards a > 100 or so), I'd have to repeat the process David described, once for > each of my polyhedron? Or is there some way to generate a stencil from > many closed surfaces in one go? > > Elvis > > > > > Elvis > > > >> > >> - Dean > >> > >> On Sun, Jul 23, 2017 at 11:21 PM, David Gobbi > wrote: > >>> > >>> Hi Elvis, > >>> > >>> I'd recommend generating a stencil with vtkPolyDataToImageStencil, then > >>> iterating over over all the voxels inside the stencil with > >>> vtkImagePointDataIterator: > >>> > >>> http://www.vtk.org/doc/nightly/html/classvtkPolyDataToImageStencil > .html > >>> http://www.vtk.org/doc/nightly/html/classvtkImagePointDataIterator > .html > >>> > >>> The iterator can efficiently give you the pointId for every voxel > enclosed > >>> by the polyhedral surface (works for concave as well as convex > surfaces). > >>> Once you have the pointId, you can set that voxel to whatever you want. > >>> There's a brief and vaguely relevant description on gitlab: > >>> https://gitlab.kitware.com/vtk/vtk/merge_requests/1118 > >>> > >>> - David > >>> > >>> > >>> On Sun, Jul 23, 2017 at 6:45 PM, Elvis Stansvik > >>> wrote: > >>>> > >>>> Hi all, > >>>> > >>>> I have a set of points describing multiple convex polyhedra. The > >>>> polyhedra are for the most part disjoint in space, but they may > >>>> intersect slightly in some places. > >>>> > >>>> I need to create an empty voxel volume (all scalars 0), and then > >>>> "fill" the voxels that are inside one (or several) of the polyhedrons > >>>> with some Perlin noise. I also have access to normals for the faces > >>>> constituting the polyhedra, if necessary. > >>>> > >>>> Finally, I also have a single separate polyhedron (non-convex this > >>>> time), and as a finishing step, I'd like to fill the voxels that are > >>>> inside this polyhedron with a constant scalar value. > >>>> > >>>> Can VTK help me here? > >>>> > >>>> As this is new territory for me as far as VTK goes, any > >>>> pointers/advice on how to go about it would be much appreciated. > >>>> > >>>> Cheers, > >>>> Elvis > >>> > >>> > >>> _______________________________________________ > >>> 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 > >>> > >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From elvis.stansvik at orexplore.com Sun Jul 23 23:58:32 2017 From: elvis.stansvik at orexplore.com (Elvis Stansvik) Date: Mon, 24 Jul 2017 05:58:32 +0200 Subject: [vtkusers] "Filling" parts of a volume that are "inside" a set of polyhedra In-Reply-To: References: Message-ID: 2017-07-24 5:43 GMT+02:00 David Gobbi : > You can use as many closed surfaces as you want with > vtkPolyDataToImageStencil, as long as the surfaces don't intersect. > Intersection would break the topological constraints of the filter. Alright. Good to know. My polyhedra will be the result result of a rigid body physics simulation, and I'm not sure yet whether, in the final resting state, the bodies may intersect slightly or not, they probably can. > > But if you have each polyhedron as a separate vtkPolyData, then iterating > over them all should still be fast, because for each polyhedron you can > ignore all voxels except for the ones that are inside. Okay, then I'll definitely process them one by one. Elvis > > - David > > On Sun, Jul 23, 2017 at 9:34 PM, Elvis Stansvik > wrote: >> >> 2017-07-24 5:30 GMT+02:00 Elvis Stansvik : >> > 2017-07-24 5:25 GMT+02:00 Dean Inglis : >> >> good to know David, thanks!!! >> > >> > Many thanks to both of you. I had not found vtkPolyDataToImageStencil >> > yet, but was looking more towards the concept of implicit functions. >> > But this sounds like a much better approach, so I think I was right in >> > reaching out :) >> >> Just one thing I saw in the docs for vtkPolyDataToImageStencil now: >> >> "The polydata can either be a closed surface mesh or a series of >> polyline contours (one contour per slice)." >> >> Does this mean that, since I have a set of closed surfaces (upwards a >> 100 or so), I'd have to repeat the process David described, once for >> each of my polyhedron? Or is there some way to generate a stencil from >> many closed surfaces in one go? >> >> Elvis >> >> > >> > Elvis >> > >> >> >> >> - Dean >> >> >> >> On Sun, Jul 23, 2017 at 11:21 PM, David Gobbi >> >> wrote: >> >>> >> >>> Hi Elvis, >> >>> >> >>> I'd recommend generating a stencil with vtkPolyDataToImageStencil, >> >>> then >> >>> iterating over over all the voxels inside the stencil with >> >>> vtkImagePointDataIterator: >> >>> >> >>> >> >>> http://www.vtk.org/doc/nightly/html/classvtkPolyDataToImageStencil.html >> >>> >> >>> http://www.vtk.org/doc/nightly/html/classvtkImagePointDataIterator.html >> >>> >> >>> The iterator can efficiently give you the pointId for every voxel >> >>> enclosed >> >>> by the polyhedral surface (works for concave as well as convex >> >>> surfaces). >> >>> Once you have the pointId, you can set that voxel to whatever you >> >>> want. >> >>> There's a brief and vaguely relevant description on gitlab: >> >>> https://gitlab.kitware.com/vtk/vtk/merge_requests/1118 >> >>> >> >>> - David >> >>> >> >>> >> >>> On Sun, Jul 23, 2017 at 6:45 PM, Elvis Stansvik >> >>> wrote: >> >>>> >> >>>> Hi all, >> >>>> >> >>>> I have a set of points describing multiple convex polyhedra. The >> >>>> polyhedra are for the most part disjoint in space, but they may >> >>>> intersect slightly in some places. >> >>>> >> >>>> I need to create an empty voxel volume (all scalars 0), and then >> >>>> "fill" the voxels that are inside one (or several) of the polyhedrons >> >>>> with some Perlin noise. I also have access to normals for the faces >> >>>> constituting the polyhedra, if necessary. >> >>>> >> >>>> Finally, I also have a single separate polyhedron (non-convex this >> >>>> time), and as a finishing step, I'd like to fill the voxels that are >> >>>> inside this polyhedron with a constant scalar value. >> >>>> >> >>>> Can VTK help me here? >> >>>> >> >>>> As this is new territory for me as far as VTK goes, any >> >>>> pointers/advice on how to go about it would be much appreciated. >> >>>> >> >>>> Cheers, >> >>>> Elvis >> >>> >> >>> >> >>> _______________________________________________ >> >>> 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 >> >>> >> >> > > From taron2000 at gmx.de Mon Jul 24 02:11:54 2017 From: taron2000 at gmx.de (Taron) Date: Sun, 23 Jul 2017 23:11:54 -0700 (MST) Subject: [vtkusers] VTK 8.0.0 OpenGL2 Invisible surfaces In-Reply-To: References: <1500628878599-5744093.post@n5.nabble.com> Message-ID: <1500876714977-5744133.post@n5.nabble.com> Hi Ken, indeed ForcingOpaque on the actors renders all surfaces. And the actors have a LUT witch contains opacity values < 1. In fact the border pixels have opacity = 0. Even when I use FroceOpaque these transculent borders are correctly invisible. What I still do not understand is, why vtk thinks that one face has to be completely transparent, when ForceOpaque is off and why it works when Depthpeeling is enabled? I hope you can shed some light into this. -- View this message in context: http://vtk.1045678.n5.nabble.com/VTK-8-0-0-OpenGL2-Invisible-surfaces-tp5744093p5744133.html Sent from the VTK - Users mailing list archive at Nabble.com. From taron2000 at gmx.de Mon Jul 24 02:45:59 2017 From: taron2000 at gmx.de (Taron) Date: Sun, 23 Jul 2017 23:45:59 -0700 (MST) Subject: [vtkusers] vtk-7.1 openGL 2.0 crash In-Reply-To: References: <1500465504824-5744014.post@n5.nabble.com> <1500553235143-5744049.post@n5.nabble.com> Message-ID: <1500878759070-5744134.post@n5.nabble.com> To the compatibility problems with the new backend on machines that do not have OpenGL 3.2 like virtual machines. We solved the problem here (for windows only, but I dont see why it should not work under linux as well) like this: We built the latest MESA driver under Windows and tested the application with that. Everything runs fine but slow since it is a software renderer. To test it you can simply copy the opengl32.dll (and maybe the swrAVX dlls) in the folder of you executable. When everything works we set up mechanism to load the system opengl when a 3.2 OpenGL context is available and otherwise load the MESA driver. To do so we build VTK with the Linker-Option /DELAYLOAD:opengl32.dll This will delay the loading of the specified DLL to the first call instead of on application start up. This gives you the chance to use SetDLLDirectory to point to the folder where the MESA drivers are stored when no sufficient opengl is found and thus the program will use the mesa drivers. Now the tricky part is to detect if opengl 3.2 is available. To do so you need to create a opengl context and see if it worked or failed. To create a context you have to load the opengl32.dll. This is bad because we want to switch that. The easiest solution for us was to write a very small program (<200 SLOC) which checks if opengl in a certain version is available on the system, since it can load the system opengl32.dll. We call this checker program on startup of the main application and then decide which DLL to load for the main app. -- View this message in context: http://vtk.1045678.n5.nabble.com/vtk-7-1-openGL-2-0-crash-tp5744014p5744134.html Sent from the VTK - Users mailing list archive at Nabble.com. From l1q1d at yahoo.it Mon Jul 24 05:35:25 2017 From: l1q1d at yahoo.it (Mattia M) Date: Mon, 24 Jul 2017 11:35:25 +0200 Subject: [vtkusers] Contourf plot with dynamic resize Message-ID: <0514C8B1-BE37-4823-90FC-BF6D1495D597@yahoo.it> Hi to all, this is my first post in the mailing list. I'm trying to develop a plot application thant is able to create the controuf similar to matlab https://it.mathworks.com/help/matlab/ref/contourf.html I succeed in creating something like it but my actual issues are place the plot in the center and resize dynamically with the window. This is the code that I'm using so far: void CreateBaseData(vtkImageData* image) { datastructure * dataInput = new datastructure(FILEPATH); image->SetDimensions(dataInput->shape()->Xsize, dataInput->shape()->Ysize, 1); // image->SetSpacing(dataInput->shape()->Xres,dataInput->shape()->Yres,0); // image->SetOrigin(dataInput->shape()->Xmin,dataInput->shape()->Ymin,0); image->AllocateScalars(VTK_DOUBLE,1); for(unsigned int x = 0; x < dataInput->shape()->Xsize; x++) { for(unsigned int y = 0; y < dataInput->shape()->Ysize; y++) { double* pixel = static_cast(image->GetScalarPointer(x,y,0)); pixel[0] = dataInput->z[y][x]; } } delete dataInput; //image->Modified(); } void RenderWindowUISingleInheritance::ModifiedHandler() { ui->qvtkWidget->GetRenderWindow()->Render(); } // Constructor RenderWindowUISingleInheritance::RenderWindowUISingleInheritance(QWidget *parent) : QMainWindow(parent), ui(new Ui::RenderWindowUISingleInheritanceUI) { ui->setupUi(this); vtkSmartPointer style = vtkSmartPointer::New(); ui->qvtkWidget->GetRenderWindow()->GetInteractor()->SetInteractorStyle(style); int numberOfContours = 15; double scalarRange[2]; float levels[] = { 0.4, 1.0, 2.0, 4, 10.0, 20.0, 40, 100, 200, 400, 1000, 2000, 4000, 10000, 20000, 40000 }; vtkSmartPointer colorImage = vtkSmartPointer::New(); vtkSmartPointer lut = vtkSmartPointer::New(); vtkSmartPointer convert = vtkSmartPointer::New(); vtkSmartPointer bf = vtkSmartPointer::New(); vtkSmartPointer filledContourMapper = vtkSmartPointer::New(); vtkSmartPointer contourLineMapperer =vtkSmartPointer::New(); vtkSmartPointer ren1 = vtkSmartPointer::New(); vtkSmartPointer filledContourActor =vtkSmartPointer::New(); vtkSmartPointer contourLineActor = vtkSmartPointer::New(); vtkSmartPointer cubeAxesActor = vtkSmartPointer::New(); vtkSmartPointer scalarBarActor =vtkSmartPointer::New(); CreateBaseData(colorImage); colorImage->GetScalarRange(scalarRange); int l_min; int l_max; for (l_min=numberOfContours-1;l_min>=0;l_min--) { if (levels[l_min] <= scalarRange[0]) break; } for (l_max=0;l_max scalarRange[1]) break; } numberOfContours = l_max - l_min; // colormap::setColorMap(lut,1,1); char label[10]; for (vtkIdType i = l_min; i < numberOfContours+1; ++i) { //std::cout << lut->GetAnnotatedValue(i).ToString() << std::endl; sprintf(label,"%4.2f",levels[i]); lut->SetAnnotation(i, label); } convert->SetInputData(colorImage); bf->SetInputConnection(convert->GetOutputPort()); bf->SetNumberOfContours(numberOfContours); for (int i=l_min;iSetValue(i,levels[i]); } bf->GenerateContourEdgesOn(); filledContourMapper->SetInputConnection(bf->GetOutputPort()); filledContourMapper->SetScalarModeToUseCellData(); // filledContourMapper->SetColorModeToMapScalars(); filledContourMapper->SetScalarRange(0,numberOfContours); filledContourMapper->SetLookupTable(lut); filledContourActor->SetMapper(filledContourMapper); filledContourActor->PickableOn(); filledContourActor->GetPosition2Coordinate()->SetValue(0.17, 0.8); filledContourActor->GetPositionCoordinate()->SetCoordinateSystemToNormalizedViewport(); filledContourActor->GetPositionCoordinate()->SetValue(0.82, 0.1); filledContourActor->SetWidth( 0.7 ); filledContourActor->SetHeight( 0.1 ); filledContourActor->SetPosition( 0.1, 0.01 ); contourLineMapperer->SetInputData(bf->GetContourEdgesOutput()); contourLineMapperer->ScalarVisibilityOn(); contourLineActor->SetMapper(contourLineMapperer); contourLineActor->GetProperty()->SetLineWidth(0.5); contourLineActor->GetProperty()->SetColor(0., 0., 0.); scalarBarActor->SetLookupTable(filledContourMapper->GetLookupTable()); scalarBarActor->SetNumberOfLabels(numberOfContours); scalarBarActor->SetOrientationToHorizontal(); scalarBarActor->SetPosition(0.05,0.2); scalarBarActor->SetWidth(0.9); scalarBarActor->SetHeight(0.05); scalarBarActor->SetDrawTickLabels(0); scalarBarActor->SetDrawAnnotations(1); scalarBarActor->GetAnnotationTextProperty()->SetFontFamilyToCourier(); //scalarBar->GetAnnotationTextProperty()->SetVerticalJustificationToCentered(); scalarBarActor->GetAnnotationTextProperty()->BoldOff(); scalarBarActor->GetAnnotationTextProperty()->ItalicOff(); scalarBarActor->GetAnnotationTextProperty()->ShadowOff() ; scalarBarActor->GetAnnotationTextProperty()->SetColor(0, 0, 0); scalarBarActor->GetAnnotationTextProperty()->SetJustificationToRight(); scalarBarActor->SetUseBounds(true); // cubeAxesActor->SetBounds(filledContourMapper->GetBounds()); cubeAxesActor->SetCamera(ren1->GetActiveCamera()); cubeAxesActor->GetTitleTextProperty(0)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->GetLabelTextProperty(0)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->GetTitleTextProperty(1)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->GetLabelTextProperty(1)->SetColor(0.0, 0.0, 0.0); cubeAxesActor->DrawXGridlinesOn(); cubeAxesActor->DrawYGridlinesOn(); cubeAxesActor->DrawZGridlinesOff(); cubeAxesActor->GetXAxesLinesProperty()->SetColor(0.0, 0.0,0.0); cubeAxesActor->GetYAxesLinesProperty()->SetColor(0.0, 0.0,0.0); cubeAxesActor->GetYAxesGridlinesProperty ()->SetColor(0,0,0); cubeAxesActor->GetXAxesGridlinesProperty ()->SetColor(0,0,0); cubeAxesActor->SetTickLocationToOutside(); // cubeAxesActor->SetGridLineLocation(cubeAxesActor->VTK_GRID_LINES_CLOSEST); ren1->SetBackground(1, 1, 1); // Add the actors ren1->AddActor(filledContourActor); ren1->AddActor(contourLineActor); ren1->AddActor(scalarBarActor); // ren1->AddActor(cubeAxesActor); ren1->ResetCamera(); // VTK/Qt wedded ui->qvtkWidget->GetRenderWindow()->AddRenderer(ren1); ui->qvtkWidget->GetRenderWindow()->AddObserver(vtkCommand::ModifiedEvent,this,&RenderWindowUISingleInheritance::ModifiedHandler); // Set up action signals and slots connect(ui->actionExit, SIGNAL(triggered()), this, SLOT(slotExit())); } void RenderWindowUISingleInheritance::slotExit() { qApp->exit(); } RenderWindowUISingleInheritance::~RenderWindowUISingleInheritance() { delete ui; }; Do you have any suggestion? Thanks Mattia -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjordan at live.at Mon Jul 24 08:28:10 2017 From: mjordan at live.at (M. Jordan) Date: Mon, 24 Jul 2017 12:28:10 +0000 Subject: [vtkusers] Check if picked actor is a sphere or not Message-ID: Hello, i used this example: http://www.vtk.org/Wiki/VTK/Examples/Cxx/Picking/HighlightPickedActor to change the color of a picked actor to red. In my scene there are many different actors (spheres, cubes,..). Now i want to only highlight actors which are spheres and nothing else. Using PickableOff () for the other things is not suitable for my application, I need to get information about the source of the actor from this->LastPickedActor. Any ideas? Thank you very much! Best Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Mon Jul 24 09:11:06 2017 From: ken.martin at kitware.com (Ken Martin) Date: Mon, 24 Jul 2017 09:11:06 -0400 Subject: [vtkusers] VTK 8.0.0 OpenGL2 Invisible surfaces In-Reply-To: <1500876714977-5744133.post@n5.nabble.com> References: <1500628878599-5744093.post@n5.nabble.com> <1500876714977-5744133.post@n5.nabble.com> Message-ID: Rendering transparent surfaces is tricky because the order they are composited impacts the final color. There are a few techniques to address this issue one of which is depth peeling. When you have depth peeling on, then even if VTK thinks your surface is transparent, it will render it correctly. Without depth peeling, transparent surfaces are rendered by blending the transparent surfaces all together in whatever order they happen to get rendered. To make sure they *all* get blended together VTK turns off writing to the z buffer for transparent surfaces. So everything in front of the opaque actors gets rendered and blended together based on their opacity. This is called alpha blending and if you sort your polygons from back to front it gives correct results. But sorting is computationally expensive and we do not do it. Depth peeling is better in that case. In your case all, or most, of your pixels on the surface are opaque even though they get rendered in the translucent pass. So the blending operation ends up being the last thing rendered wins (because they are opaque and z writing is off). So if you have a sphere made up of lots of small triangles what you will see is the last half of the triangles rendered. Depending on camera direction sometimes that will be the front side of the sphere and it will look correct, from other directions those triangles will be the back side and it will look incorrect. Either way you are just seeing the last half of the triangles rendered (because as in most closed surfaces there in a front and a back, so you see half). If the triangles were randomly ordered you would always see a mishmash of front and back. Hopefully that makes sense. All the faces are being rendered, it is just that the last face rendered (regardless of front or back) wins. The Opaque/Translucent setting controls when an actor renders (opaque pass versus translucent pass) and whether it will write to the zbuffer. Opaque writes to the zbuffer blocking anything else below it from rendering, translucent does not write to the zbuffer allowing later polygons underneath it to be rendered. On Mon, Jul 24, 2017 at 2:11 AM, Taron wrote: > Hi Ken, > > indeed ForcingOpaque on the actors renders all surfaces. And the actors > have > a LUT witch contains opacity values < 1. In fact the border pixels have > opacity = 0. Even when I use FroceOpaque these transculent borders are > correctly invisible. What I still do not understand is, why vtk thinks that > one face has to be completely transparent, when ForceOpaque is off and why > it works when Depthpeeling is enabled? > I hope you can shed some light into this. > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/VTK-8-0-0-OpenGL2-Invisible-surfaces-tp5744093p5744133.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 tjlp at netease.com Tue Jul 25 11:47:32 2017 From: tjlp at netease.com (Liu_tj) Date: Tue, 25 Jul 2017 23:47:32 +0800 (CST) Subject: [vtkusers] One question about the implementation of function vtkAngleRepresentation3D::BuildRepresentation() Message-ID: Hi, VTK guys, I check the implementation of vtkAngleRepresentation3D::BuildRepresentation() of the master branch. Line 301 (https://github.com/Kitware/VTK/blob/master/Interaction/Widgets/vtkAngleRepresentation3D.cxx#L301) compares x coordinate of point1 and centerpoint or point2 and centerpoint, if either of them is 0.0, the function will return and the angle value won't be updated. Now I get an issue raised by this check. If I draw an angle on the sagittal view on the vtkImageViewer2, the x coordinate of the 3 points should be the same. That will cause I can't get the right value. Why is the comparation added? Although there is some comment "Compute the angle (only if necessary since we don't want fluctuations in angle value as the camera moves, etc.)". I don't understand it. Would any guys give explainments? Add @Ken martin as Martin is one of the authors. Thanks Liu Peng -------------- next part -------------- An HTML attachment was scrubbed... URL: From arw.tyx-ouy_mz at ezweb.ne.jp Wed Jul 26 04:02:54 2017 From: arw.tyx-ouy_mz at ezweb.ne.jp (arwtyxouymz) Date: Wed, 26 Jul 2017 01:02:54 -0700 (MST) Subject: [vtkusers] Create cylinder whose cross section is ellipse Message-ID: <1501056174249-5744148.post@n5.nabble.com> Hi, I'm a newer of VTK, and use VTK-8.0.0 by C++. I want to create a cylinder whose cross section is ellipse. Firstly I create 2d ellipse, then I extrude the ellipse along z axis. I could create 2d ellipse, and render it. But I have applied vtkLinearExtrusionFilter, my code crash with exit code 11. What shoud i do? please help me. This is my code. ``` #include "vtkPoints.h" #include "vtkSmartPointer.h" #include "vtkLinearExtrusionFilter.h" #include "vtkDataSetMapper.h" #include "vtkPolyDataMapper.h" #include "vtkActor.h" #include "vtkProperty.h" #include "vtkCamera.h" #include "vtkRenderer.h" #include "vtkRenderWindow.h" #include "vtkRenderWindowInteractor.h" #include "vtkInteractorStyleTrackballCamera.h" int main(int argc, char *argv[]) { double angle = 0; double r1, r2; int id = 0; int CenterX, CenterY; r1 = 50; r2 = 30; vtkSmartPointer points = vtkSmartPointer::New(); points->SetNumberOfPoints(31); while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 60.0)) { points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) + CenterY, 0); angle = angle + (vtkMath::Pi() / 60.0); id++; } vtkSmartPointer lines = vtkSmartPointer::New(); lines->Allocate(1, 1); lines->InsertNextCell(id); lines->SetNumberOfCells(id); for (int k = 0; k < id; ++k) { lines->InsertCellPoint(k); } vtkSmartPointer polyData = vtkSmartPointer::New(); polyData->GlobalReleaseDataFlagOff(); polyData->Allocate(1, 1); polyData->SetPoints(points); polyData->SetLines(lines); vtkSmartPointer extrude = vtkSmartPointer::New(); extrude->SetInputData(polyData); extrude->SetExtrusionTypeToNormalExtrusion(); extrude->SetVector(0, 0, 30.0); extrude->SetScaleFactor(0.5); extrude->Update(); vtkSmartPointer mapper = vtkSmartPointer::New(); mapper->SetInputConnection(extrude->GetOutputPort()); vtkSmartPointer actor = vtkSmartPointer::New(); actor->SetMapper(mapper); actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); vtkSmartPointer ren = vtkSmartPointer::New(); ren->SetBackground(.4, .5, .7); ren->AddActor(actor); vtkSmartPointer renWin = vtkSmartPointer::New(); renWin->AddRenderer(ren); renWin->SetSize(600, 600); vtkSmartPointer iren = vtkSmartPointer::New(); iren->SetRenderWindow(renWin); vtkSmartPointer style = vtkSmartPointer::New(); iren->SetInteractorStyle(style); renWin->Render(); iren->Initialize(); iren->Start(); return EXIT_SUCCESS; } ``` -- View this message in context: http://vtk.1045678.n5.nabble.com/Create-cylinder-whose-cross-section-is-ellipse-tp5744148.html Sent from the VTK - Users mailing list archive at Nabble.com. From coyarzunlaura at googlemail.com Wed Jul 26 05:31:11 2017 From: coyarzunlaura at googlemail.com (Cristina Oyarzun) Date: Wed, 26 Jul 2017 11:31:11 +0200 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Dear Scott and Aron, thank you for your answers. I was indeed using an older version of Webpack, but I already upgraded to the newest version. Unfortunately I keep getting errors when I try to read the JSON file. To this I have to add that although I have been using vtk for quite a long time now, I am completely new to javascript. If I understood correctly with webpack 2 I do not need to add anything to the webpack.config.js to be able to read json files in the index.js. Is this right? However, I try to read the json file with the following command in index.js: const json = require('./file.json'); apart of that line of code I didnt write anything else related to the json file. I got the following error: ERROR in ./src/file.json Module build failed: SyntaxError: Unexpected token / in JSON at position 146 at Object.parse (native) at Object.module.exports (D:\VTK-JS\node_modules\json-loader\index.js:4: 49) @ ./src/index.js 285:13-35 @ ./src/index.js @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/index.js webpack: Failed to compile. Thank you very much!!! Cristina On Fri, Jul 21, 2017 at 5:50 PM, Scott Wittenburg < scott.wittenburg at kitware.com> wrote: > Hi Cristina, > > In vtk.js we now use webpack2 (in master at least, you may have picked an > older version though), and the webpack2 documentation states that you no > longer need a loader for json: > > https://webpack.js.org/guides/migrating/#json-loader-is-not- > required-anymore > > Is your project also using webpack2? In that case you shouldn't need the > json loader. Also, when you refer to "Build-in modules of Node.js", does > that refer specifically to this: > > https://github.com/sindresorhus/builtin-modules > > or do you mean something else? > > Cheers, > Scott > > On Fri, Jul 21, 2017 at 8:57 AM, Aron Helser > wrote: > >> Hi Cristina, >> ParaViewWeb uses this webpack 1.x loader: >> { >> test: /\.json$/, >> loader: 'json-loader', >> }, >> That should allow you to 'include' a json file in your javascript, and >> then you might need to use the built-in JSON.parse() to turn it into an >> object. >> >> Regards, >> Aron >> >> On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < >> vtkusers at vtk.org> wrote: >> >>> Dear all, >>> >>> I visualized several actors using VTK-js. Now I want to read a .json >>> file and according to the information that it is included there assign >>> different colors to the actors. >>> >>> Unfortunately as soon as I try to use the Build-in modules of Node.js I >>> start getting errors. I didnt manage to find out how do I have to adapt the >>> "webpack.config.js" (or the "package.json"?) so that it works. >>> >>> I found somewhere in a forum that it should work by adding " target: >>> 'node' " to the webpack.config.js but it didnt. Any help would be great! >>> >>> Thank you! >>> Cristina >>> >>> _______________________________________________ >>> 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 >>> >>> >> >> _______________________________________________ >> 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 >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kor1581 at gmail.com Wed Jul 26 06:35:44 2017 From: kor1581 at gmail.com (K O ranjith) Date: Wed, 26 Jul 2017 16:05:44 +0530 Subject: [vtkusers] fit to screen in vtkImageViewer2 + QVTKWidget Message-ID: Hello, Using vtkImageViewer2 + QVTKWidget and vtkInteractorStyleImage, I created a DICOM image viewer. But the image mot filling to the the entire viewport. I need the fit the image to the viewport. For this I tried different suggestion available online, but no effect, like m_vtkImViewer->GetRenderer()->GetActiveCamera()->ParallelProjectionOn(); m_vtkImViewer->GetRenderer()->GetActiveCamera()->SetParallelScale(1000); m_vtkImViewer->GetRenderer()->GetActiveCamera()->Dolly(10); m_vtkImViewer->GetRenderWindow()->SetSize(50, 50); Please help to fit the image in window. Screenshot of current viewer is attached. As shown in the screnshot the image is displaying within a margin inside the viewport. But the corner annotations (set using vtkCornerAnnotation) are set in corners of the view port. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Untitled.jpg Type: image/jpeg Size: 170473 bytes Desc: not available URL: From bill.lorensen at gmail.com Wed Jul 26 07:46:59 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Wed, 26 Jul 2017 07:46:59 -0400 Subject: [vtkusers] fit to screen in vtkImageViewer2 + QVTKWidget In-Reply-To: References: Message-ID: This example may help. https://lorensen.github.io/VTKExamples/site/Cxx/Images/FillWindow/ On Jul 26, 2017 6:36 AM, "K O ranjith" wrote: > Hello, > Using vtkImageViewer2 + QVTKWidget and vtkInteractorStyleImage, I > created a DICOM image viewer. But the image mot filling to the the > entire viewport. I need the fit the image to the viewport. For this I > tried different suggestion available online, but no effect, > like > > m_vtkImViewer->GetRenderer()->GetActiveCamera()->ParallelProjectionOn(); > > m_vtkImViewer->GetRenderer()->GetActiveCamera()->SetParallelScale(1000); > > > m_vtkImViewer->GetRenderer()->GetActiveCamera()->Dolly(10); > > > m_vtkImViewer->GetRenderWindow()->SetSize(50, 50); > > > Please help to fit the image in window. > > Screenshot of current viewer is attached. > > As shown in the screnshot the image is displaying within a margin inside the viewport. > > But the corner annotations (set using vtkCornerAnnotation) are set in corners of the view port. > > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill.lorensen at gmail.com Wed Jul 26 09:05:11 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Wed, 26 Jul 2017 09:05:11 -0400 Subject: [vtkusers] Create cylinder whose cross section is ellipse In-Reply-To: <1501056174249-5744148.post@n5.nabble.com> References: <1501056174249-5744148.post@n5.nabble.com> Message-ID: Your creation of the polydata was flawed. This works: #include "vtkPoints.h" #include "vtkPolyLine.h" #include "vtkSmartPointer.h" #include "vtkLinearExtrusionFilter.h" #include "vtkDataSetMapper.h" #include "vtkPolyDataMapper.h" #include "vtkActor.h" #include "vtkProperty.h" #include "vtkCamera.h" #include "vtkRenderer.h" #include "vtkRenderWindow.h" #include "vtkRenderWindowInteractor.h" #include "vtkInteractorStyleTrackballCamera.h" int main(int argc, char *argv[]) { double angle = 0; double r1, r2; int id = 0; int CenterX, CenterY; r1 = 50; r2 = 30; vtkSmartPointer points = vtkSmartPointer::New(); points->SetNumberOfPoints(31); while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 60.0)) { points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) + CenterY, 0); angle = angle + (vtkMath::Pi() / 60.0); id++; } vtkSmartPointer line = vtkSmartPointer::New(); line->GetPointIds()->SetNumberOfIds(id); for(unsigned int i = 0; i < id; i++) { line->GetPointIds()->SetId(i,i); } vtkSmartPointer lines = vtkSmartPointer::New(); lines->InsertNextCell(line); vtkSmartPointer polyData = vtkSmartPointer::New(); polyData->GlobalReleaseDataFlagOff(); polyData->Allocate(1, 1); polyData->SetPoints(points); polyData->SetLines(lines); vtkSmartPointer extrude = vtkSmartPointer::New(); extrude->SetInputData(polyData); extrude->SetExtrusionTypeToNormalExtrusion(); extrude->SetVector(0, 0, 30.0); extrude->SetScaleFactor(0.5); extrude->Update(); vtkSmartPointer mapper = vtkSmartPointer::New(); mapper->SetInputConnection(extrude->GetOutputPort()); vtkSmartPointer actor = vtkSmartPointer::New(); actor->SetMapper(mapper); actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); vtkSmartPointer ren = vtkSmartPointer::New(); ren->SetBackground(.4, .5, .7); ren->AddActor(actor); vtkSmartPointer renWin = vtkSmartPointer::New(); renWin->AddRenderer(ren); renWin->SetSize(600, 600); vtkSmartPointer iren = vtkSmartPointer::New(); iren->SetRenderWindow(renWin); vtkSmartPointer style = vtkSmartPointer::New(); iren->SetInteractorStyle(style); renWin->Render(); iren->Initialize(); iren->Start(); return EXIT_SUCCESS; } On Wed, Jul 26, 2017 at 4:02 AM, arwtyxouymz wrote: > Hi, > > I'm a newer of VTK, and use VTK-8.0.0 by C++. > > I want to create a cylinder whose cross section is ellipse. > > Firstly I create 2d ellipse, then I extrude the ellipse along z axis. > I could create 2d ellipse, and render it. > But I have applied vtkLinearExtrusionFilter, my code crash with exit code > 11. > What shoud i do? > > please help me. > > This is my code. > > ``` > #include "vtkPoints.h" > #include "vtkSmartPointer.h" > #include "vtkLinearExtrusionFilter.h" > #include "vtkDataSetMapper.h" > #include "vtkPolyDataMapper.h" > #include "vtkActor.h" > #include "vtkProperty.h" > #include "vtkCamera.h" > #include "vtkRenderer.h" > #include "vtkRenderWindow.h" > #include "vtkRenderWindowInteractor.h" > #include "vtkInteractorStyleTrackballCamera.h" > > int main(int argc, char *argv[]) > { > > double angle = 0; > double r1, r2; > int id = 0; > int CenterX, CenterY; > r1 = 50; > r2 = 30; > > vtkSmartPointer points = > vtkSmartPointer::New(); > points->SetNumberOfPoints(31); > while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 60.0)) > { > points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) + > CenterY, 0); > angle = angle + (vtkMath::Pi() / 60.0); > id++; > } > > vtkSmartPointer lines = > vtkSmartPointer::New(); > lines->Allocate(1, 1); > lines->InsertNextCell(id); > lines->SetNumberOfCells(id); > for (int k = 0; k < id; ++k) { > lines->InsertCellPoint(k); > } > > vtkSmartPointer polyData = > vtkSmartPointer::New(); > polyData->GlobalReleaseDataFlagOff(); > polyData->Allocate(1, 1); > polyData->SetPoints(points); > polyData->SetLines(lines); > > vtkSmartPointer extrude = > vtkSmartPointer::New(); > extrude->SetInputData(polyData); > extrude->SetExtrusionTypeToNormalExtrusion(); > extrude->SetVector(0, 0, 30.0); > extrude->SetScaleFactor(0.5); > extrude->Update(); > > vtkSmartPointer mapper = > vtkSmartPointer::New(); > mapper->SetInputConnection(extrude->GetOutputPort()); > > vtkSmartPointer actor = > vtkSmartPointer::New(); > actor->SetMapper(mapper); > actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); > > vtkSmartPointer ren = > vtkSmartPointer::New(); > ren->SetBackground(.4, .5, .7); > ren->AddActor(actor); > > > vtkSmartPointer renWin = > vtkSmartPointer::New(); > renWin->AddRenderer(ren); > renWin->SetSize(600, 600); > > vtkSmartPointer iren = > vtkSmartPointer::New(); > iren->SetRenderWindow(renWin); > > vtkSmartPointer style = > vtkSmartPointer::New(); > iren->SetInteractorStyle(style); > > renWin->Render(); > iren->Initialize(); > iren->Start(); > > return EXIT_SUCCESS; > } > ``` > > > > -- > View this message in context: http://vtk.1045678.n5.nabble.com/Create-cylinder-whose-cross-section-is-ellipse-tp5744148.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 -- Unpaid intern in BillsBasement at noware dot com From aron.helser at kitware.com Wed Jul 26 09:35:59 2017 From: aron.helser at kitware.com (Aron Helser) Date: Wed, 26 Jul 2017 09:35:59 -0400 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Hi Cristina, I think the 'require' function may be the problem - in vtk-js and ParaViewWeb, we typically use 'import', like this: import localPresetImages from '../../presets.json'; Try it that way? Regards, Aron On Wed, Jul 26, 2017 at 5:31 AM, Cristina Oyarzun < coyarzunlaura at googlemail.com> wrote: > Dear Scott and Aron, > > thank you for your answers. I was indeed using an older version of > Webpack, but I already upgraded to the newest version. Unfortunately I keep > getting errors when I try to read the JSON file. To this I have to add that > although I have been using vtk for quite a long time now, I am completely > new to javascript. > > If I understood correctly with webpack 2 I do not need to add anything to > the webpack.config.js to be able to read json files in the index.js. Is > this right? However, I try to read the json file with the following command > in index.js: > > const json = require('./file.json'); > > apart of that line of code I didnt write anything else related to the json file. I got the following error: > > ERROR in ./src/file.json > Module build failed: SyntaxError: Unexpected token / in JSON at position 146 > at Object.parse (native) > at Object.module.exports (D:\VTK-JS\node_modules\json-loader\index.js:4: > 49) > @ ./src/index.js 285:13-35 > @ ./src/index.js > @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/index.js > webpack: Failed to compile. > > Thank you very much!!! > > Cristina > > > > On Fri, Jul 21, 2017 at 5:50 PM, Scott Wittenburg < > scott.wittenburg at kitware.com> wrote: > >> Hi Cristina, >> >> In vtk.js we now use webpack2 (in master at least, you may have picked an >> older version though), and the webpack2 documentation states that you no >> longer need a loader for json: >> >> https://webpack.js.org/guides/migrating/#json-loader-is-not- >> required-anymore >> >> Is your project also using webpack2? In that case you shouldn't need the >> json loader. Also, when you refer to "Build-in modules of Node.js", does >> that refer specifically to this: >> >> https://github.com/sindresorhus/builtin-modules >> >> or do you mean something else? >> >> Cheers, >> Scott >> >> On Fri, Jul 21, 2017 at 8:57 AM, Aron Helser >> wrote: >> >>> Hi Cristina, >>> ParaViewWeb uses this webpack 1.x loader: >>> { >>> test: /\.json$/, >>> loader: 'json-loader', >>> }, >>> That should allow you to 'include' a json file in your javascript, and >>> then you might need to use the built-in JSON.parse() to turn it into an >>> object. >>> >>> Regards, >>> Aron >>> >>> On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < >>> vtkusers at vtk.org> wrote: >>> >>>> Dear all, >>>> >>>> I visualized several actors using VTK-js. Now I want to read a .json >>>> file and according to the information that it is included there assign >>>> different colors to the actors. >>>> >>>> Unfortunately as soon as I try to use the Build-in modules of Node.js I >>>> start getting errors. I didnt manage to find out how do I have to adapt the >>>> "webpack.config.js" (or the "package.json"?) so that it works. >>>> >>>> I found somewhere in a forum that it should work by adding " target: >>>> 'node' " to the webpack.config.js but it didnt. Any help would be great! >>>> >>>> Thank you! >>>> Cristina >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>> >>> _______________________________________________ >>> 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 >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Wed Jul 26 10:12:23 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 26 Jul 2017 08:12:23 -0600 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Hi Christina, I think the issue is inside your JSON file which might not be properly formed. To make sure your file is properly formatted, you can use a service like below to spot the issue quickly. https://jsonlint.com/ Regarding the "require" or "import" method to ingest your file, they should both work but we prefer to use the "import" syntax. Seb On Wed, Jul 26, 2017 at 7:35 AM, Aron Helser wrote: > Hi Cristina, > I think the 'require' function may be the problem - in vtk-js and > ParaViewWeb, we typically use 'import', like this: > > import localPresetImages from '../../presets.json'; > > Try it that way? > Regards, > Aron > > On Wed, Jul 26, 2017 at 5:31 AM, Cristina Oyarzun < > coyarzunlaura at googlemail.com> wrote: > >> Dear Scott and Aron, >> >> thank you for your answers. I was indeed using an older version of >> Webpack, but I already upgraded to the newest version. Unfortunately I keep >> getting errors when I try to read the JSON file. To this I have to add that >> although I have been using vtk for quite a long time now, I am completely >> new to javascript. >> >> If I understood correctly with webpack 2 I do not need to add anything to >> the webpack.config.js to be able to read json files in the index.js. Is >> this right? However, I try to read the json file with the following command >> in index.js: >> >> const json = require('./file.json'); >> >> apart of that line of code I didnt write anything else related to the json file. I got the following error: >> >> ERROR in ./src/file.json >> Module build failed: SyntaxError: Unexpected token / in JSON at position 146 >> at Object.parse (native) >> at Object.module.exports (D:\VTK-JS\node_modules\json-loader\index.js:4: >> 49) >> @ ./src/index.js 285:13-35 >> @ ./src/index.js >> @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/index.js >> webpack: Failed to compile. >> >> Thank you very much!!! >> >> Cristina >> >> >> >> On Fri, Jul 21, 2017 at 5:50 PM, Scott Wittenburg < >> scott.wittenburg at kitware.com> wrote: >> >>> Hi Cristina, >>> >>> In vtk.js we now use webpack2 (in master at least, you may have picked >>> an older version though), and the webpack2 documentation states that you no >>> longer need a loader for json: >>> >>> https://webpack.js.org/guides/migrating/#json-loader-is-not- >>> required-anymore >>> >>> Is your project also using webpack2? In that case you shouldn't need >>> the json loader. Also, when you refer to "Build-in modules of Node.js", >>> does that refer specifically to this: >>> >>> https://github.com/sindresorhus/builtin-modules >>> >>> or do you mean something else? >>> >>> Cheers, >>> Scott >>> >>> On Fri, Jul 21, 2017 at 8:57 AM, Aron Helser >>> wrote: >>> >>>> Hi Cristina, >>>> ParaViewWeb uses this webpack 1.x loader: >>>> { >>>> test: /\.json$/, >>>> loader: 'json-loader', >>>> }, >>>> That should allow you to 'include' a json file in your javascript, and >>>> then you might need to use the built-in JSON.parse() to turn it into an >>>> object. >>>> >>>> Regards, >>>> Aron >>>> >>>> On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < >>>> vtkusers at vtk.org> wrote: >>>> >>>>> Dear all, >>>>> >>>>> I visualized several actors using VTK-js. Now I want to read a .json >>>>> file and according to the information that it is included there assign >>>>> different colors to the actors. >>>>> >>>>> Unfortunately as soon as I try to use the Build-in modules of Node.js >>>>> I start getting errors. I didnt manage to find out how do I have to adapt >>>>> the "webpack.config.js" (or the "package.json"?) so that it works. >>>>> >>>>> I found somewhere in a forum that it should work by adding " target: >>>>> 'node' " to the webpack.config.js but it didnt. Any help would be great! >>>>> >>>>> Thank you! >>>>> Cristina >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>> >> > > _______________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill.lorensen at gmail.com Wed Jul 26 10:24:37 2017 From: bill.lorensen at gmail.com (Bill Lorensen) Date: Wed, 26 Jul 2017 10:24:37 -0400 Subject: [vtkusers] Create cylinder whose cross section is ellipse In-Reply-To: References: <1501056174249-5744148.post@n5.nabble.com> Message-ID: I just added an example based on your code... https://lorensen.github.io/VTKExamples/site/Cxx/GeometricObjects/EllipticalCylinder/ On Wed, Jul 26, 2017 at 9:05 AM, Bill Lorensen wrote: > Your creation of the polydata was flawed. > This works: > #include "vtkPoints.h" > #include "vtkPolyLine.h" > #include "vtkSmartPointer.h" > #include "vtkLinearExtrusionFilter.h" > #include "vtkDataSetMapper.h" > #include "vtkPolyDataMapper.h" > #include "vtkActor.h" > #include "vtkProperty.h" > #include "vtkCamera.h" > #include "vtkRenderer.h" > #include "vtkRenderWindow.h" > #include "vtkRenderWindowInteractor.h" > #include "vtkInteractorStyleTrackballCamera.h" > > int main(int argc, char *argv[]) > { > > double angle = 0; > double r1, r2; > int id = 0; > int CenterX, CenterY; > r1 = 50; > r2 = 30; > > vtkSmartPointer points = > vtkSmartPointer::New(); > points->SetNumberOfPoints(31); > while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 60.0)) > { > points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) + > CenterY, 0); > angle = angle + (vtkMath::Pi() / 60.0); > id++; > } > > vtkSmartPointer line = > vtkSmartPointer::New(); > line->GetPointIds()->SetNumberOfIds(id); > for(unsigned int i = 0; i < id; i++) > { > line->GetPointIds()->SetId(i,i); > } > > vtkSmartPointer lines = > vtkSmartPointer::New(); > lines->InsertNextCell(line); > > vtkSmartPointer polyData = > vtkSmartPointer::New(); > polyData->GlobalReleaseDataFlagOff(); > polyData->Allocate(1, 1); > polyData->SetPoints(points); > polyData->SetLines(lines); > > vtkSmartPointer extrude = > vtkSmartPointer::New(); > extrude->SetInputData(polyData); > extrude->SetExtrusionTypeToNormalExtrusion(); > extrude->SetVector(0, 0, 30.0); > extrude->SetScaleFactor(0.5); > extrude->Update(); > > vtkSmartPointer mapper = > vtkSmartPointer::New(); > mapper->SetInputConnection(extrude->GetOutputPort()); > > vtkSmartPointer actor = > vtkSmartPointer::New(); > actor->SetMapper(mapper); > actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); > > vtkSmartPointer ren = > vtkSmartPointer::New(); > ren->SetBackground(.4, .5, .7); > ren->AddActor(actor); > > > vtkSmartPointer renWin = > vtkSmartPointer::New(); > renWin->AddRenderer(ren); > renWin->SetSize(600, 600); > > vtkSmartPointer iren = > vtkSmartPointer::New(); > iren->SetRenderWindow(renWin); > > vtkSmartPointer style = > vtkSmartPointer::New(); > iren->SetInteractorStyle(style); > > renWin->Render(); > iren->Initialize(); > iren->Start(); > > return EXIT_SUCCESS; > } > > On Wed, Jul 26, 2017 at 4:02 AM, arwtyxouymz wrote: >> Hi, >> >> I'm a newer of VTK, and use VTK-8.0.0 by C++. >> >> I want to create a cylinder whose cross section is ellipse. >> >> Firstly I create 2d ellipse, then I extrude the ellipse along z axis. >> I could create 2d ellipse, and render it. >> But I have applied vtkLinearExtrusionFilter, my code crash with exit code >> 11. >> What shoud i do? >> >> please help me. >> >> This is my code. >> >> ``` >> #include "vtkPoints.h" >> #include "vtkSmartPointer.h" >> #include "vtkLinearExtrusionFilter.h" >> #include "vtkDataSetMapper.h" >> #include "vtkPolyDataMapper.h" >> #include "vtkActor.h" >> #include "vtkProperty.h" >> #include "vtkCamera.h" >> #include "vtkRenderer.h" >> #include "vtkRenderWindow.h" >> #include "vtkRenderWindowInteractor.h" >> #include "vtkInteractorStyleTrackballCamera.h" >> >> int main(int argc, char *argv[]) >> { >> >> double angle = 0; >> double r1, r2; >> int id = 0; >> int CenterX, CenterY; >> r1 = 50; >> r2 = 30; >> >> vtkSmartPointer points = >> vtkSmartPointer::New(); >> points->SetNumberOfPoints(31); >> while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 60.0)) >> { >> points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) + >> CenterY, 0); >> angle = angle + (vtkMath::Pi() / 60.0); >> id++; >> } >> >> vtkSmartPointer lines = >> vtkSmartPointer::New(); >> lines->Allocate(1, 1); >> lines->InsertNextCell(id); >> lines->SetNumberOfCells(id); >> for (int k = 0; k < id; ++k) { >> lines->InsertCellPoint(k); >> } >> >> vtkSmartPointer polyData = >> vtkSmartPointer::New(); >> polyData->GlobalReleaseDataFlagOff(); >> polyData->Allocate(1, 1); >> polyData->SetPoints(points); >> polyData->SetLines(lines); >> >> vtkSmartPointer extrude = >> vtkSmartPointer::New(); >> extrude->SetInputData(polyData); >> extrude->SetExtrusionTypeToNormalExtrusion(); >> extrude->SetVector(0, 0, 30.0); >> extrude->SetScaleFactor(0.5); >> extrude->Update(); >> >> vtkSmartPointer mapper = >> vtkSmartPointer::New(); >> mapper->SetInputConnection(extrude->GetOutputPort()); >> >> vtkSmartPointer actor = >> vtkSmartPointer::New(); >> actor->SetMapper(mapper); >> actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); >> >> vtkSmartPointer ren = >> vtkSmartPointer::New(); >> ren->SetBackground(.4, .5, .7); >> ren->AddActor(actor); >> >> >> vtkSmartPointer renWin = >> vtkSmartPointer::New(); >> renWin->AddRenderer(ren); >> renWin->SetSize(600, 600); >> >> vtkSmartPointer iren = >> vtkSmartPointer::New(); >> iren->SetRenderWindow(renWin); >> >> vtkSmartPointer style = >> vtkSmartPointer::New(); >> iren->SetInteractorStyle(style); >> >> renWin->Render(); >> iren->Initialize(); >> iren->Start(); >> >> return EXIT_SUCCESS; >> } >> ``` >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.com/Create-cylinder-whose-cross-section-is-ellipse-tp5744148.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 > > > > -- > Unpaid intern in BillsBasement at noware dot com -- Unpaid intern in BillsBasement at noware dot com From coyarzunlaura at googlemail.com Wed Jul 26 10:44:02 2017 From: coyarzunlaura at googlemail.com (Cristina Oyarzun) Date: Wed, 26 Jul 2017 16:44:02 +0200 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Dear all, thank you very very much for your help! Everything is working now! Cristina On Wed, Jul 26, 2017 at 4:12 PM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Hi Christina, > > I think the issue is inside your JSON file which might not be properly > formed. > To make sure your file is properly formatted, you can use a service like > below to spot the issue quickly. > > https://jsonlint.com/ > > Regarding the "require" or "import" method to ingest your file, they > should both work but we prefer to use the "import" syntax. > > Seb > > > > On Wed, Jul 26, 2017 at 7:35 AM, Aron Helser > wrote: > >> Hi Cristina, >> I think the 'require' function may be the problem - in vtk-js and >> ParaViewWeb, we typically use 'import', like this: >> >> import localPresetImages from '../../presets.json'; >> >> Try it that way? >> Regards, >> Aron >> >> On Wed, Jul 26, 2017 at 5:31 AM, Cristina Oyarzun < >> coyarzunlaura at googlemail.com> wrote: >> >>> Dear Scott and Aron, >>> >>> thank you for your answers. I was indeed using an older version of >>> Webpack, but I already upgraded to the newest version. Unfortunately I keep >>> getting errors when I try to read the JSON file. To this I have to add that >>> although I have been using vtk for quite a long time now, I am completely >>> new to javascript. >>> >>> If I understood correctly with webpack 2 I do not need to add anything >>> to the webpack.config.js to be able to read json files in the index.js. Is >>> this right? However, I try to read the json file with the following command >>> in index.js: >>> >>> const json = require('./file.json'); >>> >>> apart of that line of code I didnt write anything else related to the json file. I got the following error: >>> >>> ERROR in ./src/file.json >>> Module build failed: SyntaxError: Unexpected token / in JSON at position 146 >>> at Object.parse (native) >>> at Object.module.exports (D:\VTK-JS\node_modules\json-loader\index.js:4: >>> 49) >>> @ ./src/index.js 285:13-35 >>> @ ./src/index.js >>> @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/index.js >>> webpack: Failed to compile. >>> >>> Thank you very much!!! >>> >>> Cristina >>> >>> >>> >>> On Fri, Jul 21, 2017 at 5:50 PM, Scott Wittenburg < >>> scott.wittenburg at kitware.com> wrote: >>> >>>> Hi Cristina, >>>> >>>> In vtk.js we now use webpack2 (in master at least, you may have picked >>>> an older version though), and the webpack2 documentation states that you no >>>> longer need a loader for json: >>>> >>>> https://webpack.js.org/guides/migrating/#json-loader-is-not- >>>> required-anymore >>>> >>>> Is your project also using webpack2? In that case you shouldn't need >>>> the json loader. Also, when you refer to "Build-in modules of Node.js", >>>> does that refer specifically to this: >>>> >>>> https://github.com/sindresorhus/builtin-modules >>>> >>>> or do you mean something else? >>>> >>>> Cheers, >>>> Scott >>>> >>>> On Fri, Jul 21, 2017 at 8:57 AM, Aron Helser >>>> wrote: >>>> >>>>> Hi Cristina, >>>>> ParaViewWeb uses this webpack 1.x loader: >>>>> { >>>>> test: /\.json$/, >>>>> loader: 'json-loader', >>>>> }, >>>>> That should allow you to 'include' a json file in your javascript, and >>>>> then you might need to use the built-in JSON.parse() to turn it into an >>>>> object. >>>>> >>>>> Regards, >>>>> Aron >>>>> >>>>> On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < >>>>> vtkusers at vtk.org> wrote: >>>>> >>>>>> Dear all, >>>>>> >>>>>> I visualized several actors using VTK-js. Now I want to read a .json >>>>>> file and according to the information that it is included there assign >>>>>> different colors to the actors. >>>>>> >>>>>> Unfortunately as soon as I try to use the Build-in modules of Node.js >>>>>> I start getting errors. I didnt manage to find out how do I have to adapt >>>>>> the "webpack.config.js" (or the "package.json"?) so that it works. >>>>>> >>>>>> I found somewhere in a forum that it should work by adding " target: >>>>>> 'node' " to the webpack.config.js but it didnt. Any help would be great! >>>>>> >>>>>> Thank you! >>>>>> Cristina >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> >>>> >>> >> >> _______________________________________________ >> 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 >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron.helser at kitware.com Wed Jul 26 10:47:30 2017 From: aron.helser at kitware.com (Aron Helser) Date: Wed, 26 Jul 2017 10:47:30 -0400 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Christina, Did you have a mistake in your JSON file? On Wed, Jul 26, 2017 at 10:44 AM, Cristina Oyarzun < coyarzunlaura at googlemail.com> wrote: > Dear all, > > thank you very very much for your help! Everything is working now! > > Cristina > > On Wed, Jul 26, 2017 at 4:12 PM, Sebastien Jourdain < > sebastien.jourdain at kitware.com> wrote: > >> Hi Christina, >> >> I think the issue is inside your JSON file which might not be properly >> formed. >> To make sure your file is properly formatted, you can use a service like >> below to spot the issue quickly. >> >> https://jsonlint.com/ >> >> Regarding the "require" or "import" method to ingest your file, they >> should both work but we prefer to use the "import" syntax. >> >> Seb >> >> >> >> On Wed, Jul 26, 2017 at 7:35 AM, Aron Helser >> wrote: >> >>> Hi Cristina, >>> I think the 'require' function may be the problem - in vtk-js and >>> ParaViewWeb, we typically use 'import', like this: >>> >>> import localPresetImages from '../../presets.json'; >>> >>> Try it that way? >>> Regards, >>> Aron >>> >>> On Wed, Jul 26, 2017 at 5:31 AM, Cristina Oyarzun < >>> coyarzunlaura at googlemail.com> wrote: >>> >>>> Dear Scott and Aron, >>>> >>>> thank you for your answers. I was indeed using an older version of >>>> Webpack, but I already upgraded to the newest version. Unfortunately I keep >>>> getting errors when I try to read the JSON file. To this I have to add that >>>> although I have been using vtk for quite a long time now, I am completely >>>> new to javascript. >>>> >>>> If I understood correctly with webpack 2 I do not need to add anything >>>> to the webpack.config.js to be able to read json files in the index.js. Is >>>> this right? However, I try to read the json file with the following command >>>> in index.js: >>>> >>>> const json = require('./file.json'); >>>> >>>> apart of that line of code I didnt write anything else related to the json file. I got the following error: >>>> >>>> ERROR in ./src/file.json >>>> Module build failed: SyntaxError: Unexpected token / in JSON at position 146 >>>> at Object.parse (native) >>>> at Object.module.exports (D:\VTK-JS\node_modules\json-loader\index.js:4: >>>> 49) >>>> @ ./src/index.js 285:13-35 >>>> @ ./src/index.js >>>> @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/index.js >>>> webpack: Failed to compile. >>>> >>>> Thank you very much!!! >>>> >>>> Cristina >>>> >>>> >>>> >>>> On Fri, Jul 21, 2017 at 5:50 PM, Scott Wittenburg < >>>> scott.wittenburg at kitware.com> wrote: >>>> >>>>> Hi Cristina, >>>>> >>>>> In vtk.js we now use webpack2 (in master at least, you may have picked >>>>> an older version though), and the webpack2 documentation states that you no >>>>> longer need a loader for json: >>>>> >>>>> https://webpack.js.org/guides/migrating/#json-loader-is-not- >>>>> required-anymore >>>>> >>>>> Is your project also using webpack2? In that case you shouldn't need >>>>> the json loader. Also, when you refer to "Build-in modules of Node.js", >>>>> does that refer specifically to this: >>>>> >>>>> https://github.com/sindresorhus/builtin-modules >>>>> >>>>> or do you mean something else? >>>>> >>>>> Cheers, >>>>> Scott >>>>> >>>>> On Fri, Jul 21, 2017 at 8:57 AM, Aron Helser >>>>> wrote: >>>>> >>>>>> Hi Cristina, >>>>>> ParaViewWeb uses this webpack 1.x loader: >>>>>> { >>>>>> test: /\.json$/, >>>>>> loader: 'json-loader', >>>>>> }, >>>>>> That should allow you to 'include' a json file in your javascript, >>>>>> and then you might need to use the built-in JSON.parse() to turn it into an >>>>>> object. >>>>>> >>>>>> Regards, >>>>>> Aron >>>>>> >>>>>> On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < >>>>>> vtkusers at vtk.org> wrote: >>>>>> >>>>>>> Dear all, >>>>>>> >>>>>>> I visualized several actors using VTK-js. Now I want to read a .json >>>>>>> file and according to the information that it is included there assign >>>>>>> different colors to the actors. >>>>>>> >>>>>>> Unfortunately as soon as I try to use the Build-in modules of >>>>>>> Node.js I start getting errors. I didnt manage to find out how do I have to >>>>>>> adapt the "webpack.config.js" (or the "package.json"?) so that it works. >>>>>>> >>>>>>> I found somewhere in a forum that it should work by adding " target: >>>>>>> 'node' " to the webpack.config.js but it didnt. Any help would be great! >>>>>>> >>>>>>> Thank you! >>>>>>> Cristina >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> 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 >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From coyarzunlaura at googlemail.com Wed Jul 26 10:55:55 2017 From: coyarzunlaura at googlemail.com (Cristina Oyarzun) Date: Wed, 26 Jul 2017 16:55:55 +0200 Subject: [vtkusers] VTK-js: how to read a .json file In-Reply-To: References: Message-ID: Yes, I had a comment in it and did not know this is not possible in a JSON file... Thanks a lot! On Wed, Jul 26, 2017 at 4:47 PM, Aron Helser wrote: > Christina, > Did you have a mistake in your JSON file? > > > On Wed, Jul 26, 2017 at 10:44 AM, Cristina Oyarzun < > coyarzunlaura at googlemail.com> wrote: > >> Dear all, >> >> thank you very very much for your help! Everything is working now! >> >> Cristina >> >> On Wed, Jul 26, 2017 at 4:12 PM, Sebastien Jourdain < >> sebastien.jourdain at kitware.com> wrote: >> >>> Hi Christina, >>> >>> I think the issue is inside your JSON file which might not be properly >>> formed. >>> To make sure your file is properly formatted, you can use a service like >>> below to spot the issue quickly. >>> >>> https://jsonlint.com/ >>> >>> Regarding the "require" or "import" method to ingest your file, they >>> should both work but we prefer to use the "import" syntax. >>> >>> Seb >>> >>> >>> >>> On Wed, Jul 26, 2017 at 7:35 AM, Aron Helser >>> wrote: >>> >>>> Hi Cristina, >>>> I think the 'require' function may be the problem - in vtk-js and >>>> ParaViewWeb, we typically use 'import', like this: >>>> >>>> import localPresetImages from '../../presets.json'; >>>> >>>> Try it that way? >>>> Regards, >>>> Aron >>>> >>>> On Wed, Jul 26, 2017 at 5:31 AM, Cristina Oyarzun < >>>> coyarzunlaura at googlemail.com> wrote: >>>> >>>>> Dear Scott and Aron, >>>>> >>>>> thank you for your answers. I was indeed using an older version of >>>>> Webpack, but I already upgraded to the newest version. Unfortunately I keep >>>>> getting errors when I try to read the JSON file. To this I have to add that >>>>> although I have been using vtk for quite a long time now, I am completely >>>>> new to javascript. >>>>> >>>>> If I understood correctly with webpack 2 I do not need to add anything >>>>> to the webpack.config.js to be able to read json files in the index.js. Is >>>>> this right? However, I try to read the json file with the following command >>>>> in index.js: >>>>> >>>>> const json = require('./file.json'); >>>>> >>>>> apart of that line of code I didnt write anything else related to the json file. I got the following error: >>>>> >>>>> ERROR in ./src/file.json >>>>> Module build failed: SyntaxError: Unexpected token / in JSON at position 146 >>>>> at Object.parse (native) >>>>> at Object.module.exports (D:\VTK-JS\node_modules\json-loader\index.js:4: >>>>> 49) >>>>> @ ./src/index.js 285:13-35 >>>>> @ ./src/index.js >>>>> @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/index.js >>>>> webpack: Failed to compile. >>>>> >>>>> Thank you very much!!! >>>>> >>>>> Cristina >>>>> >>>>> >>>>> >>>>> On Fri, Jul 21, 2017 at 5:50 PM, Scott Wittenburg < >>>>> scott.wittenburg at kitware.com> wrote: >>>>> >>>>>> Hi Cristina, >>>>>> >>>>>> In vtk.js we now use webpack2 (in master at least, you may have >>>>>> picked an older version though), and the webpack2 documentation states that >>>>>> you no longer need a loader for json: >>>>>> >>>>>> https://webpack.js.org/guides/migrating/#json-loader-is-not- >>>>>> required-anymore >>>>>> >>>>>> Is your project also using webpack2? In that case you shouldn't need >>>>>> the json loader. Also, when you refer to "Build-in modules of Node.js", >>>>>> does that refer specifically to this: >>>>>> >>>>>> https://github.com/sindresorhus/builtin-modules >>>>>> >>>>>> or do you mean something else? >>>>>> >>>>>> Cheers, >>>>>> Scott >>>>>> >>>>>> On Fri, Jul 21, 2017 at 8:57 AM, Aron Helser >>>>> > wrote: >>>>>> >>>>>>> Hi Cristina, >>>>>>> ParaViewWeb uses this webpack 1.x loader: >>>>>>> { >>>>>>> test: /\.json$/, >>>>>>> loader: 'json-loader', >>>>>>> }, >>>>>>> That should allow you to 'include' a json file in your javascript, >>>>>>> and then you might need to use the built-in JSON.parse() to turn it into an >>>>>>> object. >>>>>>> >>>>>>> Regards, >>>>>>> Aron >>>>>>> >>>>>>> On Fri, Jul 21, 2017 at 4:43 AM, Cristina Oyarzun via vtkusers < >>>>>>> vtkusers at vtk.org> wrote: >>>>>>> >>>>>>>> Dear all, >>>>>>>> >>>>>>>> I visualized several actors using VTK-js. Now I want to read a >>>>>>>> .json file and according to the information that it is included there >>>>>>>> assign different colors to the actors. >>>>>>>> >>>>>>>> Unfortunately as soon as I try to use the Build-in modules of >>>>>>>> Node.js I start getting errors. I didnt manage to find out how do I have to >>>>>>>> adapt the "webpack.config.js" (or the "package.json"?) so that it works. >>>>>>>> >>>>>>>> I found somewhere in a forum that it should work by adding " >>>>>>>> target: 'node' " to the webpack.config.js but it didnt. Any help would be >>>>>>>> great! >>>>>>>> >>>>>>>> Thank you! >>>>>>>> Cristina >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arw.tyx-ouy_mz at ezweb.ne.jp Wed Jul 26 11:22:23 2017 From: arw.tyx-ouy_mz at ezweb.ne.jp (arwtyxouymz) Date: Wed, 26 Jul 2017 08:22:23 -0700 (MST) Subject: [vtkusers] Create cylinder whose cross section is ellipse In-Reply-To: References: <1501056174249-5744148.post@n5.nabble.com> Message-ID: <1501082543249-5744164.post@n5.nabble.com> Dear Bill Lorensen Thank you for your reply! You've been very helpful. I have one more question. I wanted to render axes, and tried this example http://www.vtk.org/Wiki/VTK/Examples/Cxx/Visualization/DisplayCoordinateAxes. But this axes too little for me. I want to render axes like this picture. ellipse.png What should i do? please help me. -- View this message in context: http://vtk.1045678.n5.nabble.com/Create-cylinder-whose-cross-section-is-ellipse-tp5744148p5744164.html Sent from the VTK - Users mailing list archive at Nabble.com. From arw.tyx-ouy_mz at ezweb.ne.jp Thu Jul 27 03:51:32 2017 From: arw.tyx-ouy_mz at ezweb.ne.jp (arwtyxouymz) Date: Thu, 27 Jul 2017 00:51:32 -0700 (MST) Subject: [vtkusers] Normal vector of the surface of ellipstic cylinder Message-ID: <1501141892687-5744171.post@n5.nabble.com> I want to make normal vector of the surface of ellipstic cylinder. To each surface point, I want to render normal vector, and get surface point. The current code is this. #include "vtkPoints.h" #include "vtkSmartPointer.h" #include "vtkLinearExtrusionFilter.h" #include "vtkDataSetMapper.h" #include "vtkPolyDataMapper.h" #include "vtkActor.h" #include "vtkProperty.h" #include "vtkCamera.h" #include "vtkRenderer.h" #include "vtkRenderWindow.h" #include "vtkRenderWindowInteractor.h" #include "vtkInteractorStyleTrackballCamera.h" #include "vtkPolyLine.h" int main(int argc, char *argv[]) { double angle = 0; double r1, r2; int id = 0; int CenterX, CenterY; r1 = 50; r2 = 30; CenterX = 0; CenterY = 0; vtkSmartPointer points = vtkSmartPointer::New(); points->SetNumberOfPoints(31); while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 360.0)) { points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) + CenterY, 0); angle = angle + (vtkMath::Pi() / 360.0); id++; } vtkSmartPointer line = vtkSmartPointer::New(); line->GetPointIds()->SetNumberOfIds(id); for (int k = 0; k < id; ++k) { line->GetPointIds()->SetId(k, k); } vtkSmartPointer lines = vtkSmartPointer::New(); lines->InsertNextCell(line); vtkSmartPointer polyData = vtkSmartPointer::New(); polyData->GlobalReleaseDataFlagOff(); polyData->Allocate(1, 1); polyData->SetPoints(points); polyData->SetLines(lines); vtkSmartPointer extrude = vtkSmartPointer::New(); extrude->SetInputData(polyData); extrude->SetExtrusionTypeToNormalExtrusion(); extrude->SetVector(0, 0, 100.0); extrude->SetScaleFactor(0.5); extrude->Update(); vtkSmartPointer mapper = vtkSmartPointer::New(); mapper->SetInputConnection(extrude->GetOutputPort()); /* vtkSmartPointer cylinder = vtkSmartPointer::New(); cylinder->SetRadius(5.0); cylinder->SetHeight(10.0); cylinder->SetResolution(100); vtkSmartPointer mapper = vtkSmartPointer::New(); mapper->SetInputConnection(cylinder->GetOutputPort()); */ vtkSmartPointer actor = vtkSmartPointer::New(); actor->SetMapper(mapper); actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); vtkSmartPointer ren = vtkSmartPointer::New(); ren->SetBackground(.4, .5, .7); ren->AddActor(actor); vtkSmartPointer renWin = vtkSmartPointer::New(); renWin->AddRenderer(ren); renWin->SetSize(600, 600); vtkSmartPointer iren = vtkSmartPointer::New(); iren->SetRenderWindow(renWin); vtkSmartPointer style = vtkSmartPointer::New(); iren->SetInteractorStyle(style); renWin->Render(); iren->Initialize(); iren->Start(); return EXIT_SUCCESS; } please help me! -- View this message in context: http://vtk.1045678.n5.nabble.com/Normal-vector-of-the-surface-of-ellipstic-cylinder-tp5744171.html Sent from the VTK - Users mailing list archive at Nabble.com. From kor1581 at gmail.com Thu Jul 27 05:32:32 2017 From: kor1581 at gmail.com (K O ranjith) Date: Thu, 27 Jul 2017 15:02:32 +0530 Subject: [vtkusers] fit to screen in vtkImageViewer2 + QVTKWidget In-Reply-To: References: Message-ID: Thanks for the solution, One more doubt in my application, vtkDICOMImageReader is used for reading all the DICOM files in a folder and setting directly to vtkImageViewer2 through SetInputConnection(reader->GetOutputPort());. The DICOM images in the folder might have different size. In this case how can get "Extent" "Orgin" "spacing" parameters of each image. Have any methods to extract these from vtkDICOMImageReader or vtkImageViewer2 ? On Wed, Jul 26, 2017 at 5:16 PM, Bill Lorensen wrote: > This example may help. > https://lorensen.github.io/VTKExamples/site/Cxx/Images/FillWindow/ > > On Jul 26, 2017 6:36 AM, "K O ranjith" wrote: > >> Hello, >> Using vtkImageViewer2 + QVTKWidget and vtkInteractorStyleImage, I >> created a DICOM image viewer. But the image mot filling to the the >> entire viewport. I need the fit the image to the viewport. For this I >> tried different suggestion available online, but no effect, >> like >> >> m_vtkImViewer->GetRenderer()->GetActiveCamera()->ParallelProjectionOn(); >> >> m_vtkImViewer->GetRenderer()->GetActiveCamera()->SetParallelScale(1000); >> >> >> m_vtkImViewer->GetRenderer()->GetActiveCamera()->Dolly(10); >> >> >> m_vtkImViewer->GetRenderWindow()->SetSize(50, 50); >> >> >> Please help to fit the image in window. >> >> Screenshot of current viewer is attached. >> >> As shown in the screnshot the image is displaying within a margin inside the viewport. >> >> But the corner annotations (set using vtkCornerAnnotation) are set in corners of the view port. >> >> >> _______________________________________________ >> 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 >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From girish.lande at agiliad.com Thu Jul 27 06:10:02 2017 From: girish.lande at agiliad.com (Girish Lande) Date: Thu, 27 Jul 2017 15:40:02 +0530 Subject: [vtkusers] Normal vector of the surface of ellipstic cylinder In-Reply-To: <1501141892687-5744171.post@n5.nabble.com> References: <1501141892687-5744171.post@n5.nabble.com> Message-ID: Hi, Please refer to attached program. I hope it helps. On 27 July 2017 at 13:21, arwtyxouymz wrote: > > I want to make normal vector of the surface of ellipstic cylinder. > To each surface point, I want to render normal vector, and get surface > point. > The current code is this. > > #include "vtkPoints.h" > #include "vtkSmartPointer.h" > #include "vtkLinearExtrusionFilter.h" > #include "vtkDataSetMapper.h" > #include "vtkPolyDataMapper.h" > #include "vtkActor.h" > #include "vtkProperty.h" > #include "vtkCamera.h" > #include "vtkRenderer.h" > #include "vtkRenderWindow.h" > #include "vtkRenderWindowInteractor.h" > #include "vtkInteractorStyleTrackballCamera.h" > #include "vtkPolyLine.h" > > > int main(int argc, char *argv[]) > { > > double angle = 0; > double r1, r2; > int id = 0; > int CenterX, CenterY; > r1 = 50; > r2 = 30; > CenterX = 0; CenterY = 0; > > vtkSmartPointer points = > vtkSmartPointer::New(); > points->SetNumberOfPoints(31); > while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 360.0)) > { > points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) > + > CenterY, 0); > angle = angle + (vtkMath::Pi() / 360.0); > id++; > } > > vtkSmartPointer line = > vtkSmartPointer::New(); > line->GetPointIds()->SetNumberOfIds(id); > for (int k = 0; k < id; ++k) { > line->GetPointIds()->SetId(k, k); > } > > vtkSmartPointer lines = > vtkSmartPointer::New(); > lines->InsertNextCell(line); > > vtkSmartPointer polyData = > vtkSmartPointer::New(); > polyData->GlobalReleaseDataFlagOff(); > polyData->Allocate(1, 1); > polyData->SetPoints(points); > polyData->SetLines(lines); > > vtkSmartPointer extrude = > vtkSmartPointer::New(); > extrude->SetInputData(polyData); > extrude->SetExtrusionTypeToNormalExtrusion(); > extrude->SetVector(0, 0, 100.0); > extrude->SetScaleFactor(0.5); > extrude->Update(); > > vtkSmartPointer mapper = > vtkSmartPointer::New(); > mapper->SetInputConnection(extrude->GetOutputPort()); > > /* > vtkSmartPointer cylinder = > vtkSmartPointer::New(); > cylinder->SetRadius(5.0); > cylinder->SetHeight(10.0); > cylinder->SetResolution(100); > > vtkSmartPointer mapper = > vtkSmartPointer::New(); > mapper->SetInputConnection(cylinder->GetOutputPort()); > */ > > vtkSmartPointer actor = > vtkSmartPointer::New(); > actor->SetMapper(mapper); > actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); > > vtkSmartPointer ren = > vtkSmartPointer::New(); > ren->SetBackground(.4, .5, .7); > ren->AddActor(actor); > > > vtkSmartPointer renWin = > vtkSmartPointer::New(); > renWin->AddRenderer(ren); > renWin->SetSize(600, 600); > > vtkSmartPointer iren = > vtkSmartPointer::New(); > iren->SetRenderWindow(renWin); > > vtkSmartPointer style = > vtkSmartPointer::New(); > iren->SetInteractorStyle(style); > > renWin->Render(); > iren->Initialize(); > iren->Start(); > > return EXIT_SUCCESS; > } > > please help me! > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Normal-vector-of-the-surface-of-ellipstic-cylinder-tp5744171.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- thanks & regards, Girish -- ------------------------------------------------------------ ------------------------------------------------------------- *Disclaimer:* This email message including any attachments is confidential, and may be privileged and proprietary to Agiliad. If you are not the intended recipient, please notify us immediately by replying to this message and destroy all copies of this message including any attachments. You are NOT authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. Thank you. ------------------------------------------------------------ ------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: normals_at_Each_point_on_sphere.cpp Type: text/x-c++src Size: 7751 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: normals_at_Each_point_on_sphere.png Type: image/png Size: 29790 bytes Desc: not available URL: From rick at pile.com Thu Jul 27 07:19:55 2017 From: rick at pile.com (Rick Dailey) Date: Thu, 27 Jul 2017 04:19:55 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1500569102114-5744068.post@n5.nabble.com> Message-ID: <1501154395427-5744174.post@n5.nabble.com> I have made a substantial advance in my debugging capabilities but still not able to solve this. What I did was to move my entire tomography project into the VTK solution as an ?example? project. This allows me to step-into and debug the VTK dlls, automatically view stack traces, local variables, class member variables, etc. anywhere that I need and it works great. The problem now is that even with this capability I am still unable to locate and fix the bug. Much of it has to do with the complexity of the VTK code. As a reminder: On some volumes I display I get an assert in the VTK code that says a certain vtkTextureObject is not valid. This happens on maybe one in fifty specific volumes but still accounts for a lot of customer complaints when the program crashes or fails to display the volume. Can anyone provide hints as to how I should attempt to debug this now that I have complete debugging access to the VTK code? -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744174.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Thu Jul 27 10:33:34 2017 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 27 Jul 2017 10:33:34 -0400 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501154395427-5744174.post@n5.nabble.com> References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> Message-ID: Have you checked if the issue persists with VTK master? That would be my next suggestion. On Thu, Jul 27, 2017 at 7:19 AM, Rick Dailey wrote: > I have made a substantial advance in my debugging capabilities but still > not > able to solve this. What I did was to move my entire tomography project > into the VTK solution as an ?example? project. This allows me to step-into > and debug the VTK dlls, automatically view stack traces, local variables, > class member variables, etc. anywhere that I need and it works great. The > problem now is that even with this capability I am still unable to locate > and fix the bug. Much of it has to do with the complexity of the VTK code. > > As a reminder: > > On some volumes I display I get an assert in the VTK code that says a > certain vtkTextureObject is not valid. This happens on maybe one in fifty > specific volumes but still accounts for a lot of customer complaints when > the program crashes or fails to display the volume. > > Can anyone provide hints as to how I should attempt to debug this now that > I > have complete debugging access to the VTK code? > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068p5744174.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 swetha.bsharma at gmail.com Thu Jul 27 10:40:35 2017 From: swetha.bsharma at gmail.com (Swetha Sharma) Date: Thu, 27 Jul 2017 14:40:35 +0000 Subject: [vtkusers] Read .vtk file and save as binary STL file Message-ID: Hi, I have .vtk file which i want to read and convert to binary stl file. The documentation has a function WriteBinarySTL (vtkPoints *pts, vtkCellArray *polys, vtkCellArray *strips) . How do I get the information about the vtkpoints and the cellarray? -swetha -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruvva at yahoo.com Thu Jul 27 13:29:26 2017 From: ruvva at yahoo.com (Koteswara Rao Ruvva) Date: Thu, 27 Jul 2017 17:29:26 +0000 (UTC) Subject: [vtkusers] Detect vtkActor motion References: <686222463.723413.1501176566488.ref@mail.yahoo.com> Message-ID: <686222463.723413.1501176566488@mail.yahoo.com> Hello All, I want to find out whether a vtkActor is moved from its initial position. I want to compare vtkActor.GetMatrix() with its initial value, but I don't see vtkMatrix comparison API, like overloaded == or equivalent methods. Please suggest. Thank youRao Ruvva -------------- next part -------------- An HTML attachment was scrubbed... URL: From allison.vacanti at kitware.com Thu Jul 27 16:02:27 2017 From: allison.vacanti at kitware.com (Allie Vacanti) Date: Thu, 27 Jul 2017 16:02:27 -0400 Subject: [vtkusers] Detect vtkActor motion In-Reply-To: <686222463.723413.1501176566488@mail.yahoo.com> References: <686222463.723413.1501176566488.ref@mail.yahoo.com> <686222463.723413.1501176566488@mail.yahoo.com> Message-ID: On Thu, Jul 27, 2017 at 1:29 PM, Koteswara Rao Ruvva via vtkusers wrote: > Hello All, > > I want to find out whether a vtkActor is moved from its initial position. I > want to compare vtkActor.GetMatrix() with its initial value, but I don't see > vtkMatrix comparison API, like overloaded == or equivalent methods. Please > suggest. You'll either need to pull the elements of the matrix out (aMatrix->GetData()) and compare them, or you can just check the modification time (someMatrix->GetMTime()) to see if anything has modified it since the last check, depending on your usecase. HTH, Allie From adarshdesai.dsp at gmail.com Thu Jul 27 18:04:06 2017 From: adarshdesai.dsp at gmail.com (abcd efgh) Date: Thu, 27 Jul 2017 15:04:06 -0700 Subject: [vtkusers] Problem with 2D widgets in multiple viewports Message-ID: Hello All, Previously I have posted similar issues with 2D Slider widget that its not working in multiple view ports. I read something related to old bug, if anyone is aware of the fix or work around please let me know. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayavardhanravi at outlook.com Thu Jul 27 19:05:17 2017 From: jayavardhanravi at outlook.com (Jay) Date: Thu, 27 Jul 2017 16:05:17 -0700 (MST) Subject: [vtkusers] Is it possible change the resolution of actor created by vtkSTLReader Message-ID: <1501196717774-5744181.post@n5.nabble.com> I use the vtkSTLReader to load the data. Can the resolution of the data be reduced after loading the source or is there any method in vtk 7.1 like vtkDecimate to reduce the number of mesh triangles. Any suggestions would be helpful. Regards, Jay -- View this message in context: http://vtk.1045678.n5.nabble.com/Is-it-possible-change-the-resolution-of-actor-created-by-vtkSTLReader-tp5744181.html Sent from the VTK - Users mailing list archive at Nabble.com. From ruvva at yahoo.com Thu Jul 27 18:47:24 2017 From: ruvva at yahoo.com (Koteswara Rao Ruvva) Date: Thu, 27 Jul 2017 22:47:24 +0000 (UTC) Subject: [vtkusers] Detect vtkActor motion In-Reply-To: References: <686222463.723413.1501176566488.ref@mail.yahoo.com> <686222463.723413.1501176566488@mail.yahoo.com> Message-ID: <1295260588.932935.1501195644515@mail.yahoo.com> Thank you Allie. I used the first approach of comparing individual elements of vtkMatrix4x4.BTW, the vtkMatrix.GetData() does not exist in VtkPython. I had to use GetElement(i,j). On Thursday, July 27, 2017, 1:02:48 PM PDT, Allie Vacanti wrote: On Thu, Jul 27, 2017 at 1:29 PM, Koteswara Rao Ruvva via vtkusers wrote: > Hello All, > > I want to find out whether a vtkActor is moved from its initial position. I > want to compare vtkActor.GetMatrix() with its initial value, but I don't see > vtkMatrix comparison API, like overloaded == or equivalent methods. Please > suggest. You'll either need to pull the elements of the matrix out (aMatrix->GetData()) and compare them, or you can just check the modification time (someMatrix->GetMTime()) to see if anything has modified it since the last check, depending on your usecase. HTH, Allie -------------- next part -------------- An HTML attachment was scrubbed... URL: From arw.tyx-ouy_mz at ezweb.ne.jp Thu Jul 27 22:45:24 2017 From: arw.tyx-ouy_mz at ezweb.ne.jp (arwtyxouymz) Date: Thu, 27 Jul 2017 19:45:24 -0700 (MST) Subject: [vtkusers] Normal vector of the surface of ellipstic cylinder In-Reply-To: References: <1501141892687-5744171.post@n5.nabble.com> Message-ID: <1501209924782-5744183.post@n5.nabble.com> Thank you Girish Lande! I tried to implement your code, but result is something wrong. Why? My code is below and the result is in an attachment picture. I want to calculat normal vectors on the side of the cylinder. please help! result.png #include "vtkPoints.h" #include "vtkSmartPointer.h" #include "vtkLinearExtrusionFilter.h" #include "vtkDataSetMapper.h" #include "vtkPolyDataMapper.h" #include "vtkActor.h" #include "vtkProperty.h" #include "vtkCamera.h" #include "vtkRenderer.h" #include "vtkRenderWindow.h" #include "vtkRenderWindowInteractor.h" #include "vtkInteractorStyleTrackballCamera.h" #include "vtkPolyLine.h" #include "vtkLineSource.h" #include "vtkSphereSource.h" #include "vtkDoubleArray.h" #include "vtkFloatArray.h" #include "vtkCellData.h" #include "vtkPolyDataNormals.h" #include "vtkPointData.h" #include "vtkBrownianPoints.h" #include "vtkArrowSource.h" #include "vtkGlyph3D.h" bool GetPointNormals(vtkPolyData* polydata); void TestPointNormals(vtkPolyData* polydata); int main(int argc, char *argv[]) { // 2???? double angle = 0; double r1, r2; int id = 0; double CenterX, CenterY; r1 = 50; r2 = 30; double z_length = 50.0; CenterX = 0.0; CenterY = 0.0; vtkSmartPointer points = vtkSmartPointer::New(); points->SetNumberOfPoints(720); while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 360.0)) { points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) + CenterY, 0); angle = angle + (vtkMath::Pi() / 360.0); id++; } vtkSmartPointer line = vtkSmartPointer::New(); line->GetPointIds()->SetNumberOfIds(id); for (int k = 0; k < id; ++k) { line->GetPointIds()->SetId(k, k); } vtkSmartPointer lines = vtkSmartPointer::New(); lines->InsertNextCell(line); vtkSmartPointer polyData = vtkSmartPointer::New(); polyData->GlobalReleaseDataFlagOff(); polyData->Allocate(1, 1); polyData->SetPoints(points); polyData->SetLines(lines); // 3??? vtkSmartPointer extrude = vtkSmartPointer::New(); extrude->SetInputData(polyData); extrude->SetExtrusionTypeToNormalExtrusion(); extrude->SetVector(0, 0, -z_length); extrude->SetScaleFactor(1.0); extrude->Update(); vtkSmartPointer elliptic_mapper = vtkSmartPointer::New(); elliptic_mapper->SetInputConnection(extrude->GetOutputPort()); vtkSmartPointer elliptic_actor = vtkSmartPointer::New(); elliptic_actor->SetMapper(elliptic_mapper); elliptic_actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); // ?????? vtkPolyData* elliptic_cylinder = extrude->GetOutput(); TestPointNormals(elliptic_cylinder); vtkMath::RandomSeed(100); vtkSmartPointer brownianPoints = vtkSmartPointer::New(); brownianPoints->SetInputConnection(extrude->GetOutputPort()); vtkSmartPointer arrowSource = vtkSmartPointer::New(); vtkSmartPointer glyph3D = vtkSmartPointer::New(); glyph3D->SetSourceConnection(arrowSource->GetOutputPort()); glyph3D->SetInputConnection(brownianPoints->GetOutputPort()); glyph3D->SetVectorModeToUseNormal(); glyph3D->SetScaleFactor(10.0); vtkSmartPointer glyphMapper = vtkSmartPointer::New(); glyphMapper->SetInputConnection(glyph3D->GetOutputPort()); vtkSmartPointer glyphActor = vtkSmartPointer::New(); glyphActor->GetProperty()->SetColor(.0, 1.0, .0); glyphActor->SetMapper(glyphMapper); // ?? double TARGET_X, TARGET_Y, TARGET_Z; TARGET_X = -sqrt(pow(r1, 2.0) - pow(r2, 2.0)); TARGET_Y = 0.0; TARGET_Z = -z_length/2.0; vtkSmartPointer target = vtkSmartPointer::New(); target->SetRadius(1.0); target->SetCenter(TARGET_X, TARGET_Y, TARGET_Z); vtkSmartPointer target_mapper = vtkSmartPointer::New(); target_mapper->SetInputConnection(target->GetOutputPort()); vtkSmartPointer target_actor = vtkSmartPointer::New(); target_actor->SetMapper(target_mapper); target_actor->GetProperty()->SetColor(1.0, 0.0, 0.0); // ???? for (vtkIdType id= 0; id <= 720; id++) { double p[3]; points->GetPoint(id, p); // ?????? vtkVector3d v(p[0] - TARGET_X, p[1] - TARGET_Y, p[2] - TARGET_Z); } // ?? vtkSmartPointer lineSource = vtkSmartPointer::New(); lineSource->SetPoint1(TARGET_X, TARGET_Y, TARGET_Z); lineSource->SetPoint2(0.0, 0.0, 0.0); lineSource->Update(); vtkSmartPointer line_mapper = vtkSmartPointer::New(); line_mapper->SetInputData(lineSource->GetOutput()); vtkSmartPointer line_actor = vtkSmartPointer::New(); line_actor->SetMapper(line_mapper); line_actor->GetProperty()->SetLineWidth(0.5); // ?? vtkSmartPointer ren = vtkSmartPointer::New(); vtkSmartPointer renWin = vtkSmartPointer::New(); renWin->AddRenderer(ren); renWin->SetSize(600, 600); vtkSmartPointer iren = vtkSmartPointer::New(); iren->SetRenderWindow(renWin); //ren->AddActor(line_actor); //ren->AddActor(target_actor); ren->AddActor(glyphActor); ren->AddActor(elliptic_actor); ren->SetBackground(.3, .6, .3); vtkSmartPointer style = vtkSmartPointer::New(); iren->SetInteractorStyle(style); renWin->Render(); iren->Initialize(); iren->Start(); return EXIT_SUCCESS; } bool GetPointNormals(vtkPolyData* polydata) { std::cout << "In GetPointNormals: " << polydata << polydata->GetNumberOfPoints() << std::endl; std::cout << "Looking for point normals..." << std::endl; vtkIdType numPoints = polydata->GetNumberOfPoints(); std::cout << "There are " << numPoints << " points." << std::endl; vtkIdType numPolys = polydata->GetNumberOfPolys(); std::cout << "There are " << numPolys << " polys." << std::endl; // Double normals in an array vtkDoubleArray* normalDataDouble = vtkDoubleArray::SafeDownCast(polydata->GetPointData()->GetArray("Normals")); if (normalDataDouble) { vtkIdType nc = normalDataDouble->GetNumberOfTuples(); std::cout << "There are " << nc << " components in normalDataDouble" << std::endl; return true; } // Float normals in an array vtkFloatArray* normalDataFloat = vtkFloatArray::SafeDownCast(polydata->GetPointData()->GetArray("Normals")); if (normalDataFloat) { vtkIdType nc = normalDataFloat->GetNumberOfTuples(); std::cout << "There are " << nc << " components in normalDataFloat" << std::endl; return true; } // Point normals vtkDoubleArray* normalsDouble = vtkDoubleArray::SafeDownCast(polydata->GetPointData()->GetNormals()); if (normalsDouble) { std::cout << "There are " << normalsDouble->GetNumberOfComponents() << " components in normalsDouble" << std::endl; return true; } // Point normals vtkFloatArray* normalsFloat = vtkFloatArray::SafeDownCast(polydata->GetPointData()->GetNormals()); if (normalsFloat) { std::cout << "There are " << normalsFloat->GetNumberOfComponents() << " components in normalsFloat" << std::endl; return true; } // Generic type point normals vtkDataArray* normalsGeneric = polydata->GetPointData()->GetNormals(); if (normalsGeneric) { std::cout << "There are " << normalsGeneric->GetNumberOfTuples() << " normals in normalsGeneric" << std::endl; double testDouble[3]; normalsGeneric->GetTuple(0, testDouble); std::cout << "Double: " << testDouble[0] << " " << testDouble[1] << " " << testDouble[2] << std::endl; return true; } std::cout << "Normals not found!" << std::endl; return false; } void TestPointNormals(vtkPolyData* polydata) { std::cout << "In TestPointNormals: " << polydata->GetNumberOfPoints() << std::endl; bool hasPointNormals = GetPointNormals(polydata); if (!hasPointNormals) { std::cout << "No point normals were found. Computing normals..." << std::endl; vtkSmartPointer normalGenerator = vtkSmartPointer::New(); normalGenerator->SetInputData(polydata); normalGenerator->ComputePointNormalsOn(); normalGenerator->Update(); polydata = normalGenerator->GetOutput(); hasPointNormals = GetPointNormals(polydata); std::cout << "On the second try, has point normals? " << hasPointNormals << std::endl; } else { std::cout << "Point normals were found!" << std::endl; } } -- View this message in context: http://vtk.1045678.n5.nabble.com/Normal-vector-of-the-surface-of-ellipstic-cylinder-tp5744171p5744183.html Sent from the VTK - Users mailing list archive at Nabble.com. From girish.lande at agiliad.com Thu Jul 27 23:11:16 2017 From: girish.lande at agiliad.com (Girish Lande) Date: Fri, 28 Jul 2017 08:41:16 +0530 Subject: [vtkusers] Normal vector of the surface of ellipstic cylinder In-Reply-To: <1501209924782-5744183.post@n5.nabble.com> References: <1501141892687-5744171.post@n5.nabble.com> <1501209924782-5744183.post@n5.nabble.com> Message-ID: It may not be wrong . I think what you have done is taken ellipse and extruded it to form cylinder shape. If you observe points in your polydata, they are only at the edge of cylinder shape. SO normals are drawn only in that region. You have done too much scaling and hence "arrows" are mixing up to see that graphics that you see there. I modified your code and you can see normals drawn correctly. There is output image attached. [image: Inline images 1][image: Inline images 2] On 28 July 2017 at 08:15, arwtyxouymz wrote: > Thank you Girish Lande! > > I tried to implement your code, but result is something wrong. > Why? > My code is below and the result is in an attachment picture. > I want to calculat normal vectors on the side of the cylinder. > > please help! > > result.png > > #include "vtkPoints.h" > #include "vtkSmartPointer.h" > #include "vtkLinearExtrusionFilter.h" > #include "vtkDataSetMapper.h" > #include "vtkPolyDataMapper.h" > #include "vtkActor.h" > #include "vtkProperty.h" > #include "vtkCamera.h" > #include "vtkRenderer.h" > #include "vtkRenderWindow.h" > #include "vtkRenderWindowInteractor.h" > #include "vtkInteractorStyleTrackballCamera.h" > #include "vtkPolyLine.h" > #include "vtkLineSource.h" > > > #include "vtkSphereSource.h" > #include "vtkDoubleArray.h" > #include "vtkFloatArray.h" > #include "vtkCellData.h" > #include "vtkPolyDataNormals.h" > #include "vtkPointData.h" > #include "vtkBrownianPoints.h" > #include "vtkArrowSource.h" > #include "vtkGlyph3D.h" > > > bool GetPointNormals(vtkPolyData* polydata); > void TestPointNormals(vtkPolyData* polydata); > > int main(int argc, char *argv[]) > { > // 2???? > double angle = 0; > double r1, r2; > int id = 0; > double CenterX, CenterY; > r1 = 50; > r2 = 30; > double z_length = 50.0; > CenterX = 0.0; CenterY = 0.0; > > vtkSmartPointer points = > vtkSmartPointer::New(); > points->SetNumberOfPoints(720); > while (angle <= 2.0 * vtkMath::Pi() + (vtkMath::Pi() / 360.0)) > { > points->InsertPoint(id, r1 * cos(angle) + CenterX, r2 * sin(angle) > + > CenterY, 0); > angle = angle + (vtkMath::Pi() / 360.0); > id++; > } > > > vtkSmartPointer line = > vtkSmartPointer::New(); > line->GetPointIds()->SetNumberOfIds(id); > for (int k = 0; k < id; ++k) { > line->GetPointIds()->SetId(k, k); > } > > vtkSmartPointer lines = > vtkSmartPointer::New(); > lines->InsertNextCell(line); > > vtkSmartPointer polyData = > vtkSmartPointer::New(); > polyData->GlobalReleaseDataFlagOff(); > polyData->Allocate(1, 1); > polyData->SetPoints(points); > polyData->SetLines(lines); > > // 3??? > vtkSmartPointer extrude = > vtkSmartPointer::New(); > extrude->SetInputData(polyData); > extrude->SetExtrusionTypeToNormalExtrusion(); > extrude->SetVector(0, 0, -z_length); > extrude->SetScaleFactor(1.0); > extrude->Update(); > > vtkSmartPointer elliptic_mapper = > vtkSmartPointer::New(); > elliptic_mapper->SetInputConnection(extrude->GetOutputPort()); > > vtkSmartPointer elliptic_actor = > vtkSmartPointer::New(); > elliptic_actor->SetMapper(elliptic_mapper); > elliptic_actor->GetProperty()->SetColor(0.8900, 0.8100, 0.3400); > > // ?????? > vtkPolyData* elliptic_cylinder = extrude->GetOutput(); > TestPointNormals(elliptic_cylinder); > > vtkMath::RandomSeed(100); > vtkSmartPointer brownianPoints = > vtkSmartPointer::New(); > brownianPoints->SetInputConnection(extrude->GetOutputPort()); > > vtkSmartPointer arrowSource = > vtkSmartPointer::New(); > vtkSmartPointer glyph3D = > vtkSmartPointer::New(); > glyph3D->SetSourceConnection(arrowSource->GetOutputPort()); > glyph3D->SetInputConnection(brownianPoints->GetOutputPort()); > glyph3D->SetVectorModeToUseNormal(); > glyph3D->SetScaleFactor(10.0); > > vtkSmartPointer glyphMapper = > vtkSmartPointer::New(); > glyphMapper->SetInputConnection(glyph3D->GetOutputPort()); > > vtkSmartPointer glyphActor = > vtkSmartPointer::New(); > glyphActor->GetProperty()->SetColor(.0, 1.0, .0); > glyphActor->SetMapper(glyphMapper); > > > // ?? > double TARGET_X, TARGET_Y, TARGET_Z; > TARGET_X = -sqrt(pow(r1, 2.0) - pow(r2, 2.0)); > TARGET_Y = 0.0; > TARGET_Z = -z_length/2.0; > > vtkSmartPointer target = > vtkSmartPointer::New(); > target->SetRadius(1.0); > target->SetCenter(TARGET_X, TARGET_Y, TARGET_Z); > > vtkSmartPointer target_mapper = > vtkSmartPointer::New(); > target_mapper->SetInputConnection(target->GetOutputPort()); > > vtkSmartPointer target_actor = > vtkSmartPointer::New(); > target_actor->SetMapper(target_mapper); > target_actor->GetProperty()->SetColor(1.0, 0.0, 0.0); > > // ???? > for (vtkIdType id= 0; id <= 720; id++) > { > double p[3]; > points->GetPoint(id, p); > // ?????? > vtkVector3d v(p[0] - TARGET_X, > p[1] - TARGET_Y, > p[2] - TARGET_Z); > } > > // ?? > vtkSmartPointer lineSource = > vtkSmartPointer::New(); > lineSource->SetPoint1(TARGET_X, TARGET_Y, TARGET_Z); > lineSource->SetPoint2(0.0, 0.0, 0.0); > lineSource->Update(); > > vtkSmartPointer line_mapper = > vtkSmartPointer::New(); > line_mapper->SetInputData(lineSource->GetOutput()); > > vtkSmartPointer line_actor = > vtkSmartPointer::New(); > line_actor->SetMapper(line_mapper); > line_actor->GetProperty()->SetLineWidth(0.5); > > > // ?? > vtkSmartPointer ren = > vtkSmartPointer::New(); > vtkSmartPointer renWin = > vtkSmartPointer::New(); > renWin->AddRenderer(ren); > renWin->SetSize(600, 600); > > vtkSmartPointer iren = > vtkSmartPointer::New(); > iren->SetRenderWindow(renWin); > > //ren->AddActor(line_actor); > //ren->AddActor(target_actor); > ren->AddActor(glyphActor); > ren->AddActor(elliptic_actor); > ren->SetBackground(.3, .6, .3); > > vtkSmartPointer style = > vtkSmartPointer::New(); > iren->SetInteractorStyle(style); > > renWin->Render(); > iren->Initialize(); > iren->Start(); > > return EXIT_SUCCESS; > } > > bool GetPointNormals(vtkPolyData* polydata) > { > std::cout << "In GetPointNormals: " << polydata << > polydata->GetNumberOfPoints() << std::endl; > std::cout << "Looking for point normals..." << std::endl; > > vtkIdType numPoints = polydata->GetNumberOfPoints(); > std::cout << "There are " << numPoints << " points." << std::endl; > > vtkIdType numPolys = polydata->GetNumberOfPolys(); > std::cout << "There are " << numPolys << " polys." << std::endl; > > // Double normals in an array > vtkDoubleArray* normalDataDouble = > > vtkDoubleArray::SafeDownCast(polydata->GetPointData()-> > GetArray("Normals")); > > if (normalDataDouble) > { > vtkIdType nc = normalDataDouble->GetNumberOfTuples(); > std::cout << "There are " << nc << " components in > normalDataDouble" > << std::endl; > return true; > } > > // Float normals in an array > vtkFloatArray* normalDataFloat = > > vtkFloatArray::SafeDownCast(polydata->GetPointData()-> > GetArray("Normals")); > > if (normalDataFloat) > { > vtkIdType nc = normalDataFloat->GetNumberOfTuples(); > std::cout << "There are " << nc << " components in normalDataFloat" > << std::endl; > return true; > } > > // Point normals > vtkDoubleArray* normalsDouble = > > vtkDoubleArray::SafeDownCast(polydata->GetPointData()->GetNormals()); > > if (normalsDouble) > { > std::cout << "There are " << normalsDouble-> > GetNumberOfComponents() > << " components in normalsDouble" << std::endl; > return true; > } > > // Point normals > vtkFloatArray* normalsFloat = > > vtkFloatArray::SafeDownCast(polydata->GetPointData()->GetNormals()); > > if (normalsFloat) > { > std::cout << "There are " << normalsFloat->GetNumberOfComponents() > << " components in normalsFloat" << std::endl; > return true; > } > > // Generic type point normals > vtkDataArray* normalsGeneric = polydata->GetPointData()->GetNormals(); > > if (normalsGeneric) > { > std::cout << "There are " << normalsGeneric->GetNumberOfTuples() > << " normals in normalsGeneric" << std::endl; > > double testDouble[3]; > normalsGeneric->GetTuple(0, testDouble); > > std::cout << "Double: " << testDouble[0] << " " > << testDouble[1] << " " << testDouble[2] << std::endl; > return true; > } > > std::cout << "Normals not found!" << std::endl; > return false; > } > > > void TestPointNormals(vtkPolyData* polydata) > { > std::cout << "In TestPointNormals: " << polydata->GetNumberOfPoints() > << > std::endl; > bool hasPointNormals = GetPointNormals(polydata); > > if (!hasPointNormals) > { > std::cout << "No point normals were found. Computing normals..." << > std::endl; > > vtkSmartPointer normalGenerator = > vtkSmartPointer::New(); > normalGenerator->SetInputData(polydata); > normalGenerator->ComputePointNormalsOn(); > normalGenerator->Update(); > > polydata = normalGenerator->GetOutput(); > hasPointNormals = GetPointNormals(polydata); > > std::cout << "On the second try, has point normals? " > << hasPointNormals << std::endl; > } > else > { > std::cout << "Point normals were found!" << std::endl; > } > } > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Normal-vector-of-the-surface-of-ellipstic-cylinder- > tp5744171p5744183.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- thanks & regards, Girish -- ------------------------------------------------------------ ------------------------------------------------------------- *Disclaimer:* This email message including any attachments is confidential, and may be privileged and proprietary to Agiliad. If you are not the intended recipient, please notify us immediately by replying to this message and destroy all copies of this message including any attachments. You are NOT authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. Thank you. ------------------------------------------------------------ ------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 1.png Type: image/png Size: 62613 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2_zoom.png Type: image/png Size: 55558 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: normals_at_each_point_in_cylinder.cpp Type: text/x-c++src Size: 8957 bytes Desc: not available URL: From arw.tyx-ouy_mz at ezweb.ne.jp Thu Jul 27 23:49:28 2017 From: arw.tyx-ouy_mz at ezweb.ne.jp (arwtyxouymz) Date: Thu, 27 Jul 2017 20:49:28 -0700 (MST) Subject: [vtkusers] Normal vector of the surface of ellipstic cylinder In-Reply-To: References: <1501141892687-5744171.post@n5.nabble.com> <1501209924782-5744183.post@n5.nabble.com> Message-ID: <1501213768043-5744185.post@n5.nabble.com> Thank you Girish Lande! Can I not get normals the side surface of about my extruded object? Should i change the extrusion method to create elliptic cylinder if I want to get the side surface normals? But I don't know other ways.... please tell me! -- View this message in context: http://vtk.1045678.n5.nabble.com/Normal-vector-of-the-surface-of-ellipstic-cylinder-tp5744171p5744185.html Sent from the VTK - Users mailing list archive at Nabble.com. From girish.lande at agiliad.com Fri Jul 28 00:30:44 2017 From: girish.lande at agiliad.com (Girish Lande) Date: Fri, 28 Jul 2017 10:00:44 +0530 Subject: [vtkusers] Normal vector of the surface of ellipstic cylinder In-Reply-To: <1501213768043-5744185.post@n5.nabble.com> References: <1501141892687-5744171.post@n5.nabble.com> <1501209924782-5744183.post@n5.nabble.com> <1501213768043-5744185.post@n5.nabble.com> Message-ID: I think you need to find a way to introduce more triangles in your polydata. One way I can think of is to create multiple successive extrusions instead of creating one single extrusion. And then append polydata of these multiple extrusions which will definitely have more points and triangles. (Please see attached image). Your current polydata is represented by fig. A. and what you need is polydata as per figure B. [image: Inline images 1] On 28 July 2017 at 09:19, arwtyxouymz wrote: > Thank you Girish Lande! > > Can I not get normals the side surface of about my extruded object? > Should i change the extrusion method to create elliptic cylinder if I want > to get the side surface normals? > > But I don't know other ways.... > > please tell me! > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/Normal-vector-of-the-surface-of-ellipstic-cylinder- > tp5744171p5744185.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- thanks & regards, Girish -- ------------------------------------------------------------ ------------------------------------------------------------- *Disclaimer:* This email message including any attachments is confidential, and may be privileged and proprietary to Agiliad. If you are not the intended recipient, please notify us immediately by replying to this message and destroy all copies of this message including any attachments. You are NOT authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. Thank you. ------------------------------------------------------------ ------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dense_triangles.png Type: image/png Size: 44020 bytes Desc: not available URL: From Andx_roo at live.com Fri Jul 28 02:12:17 2017 From: Andx_roo at live.com (Andaharoo) Date: Thu, 27 Jul 2017 23:12:17 -0700 (MST) Subject: [vtkusers] fit to screen in vtkImageViewer2 + QVTKWidget In-Reply-To: References: Message-ID: <1501222337728-5744187.post@n5.nabble.com> Hi, I can't say why it does this but I've battled this effect by doing the following with parallel scale defined as half the size of the image. I usually do something like this: extent = new double[3] { image->GetDimensions()[0] * image->GetSpacing()[0] * 0.5, image->GetDimensions()[1] * image->GetSpacing()[1] * 0.5, image->GetDimensions()[2] * image->GetSpacing()[2] * 0.5 }; imageViewer->GetRenderer()->ResetCamera(); vtkCamera* cam = imageViewer->GetRenderer()->GetActiveCamera(); cam->ParallelProjectionOn(); cam->SetParallelScale(extent[0]); This gets a little more complicated if you want to use a different orientation though. Here's some psuedo if (XY orientation) SetParallelScale(extent[0]); cam->SetViewUp(0, 1, 0); else if (YZ orientation) SetParallelScale(std::max(extent[1], extent[2] * h / w)) cam->SetViewUp(0, 0, 1); else if (XZ orientation) SetParallelScale(std::max(extent[0], extent[2] * h / w)); cam->SetViewUp(0, 0, 1); -- View this message in context: http://vtk.1045678.n5.nabble.com/fit-to-screen-in-vtkImageViewer2-QVTKWidget-tp5744151p5744187.html Sent from the VTK - Users mailing list archive at Nabble.com. From zhang07101 at 126.com Fri Jul 28 03:32:47 2017 From: zhang07101 at 126.com (zhang qiang) Date: Fri, 28 Jul 2017 00:32:47 -0700 (MST) Subject: [vtkusers] How to understand the slab thickness, slab resolution, spacing Message-ID: <1501227167522-5744188.post@n5.nabble.com> Dear all I feel confused about some concepts about VTK. Currently, I need to reslice a 3D data to make the data isotropic, and I use vtkImageSlabReslice. Firstly, I read the data, the code is : vtkSmartPointer reader = vtkSmartPointer::New(); reader->SetDirectoryName("G:\\SNAP_Signal_Analysis\\snap_simulation\\SNAP_TOF_Data\\Chang Cheng\\TOF"); reader->Update(); vtkSmartPointer originalData = reader->GetOutput(); int originalDims[3]; double originalSpacing[3]; originalData->GetDimensions(originalDims); originalData->GetSpacing(originalSpacing); My question is: how does the originalData record the data thickness information? Because I can not find the thickness from originalData. Then, I reslice the data by the following code: vtkSmartPointer resliceFilter = vtkSmartPointer::New(); resliceFilter->SetInputData(originalData); resliceFilter->SetOutputSpacing(0.4,0.4,0.4); //resliceFilter->SetSlabResolution(0.4); resliceFilter->SetInterpolationModeToLinear(); resliceFilter->SetOutputDimensionality(3); resliceFilter->Update(); Then, I check the output by: vtkSmartPointer reslicedData = resliceFilter->GetOutput(); int reslicedDims[3]; double reslicedSpacing[3]; reslicedData->GetDimensions(reslicedDims); reslicedData->GetSpacing(reslicedSpacing); I find that the resliceFilter->SetSlabResolution is critical to get the correct pixel spacing. Without the resliceFilter->SetSlabResolution, the reslicedSpacing is (0.4,0.4,1), which means the SetOutputSpacing do not work. In the SetOutputSpacing(spacing[0],spaicng[1],spacing[3]), what's the meaning of spacing[3]? It is the thickness, or it is the spacing between slice? Through dicom viewer, I refer to the dicom header, and I am sure that originalSpacing[3] is the spacing between slice. So, Why resliceFilter->SetOutputSpacing(0.4,0.4,0.4) do not make reslicedSpacing[3]=0.4? In addition, I find two function in vtkImageSlabReslice: SetSlabThickness and SetSlabResolution. From some explanation from Internet, I guess that SetSlabThickness *NumBlendSamplePoints=SetSlabResolution. But, after test some case, I find it is wrong. And I have no idea about what is the relationship between slab thickness and slab resolution. zhang qiang -- View this message in context: http://vtk.1045678.n5.nabble.com/How-to-understand-the-slab-thickness-slab-resolution-spacing-tp5744188.html Sent from the VTK - Users mailing list archive at Nabble.com. From arw.tyx-ouy_mz at ezweb.ne.jp Fri Jul 28 03:47:26 2017 From: arw.tyx-ouy_mz at ezweb.ne.jp (arwtyxouymz) Date: Fri, 28 Jul 2017 00:47:26 -0700 (MST) Subject: [vtkusers] Normal vector of the surface of ellipstic cylinder In-Reply-To: References: <1501141892687-5744171.post@n5.nabble.com> <1501209924782-5744183.post@n5.nabble.com> <1501213768043-5744185.post@n5.nabble.com> Message-ID: <1501228046666-5744189.post@n5.nabble.com> Thank you! So, I should change cylinder creation method from: 2D EllipsePolyData -> extrude 50.0point -> Convert to PolyData to: 2D EllipsePolyData -> extrude 0.50point -> Convert to PolyData -> extrude 0.50point -> Convert to PolyData -> .....until reach to 50.0point Is this right? I have created this part, but it doesn't work. please check. ============================================= // 2D ellipse vtkSmartPointer ellipse = vtkSmartPointer::New(); ellipse->GlobalReleaseDataFlagOff(); ellipse->Allocate(1, 1); ellipse->SetPoints(points); ellipse->SetLines(lines); // extrude 0.5point vtkSmartPointer extrude = vtkSmartPointer::New(); extrude->SetInputData(ellipse); extrude->SetExtrusionTypeToNormalExtrusion(); extrude->SetScaleFactor(1.0); extrude->SetVector(0, 0, -0.50); extrude->Update(); // convert to polyData vtkSmartPointer ellipticCylinder = extrude->GetOutput(); double dl = 0.5; // loop until z_length while (dl <= z_length) { extrude->InitializeObjectBase(); extrude->SetInputData(ellipticCylinder); extrude->SetExtrusionTypeToNormalExtrusion(); extrude->SetScaleFactor(1.0); extrude->SetVector(0, 0, -0.50); extrude->Update(); ellipticCylinder = extrude->GetOutput(); dl += 0.50; } // next connect to polyDataMapper ================================================ please help me! -- View this message in context: http://vtk.1045678.n5.nabble.com/Normal-vector-of-the-surface-of-ellipstic-cylinder-tp5744171p5744189.html Sent from the VTK - Users mailing list archive at Nabble.com. From swetha.bsharma at gmail.com Fri Jul 28 06:25:21 2017 From: swetha.bsharma at gmail.com (Swetha Sharma) Date: Fri, 28 Jul 2017 15:55:21 +0530 Subject: [vtkusers] problem reading .vtk file: error reading ascii file.possible mismatch of datasize with declaration Message-ID: Hi All, I am new to vtk . The following is the format of my vtk file # vtk DataFile Version 2.0 File written by itkVTKPolyDataWriter ASCII DATASET POLYDATA POINTS 28510 float 105.668 85.3688 60.1681 105.857 85.1791 60.1681 105.857 85.3688 59.8223 106.047 85.3688 60.1681 105.668 85.7482 60.1681 105.857 85.7482 59.8223 106.047 85.5585 59.8223 106.237 85.5585 60.1681 106.237 85.7482 59.8223 106.426 85.7482 60.1681 105.288 86.1277 60.1681 I am trying to read it in vtk with the following code: vtkSmartPointer reader = vtkSmartPointer::New(); std::cout<<"filename:"<SetFileName(argv[1]); reader->Update(); I am getting an error: error reading ascii file.possible mismatch of datasize with declaration. How do I fix this? -swetha -------------- next part -------------- An HTML attachment was scrubbed... URL: From majid.msadeghi at yahoo.com Fri Jul 28 07:31:19 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Fri, 28 Jul 2017 11:31:19 +0000 (UTC) Subject: [vtkusers] Any experience with other libraries just for boolean operation? References: <1011766215.1244494.1501241479773.ref@mail.yahoo.com> Message-ID: <1011766215.1244494.1501241479773@mail.yahoo.com> Hi to all VTK users, As many of you might have faced the problems with?vtkBooleanOperationPolyDataFilter,?you know that there are many occasions that it really does not work and it is a pain in the neck. I have done some search and I know there are a couple of other libraries to use for this specific operation, like CGAL, LIBIGL, Cork, etc. Has anyone ever tried any of the libraries? Can you guide me on which one is smoother or easier to use based on your experience? Thanks a lot. Majid Mohammad Sadeghi PhD Candidate Mechatronics Engineering Department Istanbul Technical University -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.maynard at kitware.com Fri Jul 28 09:21:11 2017 From: robert.maynard at kitware.com (Robert Maynard) Date: Fri, 28 Jul 2017 09:21:11 -0400 Subject: [vtkusers] VTK Development Survey In-Reply-To: References: Message-ID: Hi Everybody, I would like to remind everyone that the developer survey is closing in 4 days so please respond. On Tue, Jul 18, 2017 at 11:32 AM, Robert Maynard wrote: > Hi Everybody, > > The VTK team is always looking to attract new developers and improve > the experience of developing VTK. > > To further that, we are putting out an anonymous survey to collect > data on people's thoughts about the current software development > process for VTK. We would love to hear all your rants ( or raves ) on > the development process. We will gather the results after August 1'st. > > https://goo.gl/forms/WlqyiF0sBTZT7klJ3 > > Thank you for your inputs. From cory.quammen at kitware.com Fri Jul 28 10:42:02 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 28 Jul 2017 10:42:02 -0400 Subject: [vtkusers] Any experience with other libraries just for boolean operation? In-Reply-To: <1011766215.1244494.1501241479773@mail.yahoo.com> References: <1011766215.1244494.1501241479773.ref@mail.yahoo.com> <1011766215.1244494.1501241479773@mail.yahoo.com> Message-ID: A different boolean operation method was recently merged into VTK master. Please see http://www.vtk.org/doc/nightly/html/classvtkLoopBooleanPolyDataFilter.html It would be great to get some feedback from you on whether this version works better. Thanks, Cory On Fri, Jul 28, 2017 at 7:31 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi to all VTK users, > > As many of you might have faced the problems with > vtkBooleanOperationPolyDataFilter, you know that there are many occasions > that it really does not work and it is a pain in the neck. > > I have done some search and I know there are a couple of other libraries to > use for this specific operation, like CGAL, LIBIGL, Cork, etc. > > Has anyone ever tried any of the libraries? Can you guide me on which one is > smoother or easier to use based on your experience? > > Thanks a lot. > > Majid Mohammad Sadeghi > PhD Candidate > Mechatronics Engineering Department > Istanbul Technical University > > _______________________________________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From david.gobbi at gmail.com Fri Jul 28 10:53:49 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Fri, 28 Jul 2017 08:53:49 -0600 Subject: [vtkusers] How to understand the slab thickness, slab resolution, spacing In-Reply-To: <1501227167522-5744188.post@n5.nabble.com> References: <1501227167522-5744188.post@n5.nabble.com> Message-ID: Hi Zhang, To make your data isotropic, I suggest using vtkImageReslice. I don't see any reason to use vtkImageSlabReslice, but maybe you can explain in more detail why the "slab" part is important for your result. VTK does not record the SliceThickness. The VTK spacing measures the distance from the center of one slice to the center of the next slice. If you need the thickness, you must get it from the DICOM metadata (e.g. you could use the vtkDICOMReader from github.com/dgobbi/vtk-dicom, which reads all of the metadata). If you use vtkImageReslice, making the data isotropic should be as easy as this: vtkSmartPointer resliceFilter = vtkSmartPointer< vtkImageReslice>::New(); resliceFilter->SetInputData(originalData); resliceFilter->SetOutputSpacing(0.4,0.4,0.4); resliceFilter->SetInterpolationModeToLinear(); resliceFilter->Update(); There is no need to call resliceFilter->SetOutputDimensionality(3), since this is already the default. - David On Fri, Jul 28, 2017 at 1:32 AM, zhang qiang wrote: > Dear all > > I feel confused about some concepts about VTK. Currently, I need to > reslice a 3D data to make the data isotropic, and I use > vtkImageSlabReslice. > > Firstly, I read the data, the code is : > > vtkSmartPointer reader = > vtkSmartPointer::New(); > > reader->SetDirectoryName("G:\\SNAP_Signal_Analysis\\snap_sim > ulation\\SNAP_TOF_Data\\Chang > Cheng\\TOF"); > reader->Update(); > > vtkSmartPointer originalData = reader->GetOutput(); > int originalDims[3]; > double originalSpacing[3]; > originalData->GetDimensions(originalDims); > originalData->GetSpacing(originalSpacing); > > My question is: how does the originalData record the data thickness > information? Because I can not find the thickness from originalData. > > Then, I reslice the data by the following code: > > vtkSmartPointer resliceFilter = > vtkSmartPointer::New(); > resliceFilter->SetInputData(originalData); > resliceFilter->SetOutputSpacing(0.4,0.4,0.4); > //resliceFilter->SetSlabResolution(0.4); > resliceFilter->SetInterpolationModeToLinear(); > resliceFilter->SetOutputDimensionality(3); > resliceFilter->Update(); > > Then, I check the output by: > > vtkSmartPointer reslicedData = > resliceFilter->GetOutput(); > int reslicedDims[3]; > double reslicedSpacing[3]; > reslicedData->GetDimensions(reslicedDims); > reslicedData->GetSpacing(reslicedSpacing); > > I find that the resliceFilter->SetSlabResolution is critical to get > the > correct pixel spacing. Without the resliceFilter->SetSlabResolution, the > reslicedSpacing is (0.4,0.4,1), which means the SetOutputSpacing do not > work. In the SetOutputSpacing(spacing[0],spaicng[1],spacing[3]), what's > the > meaning of spacing[3]? It is the thickness, or it is the spacing between > slice? > > Through dicom viewer, I refer to the dicom header, and I am sure that > originalSpacing[3] is the spacing between slice. So, Why > resliceFilter->SetOutputSpacing(0.4,0.4,0.4) do not make > reslicedSpacing[3]=0.4? > > In addition, I find two function in vtkImageSlabReslice: > SetSlabThickness and SetSlabResolution. From some explanation from > Internet, > I guess that SetSlabThickness *NumBlendSamplePoints=SetSlabResolution. > But, > after test some case, I find it is wrong. And I have no idea about what is > the relationship between slab thickness and slab resolution. > > zhang qiang > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rick at pile.com Fri Jul 28 11:01:09 2017 From: rick at pile.com (Rick Dailey) Date: Fri, 28 Jul 2017 08:01:09 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> Message-ID: <1501254069970-5744196.post@n5.nabble.com> I have converted my project to use VTK master (8.1) and the problem persists. Note again that for current purposes my project is essentially a part of the VTK build. I am able to debug, set breakpoints, view call stacks, step into VTK code, monitor VTK local and class variables, etc. Unfortunately, I find the VTK code far too complex to track down texture object binding errors without guidance - especially when it is the VTK code, not mine, that creates these objects. -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744196.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Fri Jul 28 11:12:59 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 28 Jul 2017 11:12:59 -0400 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501254069970-5744196.post@n5.nabble.com> References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> Message-ID: Can you email me off list the stack trace when the assert happens? On Fri, Jul 28, 2017 at 11:01 AM, Rick Dailey wrote: > I have converted my project to use VTK master (8.1) and the problem > persists. > > Note again that for current purposes my project is essentially a part of > the > VTK build. I am able to debug, set breakpoints, view call stacks, step > into VTK code, monitor VTK local and class variables, etc. > > Unfortunately, I find the VTK code far too complex to track down texture > object binding errors without guidance - especially when it is the VTK > code, > not mine, that creates these objects. > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068p5744196.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 rick at pile.com Fri Jul 28 11:26:21 2017 From: rick at pile.com (Rick Dailey) Date: Fri, 28 Jul 2017 08:26:21 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> Message-ID: <1501255581924-5744198.post@n5.nabble.com> Note 1: PDI-TOMO.exe vtkControlBase::Render() is my code that starts the render process from a Windows WM_PAINT message. I should not have have named this class with the vtk prefix (may be confusing) and will probably change it eventually. Note 2: This stack trace only includes the render portion of the code - not adding the objects to the renderer. I could probably supply that too if necessary. Note 3: Remember that this error occurs only on a fraction of the volumes that are rendered. Most work fine. > ucrtbased.dll!common_assert_to_message_box(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number, void * const return_address) Line 351 C++ ucrtbased.dll!common_assert(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number, void * const return_address) Line 386 C++ ucrtbased.dll!_wassert(const wchar_t * expression, const wchar_t * file_name, unsigned int line_number) Line 404 C++ vtkRenderingOpenGL2-8.1.dll!vtkTextureObject::Bind() Line 546 C++ vtkRenderingOpenGL2-8.1.dll!vtkTextureObject::Activate() Line 491 C++ vtkRenderingVolumeOpenGL2-8.1.dll!vtkVolumeTexture::LoadTexture(const int interpolation, vtkVolumeTexture::VolumeBlock * volBlock) Line 268 C++ vtkRenderingVolumeOpenGL2-8.1.dll!vtkVolumeTexture::LoadVolume(vtkRenderer * ren, vtkImageData * data, vtkDataArray * scalars, const int interpolation) Line 114 C++ vtkRenderingVolumeOpenGL2-8.1.dll!vtkOpenGLGPUVolumeRayCastMapper::vtkInternal::LoadData(vtkRenderer * ren, vtkVolume * vol, vtkVolumeProperty * volProp, vtkImageData * input, vtkDataArray * scalars) Line 900 C++ vtkRenderingVolumeOpenGL2-8.1.dll!vtkOpenGLGPUVolumeRayCastMapper::GPURender(vtkRenderer * ren, vtkVolume * vol) Line 3427 C++ vtkRenderingVolume-8.1.dll!vtkGPUVolumeRayCastMapper::Render(vtkRenderer * ren, vtkVolume * vol) Line 154 C++ vtkRenderingCore-8.1.dll!vtkVolume::RenderVolumetricGeometry(vtkViewport * vp) Line 370 C++ vtkRenderingOpenGL2-8.1.dll!vtkOpenGLRenderer::UpdateGeometry() Line 273 C++ vtkRenderingOpenGL2-8.1.dll!vtkOpenGLRenderer::DeviceRender() Line 170 C++ vtkRenderingCore-8.1.dll!vtkRenderer::Render() Line 351 C++ vtkRenderingCore-8.1.dll!vtkRendererCollection::Render() Line 51 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::DoStereoRender() Line 781 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::DoFDRender() Line 747 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::DoAARender() Line 626 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::Render() Line 439 C++ PDI-TOMO.exe!vtkControlBase::Render(HDC dc, const wchar_t * location) Line 694 C++ -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744198.html Sent from the VTK - Users mailing list archive at Nabble.com. From david.gobbi at gmail.com Fri Jul 28 12:04:56 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Fri, 28 Jul 2017 10:04:56 -0600 Subject: [vtkusers] How to understand the slab thickness, slab resolution, spacing In-Reply-To: <597B55EF.EDCF82.03690@m15-113.126.com> References: <1501227167522-5744188.post@n5.nabble.com> <597B55EF.EDCF82.03690@m15-113.126.com> Message-ID: Hi Zhang, Please explain exactly what you mean by "thickness". Usually only the spacing is needed for reslicing, so you need to help me understand why your situation is different. Also, always CC your replies to the VTK users list. - David On Fri, Jul 28, 2017 at 9:19 AM, zhang07101 at 126.com wrote: > Dear David > > because i need to set the thickness in the resliced image, and > vtkimagereslice can not set the thickness. vtkimageslabreslice may have > function to set thickness for the resliced image. so i need to know what is > the meaning of slab. > > zhang qiang > > > -------- ???? -------- > ???Re: [vtkusers] How to understand the slab thickness, slab resolution, > spacing > ????David Gobbi > ????zhang qiang > ???VTK Users > > > Hi Zhang, > > To make your data isotropic, I suggest using vtkImageReslice. I don't see > any reason to use vtkImageSlabReslice, but maybe you can explain in more > detail why the "slab" part is important for your result. > > VTK does not record the SliceThickness. The VTK spacing measures the > distance from the center of one slice to the center of the next slice. If > you need the thickness, you must get it from the DICOM metadata (e.g. you > could use the vtkDICOMReader from github.com/dgobbi/vtk-dicom, which > reads all of the metadata). > > If you use vtkImageReslice, making the data isotropic should be as easy as > this: > > vtkSmartPointer resliceFilter = > vtkSmartPointer::New(); > resliceFilter->SetInputData(originalData); > resliceFilter->SetOutputSpacing(0.4,0.4,0.4); > resliceFilter->SetInterpolationModeToLinear(); > resliceFilter->Update(); > > There is no need to call resliceFilter->SetOutputDimensionality(3), since > this is already the default. > > - David > > > On Fri, Jul 28, 2017 at 1:32 AM, zhang qiang wrote: > >> Dear all >> >> I feel confused about some concepts about VTK. Currently, I need to >> reslice a 3D data to make the data isotropic, and I use >> vtkImageSlabReslice. >> >> Firstly, I read the data, the code is : >> >> vtkSmartPointer reader = >> vtkSmartPointer::New(); >> >> reader->SetDirectoryName("G:\\SNAP_Signal_Analysis\\snap_sim >> ulation\\SNAP_TOF_Data\\Chang >> Cheng\\TOF"); >> reader->Update(); >> >> vtkSmartPointer originalData = reader->GetOutput(); >> int originalDims[3]; >> double originalSpacing[3]; >> originalData->GetDimensions(originalDims); >> originalData->GetSpacing(originalSpacing); >> >> My question is: how does the originalData record the data thickness >> information? Because I can not find the thickness from originalData. >> >> Then, I reslice the data by the following code: >> >> vtkSmartPointer resliceFilter = >> vtkSmartPointer::New(); >> resliceFilter->SetInputData(originalData); >> resliceFilter->SetOutputSpacing(0.4,0.4,0.4); >> //resliceFilter->SetSlabResolution(0.4); >> resliceFilter->SetInterpolationModeToLinear(); >> resliceFilter->SetOutputDimensionality(3); >> resliceFilter->Update(); >> >> Then, I check the output by: >> >> vtkSmartPointer reslicedData = >> resliceFilter->GetOutput(); >> int reslicedDims[3]; >> double reslicedSpacing[3]; >> reslicedData->GetDimensions(reslicedDims); >> reslicedData->GetSpacing(reslicedSpacing); >> >> I find that the resliceFilter->SetSlabResolution is critical to get >> the >> correct pixel spacing. Without the resliceFilter->SetSlabResolution, the >> reslicedSpacing is (0.4,0.4,1), which means the SetOutputSpacing do not >> work. In the SetOutputSpacing(spacing[0],spaicng[1],spacing[3]), what's >> the >> meaning of spacing[3]? It is the thickness, or it is the spacing between >> slice? >> >> Through dicom viewer, I refer to the dicom header, and I am sure that >> originalSpacing[3] is the spacing between slice. So, Why >> resliceFilter->SetOutputSpacing(0.4,0.4,0.4) do not make >> reslicedSpacing[3]=0.4? >> >> In addition, I find two function in vtkImageSlabReslice: >> SetSlabThickness and SetSlabResolution. From some explanation from >> Internet, >> I guess that SetSlabThickness *NumBlendSamplePoints=SetSlabResolution. >> But, >> after test some case, I find it is wrong. And I have no idea about what is >> the relationship between slab thickness and slab resolution. >> >> zhang qiang >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rick at pile.com Fri Jul 28 12:43:34 2017 From: rick at pile.com (Rick Dailey) Date: Fri, 28 Jul 2017 09:43:34 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501255581924-5744198.post@n5.nabble.com> References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> Message-ID: <1501260214312-5744200.post@n5.nabble.com> The assert you asked me to add never gets hit. Here is an updated error log: ERROR: In E:\VTK\VTK-master\Rendering\VolumeOpenGL2\vtkVolumeTexture.cxx, line 720 vtkVolumeTexture (10FA4E18): Invalid texture dimensions [53, 54, 3191] ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 549 vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors detected 0 : (1280) Invalid enum ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 678 vtkTextureObject (1421E0A8): failed after SendParameters 1 OpenGL errors detected 0 : (1280) Invalid enum ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 549 vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors detected 0 : (1280) Invalid enum ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 678 vtkTextureObject (1421E0A8): failed after SendParameters 1 OpenGL errors detected 0 : (1280) Invalid enum ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 549 vtkTextureObject (1421E180): failed at glBindTexture 1 OpenGL errors detected 0 : (1280) Invalid enum ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 678 vtkTextureObject (1421E180): failed after SendParameters 1 OpenGL errors detected 0 : (1280) Invalid enum ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 549 vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors detected 0 : (1280) Invalid enum ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 549 vtkTextureObject (1421E180): failed at glBindTexture 1 OpenGL errors detected 0 : (1280) Invalid enum -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744200.html Sent from the VTK - Users mailing list archive at Nabble.com. From ken.martin at kitware.com Fri Jul 28 12:53:29 2017 From: ken.martin at kitware.com (Ken Martin) Date: Fri, 28 Jul 2017 12:53:29 -0400 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501260214312-5744200.post@n5.nabble.com> References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> Message-ID: Ahh, it seems your graphics card cannot handle the size volume you are trying to render. I would guess the issue is the 3191 dimension. A few options come to mind depending on your situation. 1) require a larger graphics card 2) shrink any volumes that to fit in 2048 (that would be my guess for the largest size on your card) 3) The volume rendering folks may some other tricks to handle this by streaming or etc On Fri, Jul 28, 2017 at 12:43 PM, Rick Dailey wrote: > The assert you asked me to add never gets hit. > > Here is an updated error log: > > ERROR: In E:\VTK\VTK-master\Rendering\VolumeOpenGL2\vtkVolumeTexture.cxx, > line 720 > vtkVolumeTexture (10FA4E18): Invalid texture dimensions [53, 54, 3191] > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 549 > vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 678 > vtkTextureObject (1421E0A8): failed after SendParameters 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 549 > vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 678 > vtkTextureObject (1421E0A8): failed after SendParameters 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 549 > vtkTextureObject (1421E180): failed at glBindTexture 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 678 > vtkTextureObject (1421E180): failed after SendParameters 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 549 > vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 549 > vtkTextureObject (1421E180): failed at glBindTexture 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > > > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068p5744200.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Ken Martin PhD Distinguished Engineer Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 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 rick at pile.com Fri Jul 28 13:08:57 2017 From: rick at pile.com (Rick Dailey) Date: Fri, 28 Jul 2017 10:08:57 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> Message-ID: <1501261737667-5744202.post@n5.nabble.com> Thanks for all your help. This is certainly the cause of the crash. 1) require a larger graphics card - Not practical at this point. We have numerous customer support issues and we can't tell the to get a new computer. 2) shrink any volumes that to fit in 2048 (that would be my guess for the largest size on your card) - Don't know how I would go about doing something like this. It's a large and complex program and it seems to me that a change like this would touch the code widely. In other words, a major re-write. 3) The volume rendering folks may some other tricks to handle this by streaming or etc. - TRICKS ARE WELCOME! Thanks again -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744202.html Sent from the VTK - Users mailing list archive at Nabble.com. From david.gobbi at gmail.com Fri Jul 28 13:18:40 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Fri, 28 Jul 2017 11:18:40 -0600 Subject: [vtkusers] How to understand the slab thickness, slab resolution, spacing In-Reply-To: <597B6A83.F8E908.22999@m15-114.126.com> References: <1501227167522-5744188.post@n5.nabble.com> <597B55EF.EDCF82.03690@m15-113.126.com> <597B6A83.F8E908.22999@m15-114.126.com> Message-ID: Hi Zhang, Please CC the vtkusers list in your replies! Also please use proper capitalization and punctuation, otherwise I will simply ignore your emails. In order to average slices to reduce noise, use this vtkImageReslice method: resliceFilter->SetSlabNumberOfSlices(N); where N is the number of slices you want to be averaged. So, to average over 10mm when the slices have 0.4mm spacing, use N=25. The output slice spacing will still be 0.4mm. The documentation for all the "Slab" methods for vtkImageReslice starts here: http://www.vtk.org/doc/nightly/html/classvtkImageReslice.html#ac46cc094b1fb577d2a3983fa2f90350d - David On Fri, Jul 28, 2017 at 10:46 AM, zhang07101 at 126.com wrote: > dear david > > for example, if the thickness of image is 0, the image may have lots of > noise. if the.thickness of image is 10mm, the image will look more smooth. > i want the thickness of resliced image to be 10mm, which will make the > image more smooth. can i set the thickness for the resliced image. > > zhang qiang > > > -------- ???? -------- > ???Re: [vtkusers] How to understand the slab thickness, slab resolution, > spacing > ????David Gobbi > ????zhang07101 at 126.com,VTK Users > ??? > > > > Hi Zhang, > > Please explain exactly what you mean by "thickness". Usually only the > spacing is needed for reslicing, so you need to help me understand why your > situation is different. > > Also, always CC your replies to the VTK users list. > > - David > > > On Fri, Jul 28, 2017 at 9:19 AM, zhang07101 at 126.com > wrote: > >> Dear David >> >> because i need to set the thickness in the resliced image, and >> vtkimagereslice can not set the thickness. vtkimageslabreslice may have >> function to set thickness for the resliced image. so i need to know what is >> the meaning of slab. >> >> zhang qiang >> >> >> -------- ???? -------- >> ???Re: [vtkusers] How to understand the slab thickness, slab resolution, >> spacing >> ????David Gobbi >> ????zhang qiang >> ???VTK Users >> >> >> Hi Zhang, >> >> To make your data isotropic, I suggest using vtkImageReslice. I don't >> see any reason to use vtkImageSlabReslice, but maybe you can explain in >> more detail why the "slab" part is important for your result. >> >> VTK does not record the SliceThickness. The VTK spacing measures the >> distance from the center of one slice to the center of the next slice. If >> you need the thickness, you must get it from the DICOM metadata (e.g. you >> could use the vtkDICOMReader from github.com/dgobbi/vtk-dicom, which >> reads all of the metadata). >> >> If you use vtkImageReslice, making the data isotropic should be as easy >> as this: >> >> vtkSmartPointer resliceFilter = >> vtkSmartPointer::New(); >> resliceFilter->SetInputData(originalData); >> resliceFilter->SetOutputSpacing(0.4,0.4,0.4); >> resliceFilter->SetInterpolationModeToLinear(); >> resliceFilter->Update(); >> >> There is no need to call resliceFilter->SetOutputDimensionality(3), >> since this is already the default. >> >> - David >> >> >> On Fri, Jul 28, 2017 at 1:32 AM, zhang qiang wrote: >> >>> Dear all >>> >>> I feel confused about some concepts about VTK. Currently, I need to >>> reslice a 3D data to make the data isotropic, and I use >>> vtkImageSlabReslice. >>> >>> Firstly, I read the data, the code is : >>> >>> vtkSmartPointer reader = >>> vtkSmartPointer::New(); >>> >>> reader->SetDirectoryName("G:\\SNAP_Signal_Analysis\\snap_sim >>> ulation\\SNAP_TOF_Data\\Chang >>> Cheng\\TOF"); >>> reader->Update(); >>> >>> vtkSmartPointer originalData = reader->GetOutput(); >>> int originalDims[3]; >>> double originalSpacing[3]; >>> originalData->GetDimensions(originalDims); >>> originalData->GetSpacing(originalSpacing); >>> >>> My question is: how does the originalData record the data thickness >>> information? Because I can not find the thickness from originalData. >>> >>> Then, I reslice the data by the following code: >>> >>> vtkSmartPointer resliceFilter = >>> vtkSmartPointer::New(); >>> resliceFilter->SetInputData(originalData); >>> resliceFilter->SetOutputSpacing(0.4,0.4,0.4); >>> //resliceFilter->SetSlabResolution(0.4); >>> resliceFilter->SetInterpolationModeToLinear(); >>> resliceFilter->SetOutputDimensionality(3); >>> resliceFilter->Update(); >>> >>> Then, I check the output by: >>> >>> vtkSmartPointer reslicedData = >>> resliceFilter->GetOutput(); >>> int reslicedDims[3]; >>> double reslicedSpacing[3]; >>> reslicedData->GetDimensions(reslicedDims); >>> reslicedData->GetSpacing(reslicedSpacing); >>> >>> I find that the resliceFilter->SetSlabResolution is critical to >>> get the >>> correct pixel spacing. Without the resliceFilter->SetSlabResolution, the >>> reslicedSpacing is (0.4,0.4,1), which means the SetOutputSpacing do not >>> work. In the SetOutputSpacing(spacing[0],spaicng[1],spacing[3]), what's >>> the >>> meaning of spacing[3]? It is the thickness, or it is the spacing between >>> slice? >>> >>> Through dicom viewer, I refer to the dicom header, and I am sure >>> that >>> originalSpacing[3] is the spacing between slice. So, Why >>> resliceFilter->SetOutputSpacing(0.4,0.4,0.4) do not make >>> reslicedSpacing[3]=0.4? >>> >>> In addition, I find two function in vtkImageSlabReslice: >>> SetSlabThickness and SetSlabResolution. From some explanation from >>> Internet, >>> I guess that SetSlabThickness *NumBlendSamplePoints=SetSlabResolution. >>> But, >>> after test some case, I find it is wrong. And I have no idea about what >>> is >>> the relationship between slab thickness and slab resolution. >>> >>> zhang qiang >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alvaro.sanchez at kitware.com Fri Jul 28 13:33:57 2017 From: alvaro.sanchez at kitware.com (Alvaro Sanchez) Date: Fri, 28 Jul 2017 13:33:57 -0400 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501261737667-5744202.post@n5.nabble.com> References: <1500569102114-5744068.post@n5.nabble.com> <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> Message-ID: Hi Rick, > 3) The volume rendering folks may some other tricks to handle this by > streaming or etc. - TRICKS ARE WELCOME! > You can enable streaming by setting a number of partitions (vtkOpenGLGPUVolumeRayCastMapper::SetPartitions). Check-out the following test , let me know if you have any questions. > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068p5744202.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Alvaro Sanchez Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4901 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rick at pile.com Fri Jul 28 13:38:43 2017 From: rick at pile.com (Rick Dailey) Date: Fri, 28 Jul 2017 10:38:43 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> Message-ID: <1501263523440-5744205.post@n5.nabble.com> Great idea Alvaro. I won't be able to test this until Monday morning but will post with results when available. Thanks -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744205.html Sent from the VTK - Users mailing list archive at Nabble.com. From rccm.kyoshimi at gmail.com Sat Jul 29 02:03:39 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Sat, 29 Jul 2017 15:03:39 +0900 Subject: [vtkusers] Read .vtk file and save as binary STL file In-Reply-To: References: Message-ID: Hi Swetha, Assuming that your data is a triangle polydata set, all vtkSTLWriter have to do is set the file type to binary, so as to output as binary STL file. You don't need to call WriteBinarySTL(). Ex: vtkSmartPointer stlWriter = vtkSmartPointer::New(); stlWriter->SetFileName(filename.c_str()); stlWriter->SetInputData(polyData); stlWriter->SetFileTypeToBinary(); stlWriter->Write(); Thanks 2017-07-27 23:40 GMT+09:00 Swetha Sharma : > Hi, > > I have .vtk file which i want to read and convert to binary stl file. The > documentation has a function > WriteBinarySTL (vtkPoints *pts, vtkCellArray *polys, vtkCellArray *strips) . > How do I get the information about the vtkpoints and the cellarray? > > > > -swetha > _______________________________________________ > 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 > From andrew.amaclean at gmail.com Sat Jul 29 02:21:53 2017 From: andrew.amaclean at gmail.com (Andrew Maclean) Date: Sat, 29 Jul 2017 16:21:53 +1000 Subject: [vtkusers] =?utf-8?q?=E2=80=8BRe=3A_Normal_vector_of_the_surface_?= =?utf-8?q?of_ellipstic_cylinder?= Message-ID: Hi all, In order to introduce more triangles, I don't think that there is any need to do multiple successive extrusions. I would suggest using vtkLinearSubdivisionFilter to achieve what I think you want. Please see the attached modification of your code. Note: 1) You need to pass extrude through vtkTriangleFilter then apply vtkLinearSubdivisionFilter. 2) Experiment with changing numberOfSubdivisions in the attached code. Regards Andrew > ---------- Forwarded message ---------- > From: > ?? > Girish Lande > To: > ?? > arwtyxouymz > Cc: vtkusers at vtk.org > Bcc: > Date: Fri, 28 Jul 2017 10:00:44 +0530 > Subject: Re: [vtkusers] Normal vector of the surface of ellipstic cylinder > I think you need to find a way to introduce more triangles in your > polydata. > > One way I can think of is to create multiple successive extrusions instead > of creating one single extrusion. And then append polydata of these > multiple extrusions which will definitely have more points and triangles. > (Please see attached image). Your current polydata is represented by fig. > A. and what you need is polydata as per figure B. > [image: Inline images 1] > > On 28 July 2017 at 09:19, arwtyxouymz wrote: > >> Thank you Girish Lande! >> >> Can I not get normals the side surface of about my extruded object? >> Should i change the extrusion method to create elliptic cylinder if I want >> to get the side surface normals? >> >> But I don't know other ways.... >> >> please tell me! >> >> >> >> -- >> View this message in context: http://vtk.1045678.n5.nabble.c >> om/Normal-vector-of-the-surface-of-ellipstic-cylinder-tp5744 >> 171p5744185.html >> Sent from the VTK - Users mailing list archive at Nabble.com. >> _______________________________________________ >> 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 >> > > > > -- > thanks & regards, > Girish > > -- ___________________________________________ Andrew J. P. Maclean ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dense_triangles.png Type: image/png Size: 44020 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: normals_at_each_point_in_cylinder.cpp Type: text/x-c++src Size: 9920 bytes Desc: not available URL: From zhang07101 at 126.com Sat Jul 29 05:06:29 2017 From: zhang07101 at 126.com (zhang qiang) Date: Sat, 29 Jul 2017 02:06:29 -0700 (MST) Subject: [vtkusers] How to understand the slab thickness, slab resolution, spacing In-Reply-To: References: <1501227167522-5744188.post@n5.nabble.com> Message-ID: <1501319189185-5744208.post@n5.nabble.com> Dear David: Sorry for not CC to vtkusers list. For vtkImageReslice, if the output spacing[2] = 0.4, I can set the thickness of resliced image to 0.4*n by set the SetSlabNumberOfSlices to n. If I want the thickness to be 1mm, n will be 2.5. But the type of n is int, so n can not be 2.5, which means the thickness can not be 1mm if the outputspacing[2]=0.4. Am I right? On the other hand, I still feel confused about the vtkImageSlabReslice. What's the meaning of slab resolution and slab thickness? And after set the output spacing to (0.4,0.4,0.4), why the reslicedSpacing[2] of resliced image was not 0.4? vtkSmartPointer resliceFilter = vtkSmartPointer::New(); resliceFilter->SetInputData(originalData); resliceFilter->SetOutputSpacing(0.4,0.4,0.4); resliceFilter->SetInterpolationModeToLinear(); resliceFilter->SetOutputDimensionality(3); resliceFilter->Update(); double reslicedSpacing[3]; reslicedData->GetSpacing(reslicedSpacing); Best wishes! zhang qiang -- View this message in context: http://vtk.1045678.n5.nabble.com/How-to-understand-the-slab-thickness-slab-resolution-spacing-tp5744188p5744208.html Sent from the VTK - Users mailing list archive at Nabble.com. From david.gobbi at gmail.com Sat Jul 29 09:11:54 2017 From: david.gobbi at gmail.com (David Gobbi) Date: Sat, 29 Jul 2017 07:11:54 -0600 Subject: [vtkusers] How to understand the slab thickness, slab resolution, spacing In-Reply-To: <1501319189185-5744208.post@n5.nabble.com> References: <1501227167522-5744188.post@n5.nabble.com> <1501319189185-5744208.post@n5.nabble.com> Message-ID: Hi Zhang, The code for vtkImageSlabReslice shows what SlabThickness and SlabResolution do: https://gitlab.kitware.com/vtk/vtk/blob/master/Imaging/ General/vtkImageSlabReslice.cxx#L47 this->NumBlendSamplePoints = 2*(static_cast< int >(this->SlabThickness/(2.0 * this->SlabResolution))) + 1; this->SlabNumberOfSlices = this->NumBlendSamplePoints; and: spacing[2] = this->SlabResolution; The SlabThickness is only used to compute the SlabNumberOfSlices (which is an integer). And the SlabResolution overrides the slice spacing. The vtkImageSlabReslice filter is not meant to be used as a 3D output filter. The output slice thickness is always an integer multiple of the output slice spacing. This can be tweaked a little with the TrapezoidIntegration option, but a true fractional slice thickness isn't possible. http://www.vtk.org/doc/nightly/html/classvtkImageReslice.html# a9a8fb0ce5f767733bbce72f5be32b409 https://en.wikipedia.org/wiki/Trapezoidal_rule A different way to reduce image noise when reslicing is to use vtkImageSincInterpolator with SetBlurFactors: http://www.vtk.org/doc/nightly/html/classvtkImageSincInterpolator.html# aa662697dec4b11dacfc21e062fb1551f but the result will be different from thick slicing. - David On Sat, Jul 29, 2017 at 3:06 AM, zhang qiang wrote: > Dear David: > > Sorry for not CC to vtkusers list. > > For vtkImageReslice, if the output spacing[2] = 0.4, I can set the > thickness of resliced image to 0.4*n by set the SetSlabNumberOfSlices to n. > If I want the thickness to be 1mm, n will be 2.5. But the type of n is int, > so n can not be 2.5, which means the thickness can not be 1mm if the > outputspacing[2]=0.4. Am I right? > > On the other hand, I still feel confused about the vtkImageSlabReslice. > What's the meaning of slab resolution and slab thickness? And after set the > output spacing to (0.4,0.4,0.4), why the reslicedSpacing[2] of resliced > image was not 0.4? > > vtkSmartPointer resliceFilter = > vtkSmartPointer::New(); > resliceFilter->SetInputData(originalData); > resliceFilter->SetOutputSpacing(0.4,0.4,0.4); > resliceFilter->SetInterpolationModeToLinear(); > resliceFilter->SetOutputDimensionality(3); > resliceFilter->Update(); > > double reslicedSpacing[3]; > reslicedData->GetSpacing(reslicedSpacing); > > Best wishes! > zhang qiang > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From majid.msadeghi at yahoo.com Sat Jul 29 13:53:48 2017 From: majid.msadeghi at yahoo.com (Majid Mohammad sadeghi) Date: Sat, 29 Jul 2017 17:53:48 +0000 (UTC) Subject: [vtkusers] Any experience with other libraries just for boolean operation? In-Reply-To: References: <1011766215.1244494.1501241479773.ref@mail.yahoo.com> <1011766215.1244494.1501241479773@mail.yahoo.com> Message-ID: <226052441.2143271.1501350828734@mail.yahoo.com> I built VTK Master today and tested the vtkLoopBooleanPolyDataFilter, it worked better for basic geometries and extruded objects, but takes the same amount of time to process for complex polydatas and also does not keep the normal data array. On Friday, July 28, 2017, 5:42:04 PM GMT+3, Cory Quammen wrote: A different boolean operation method was recently merged into VTK master. Please see http://www.vtk.org/doc/nightly/html/classvtkLoopBooleanPolyDataFilter.html It would be great to get some feedback from you on whether this version works better. Thanks, Cory On Fri, Jul 28, 2017 at 7:31 AM, Majid Mohammad sadeghi via vtkusers wrote: > Hi to all VTK users, > > As many of you might have faced the problems with > vtkBooleanOperationPolyDataFilter, you know that there are many occasions > that it really does not work and it is a pain in the neck. > > I have done some search and I know there are a couple of other libraries to > use for this specific operation, like CGAL, LIBIGL, Cork, etc. > > Has anyone ever tried any of the libraries? Can you guide me on which one is > smoother or easier to use based on your experience? > > Thanks a lot. > > Majid Mohammad Sadeghi > PhD Candidate > Mechatronics Engineering Department > Istanbul Technical University > > _______________________________________________ > 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 > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From swetha.bsharma at gmail.com Mon Jul 31 04:55:20 2017 From: swetha.bsharma at gmail.com (Swetha Sharma) Date: Mon, 31 Jul 2017 14:25:20 +0530 Subject: [vtkusers] Read .vtk file and save as binary STL file In-Reply-To: References: Message-ID: Hi kenichiro, Thanks for the reply. I have a problem reading the .vtk file .Below is the code which I had used to read .vtk vtkSmartPointer reader = vtkSmartPointer::New(); std::cout<<"filename:"<SetFileName(argv[1]); reader->Update(); I am getting an error: error reading ascii file.possible mismatch of datasize with declaration. How do I fix this? -swetha On Sat, 29 Jul 2017, 11:33 kenichiro yoshimi, wrote: > Hi Swetha, > > Assuming that your data is a triangle polydata set, all vtkSTLWriter > have to do is set the file type to binary, so as to output as binary > STL file. You don't need to call WriteBinarySTL(). Ex: > > vtkSmartPointer stlWriter = > vtkSmartPointer::New(); > stlWriter->SetFileName(filename.c_str()); > stlWriter->SetInputData(polyData); > stlWriter->SetFileTypeToBinary(); > stlWriter->Write(); > > Thanks > > 2017-07-27 23:40 GMT+09:00 Swetha Sharma : > > Hi, > > > > I have .vtk file which i want to read and convert to binary stl file. The > > documentation has a function > > WriteBinarySTL (vtkPoints *pts, vtkCellArray *polys, vtkCellArray > *strips) . > > How do I get the information about the vtkpoints and the cellarray? > > > > > > > > -swetha > > _______________________________________________ > > 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 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rick at pile.com Mon Jul 31 06:54:07 2017 From: rick at pile.com (Rick Dailey) Date: Mon, 31 Jul 2017 03:54:07 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> Message-ID: <1501498447377-5744215.post@n5.nabble.com> The suggested solution (setting partitions) does not work for me. Although the error message indicating invalid texture dimensions is gone there is still a failure to bind the texture. This error message (in vtkVolumeTexture::SafeLoadTexture()) is no longer seen: ERROR: In E:\VTK\VTK-master\Rendering\VolumeOpenGL2\vtkVolumeTexture.cxx, line 720 vtkVolumeTexture (10FA4E18): Invalid texture dimensions [53, 54, 3191] This assert (in vtkTextureObject::Bind()) still fires: assert(this->Handle); ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line 549 vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors detected 0 : (1280) Invalid enum -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744215.html Sent from the VTK - Users mailing list archive at Nabble.com. From rccm.kyoshimi at gmail.com Mon Jul 31 07:38:05 2017 From: rccm.kyoshimi at gmail.com (kenichiro yoshimi) Date: Mon, 31 Jul 2017 20:38:05 +0900 Subject: [vtkusers] problem reading .vtk file: error reading ascii file.possible mismatch of datasize with declaration In-Reply-To: References: Message-ID: Hi Swetha, Your code may not be wrong. I regret to say that there is no way to know if the file can be read. I highly recommend that you look into a PDF of VTK file formats. http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf Regards 2017-07-28 19:25 GMT+09:00 Swetha Sharma : > Hi All, > > I am new to vtk . The following is the format of my vtk file > > # vtk DataFile Version 2.0 > File written by itkVTKPolyDataWriter > ASCII > DATASET POLYDATA > POINTS 28510 float > 105.668 85.3688 60.1681 > 105.857 85.1791 60.1681 > 105.857 85.3688 59.8223 > 106.047 85.3688 60.1681 > 105.668 85.7482 60.1681 > 105.857 85.7482 59.8223 > 106.047 85.5585 59.8223 > 106.237 85.5585 60.1681 > 106.237 85.7482 59.8223 > 106.426 85.7482 60.1681 > 105.288 86.1277 60.1681 > > > I am trying to read it in vtk with the following code: > > vtkSmartPointer reader = > vtkSmartPointer::New(); > std::cout<<"filename:"< reader->SetFileName(argv[1]); > > > reader->Update(); > > > I am getting an error: error reading ascii file.possible mismatch of > datasize with declaration. How do I fix this? > > -swetha > > > > _______________________________________________ > 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 > From alvaro.sanchez at kitware.com Mon Jul 31 11:01:05 2017 From: alvaro.sanchez at kitware.com (Alvaro Sanchez) Date: Mon, 31 Jul 2017 11:01:05 -0400 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501498447377-5744215.post@n5.nabble.com> References: <1501154395427-5744174.post@n5.nabble.com> <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> <1501498447377-5744215.post@n5.nabble.com> Message-ID: Could you run the texture-streaming test? $ ctest -R CastTextureStreaming It might help to know if that also fails. On Mon, Jul 31, 2017 at 6:54 AM, Rick Dailey wrote: > The suggested solution (setting partitions) does not work for me. Although > the error message indicating invalid texture dimensions is gone there is > still a failure to bind the texture. > > This error message (in vtkVolumeTexture::SafeLoadTexture()) is no longer > seen: > > ERROR: In E:\VTK\VTK-master\Rendering\VolumeOpenGL2\vtkVolumeTexture.cxx, > line 720 > vtkVolumeTexture (10FA4E18): Invalid texture dimensions [53, 54, 3191] > > This assert (in vtkTextureObject::Bind()) still fires: > > assert(this->Handle); > > ERROR: In E:\VTK\VTK-master\Rendering\OpenGL2\vtkTextureObject.cxx, line > 549 > vtkTextureObject (1421E0A8): failed at glBindTexture 1 OpenGL errors > detected > 0 : (1280) Invalid enum > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068p5744215.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Alvaro Sanchez Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4901 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kor1581 at gmail.com Mon Jul 31 11:06:22 2017 From: kor1581 at gmail.com (K O ranjith) Date: Mon, 31 Jul 2017 20:36:22 +0530 Subject: [vtkusers] Reset window level and window width (vtkImagevewer2 + vtkInteractorStyleImage) Message-ID: Hello all, I'm using QVtkWinget+vtkImageviewer2+custom inherited vtkInteractorStyleImage to develop an DICOM imageviewer ( same as ReadDICOMSeries vtk example). The images in the series are loaded in viewer with mouse scroll. Also left mouse move changes the window level and width. In my imageviewer i need to reset the windowlevel and window width in viewer to custom values while loading a new image in series(and also in a predefined even like Crtl+R key). The values to be set are default values of DICOM meta data (For that I'm reading the window values from dicom meta data) The problem is I can't reset the window level and window width values of vtkImageviewer2. I tried with vtkImageViewer2->SetColorWindow and vtkImageViewer2->SetColorLevel methods, but it working on first image only. After that while loading the remaining image in the series (using the mouse scroll), the window level & width in viewer remaining in the last set values, later call to vtkImageViewer2->SetColorWindow and vtkImageViewer2->SetColorLevel methods not updating in viewer. (but can change the values through mouse, but intention is to change to a custom value.) I tried with the below method after setting the window values but nothing updating the new values in viewer. vtkImageViewer2->Render(); vtkImageViewer2->RemoveAllObservers(); vtkImageViewer2->GetRenderer()->ResetCamera(); vtkImageViewer2->->RemoveAllObservers(); How can set custom window width and values to the vtkImageViewer2? Where have to set it in vtkImageViewer2/ vtkInteractorStyleImage Please help.. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rick at pile.com Mon Jul 31 12:35:20 2017 From: rick at pile.com (Rick Dailey) Date: Mon, 31 Jul 2017 09:35:20 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> <1501498447377-5744215.post@n5.nabble.com> Message-ID: <1501518920479-5744223.post@n5.nabble.com> I tried running ctest but no matter what I do it always says "No tests were found!!!" I tried running it from several folders (bin, testing, etc.) but still the same message. It seems that I have built VTK with testing enabled (BUILD_TESTING check set) so a I am out of ideas. What is the correct way of running ctest? The latest stack trace: > ucrtbased.dll!common_assert_to_message_box(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number, void * const return_address) Line 351 C++ ucrtbased.dll!common_assert(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number, void * const return_address) Line 386 C++ ucrtbased.dll!_wassert(const wchar_t * expression, const wchar_t * file_name, unsigned int line_number) Line 404 C++ vtkRenderingOpenGL2-8.1.dll!vtkTextureObject::Bind() Line 546 C++ vtkRenderingOpenGL2-8.1.dll!vtkTextureObject::Activate() Line 491 C++ vtkRenderingVolumeOpenGL2-8.1.dll!vtkVolumeMask::Activate() Line 64 C++ vtkRenderingVolumeOpenGL2-8.1.dll!vtkOpenGLGPUVolumeRayCastMapper::DoGPURender(vtkRenderer * ren, vtkVolume * vol, vtkOpenGLCamera * cam, vtkShaderProgram * prog, int noOfComponents, int independentComponents) Line 3739 C++ vtkRenderingVolumeOpenGL2-8.1.dll!vtkOpenGLGPUVolumeRayCastMapper::GPURender(vtkRenderer * ren, vtkVolume * vol) Line 3610 C++ vtkRenderingVolume-8.1.dll!vtkGPUVolumeRayCastMapper::Render(vtkRenderer * ren, vtkVolume * vol) Line 154 C++ vtkRenderingCore-8.1.dll!vtkVolume::RenderVolumetricGeometry(vtkViewport * vp) Line 370 C++ vtkRenderingOpenGL2-8.1.dll!vtkOpenGLRenderer::UpdateGeometry() Line 273 C++ vtkRenderingOpenGL2-8.1.dll!vtkOpenGLRenderer::DeviceRender() Line 170 C++ vtkRenderingCore-8.1.dll!vtkRenderer::Render() Line 351 C++ vtkRenderingCore-8.1.dll!vtkRendererCollection::Render() Line 51 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::DoStereoRender() Line 781 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::DoFDRender() Line 747 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::DoAARender() Line 626 C++ vtkRenderingCore-8.1.dll!vtkRenderWindow::Render() Line 439 C++ PDI-TOMO.exe!vtkControlBase::Render(HDC * dc, const wchar_t * location) Line 694 C++ -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744223.html Sent from the VTK - Users mailing list archive at Nabble.com. From alvaro.sanchez at kitware.com Mon Jul 31 13:32:33 2017 From: alvaro.sanchez at kitware.com (Alvaro Sanchez) Date: Mon, 31 Jul 2017 10:32:33 -0700 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501518920479-5744223.post@n5.nabble.com> References: <1501254069970-5744196.post@n5.nabble.com> <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> <1501498447377-5744215.post@n5.nabble.com> <1501518920479-5744223.post@n5.nabble.com> Message-ID: If you built vtk with BUILD_TESTING checked then you should be able to run it from the build directory as C:\YOUR_VS_SOLUTION_DIR>ctest -R TextureStreaming -C Debug Change the last parameter to your particular configuration. Are you setting a volume mask or are you only rendering input data? On Mon, Jul 31, 2017 at 9:35 AM, Rick Dailey wrote: > I tried running ctest but no matter what I do it always says "No tests were > found!!!" I tried running it from several folders (bin, testing, etc.) but > still the same message. It seems that I have built VTK with testing > enabled > (BUILD_TESTING check set) so a I am out of ideas. What is the correct way > of running ctest? > > The latest stack trace: > > > ucrtbased.dll!common_assert_to_message_box(const wchar_t > * const > expression, const wchar_t * const file_name, const unsigned int > line_number, > void * const return_address) Line 351 C++ > ucrtbased.dll!common_assert(const wchar_t * const > expression, > const wchar_t * const file_name, const unsigned int line_number, void * > const return_address) Line 386 C++ > ucrtbased.dll!_wassert(const wchar_t * expression, const wchar_t * > file_name, unsigned int line_number) Line 404 C++ > vtkRenderingOpenGL2-8.1.dll!vtkTextureObject::Bind() Line 546 > C++ > vtkRenderingOpenGL2-8.1.dll!vtkTextureObject::Activate() Line > 491 C++ > vtkRenderingVolumeOpenGL2-8.1.dll!vtkVolumeMask::Activate() Line > 64 C++ > > vtkRenderingVolumeOpenGL2-8.1.dll!vtkOpenGLGPUVolumeRayCastMappe > r::DoGPURender(vtkRenderer > * ren, vtkVolume * vol, vtkOpenGLCamera * cam, vtkShaderProgram * prog, int > noOfComponents, int independentComponents) Line 3739 C++ > > vtkRenderingVolumeOpenGL2-8.1.dll!vtkOpenGLGPUVolumeRayCastMappe > r::GPURender(vtkRenderer > * ren, vtkVolume * vol) Line 3610 C++ > vtkRenderingVolume-8.1.dll!vtkGPUVolumeRayCastMapper::Render(vtkRenderer > * > ren, vtkVolume * vol) Line 154 C++ > vtkRenderingCore-8.1.dll!vtkVolume::RenderVolumetricGeometry(vtkViewport > * > vp) Line 370 C++ > vtkRenderingOpenGL2-8.1.dll!vtkOpenGLRenderer::UpdateGeometry() > Line 273 > C++ > vtkRenderingOpenGL2-8.1.dll!vtkOpenGLRenderer::DeviceRender() > Line 170 C++ > vtkRenderingCore-8.1.dll!vtkRenderer::Render() Line 351 C++ > vtkRenderingCore-8.1.dll!vtkRendererCollection::Render() Line 51 > C++ > vtkRenderingCore-8.1.dll!vtkRenderWindow::DoStereoRender() Line > 781 C++ > vtkRenderingCore-8.1.dll!vtkRenderWindow::DoFDRender() Line 747 > C++ > vtkRenderingCore-8.1.dll!vtkRenderWindow::DoAARender() Line 626 > C++ > vtkRenderingCore-8.1.dll!vtkRenderWindow::Render() Line 439 > C++ > PDI-TOMO.exe!vtkControlBase::Render(HDC * dc, const wchar_t * > location) > Line 694 C++ > > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068p5744223.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Alvaro Sanchez Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4901 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rick at pile.com Mon Jul 31 13:41:55 2017 From: rick at pile.com (Rick Dailey) Date: Mon, 31 Jul 2017 10:41:55 -0700 (MST) Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: References: <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> <1501498447377-5744215.post@n5.nabble.com> <1501518920479-5744223.post@n5.nabble.com> Message-ID: <1501522915867-5744226.post@n5.nabble.com> With the additional information you supplied I was able to successfully run ctest. 100% tests passed, 0 tests failed out of 1 Yes, I am using a volume mask. -- View this message in context: http://vtk.1045678.n5.nabble.com/vtkTextureObject-bind-error-tp5744068p5744226.html Sent from the VTK - Users mailing list archive at Nabble.com. From robert.maynard at kitware.com Mon Jul 31 14:25:26 2017 From: robert.maynard at kitware.com (Robert Maynard) Date: Mon, 31 Jul 2017 14:25:26 -0400 Subject: [vtkusers] VTK Development Survey In-Reply-To: References: Message-ID: I would like to remind everyone that the survey closes tomorrow. On Fri, Jul 28, 2017 at 9:21 AM, Robert Maynard wrote: > Hi Everybody, > > I would like to remind everyone that the developer survey is closing > in 4 days so please respond. > > On Tue, Jul 18, 2017 at 11:32 AM, Robert Maynard > wrote: >> Hi Everybody, >> >> The VTK team is always looking to attract new developers and improve >> the experience of developing VTK. >> >> To further that, we are putting out an anonymous survey to collect >> data on people's thoughts about the current software development >> process for VTK. We would love to hear all your rants ( or raves ) on >> the development process. We will gather the results after August 1'st. >> >> https://goo.gl/forms/WlqyiF0sBTZT7klJ3 >> >> Thank you for your inputs. From alvaro.sanchez at kitware.com Mon Jul 31 14:29:48 2017 From: alvaro.sanchez at kitware.com (Alvaro Sanchez) Date: Mon, 31 Jul 2017 14:29:48 -0400 Subject: [vtkusers] vtkTextureObject bind error In-Reply-To: <1501522915867-5744226.post@n5.nabble.com> References: <1501255581924-5744198.post@n5.nabble.com> <1501260214312-5744200.post@n5.nabble.com> <1501261737667-5744202.post@n5.nabble.com> <1501498447377-5744215.post@n5.nabble.com> <1501518920479-5744223.post@n5.nabble.com> <1501522915867-5744226.post@n5.nabble.com> Message-ID: Using masks with streaming enabled might be the issue. Currently, only the input supports texture streaming. Could you try rendering without any masks? On Mon, Jul 31, 2017 at 1:41 PM, Rick Dailey wrote: > With the additional information you supplied I was able to successfully run > ctest. > > 100% tests passed, 0 tests failed out of 1 > > Yes, I am using a volume mask. > > > > -- > View this message in context: http://vtk.1045678.n5.nabble. > com/vtkTextureObject-bind-error-tp5744068p5744226.html > Sent from the VTK - Users mailing list archive at Nabble.com. > _______________________________________________ > 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 > -- Alvaro Sanchez Kitware, Inc. Senior R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4901 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikewithascarf at yahoo.com Mon Jul 31 17:43:45 2017 From: mikewithascarf at yahoo.com (mikewithascarf) Date: Mon, 31 Jul 2017 14:43:45 -0700 (MST) Subject: [vtkusers] image rendering speed In-Reply-To: References: <1500661004209-5744115.post@n5.nabble.com> Message-ID: <1501537425830-5744230.post@n5.nabble.com> Thanks Ken. Unfortunately vtkRenderTimerLog doesn't appear to be in VTK as far as I can tell? I'm using VTK 7.1.0. -- View this message in context: http://vtk.1045678.n5.nabble.com/image-rendering-speed-tp5744115p5744230.html Sent from the VTK - Users mailing list archive at Nabble.com. From chenshaoqiang at buaa.edu.cn Mon Jul 31 22:18:08 2017 From: chenshaoqiang at buaa.edu.cn (chensq) Date: Tue, 1 Aug 2017 10:18:08 +0800 Subject: [vtkusers] Is it possible to make the VTKTextbook.pdf better? Message-ID: <8963ED62896641DEA819B1963E997040@chensqPC> All of the formulas are disordered. Sincerely Chen -------------- next part -------------- An HTML attachment was scrubbed... URL: From landinghere at 163.com Mon Jul 31 22:49:07 2017 From: landinghere at 163.com (landings) Date: Mon, 31 Jul 2017 19:49:07 -0700 (MST) Subject: [vtkusers] How to split large models into smaller pieces when exporting the scene? Message-ID: <1501555747988-5744232.post@n5.nabble.com> Hi, I'm using VTK with Unity 3D. I use vtkX3DExporter to export my VTK scene, and rebuild the meshes in Unity. Unity and maybe all game engines don't support single models that have more than 65536 vertices. I must split large models into smaller pieces. Is there an existing method to do this, or do I need to implement this myself? If the latter, could you give me some hints? -- View this message in context: http://vtk.1045678.n5.nabble.com/How-to-split-large-models-into-smaller-pieces-when-exporting-the-scene-tp5744232.html Sent from the VTK - Users mailing list archive at Nabble.com.