From felipebordeu at gmail.com Fri Jul 1 05:44:36 2016 From: felipebordeu at gmail.com (Felipe Bordeu) Date: Fri, 1 Jul 2016 11:44:36 +0200 Subject: [Paraview-developers] [Non-DoD Source] Bug in the xdmf Reader 3 In-Reply-To: References: Message-ID: I think the problem is in the reader. You can see, in Wireframe mode, that the number of elements displayed is not correct. Another way of see the problem is if you put the second time step as the first one. Then for the first time step you can se 2 element, but for the second time step, one face is missing on the cube. I think all this is related to the update extent in the reader. Can some one confirm this behavior. ps: my problem is using different sizes of grids in different timesteps. Thanks Felipe 2016-06-30 15:05 GMT+02:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) < andrew.j.burns35.ctr at mail.mil>: > In this case, it looks like an issue with the "clean to grid" filter. Once > the grid is initially loaded, the data is outside of the Xdmf3 reader. I'm > not particularly familiar with that functionality, so I can't say > specifically what is wrong. > > Andrew Burns > Lockheed Martin > Software Engineer > 410-306-0409 > ARL DSRC > andrew.j.burns35.ctr at mail.mil > > -----Original Message----- > From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] > On Behalf Of Felipe Bordeu > Sent: Thursday, June 30, 2016 5:50 AM > To: ParaView Developers > Subject: Re: [Paraview-developers] [Non-DoD Source] Bug in the xdmf Reader > 3 > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm the authenticity of all links contained > within the message prior to copying and pasting the address to a Web > browser. > > > ________________________________ > > > > ok, lest work with your file. if you look at the information tab, for the > first timestep you get : > number of cells 1 > number of points : 8 > bounds: Z range 0 to 1 (delta: 1 ) > > for the second timestep you get > number of cells 2 > number of points : 12 > bounds: Z range 1 to 5 (delta: 4) > > > and if you apply a "clean to grid" filter in the information tab (of the > clean to grid filter o of course) you get: > > for the first timestep you get : > number of cells 1 > number of points : 8 > bounds: Z range 0 to 1 (delta: 1 ) > > for the second timestep you get > number of cells 1 > number of points : 8 > bounds: Z range 1 to 3 (delta: 2) > > > > this is wrong. > > Felipe > > > > > 2016-06-29 17:01 GMT+02:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) < > andrew.j.burns35.ctr at mail.mil < Caution-mailto: > andrew.j.burns35.ctr at mail.mil > >: > > > Xdmf's latest version prefers having each grid declare its time > value separately. > > > > > CollectionType="Temporal" > > > > > > > > > > It looks to me that both grids are the same "size," one unit in > each dimension. The difference is that in the second grid the first > dimension is divided into three subidivisions instead of the two > subdivisions in the first one. This results in cells that are 0.5x.x0.5x0.5 > in the first grid and 0.33x0.5x0.5 in the second grid. > > If you aren't filling the cells with an attribute both grids would > look the same. > > -Andrew Burns > > > -----Original Message----- > From: Paraview-developers [Caution-mailto: > paraview-developers-bounces at paraview.org < Caution-mailto: > paraview-developers-bounces at paraview.org > ] On Behalf Of Felipe Bordeu > Sent: Wednesday, June 29, 2016 10:51 AM > To: ParaView Developers Caution-mailto:paraview-developers at paraview.org > > > Subject: [Non-DoD Source] [Paraview-developers] Bug in the xdmf > Reader 3 > > Hi, > > I'm working with 3DCoRectMesh meshes. the attached file contains 2 > time steps with two 3DCoRectMesh with different topologies. Paraview only > update the UpdateExtent for the first time step, making the solution of the > second timestep croped. > > Any ideas for a fast workaround? > I tried clean to grid but does not work. > > In the information tab you can see the total number of element and > point is correct but after the clean to grid filter only half of the mesh > is treated. > > using latest ParaView from web (5.1.0 64-bit windows ) Felipe > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Fri Jul 1 11:19:58 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Fri, 1 Jul 2016 15:19:58 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> Message-ID: <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> Reason 1: Increasing the resolution 2X increases the compositing overhead by up to 4. Increasing the resolution 4X increases the compositing time by up to 16. It can be a noticeable difference when rendering interactively. Reason 2: There can be technical difficulties in rendering images that large. You are likely to have a rendering context of the original resolution. To render such large images with images/movies, it renders image tiles and stitches them together. This adds further overhead and complication in rendering. Reason 3: Line width is measured in pixels. Changing the resolution of the image in this way will change the perceived line width. -Ken From: Paraview-developers on behalf of Walter Scott Date: Thursday, June 30, 2016 at 7:48 PM To: David E DeMarle Cc: "paraview-developers at paraview.org" Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA OK, why can?t we do that? Have a mode that internally runs 2X or 4X resolution, does the compositing, and then shrinks back to what the user wants? Only turn it on when 3d lines are in the image? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, June 30, 2016 7:46 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA Antialiasing confuses depth compositing. Better to save out images/movies at 4x resolution and resample outside of paraview. On Thursday, June 30, 2016, Scott, W Alan > wrote: Why can?t we turn anti alias lines on? I am doing a feature edges, and it looks horrible. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -- David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Fri Jul 1 14:12:56 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 1 Jul 2016 18:12:56 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> Message-ID: Makes sense. But? 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for better images when lines are visible. Default off. You want better images, it will be slower (when lines are visible). 2) We do it (when rendering off screen) all the time when making movies for the power wall. I don?t see this as an issue? 3) Have the line widths automatically written 2X requested width. Thus, when it shrinks by 2, you get normal, poor man?s AA lines. Alan From: Moreland, Kenneth Sent: Friday, July 01, 2016 9:20 AM To: Scott, W Alan ; David E DeMarle Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA Reason 1: Increasing the resolution 2X increases the compositing overhead by up to 4. Increasing the resolution 4X increases the compositing time by up to 16. It can be a noticeable difference when rendering interactively. Reason 2: There can be technical difficulties in rendering images that large. You are likely to have a rendering context of the original resolution. To render such large images with images/movies, it renders image tiles and stitches them together. This adds further overhead and complication in rendering. Reason 3: Line width is measured in pixels. Changing the resolution of the image in this way will change the perceived line width. -Ken From: Paraview-developers > on behalf of Walter Scott > Date: Thursday, June 30, 2016 at 7:48 PM To: David E DeMarle > Cc: "paraview-developers at paraview.org" > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA OK, why can?t we do that? Have a mode that internally runs 2X or 4X resolution, does the compositing, and then shrinks back to what the user wants? Only turn it on when 3d lines are in the image? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, June 30, 2016 7:46 PM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA Antialiasing confuses depth compositing. Better to save out images/movies at 4x resolution and resample outside of paraview. On Thursday, June 30, 2016, Scott, W Alan > wrote: Why can?t we turn anti alias lines on? I am doing a feature edges, and it looks horrible. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -- David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Fri Jul 1 21:58:14 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Sat, 2 Jul 2016 01:58:14 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> Message-ID: <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> OK, let me rephrase my pushback. There are several technical hurtles to implement this feature. We know how to achive this effect, but it requires a non-trivial change to the rendering system that will take significant development cycles, add complexity to the rendering system, and potentially destabilize several features relying on the rendering. Plus, this is all happening in the middle of a push for other (more important) rendering features (OpenGL2, OpenSWR, Ospray, IndeX). We turned off antialiasing in ParaView years ago because it caused way more problems than it was worth. The question is, do you really think it is important enough now to have a software push for it? -Ken From: Walter Scott Date: Friday, July 1, 2016 at 12:12 PM To: Kenneth Moreland , David E DeMarle Cc: "paraview-developers at paraview.org" Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA Makes sense. But? 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for better images when lines are visible. Default off. You want better images, it will be slower (when lines are visible). 2) We do it (when rendering off screen) all the time when making movies for the power wall. I don?t see this as an issue? 3) Have the line widths automatically written 2X requested width. Thus, when it shrinks by 2, you get normal, poor man?s AA lines. Alan From: Moreland, Kenneth Sent: Friday, July 01, 2016 9:20 AM To: Scott, W Alan ; David E DeMarle Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA Reason 1: Increasing the resolution 2X increases the compositing overhead by up to 4. Increasing the resolution 4X increases the compositing time by up to 16. It can be a noticeable difference when rendering interactively. Reason 2: There can be technical difficulties in rendering images that large. You are likely to have a rendering context of the original resolution. To render such large images with images/movies, it renders image tiles and stitches them together. This adds further overhead and complication in rendering. Reason 3: Line width is measured in pixels. Changing the resolution of the image in this way will change the perceived line width. -Ken From: Paraview-developers > on behalf of Walter Scott > Date: Thursday, June 30, 2016 at 7:48 PM To: David E DeMarle > Cc: "paraview-developers at paraview.org" > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA OK, why can?t we do that? Have a mode that internally runs 2X or 4X resolution, does the compositing, and then shrinks back to what the user wants? Only turn it on when 3d lines are in the image? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, June 30, 2016 7:46 PM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA Antialiasing confuses depth compositing. Better to save out images/movies at 4x resolution and resample outside of paraview. On Thursday, June 30, 2016, Scott, W Alan > wrote: Why can?t we turn anti alias lines on? I am doing a feature edges, and it looks horrible. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -- David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Jul 5 22:08:41 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 6 Jul 2016 02:08:41 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> Message-ID: <8dc4fc3e4333438a9da987d6d94ece71@ES01AMSNLNT.srn.sandia.gov> OK, much better pushback. I would say AA (either the hack mentioned below or real) probably isn?t worth a non-trivial software change at this point. We should keep it on the table for future work. Alan From: Moreland, Kenneth Sent: Friday, July 01, 2016 7:58 PM To: Scott, W Alan ; David E DeMarle Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA OK, let me rephrase my pushback. There are several technical hurtles to implement this feature. We know how to achive this effect, but it requires a non-trivial change to the rendering system that will take significant development cycles, add complexity to the rendering system, and potentially destabilize several features relying on the rendering. Plus, this is all happening in the middle of a push for other (more important) rendering features (OpenGL2, OpenSWR, Ospray, IndeX). We turned off antialiasing in ParaView years ago because it caused way more problems than it was worth. The question is, do you really think it is important enough now to have a software push for it? -Ken From: Walter Scott > Date: Friday, July 1, 2016 at 12:12 PM To: Kenneth Moreland >, David E DeMarle > Cc: "paraview-developers at paraview.org" > Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA Makes sense. But? 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for better images when lines are visible. Default off. You want better images, it will be slower (when lines are visible). 2) We do it (when rendering off screen) all the time when making movies for the power wall. I don?t see this as an issue? 3) Have the line widths automatically written 2X requested width. Thus, when it shrinks by 2, you get normal, poor man?s AA lines. Alan From: Moreland, Kenneth Sent: Friday, July 01, 2016 9:20 AM To: Scott, W Alan >; David E DeMarle > Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA Reason 1: Increasing the resolution 2X increases the compositing overhead by up to 4. Increasing the resolution 4X increases the compositing time by up to 16. It can be a noticeable difference when rendering interactively. Reason 2: There can be technical difficulties in rendering images that large. You are likely to have a rendering context of the original resolution. To render such large images with images/movies, it renders image tiles and stitches them together. This adds further overhead and complication in rendering. Reason 3: Line width is measured in pixels. Changing the resolution of the image in this way will change the perceived line width. -Ken From: Paraview-developers > on behalf of Walter Scott > Date: Thursday, June 30, 2016 at 7:48 PM To: David E DeMarle > Cc: "paraview-developers at paraview.org" > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA OK, why can?t we do that? Have a mode that internally runs 2X or 4X resolution, does the compositing, and then shrinks back to what the user wants? Only turn it on when 3d lines are in the image? From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Thursday, June 30, 2016 7:46 PM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA Antialiasing confuses depth compositing. Better to save out images/movies at 4x resolution and resample outside of paraview. On Thursday, June 30, 2016, Scott, W Alan > wrote: Why can?t we turn anti alias lines on? I am doing a feature edges, and it looks horrible. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -- David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Wed Jul 6 10:49:09 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Wed, 6 Jul 2016 16:49:09 +0200 Subject: [Paraview-developers] VTK/Paraview Courses in October Message-ID: Hello Kitware will be holding a 2-day VTK and ParaView course on October 11th and 12th 2016 in Lyon, France. Please visit our web site for more information and registration details at VTK (English) : http://training.kitware.fr/browse/130 VTK (French) : http://formations.kitware.fr/browse/130 ParaView (English) : http://training.kitware.fr/browse/131 ParaView (French) : http://formations.kitware.fr/browse/131 Note that the course will be taught in English. If you have any question, please contact us at formations at http://www.kitware.fr Thank you, Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From julia.ute.fischer at gmail.com Wed Jul 6 16:23:36 2016 From: julia.ute.fischer at gmail.com (Julia Fischer) Date: Wed, 6 Jul 2016 22:23:36 +0200 Subject: [Paraview-developers] memory Leak by MultiBlockData Set Message-ID: Hello everyone, I am having a hard time by using a vtkMultiBlockDataSet , I have attached a small but working example of what I want to achieve, a dummy reader , it does not read but add a bunch of vtkStructuredGrid's My problem is a bit more complex, but long story short; I have a hierarchical vtkMultiBlockDataSet vtkMultiBlockDataSet (level0) declared using a vtkSmartPointer -vtkMultiBlockDataSet (level1) --vtkMultiBlockDataSet (level2) --vtkMultiBlockDataSet (level2) ---vtkStructucuredGrid (level3) ---vtkStructucuredGrid (level3) ---vtkStructucuredGrid (level3) --vtkMultiBlockDataSet (level2) In my RequestData I create the structure all with smart pointers, if it is not created , and flag is set to avoid creating again the skeleton *** if !this->rootMB_init *** I use a vtkIntProperty (Select Block) to tell the server to fill up any level3 (StructuredGrid), for example SelectBlock: 4 -> Apply, (it loads grid 4, marked as unloaded ) SelectBlock:-1 -> Apply (nothing) SelectBlock:4 -> Apply (unload grid 4 , since is loaded and marked as loaded ) when I repeat the sequence with several blocks the memory is not being released somehow. I think my problem is here, but i cannot see it.. if (block loaded) //line 110 { vtkSmartPointergrid=ReadGrid(500 ,0.01, iL3 , iL3, iL3); //500x500x500 nodes ~2.6GB vtkMultiBlockDataSet->SetBlock(block, grid); } else if ( !blockIsLoaded) //line 118 { vtkSmartPointergrid=vtkSmartPointer::New() vtkMultiBlockDataSet->SetBlock(block, grid); isBlockLoaded=false; } maybe I am initializing wrong . I have read the recommendations about vtkSmartPointer . Smart pointers for new objects and std pointer (vtkMultiBlockDataSet *, etc) for references In order to compile just untar ; cd build , cmake .. ; make the extension is *.mem i have included an empty dummy.mem for reading maybe you can give me a hint , or an advice of a better way to Thank you so much in advance Julia -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mem_leak.tar Type: application/x-tar Size: 20480 bytes Desc: not available URL: From julia.ute.fischer at gmail.com Thu Jul 7 13:25:29 2016 From: julia.ute.fischer at gmail.com (Julia Fischer) Date: Thu, 7 Jul 2016 19:25:29 +0200 Subject: [Paraview-developers] memory Leak by MultiBlockData Set In-Reply-To: References: Message-ID: Hello again I just realized , I forgot the xml file in my tar file Thanks ! Julia On 6 July 2016 at 22:23, Julia Fischer wrote: > Hello everyone, > > > I am having a hard time by using a vtkMultiBlockDataSet , I have attached > a small but working example of what I want to achieve, a dummy reader , it > does not read but add a bunch of vtkStructuredGrid's > > My problem is a bit more complex, but long story short; I have a > hierarchical vtkMultiBlockDataSet > > vtkMultiBlockDataSet (level0) declared using a > vtkSmartPointer > -vtkMultiBlockDataSet (level1) > --vtkMultiBlockDataSet (level2) > --vtkMultiBlockDataSet (level2) > ---vtkStructucuredGrid (level3) > ---vtkStructucuredGrid (level3) > ---vtkStructucuredGrid (level3) > --vtkMultiBlockDataSet (level2) > > In my RequestData I create the structure all with smart pointers, if it > is not created , and flag is set to avoid creating again the skeleton > *** if !this->rootMB_init *** > > I use a vtkIntProperty (Select Block) to tell the server to fill up any > level3 (StructuredGrid), for example > SelectBlock: 4 -> Apply, (it loads grid 4, marked as unloaded ) > SelectBlock:-1 -> Apply (nothing) > SelectBlock:4 -> Apply (unload grid 4 , since is loaded and marked as > loaded ) > > when I repeat the sequence with several blocks the memory is not being > released somehow. I think my problem is here, but i cannot see it.. > > if (block loaded) //line 110 > { > vtkSmartPointergrid=ReadGrid(500 ,0.01, iL3 , > iL3, iL3); //500x500x500 nodes ~2.6GB > vtkMultiBlockDataSet->SetBlock(block, grid); > } > else if ( !blockIsLoaded) //line 118 > { > > vtkSmartPointergrid=vtkSmartPointer::New() > vtkMultiBlockDataSet->SetBlock(block, grid); > isBlockLoaded=false; > } > > > maybe I am initializing wrong . I have read the recommendations about > vtkSmartPointer . Smart pointers for new objects and std pointer > (vtkMultiBlockDataSet *, etc) for references > > In order to compile just untar ; cd build , cmake .. ; make the > extension is *.mem i have included an empty dummy.mem for reading > > maybe you can give me a hint , or an advice of a better way to > > Thank you so much in advance > > Julia > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mem_leak.tar Type: application/x-tar Size: 20480 bytes Desc: not available URL: From dave.demarle at kitware.com Thu Jul 7 19:11:05 2016 From: dave.demarle at kitware.com (David E DeMarle) Date: Thu, 7 Jul 2016 19:11:05 -0400 Subject: [Paraview-developers] [Non-DoD Source] Bug in the xdmf Reader 3 In-Reply-To: References: Message-ID: Felipe, As you have discovered, the VTK and ParaView pipelines do not deal well with handle time varying structured data extents. It is not necessarily an XDMF related problem. As I recall a work around at one point was to put the grid into a multiblock in which case the extent handling goes though a different path. HTH David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Jul 1, 2016 at 5:44 AM, Felipe Bordeu wrote: > I think the problem is in the reader. You can see, in Wireframe mode, > that the number of elements displayed is not correct. > Another way of see the problem is if you put the second time step as the > first one. Then for the first time step you can se 2 element, but for the > second time step, one face is missing on the cube. > > I think all this is related to the update extent in the reader. > > Can some one confirm this behavior. > > ps: my problem is using different sizes of grids in different timesteps. > > Thanks > Felipe > > 2016-06-30 15:05 GMT+02:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) < > andrew.j.burns35.ctr at mail.mil>: > >> In this case, it looks like an issue with the "clean to grid" filter. >> Once the grid is initially loaded, the data is outside of the Xdmf3 reader. >> I'm not particularly familiar with that functionality, so I can't say >> specifically what is wrong. >> >> Andrew Burns >> Lockheed Martin >> Software Engineer >> 410-306-0409 >> ARL DSRC >> andrew.j.burns35.ctr at mail.mil >> >> -----Original Message----- >> From: Paraview-developers [mailto: >> paraview-developers-bounces at paraview.org] On Behalf Of Felipe Bordeu >> Sent: Thursday, June 30, 2016 5:50 AM >> To: ParaView Developers >> Subject: Re: [Paraview-developers] [Non-DoD Source] Bug in the xdmf >> Reader 3 >> >> All active links contained in this email were disabled. Please verify the >> identity of the sender, and confirm the authenticity of all links contained >> within the message prior to copying and pasting the address to a Web >> browser. >> >> >> ________________________________ >> >> >> >> ok, lest work with your file. if you look at the information tab, for the >> first timestep you get : >> number of cells 1 >> number of points : 8 >> bounds: Z range 0 to 1 (delta: 1 ) >> >> for the second timestep you get >> number of cells 2 >> number of points : 12 >> bounds: Z range 1 to 5 (delta: 4) >> >> >> and if you apply a "clean to grid" filter in the information tab (of the >> clean to grid filter o of course) you get: >> >> for the first timestep you get : >> number of cells 1 >> number of points : 8 >> bounds: Z range 0 to 1 (delta: 1 ) >> >> for the second timestep you get >> number of cells 1 >> number of points : 8 >> bounds: Z range 1 to 3 (delta: 2) >> >> >> >> this is wrong. >> >> Felipe >> >> >> >> >> 2016-06-29 17:01 GMT+02:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) < >> andrew.j.burns35.ctr at mail.mil < Caution-mailto: >> andrew.j.burns35.ctr at mail.mil > >: >> >> >> Xdmf's latest version prefers having each grid declare its time >> value separately. >> >> >> >> >> > CollectionType="Temporal" > >> >> >> >> >> >> >> >> >> It looks to me that both grids are the same "size," one unit in >> each dimension. The difference is that in the second grid the first >> dimension is divided into three subidivisions instead of the two >> subdivisions in the first one. This results in cells that are 0.5x.x0.5x0.5 >> in the first grid and 0.33x0.5x0.5 in the second grid. >> >> If you aren't filling the cells with an attribute both grids >> would look the same. >> >> -Andrew Burns >> >> >> -----Original Message----- >> From: Paraview-developers [Caution-mailto: >> paraview-developers-bounces at paraview.org < Caution-mailto: >> paraview-developers-bounces at paraview.org > ] On Behalf Of Felipe Bordeu >> Sent: Wednesday, June 29, 2016 10:51 AM >> To: ParaView Developers > Caution-mailto:paraview-developers at paraview.org > > >> Subject: [Non-DoD Source] [Paraview-developers] Bug in the xdmf >> Reader 3 >> >> Hi, >> >> I'm working with 3DCoRectMesh meshes. the attached file contains >> 2 time steps with two 3DCoRectMesh with different topologies. Paraview only >> update the UpdateExtent for the first time step, making the solution of the >> second timestep croped. >> >> Any ideas for a fast workaround? >> I tried clean to grid but does not work. >> >> In the information tab you can see the total number of element >> and point is correct but after the clean to grid filter only half of the >> mesh is treated. >> >> using latest ParaView from web (5.1.0 64-bit windows ) Felipe >> >> >> >> >> >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jul 7 20:53:37 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 8 Jul 2016 00:53:37 +0000 Subject: [Paraview-developers] D3 and higher order elements Message-ID: <86a8c72d07754943975608b2009312cb@ES01AMSNLNT.srn.sandia.gov> I have a user that tried to run the D3 filter on higher order elements. D3 failed, silently. The confusing hack was to run the Tesselate filter before D3. What is the correct solution? * Have D3 deal with higher order elements? Ditto the Ghost Cell Generator? * Have D3 and Ghost Cell Generator call Tesselate filter under the covers? * Have an output warning message that D3 is failing due to higher order elements? I would argue for the first or second. Thoughts? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Jul 8 06:51:21 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 8 Jul 2016 06:51:21 -0400 Subject: [Paraview-developers] ParaView bug hackathon In-Reply-To: References: Message-ID: Following on the footsteps of the successful VTK hackathon, we'll be doing a ParaView hackathon next week on Wed. July 13. Please email me (or the list) if you're attending. The objectives will be similar: * clean up pending MRs * clean up bugs reported on bug tracker * update/triage dashboard machines Utkarsh On Mon, Jun 20, 2016 at 4:30 PM, Berk Geveci wrote: > Hi folks, > > We are planning a ParaView bug hackathon on July 13. Going forward, we would > like this to be a monthly event during which the community comes together to > address bugs reported to the tracker. It will be an all day event that we > will host physically at Kitware Headquarters in Clifton Park, NY as well as > online via Google Hangout. All are welcome to attend as long as they know > the code base enough to fix bugs. > > Any questions? Comments? Any potential issue with the date? > > Best, > -berk > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From kmorel at sandia.gov Sun Jul 10 10:58:38 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Sun, 10 Jul 2016 14:58:38 +0000 Subject: [Paraview-developers] D3 and higher order elements Message-ID: <2289751B-51E2-49FD-8199-BC08A788B0C5@sandia.gov> Ideally, D3 (or its replacement) and the ghost cell generator would work correctly for higher order elements. I can?t think of anything special about non-linear elements that would make it particularly harder to partition or find ghost cells. As long as you are not clipping the cells, there is no interpolation that needs to be done. -Ken From: Paraview-developers on behalf of Walter Scott Date: Thursday, July 7, 2016 at 5:53 PM To: "paraview-developers at paraview.org" Subject: [EXTERNAL] [Paraview-developers] D3 and higher order elements I have a user that tried to run the D3 filter on higher order elements. D3 failed, silently. The confusing hack was to run the Tesselate filter before D3. What is the correct solution? ? Have D3 deal with higher order elements? Ditto the Ghost Cell Generator? ? Have D3 and Ghost Cell Generator call Tesselate filter under the covers? ? Have an output warning message that D3 is failing due to higher order elements? I would argue for the first or second. Thoughts? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Tue Jul 12 01:22:02 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Tue, 12 Jul 2016 10:52:02 +0530 Subject: [Paraview-developers] paraview PVSessionCore error Message-ID: Hi, I am trying to implement a new filter in ParaView and I get the following error while executing. vtkPVSessionCore (0x162d180): Object type: MyObjectSource, could not find requested method: "setVariable" or the method was called with incorrect arguments. while processing Message 0 = Invoke Argument 0 = vtk_object_pointer {MyObjectSource(0x34b3870)} Argument 1 = string_value {setVariable} Argument 2 = float64_value {0.003} I searched the mailing list and it looks like a very similar bug has been reported http://www.paraview.org/Bug/view.php?id=15593 People have faced similar problem and here are the details http://public.kitware.com/pipermail/paraview/2016-March/036387.html Is there a solution of work-around? Chiranjib -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Hallock at pfizer.com Tue Jul 12 08:14:29 2016 From: Kevin.Hallock at pfizer.com (Hallock, Kevin) Date: Tue, 12 Jul 2016 12:14:29 +0000 Subject: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) In-Reply-To: References: Message-ID: Hi everyone, I built a model in Paraview 5.0.0 (64-bit) on my Mac (El Capitan) and several of the surfaces have 0.5 opacity, which looks fine on my Mac. When I open the same model in Paraview 5.0.0 (64-bit) on a Windows 7 computer the transparency no longer behaves well. Transparent surfaces disappear at certain angles, the back face appears less transparent, etc. Any suggestions? Thanks, Kevin PS ? I originally posted this with screen shots of the problem, but the original message was held for several days of review so I cancelled the posting. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jul 12 09:37:05 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 12 Jul 2016 09:37:05 -0400 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: Chiranjib, Usually this error means there is a mismatch between the XML used to describe the VTK-side class. Check that your XML name for the member function matches the C++, and that the member function setVariable() takes only one value. Cory On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur wrote: > Hi, > I am trying to implement a new filter in ParaView and I get the following > error while executing. > > vtkPVSessionCore (0x162d180): Object type: MyObjectSource, could not find > requested method: "setVariable" > or the method was called with incorrect arguments. > > while processing > Message 0 = Invoke > Argument 0 = vtk_object_pointer {MyObjectSource(0x34b3870)} > Argument 1 = string_value {setVariable} > Argument 2 = float64_value {0.003} > > > I searched the mailing list and it looks like a very similar bug has been > reported > http://www.paraview.org/Bug/view.php?id=15593 > > > People have faced similar problem and here are the details > http://public.kitware.com/pipermail/paraview/2016-March/036387.html > > Is there a solution of work-around? > > Chiranjib > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. From shawn.waldon at kitware.com Tue Jul 12 10:24:15 2016 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Tue, 12 Jul 2016 10:24:15 -0400 Subject: [Paraview-developers] Segfault opening ParaView on Ubuntu 14.04 Message-ID: Hi all, My laptop is running Ubuntu 14.04 with an ATI graphics card. I built paraview master (with Qt5.6 if it matters) and it got as far as the splash screen before segfaulting when I tried to run it. Here is a stack trace from GDB [1]. I'm travelling right now, but I'll be back in time for the hackathon tomorrow. Maybe we can look at it then. Shawn [1]: Program received signal SIGSEGV, Segmentation fault. 0x0000001500000001 in ?? () (gdb) where #0 0x0000001500000001 in ?? () #1 0x00007fffe7d7f8cb in XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #2 0x00007fffe7d73be2 in XInitExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #3 0x00007fffdbb1789f in XextAddDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6 #4 0x00007fffea35797a in ?? () from /usr/lib/fglrx/libGL.so.1 #5 0x00007fffcf7d32cf in ?? () from /usr/lib/dri/fglrx_dri.so #6 0x00007fffcf7c86d8 in driCreateContextAttribs () from /usr/lib/dri/fglrx_dri.so #7 0x00007fffea32b698 in ?? () from /usr/lib/fglrx/libGL.so.1 #8 0x00007fffea32bf29 in glXCreateContextAttribsARB () from /usr/lib/fglrx/libGL.so.1 #9 0x00007fffe82f7908 in vtkXOpenGLRenderWindow::CreateAWindow (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:599 #10 0x00007fffe82f8bd3 in vtkXOpenGLRenderWindow::WindowInitialize (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:976 #11 0x00007fffe82f8ca7 in vtkXOpenGLRenderWindow::Initialize (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:998 #12 0x00007fffe82f90ed in vtkXOpenGLRenderWindow::Start (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:1125 #13 0x00007ffff29f8df7 in vtkRenderWindow::DoStereoRender (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:748 #14 0x00007ffff29f8dd0 in vtkRenderWindow::DoFDRender (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:737 #15 0x00007ffff29f877c in vtkRenderWindow::DoAARender (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:616 #16 0x00007ffff29f7d4b in vtkRenderWindow::Render (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:432 #17 0x00007fffe8241180 in vtkOpenGLRenderWindow::Render (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:661 #18 0x00007fffe82fbab5 in vtkXOpenGLRenderWindow::Render (this=0x2f54da0) at /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:1786 #19 0x00007ffff38a16da in vtkPVRenderView::Render (this=0x2f01600, interactive=false, skip_rendering=false) at /home/shawn/dev/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:1506 #20 0x00007ffff38a0d7f in vtkPVRenderView::StillRender (this=0x2f01600) at /home/shawn/dev/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:1345 #21 0x00007fffee210ee8 in vtkPVRenderViewCommand (arlu=0x725860, ob=0x2f01600, method=0x2fbce59 "StillRender", msg=..., resultStream=...) at Wrapping/ClientServer/vtkPVRenderViewClientServer.cxx:234 #22 0x00007fffec9d3922 in vtkClientServerInterpreter::CallCommandFunction (this=0x725860, cname=0x7ffff3901752 "vtkPVRenderView", ptr=0x2f01600, method=0x2fbce59 "StillRender", msg=..., result=...) at /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:848 #23 0x00007fffec9d210b in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x725860, css=..., midx=0) at /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:437 #24 0x00007fffec9d1663 in vtkClientServerInterpreter::ProcessOneMessage (this=0x725860, css=..., message=0) at /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:269 #25 0x00007fffec9d14ed in vtkClientServerInterpreter::ProcessStream (this=0x725860, css=...) at /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:238 #26 0x00007ffff2fa3f57 in vtkPVSessionCore::ExecuteStreamInternal (this=0x741bb0, stream=..., ignore_errors=false) at /home/shawn/dev/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:669 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Orlando.RIVERA at mtu.de Tue Jul 12 10:39:52 2016 From: Orlando.RIVERA at mtu.de (RIVERA ROLDAN, Jorge Orlando) Date: Tue, 12 Jul 2016 14:39:52 +0000 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: Hi, Also , check if "setVariable" is in the public section of your class Orlando -----Urspr?ngliche Nachricht----- Von: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] Im Auftrag von Cory Quammen Gesendet: Tuesday, 12. July 2016 15:37 An: Chiranjib Sur Cc: Paraview Developer Mailing list Betreff: Re: [Paraview-developers] paraview PVSessionCore error Chiranjib, Usually this error means there is a mismatch between the XML used to describe the VTK-side class. Check that your XML name for the member function matches the C++, and that the member function setVariable() takes only one value. Cory On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur wrote: > Hi, > I am trying to implement a new filter in ParaView and I get the following > error while executing. > > vtkPVSessionCore (0x162d180): Object type: MyObjectSource, could not find > requested method: "setVariable" > or the method was called with incorrect arguments. > > while processing > Message 0 = Invoke > Argument 0 = vtk_object_pointer {MyObjectSource(0x34b3870)} > Argument 1 = string_value {setVariable} > Argument 2 = float64_value {0.003} > > > I searched the mailing list and it looks like a very similar bug has been > reported > http://www.paraview.org/Bug/view.php?id=15593 > > > People have faced similar problem and here are the details > http://public.kitware.com/pipermail/paraview/2016-March/036387.html > > Is there a solution of work-around? > > Chiranjib > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From utkarsh.ayachit at kitware.com Tue Jul 12 14:11:37 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 12 Jul 2016 14:11:37 -0400 Subject: [Paraview-developers] ParaView bug hackathon In-Reply-To: References: Message-ID: Folks, Thanks to all those who responded. I've create a calendar invite. Others are welcome to join in on July 13th, between 10 am - 5 pm EDT (NY time) to participate remotely using the following hangout link: https://hangouts.google.com/hangouts/_/kitware.com/paraview Everyone is free to help out as you deem fit. A few suggestions are as follows: 1. Fix bugs reported on the bug tracker. To make this easier, we've created a short list of bugs with tag "Hackathon-July-2016". You may pick ones in this list, or any other open issue. Even just trying the bug report out with latest "master" and flagging the bug as reproducible or not -- for those new to ParaView development -- is a huge help. Here's a link to these shortlisted bugs: http://tinyurl.com/hhfnjh7 Again, you are free to expand beyond these to all open bugs if you like. This short list is just a starting point for those who need it. 2. Review merge requests 3. Investigate Python 3 support 4. Review/reorganize dashboard machines Utkarsh On Mon, Jun 20, 2016 at 4:30 PM, Berk Geveci wrote: > Hi folks, > > We are planning a ParaView bug hackathon on July 13. Going forward, we would > like this to be a monthly event during which the community comes together to > address bugs reported to the tracker. It will be an all day event that we > will host physically at Kitware Headquarters in Clifton Park, NY as well as > online via Google Hangout. All are welcome to attend as long as they know > the code base enough to fix bugs. > > Any questions? Comments? Any potential issue with the date? > > Best, > -berk > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Tue Jul 12 14:39:14 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 12 Jul 2016 14:39:14 -0400 Subject: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) In-Reply-To: References: Message-ID: Kevin, I suspect it's a driver issue. For some reason depth peeling is not working (or ParaView is determining cannot work) on your Windows machine.Can you try using ParaView 5.1.0? The depth peeling code was rewritten in 5.1.0 and I wonder if it fares any better. cc-ing Dave Lonie who wrote the new depth peeling code. Utkkarsh On Tue, Jul 12, 2016 at 8:14 AM, Hallock, Kevin wrote: > Hi everyone, > > I built a model in Paraview 5.0.0 (64-bit) on my Mac (El Capitan) and > several of the surfaces have 0.5 opacity, which looks fine on my Mac. When I > open the same model in Paraview 5.0.0 (64-bit) on a Windows 7 computer the > transparency no longer behaves well. Transparent surfaces disappear at > certain angles, the back face appears less transparent, etc. > > Any suggestions? > > Thanks, > > Kevin > > PS ? I originally posted this with screen shots of the problem, but the > original message was held for several days of review so I cancelled the > posting. > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Tue Jul 12 16:27:17 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 12 Jul 2016 16:27:17 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: <8dc4fc3e4333438a9da987d6d94ece71@ES01AMSNLNT.srn.sandia.gov> References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> <8dc4fc3e4333438a9da987d6d94ece71@ES01AMSNLNT.srn.sandia.gov> Message-ID: While the technical arguments are indeed sound, we tend to get asked about this quite periodically. What do folks think about using AA by default for builtin or client-side render and not when compositing? This way, 2D charts, for example, will always have AA turned on -- just a nice little perk. Utkarsh On Tue, Jul 5, 2016 at 10:08 PM, Scott, W Alan wrote: > OK, much better pushback. I would say AA (either the hack mentioned below > or real) probably isn?t worth a non-trivial software change at this point. > We should keep it on the table for future work. > > > > Alan > > > > From: Moreland, Kenneth > Sent: Friday, July 01, 2016 7:58 PM > > > To: Scott, W Alan ; David E DeMarle > > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > OK, let me rephrase my pushback. There are several technical hurtles to > implement this feature. We know how to achive this effect, but it requires a > non-trivial change to the rendering system that will take significant > development cycles, add complexity to the rendering system, and potentially > destabilize several features relying on the rendering. Plus, this is all > happening in the middle of a push for other (more important) rendering > features (OpenGL2, OpenSWR, Ospray, IndeX). > > > > We turned off antialiasing in ParaView years ago because it caused way more > problems than it was worth. The question is, do you really think it is > important enough now to have a software push for it? > > > > -Ken > > > > From: Walter Scott > Date: Friday, July 1, 2016 at 12:12 PM > To: Kenneth Moreland , David E DeMarle > > Cc: "paraview-developers at paraview.org" > Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > Makes sense. But? > > > > 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for better > images when lines are visible. Default off. You want better images, it > will be slower (when lines are visible). > > 2) We do it (when rendering off screen) all the time when making movies > for the power wall. I don?t see this as an issue? > > 3) Have the line widths automatically written 2X requested width. > Thus, when it shrinks by 2, you get normal, poor man?s AA lines. > > > > Alan > > > > From: Moreland, Kenneth > Sent: Friday, July 01, 2016 9:20 AM > To: Scott, W Alan ; David E DeMarle > > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > Reason 1: Increasing the resolution 2X increases the compositing overhead by > up to 4. Increasing the resolution 4X increases the compositing time by up > to 16. It can be a noticeable difference when rendering interactively. > > > > Reason 2: There can be technical difficulties in rendering images that > large. You are likely to have a rendering context of the original > resolution. To render such large images with images/movies, it renders image > tiles and stitches them together. This adds further overhead and > complication in rendering. > > > > Reason 3: Line width is measured in pixels. Changing the resolution of the > image in this way will change the perceived line width. > > > > -Ken > > > > From: Paraview-developers on > behalf of Walter Scott > Date: Thursday, June 30, 2016 at 7:48 PM > To: David E DeMarle > Cc: "paraview-developers at paraview.org" > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > OK, why can?t we do that? Have a mode that internally runs 2X or 4X > resolution, does the compositing, and then shrinks back to what the user > wants? Only turn it on when 3d lines are in the image? > > > > > > > > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Thursday, June 30, 2016 7:46 PM > To: Scott, W Alan > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA > > > > > Antialiasing confuses depth compositing. > > Better to save out images/movies at 4x resolution and resample outside of > paraview. > > > On Thursday, June 30, 2016, Scott, W Alan wrote: > > Why can?t we turn anti alias lines on? I am doing a feature edges, and it > looks horrible. > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > > > -- > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From dave.demarle at kitware.com Tue Jul 12 16:32:00 2016 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 12 Jul 2016 16:32:00 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> <8dc4fc3e4333438a9da987d6d94ece71@ES01AMSNLNT.srn.sandia.gov> Message-ID: As long as it doesn't affect selection, sounds pretty snazzy. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Jul 12, 2016 at 4:27 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > While the technical arguments are indeed sound, we tend to get asked > about this quite periodically. What do folks think about using AA by > default for builtin or client-side render and not when compositing? > This way, 2D charts, for example, will always have AA turned on -- > just a nice little perk. > > Utkarsh > > On Tue, Jul 5, 2016 at 10:08 PM, Scott, W Alan wrote: > > OK, much better pushback. I would say AA (either the hack mentioned > below > > or real) probably isn?t worth a non-trivial software change at this > point. > > We should keep it on the table for future work. > > > > > > > > Alan > > > > > > > > From: Moreland, Kenneth > > Sent: Friday, July 01, 2016 7:58 PM > > > > > > To: Scott, W Alan ; David E DeMarle > > > > Cc: paraview-developers at paraview.org > > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > > > > > OK, let me rephrase my pushback. There are several technical hurtles to > > implement this feature. We know how to achive this effect, but it > requires a > > non-trivial change to the rendering system that will take significant > > development cycles, add complexity to the rendering system, and > potentially > > destabilize several features relying on the rendering. Plus, this is all > > happening in the middle of a push for other (more important) rendering > > features (OpenGL2, OpenSWR, Ospray, IndeX). > > > > > > > > We turned off antialiasing in ParaView years ago because it caused way > more > > problems than it was worth. The question is, do you really think it is > > important enough now to have a software push for it? > > > > > > > > -Ken > > > > > > > > From: Walter Scott > > Date: Friday, July 1, 2016 at 12:12 PM > > To: Kenneth Moreland , David E DeMarle > > > > Cc: "paraview-developers at paraview.org" > > > Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > > > > > Makes sense. But? > > > > > > > > 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for > better > > images when lines are visible. Default off. You want better images, it > > will be slower (when lines are visible). > > > > 2) We do it (when rendering off screen) all the time when making > movies > > for the power wall. I don?t see this as an issue? > > > > 3) Have the line widths automatically written 2X requested width. > > Thus, when it shrinks by 2, you get normal, poor man?s AA lines. > > > > > > > > Alan > > > > > > > > From: Moreland, Kenneth > > Sent: Friday, July 01, 2016 9:20 AM > > To: Scott, W Alan ; David E DeMarle > > > > Cc: paraview-developers at paraview.org > > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > > > > > Reason 1: Increasing the resolution 2X increases the compositing > overhead by > > up to 4. Increasing the resolution 4X increases the compositing time by > up > > to 16. It can be a noticeable difference when rendering interactively. > > > > > > > > Reason 2: There can be technical difficulties in rendering images that > > large. You are likely to have a rendering context of the original > > resolution. To render such large images with images/movies, it renders > image > > tiles and stitches them together. This adds further overhead and > > complication in rendering. > > > > > > > > Reason 3: Line width is measured in pixels. Changing the resolution of > the > > image in this way will change the perceived line width. > > > > > > > > -Ken > > > > > > > > From: Paraview-developers on > > behalf of Walter Scott > > Date: Thursday, June 30, 2016 at 7:48 PM > > To: David E DeMarle > > Cc: "paraview-developers at paraview.org" > > > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > > > > > OK, why can?t we do that? Have a mode that internally runs 2X or 4X > > resolution, does the compositing, and then shrinks back to what the user > > wants? Only turn it on when 3d lines are in the image? > > > > > > > > > > > > > > > > From: David E DeMarle [mailto:dave.demarle at kitware.com] > > Sent: Thursday, June 30, 2016 7:46 PM > > To: Scott, W Alan > > Cc: paraview-developers at paraview.org > > Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA > > > > > > > > > > Antialiasing confuses depth compositing. > > > > Better to save out images/movies at 4x resolution and resample outside of > > paraview. > > > > > > On Thursday, June 30, 2016, Scott, W Alan wrote: > > > > Why can?t we turn anti alias lines on? I am doing a feature edges, and > it > > looks horrible. > > > > > > > > Thanks, > > > > > > > > Alan > > > > > > > > -------------------------------------------------------- > > > > W. Alan Scott > > > > ParaView Support Manager > > > > > > > > SAIC > > > > Sandia National Laboratories, MS 0822 > > > > Org 9326 - Building 880 A1-K > > > > (505) 284-0932 FAX (505) 284-5619 > > > > --------------------------------------------------------- > > > > > > > > > > > > -- > > David E DeMarle > > Kitware, Inc. > > R&D Engineer > > 21 Corporate Drive > > Clifton Park, NY 12065-8662 > > Phone: 518-881-4909 > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Tue Jul 12 17:09:52 2016 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Tue, 12 Jul 2016 21:09:52 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> <8dc4fc3e4333438a9da987d6d94ece71@ES01AMSNLNT.srn.sandia.gov> Message-ID: <2277fecf06c544d4a6abe0f7924509d1@ES08AMSNLNT.srn.sandia.gov> I would say proceed with caution. Using antialiasing only on client side used to be our solution, but it turns out antialiasing screws up other stuff, too, and we eventually threw up our hands and got rid of it. I definitely remember picking as an issue that cropped up. I think there were others, but I don?t remember them all. I think transparency (depth peeling) was one. -Ken From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Tuesday, July 12, 2016 2:32 PM To: Utkarsh Ayachit Cc: Scott, W Alan ; Moreland, Kenneth ; paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA As long as it doesn't affect selection, sounds pretty snazzy. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Jul 12, 2016 at 4:27 PM, Utkarsh Ayachit > wrote: While the technical arguments are indeed sound, we tend to get asked about this quite periodically. What do folks think about using AA by default for builtin or client-side render and not when compositing? This way, 2D charts, for example, will always have AA turned on -- just a nice little perk. Utkarsh On Tue, Jul 5, 2016 at 10:08 PM, Scott, W Alan > wrote: > OK, much better pushback. I would say AA (either the hack mentioned below > or real) probably isn?t worth a non-trivial software change at this point. > We should keep it on the table for future work. > > > > Alan > > > > From: Moreland, Kenneth > Sent: Friday, July 01, 2016 7:58 PM > > > To: Scott, W Alan >; David E DeMarle > > > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > OK, let me rephrase my pushback. There are several technical hurtles to > implement this feature. We know how to achive this effect, but it requires a > non-trivial change to the rendering system that will take significant > development cycles, add complexity to the rendering system, and potentially > destabilize several features relying on the rendering. Plus, this is all > happening in the middle of a push for other (more important) rendering > features (OpenGL2, OpenSWR, Ospray, IndeX). > > > > We turned off antialiasing in ParaView years ago because it caused way more > problems than it was worth. The question is, do you really think it is > important enough now to have a software push for it? > > > > -Ken > > > > From: Walter Scott > > Date: Friday, July 1, 2016 at 12:12 PM > To: Kenneth Moreland >, David E DeMarle > > > Cc: "paraview-developers at paraview.org" > > Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > Makes sense. But? > > > > 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for better > images when lines are visible. Default off. You want better images, it > will be slower (when lines are visible). > > 2) We do it (when rendering off screen) all the time when making movies > for the power wall. I don?t see this as an issue? > > 3) Have the line widths automatically written 2X requested width. > Thus, when it shrinks by 2, you get normal, poor man?s AA lines. > > > > Alan > > > > From: Moreland, Kenneth > Sent: Friday, July 01, 2016 9:20 AM > To: Scott, W Alan >; David E DeMarle > > > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > Reason 1: Increasing the resolution 2X increases the compositing overhead by > up to 4. Increasing the resolution 4X increases the compositing time by up > to 16. It can be a noticeable difference when rendering interactively. > > > > Reason 2: There can be technical difficulties in rendering images that > large. You are likely to have a rendering context of the original > resolution. To render such large images with images/movies, it renders image > tiles and stitches them together. This adds further overhead and > complication in rendering. > > > > Reason 3: Line width is measured in pixels. Changing the resolution of the > image in this way will change the perceived line width. > > > > -Ken > > > > From: Paraview-developers > on > behalf of Walter Scott > > Date: Thursday, June 30, 2016 at 7:48 PM > To: David E DeMarle > > Cc: "paraview-developers at paraview.org" > > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > OK, why can?t we do that? Have a mode that internally runs 2X or 4X > resolution, does the compositing, and then shrinks back to what the user > wants? Only turn it on when 3d lines are in the image? > > > > > > > > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Thursday, June 30, 2016 7:46 PM > To: Scott, W Alan > > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA > > > > > Antialiasing confuses depth compositing. > > Better to save out images/movies at 4x resolution and resample outside of > paraview. > > > On Thursday, June 30, 2016, Scott, W Alan > wrote: > > Why can?t we turn anti alias lines on? I am doing a feature edges, and it > looks horrible. > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > > > -- > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Jul 12 17:24:04 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 12 Jul 2016 21:24:04 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: <2277fecf06c544d4a6abe0f7924509d1@ES08AMSNLNT.srn.sandia.gov> References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> <8dc4fc3e4333438a9da987d6d94ece71@ES01AMSNLNT.srn.sandia.gov> <2277fecf06c544d4a6abe0f7924509d1@ES08AMSNLNT.srn.sandia.gov> Message-ID: <3a67ecff5c5c4871aceb3c00cc0452f5@ES01AMSNLNT.srn.sandia.gov> Don?t do AA if you have transparency on? Otherwise, if you are local server, do so? From: Moreland, Kenneth Sent: Tuesday, July 12, 2016 3:10 PM To: David E DeMarle ; Utkarsh Ayachit Cc: Scott, W Alan ; paraview-developers at paraview.org Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA I would say proceed with caution. Using antialiasing only on client side used to be our solution, but it turns out antialiasing screws up other stuff, too, and we eventually threw up our hands and got rid of it. I definitely remember picking as an issue that cropped up. I think there were others, but I don?t remember them all. I think transparency (depth peeling) was one. -Ken From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Tuesday, July 12, 2016 2:32 PM To: Utkarsh Ayachit > Cc: Scott, W Alan >; Moreland, Kenneth >; paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA As long as it doesn't affect selection, sounds pretty snazzy. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Jul 12, 2016 at 4:27 PM, Utkarsh Ayachit > wrote: While the technical arguments are indeed sound, we tend to get asked about this quite periodically. What do folks think about using AA by default for builtin or client-side render and not when compositing? This way, 2D charts, for example, will always have AA turned on -- just a nice little perk. Utkarsh On Tue, Jul 5, 2016 at 10:08 PM, Scott, W Alan > wrote: > OK, much better pushback. I would say AA (either the hack mentioned below > or real) probably isn?t worth a non-trivial software change at this point. > We should keep it on the table for future work. > > > > Alan > > > > From: Moreland, Kenneth > Sent: Friday, July 01, 2016 7:58 PM > > > To: Scott, W Alan >; David E DeMarle > > > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > OK, let me rephrase my pushback. There are several technical hurtles to > implement this feature. We know how to achive this effect, but it requires a > non-trivial change to the rendering system that will take significant > development cycles, add complexity to the rendering system, and potentially > destabilize several features relying on the rendering. Plus, this is all > happening in the middle of a push for other (more important) rendering > features (OpenGL2, OpenSWR, Ospray, IndeX). > > > > We turned off antialiasing in ParaView years ago because it caused way more > problems than it was worth. The question is, do you really think it is > important enough now to have a software push for it? > > > > -Ken > > > > From: Walter Scott > > Date: Friday, July 1, 2016 at 12:12 PM > To: Kenneth Moreland >, David E DeMarle > > > Cc: "paraview-developers at paraview.org" > > Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > Makes sense. But? > > > > 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for better > images when lines are visible. Default off. You want better images, it > will be slower (when lines are visible). > > 2) We do it (when rendering off screen) all the time when making movies > for the power wall. I don?t see this as an issue? > > 3) Have the line widths automatically written 2X requested width. > Thus, when it shrinks by 2, you get normal, poor man?s AA lines. > > > > Alan > > > > From: Moreland, Kenneth > Sent: Friday, July 01, 2016 9:20 AM > To: Scott, W Alan >; David E DeMarle > > > Cc: paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > Reason 1: Increasing the resolution 2X increases the compositing overhead by > up to 4. Increasing the resolution 4X increases the compositing time by up > to 16. It can be a noticeable difference when rendering interactively. > > > > Reason 2: There can be technical difficulties in rendering images that > large. You are likely to have a rendering context of the original > resolution. To render such large images with images/movies, it renders image > tiles and stitches them together. This adds further overhead and > complication in rendering. > > > > Reason 3: Line width is measured in pixels. Changing the resolution of the > image in this way will change the perceived line width. > > > > -Ken > > > > From: Paraview-developers > on > behalf of Walter Scott > > Date: Thursday, June 30, 2016 at 7:48 PM > To: David E DeMarle > > Cc: "paraview-developers at paraview.org" > > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > OK, why can?t we do that? Have a mode that internally runs 2X or 4X > resolution, does the compositing, and then shrinks back to what the user > wants? Only turn it on when 3d lines are in the image? > > > > > > > > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Thursday, June 30, 2016 7:46 PM > To: Scott, W Alan > > Cc: paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA > > > > > Antialiasing confuses depth compositing. > > Better to save out images/movies at 4x resolution and resample outside of > paraview. > > > On Thursday, June 30, 2016, Scott, W Alan > wrote: > > Why can?t we turn anti alias lines on? I am doing a feature edges, and it > looks horrible. > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > > > -- > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Jul 12 19:46:20 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 12 Jul 2016 19:46:20 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Remind me - AA In-Reply-To: <3a67ecff5c5c4871aceb3c00cc0452f5@ES01AMSNLNT.srn.sandia.gov> References: <8f89bba739c246cd961af090450dd61b@ES01AMSNLNT.srn.sandia.gov> <5E8FC865-A8C6-4F46-9E55-61DEA32F7550@sandia.gov> <38DED064-31FC-4D3B-AA52-DF4960F7F177@sandia.gov> <8dc4fc3e4333438a9da987d6d94ece71@ES01AMSNLNT.srn.sandia.gov> <2277fecf06c544d4a6abe0f7924509d1@ES08AMSNLNT.srn.sandia.gov> <3a67ecff5c5c4871aceb3c00cc0452f5@ES01AMSNLNT.srn.sandia.gov> Message-ID: I suppose some testing is in order. I'll plan to do some testing to see how things are faring and report back. Utkarsh On Tue, Jul 12, 2016 at 5:24 PM, Scott, W Alan wrote: > Don?t do AA if you have transparency on? Otherwise, if you are local > server, do so? > > > > From: Moreland, Kenneth > Sent: Tuesday, July 12, 2016 3:10 PM > To: David E DeMarle ; Utkarsh Ayachit > > Cc: Scott, W Alan ; paraview-developers at paraview.org > > > Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > I would say proceed with caution. Using antialiasing only on client side > used to be our solution, but it turns out antialiasing screws up other > stuff, too, and we eventually threw up our hands and got rid of it. I > definitely remember picking as an issue that cropped up. I think there were > others, but I don?t remember them all. I think transparency (depth peeling) > was one. > > > > -Ken > > > > From: David E DeMarle [mailto:dave.demarle at kitware.com] > Sent: Tuesday, July 12, 2016 2:32 PM > To: Utkarsh Ayachit > Cc: Scott, W Alan ; Moreland, Kenneth > ; paraview-developers at paraview.org > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA > > > > As long as it doesn't affect selection, sounds pretty snazzy. > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > > On Tue, Jul 12, 2016 at 4:27 PM, Utkarsh Ayachit > wrote: > > While the technical arguments are indeed sound, we tend to get asked > about this quite periodically. What do folks think about using AA by > default for builtin or client-side render and not when compositing? > This way, 2D charts, for example, will always have AA turned on -- > just a nice little perk. > > Utkarsh > > > On Tue, Jul 5, 2016 at 10:08 PM, Scott, W Alan wrote: >> OK, much better pushback. I would say AA (either the hack mentioned below >> or real) probably isn?t worth a non-trivial software change at this point. >> We should keep it on the table for future work. >> >> >> >> Alan >> >> >> >> From: Moreland, Kenneth >> Sent: Friday, July 01, 2016 7:58 PM >> >> >> To: Scott, W Alan ; David E DeMarle >> >> Cc: paraview-developers at paraview.org >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA >> >> >> >> OK, let me rephrase my pushback. There are several technical hurtles to >> implement this feature. We know how to achive this effect, but it requires >> a >> non-trivial change to the rendering system that will take significant >> development cycles, add complexity to the rendering system, and >> potentially >> destabilize several features relying on the rendering. Plus, this is all >> happening in the middle of a push for other (more important) rendering >> features (OpenGL2, OpenSWR, Ospray, IndeX). >> >> >> >> We turned off antialiasing in ParaView years ago because it caused way >> more >> problems than it was worth. The question is, do you really think it is >> important enough now to have a software push for it? >> >> >> >> -Ken >> >> >> >> From: Walter Scott >> Date: Friday, July 1, 2016 at 12:12 PM >> To: Kenneth Moreland , David E DeMarle >> >> Cc: "paraview-developers at paraview.org" >> Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA >> >> >> >> Makes sense. But? >> >> >> >> 1) Make it 2X ? i.e., 4 times the pixels, if the user asks for better >> images when lines are visible. Default off. You want better images, it >> will be slower (when lines are visible). >> >> 2) We do it (when rendering off screen) all the time when making >> movies >> for the power wall. I don?t see this as an issue? >> >> 3) Have the line widths automatically written 2X requested width. >> Thus, when it shrinks by 2, you get normal, poor man?s AA lines. >> >> >> >> Alan >> >> >> >> From: Moreland, Kenneth >> Sent: Friday, July 01, 2016 9:20 AM >> To: Scott, W Alan ; David E DeMarle >> >> Cc: paraview-developers at paraview.org >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA >> >> >> >> Reason 1: Increasing the resolution 2X increases the compositing overhead >> by >> up to 4. Increasing the resolution 4X increases the compositing time by up >> to 16. It can be a noticeable difference when rendering interactively. >> >> >> >> Reason 2: There can be technical difficulties in rendering images that >> large. You are likely to have a rendering context of the original >> resolution. To render such large images with images/movies, it renders >> image >> tiles and stitches them together. This adds further overhead and >> complication in rendering. >> >> >> >> Reason 3: Line width is measured in pixels. Changing the resolution of the >> image in this way will change the perceived line width. >> >> >> >> -Ken >> >> >> >> From: Paraview-developers on >> behalf of Walter Scott >> Date: Thursday, June 30, 2016 at 7:48 PM >> To: David E DeMarle >> Cc: "paraview-developers at paraview.org" >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA >> >> >> >> OK, why can?t we do that? Have a mode that internally runs 2X or 4X >> resolution, does the compositing, and then shrinks back to what the user >> wants? Only turn it on when 3d lines are in the image? >> >> >> >> >> >> >> >> From: David E DeMarle [mailto:dave.demarle at kitware.com] >> Sent: Thursday, June 30, 2016 7:46 PM >> To: Scott, W Alan >> Cc: paraview-developers at paraview.org >> Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA >> >> >> >> >> Antialiasing confuses depth compositing. >> >> Better to save out images/movies at 4x resolution and resample outside of >> paraview. >> >> >> On Thursday, June 30, 2016, Scott, W Alan wrote: >> >> Why can?t we turn anti alias lines on? I am doing a feature edges, and it >> looks horrible. >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0822 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> --------------------------------------------------------- >> >> >> >> >> >> -- >> David E DeMarle >> Kitware, Inc. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> > >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > From sur.chiranjib at gmail.com Wed Jul 13 01:57:34 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Wed, 13 Jul 2016 11:27:34 +0530 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: Hi, Thanks for your messages the pointers. I still have some issues. Here is the attached code snippets which throws me error messages. I am bit clueless what I am missing here. Thanks, Chiranjib On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge Orlando < Orlando.RIVERA at mtu.de> wrote: > Hi, > > > Also , check if "setVariable" is in the public section of your class > > Orlando > > -----Urspr?ngliche Nachricht----- > Von: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] > Im Auftrag von Cory Quammen > Gesendet: Tuesday, 12. July 2016 15:37 > An: Chiranjib Sur > Cc: Paraview Developer Mailing list > Betreff: Re: [Paraview-developers] paraview PVSessionCore error > > Chiranjib, > > Usually this error means there is a mismatch between the XML used to > describe the VTK-side class. Check that your XML name for the member > function matches the C++, and that the member function setVariable() > takes only one value. > > Cory > > On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur > wrote: > > Hi, > > I am trying to implement a new filter in ParaView and I get the following > > error while executing. > > > > vtkPVSessionCore (0x162d180): Object type: MyObjectSource, could not find > > requested method: "setVariable" > > or the method was called with incorrect arguments. > > > > while processing > > Message 0 = Invoke > > Argument 0 = vtk_object_pointer {MyObjectSource(0x34b3870)} > > Argument 1 = string_value {setVariable} > > Argument 2 = float64_value {0.003} > > > > > > I searched the mailing list and it looks like a very similar bug has been > > reported > > http://www.paraview.org/Bug/view.php?id=15593 > > > > > > People have faced similar problem and here are the details > > http://public.kitware.com/pipermail/paraview/2016-March/036387.html > > > > Is there a solution of work-around? > > > > Chiranjib > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- > MTU Aero Engines AG > Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer > Martens, Michael Schreyoegg > Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus > Eberhardt > Sitz der Gesellschaft/Registered Office: Muenchen > Handelsregister/Commercial Register: Muenchen HRB 157206 > > Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder > rechtlich geschuetzte Informationen. > Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte > den Absender und loeschen Sie diese > E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder > Weiterleiten ist nicht gestattet. > > This e-mail and any attached documents are proprietary to MTU, > confidential or protected by law. > If you are not the intended recipient, please advise the sender and delete > this message and its attachments. > Any unauthorised storing, copying or distribution is prohibited. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: serverManagerTesting.tgz Type: application/x-gzip Size: 2160 bytes Desc: not available URL: From sur.chiranjib at gmail.com Wed Jul 13 02:43:44 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Wed, 13 Jul 2016 12:13:44 +0530 Subject: [Paraview-developers] PVSM state file reader In-Reply-To: References: Message-ID: HI Utkarsh, I am revisiting again this part now. Any clue about how to build the pqServerManagerModel from pqApplicationCore? I still have the seg fault problem. Thanks, Chiranjib On Thu, Jun 23, 2016 at 10:40 PM, Chiranjib Sur wrote: > Hi Utkarsh, > Still something I am missing, but I can't figure out what is it. > > Following is my intention: > > > 1. (From my C++ application) Load an external .pvsm file --> Scan through > all the objects in the pipeline (this part works in PV GUI extension). > > 2. instead of using the pqLoadStateReaction can I directly load the file > like this : > > std::string pvsm_file = "myOwn.pvsm"; > QString qstr = QString::fromStdString(pvsm_file); // converts > std:;string to QString > > pqApplicationCore* core = pqApplicationCore::instance(); > pqServer* server; > vtkSMStateLoader* loader; > core->loadState( pvsm_file.c_str(), server, loader); > > > If I do that, the program operated normally (no seg fault), but I can't > build the servermanager model using the pqApplicationcore, the program > give me a seg fault if I do > > pqServerManagerModel* sm = core->getServerManagerModel(); > > 3. I need this pqServerManagerModel to use it later for scanning through > the pipeline of objects as I see them in PV. > > Any help? > > Thanks, > Chiranjib > > On Mon, Jun 20, 2016 at 7:22 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> > The code compiles (all the necessary headers are taken care of) but I >> get a >> > seg fault during run time. >> >> Hard to say why. Debugger is really your friend. If you haven't >> already, I'd suggesting doing a debug build of ParaView and seeing >> what's going on. >> >> > Is there any place where I can see some examples on that. >> pqLoadStateReaction is the example of how to load a state. That's the >> code ParaView uses when you click "Load State" from the File menu. >> >> > I am familiar with step 2 by which I can scan the paraview pipeline and >> get >> > the information all object proxies. At this stage I am not able to >> figure >> > out how to link between step 1 and step 2. >> >> Just step through the code in pqLoadStateReaction. >> >> pqLoadStateReaction::loadState() --> pqApplicationCore::loadState() >> --> vtkSMSessionProxyManager::LoadXMLState() --> vtkSMStateLoader. >> >> Utkarsh >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Jul 13 07:33:03 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Jul 2016 07:33:03 -0400 Subject: [Paraview-developers] PVSM state file reader In-Reply-To: References: Message-ID: Sorry, I have no clue. State loading is oft used component and independent of how pqServerManagerModel is created. I suspect your initialization is messed up or something else is going on here. Maybe a debugger will shead light on why the segfault is happening Utkarsh On Wed, Jul 13, 2016 at 2:43 AM, Chiranjib Sur wrote: > HI Utkarsh, > I am revisiting again this part now. > Any clue about how to build the pqServerManagerModel from pqApplicationCore? > I still have the seg fault problem. > > Thanks, > Chiranjib > > On Thu, Jun 23, 2016 at 10:40 PM, Chiranjib Sur > wrote: >> >> Hi Utkarsh, >> Still something I am missing, but I can't figure out what is it. >> >> Following is my intention: >> >> >> 1. (From my C++ application) Load an external .pvsm file --> Scan through >> all the objects in the pipeline (this part works in PV GUI extension). >> >> 2. instead of using the pqLoadStateReaction can I directly load the file >> like this : >> >> std::string pvsm_file = "myOwn.pvsm"; >> QString qstr = QString::fromStdString(pvsm_file); // converts >> std:;string to QString >> >> pqApplicationCore* core = pqApplicationCore::instance(); >> pqServer* server; >> vtkSMStateLoader* loader; >> core->loadState( pvsm_file.c_str(), server, loader); >> >> >> If I do that, the program operated normally (no seg fault), but I can't >> build the servermanager model using the pqApplicationcore, the program give >> me a seg fault if I do >> >> pqServerManagerModel* sm = core->getServerManagerModel(); >> >> 3. I need this pqServerManagerModel to use it later for scanning through >> the pipeline of objects as I see them in PV. >> >> Any help? >> >> Thanks, >> Chiranjib >> >> On Mon, Jun 20, 2016 at 7:22 PM, Utkarsh Ayachit >> wrote: >>> >>> > The code compiles (all the necessary headers are taken care of) but I >>> > get a >>> > seg fault during run time. >>> >>> Hard to say why. Debugger is really your friend. If you haven't >>> already, I'd suggesting doing a debug build of ParaView and seeing >>> what's going on. >>> >>> > Is there any place where I can see some examples on that. >>> pqLoadStateReaction is the example of how to load a state. That's the >>> code ParaView uses when you click "Load State" from the File menu. >>> >>> > I am familiar with step 2 by which I can scan the paraview pipeline and >>> > get >>> > the information all object proxies. At this stage I am not able to >>> > figure >>> > out how to link between step 1 and step 2. >>> >>> Just step through the code in pqLoadStateReaction. >>> >>> pqLoadStateReaction::loadState() --> pqApplicationCore::loadState() >>> --> vtkSMSessionProxyManager::LoadXMLState() --> vtkSMStateLoader. >>> >>> Utkarsh >> >> > From Kevin.Hallock at pfizer.com Wed Jul 13 07:37:40 2016 From: Kevin.Hallock at pfizer.com (Hallock, Kevin) Date: Wed, 13 Jul 2016 11:37:40 +0000 Subject: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) In-Reply-To: References: , Message-ID: <2BC7D4E20F304247B667633FFFAF48091BE0AA@NDHAMREXDH01.amer.pfizer.com> Hi, I installed 5.1.0 and it crashes when I try to open one of the files that we built in 5.0.0; here is the crash error: Problem signature: Problem Event Name: APPCRASH Application Name: paraview.exe Application Version: 0.0.0.0 Application Timestamp: 5765d395 Fault Module Name: StackHash_b4ee Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 0000000002dbfec2 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: b4ee Additional Information 2: b4ee5de6a2322745523997a782b35692 Additional Information 3: 277e Additional Information 4: 277e19c30fbd5f6bb531ec9e027c37c3 Are there additional troubleshooting steps you would like for me to try? Thanks, Kevin ________________________________________ From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Sent: Tuesday, July 12, 2016 2:39 PM To: Hallock, Kevin; David Lonie Cc: Paraview-developers Subject: Re: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) Kevin, I suspect it's a driver issue. For some reason depth peeling is not working (or ParaView is determining cannot work) on your Windows machine.Can you try using ParaView 5.1.0? The depth peeling code was rewritten in 5.1.0 and I wonder if it fares any better. cc-ing Dave Lonie who wrote the new depth peeling code. Utkkarsh On Tue, Jul 12, 2016 at 8:14 AM, Hallock, Kevin wrote: > Hi everyone, > > I built a model in Paraview 5.0.0 (64-bit) on my Mac (El Capitan) and > several of the surfaces have 0.5 opacity, which looks fine on my Mac. When I > open the same model in Paraview 5.0.0 (64-bit) on a Windows 7 computer the > transparency no longer behaves well. Transparent surfaces disappear at > certain angles, the back face appears less transparent, etc. > > Any suggestions? > > Thanks, > > Kevin > > PS ? I originally posted this with screen shots of the problem, but the > original message was held for several days of review so I cancelled the > posting. > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Wed Jul 13 09:34:22 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Jul 2016 09:34:22 -0400 Subject: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) In-Reply-To: <2BC7D4E20F304247B667633FFFAF48091BE0AA@NDHAMREXDH01.amer.pfizer.com> References: <2BC7D4E20F304247B667633FFFAF48091BE0AA@NDHAMREXDH01.amer.pfizer.com> Message-ID: Could you share the file? Any other info to reproduce this issue? This was on Windows still? On Wed, Jul 13, 2016 at 7:37 AM, Hallock, Kevin wrote: > Hi, > > I installed 5.1.0 and it crashes when I try to open one of the files that we built in 5.0.0; here is the crash error: > > Problem signature: > Problem Event Name: APPCRASH > Application Name: paraview.exe > Application Version: 0.0.0.0 > Application Timestamp: 5765d395 > Fault Module Name: StackHash_b4ee > Fault Module Version: 0.0.0.0 > Fault Module Timestamp: 00000000 > Exception Code: c0000005 > Exception Offset: 0000000002dbfec2 > OS Version: 6.1.7601.2.1.0.256.48 > Locale ID: 1033 > Additional Information 1: b4ee > Additional Information 2: b4ee5de6a2322745523997a782b35692 > Additional Information 3: 277e > Additional Information 4: 277e19c30fbd5f6bb531ec9e027c37c3 > > Are there additional troubleshooting steps you would like for me to try? > > Thanks, > > Kevin > > ________________________________________ > From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] > Sent: Tuesday, July 12, 2016 2:39 PM > To: Hallock, Kevin; David Lonie > Cc: Paraview-developers > Subject: Re: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) > > Kevin, > > I suspect it's a driver issue. For some reason depth peeling is not > working (or ParaView is determining cannot work) on your Windows > machine.Can you try using ParaView 5.1.0? The depth peeling code was > rewritten in 5.1.0 and I wonder if it fares any better. > > cc-ing Dave Lonie who wrote the new depth peeling code. > > Utkkarsh > > On Tue, Jul 12, 2016 at 8:14 AM, Hallock, Kevin > wrote: >> Hi everyone, >> >> I built a model in Paraview 5.0.0 (64-bit) on my Mac (El Capitan) and >> several of the surfaces have 0.5 opacity, which looks fine on my Mac. When I >> open the same model in Paraview 5.0.0 (64-bit) on a Windows 7 computer the >> transparency no longer behaves well. Transparent surfaces disappear at >> certain angles, the back face appears less transparent, etc. >> >> Any suggestions? >> >> Thanks, >> >> Kevin >> >> PS ? I originally posted this with screen shots of the problem, but the >> original message was held for several days of review so I cancelled the >> posting. >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> From wascott at sandia.gov Wed Jul 13 13:44:54 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 13 Jul 2016 17:44:54 +0000 Subject: [Paraview-developers] Search blog Message-ID: <9e62225e869545608fa304a2789d4291@ES01AMSNLNT.srn.sandia.gov> Can you search the ParaView blog? I am probably being blind, but couldn't see where to do it. Specifically, I am trying to figure out how to put special characters into sources/ text or whatever other solution allows special characters on the screen. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Jul 13 14:04:39 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 13 Jul 2016 14:04:39 -0400 Subject: [Paraview-developers] Search blog In-Reply-To: <9e62225e869545608fa304a2789d4291@ES01AMSNLNT.srn.sandia.gov> References: <9e62225e869545608fa304a2789d4291@ES01AMSNLNT.srn.sandia.gov> Message-ID: Alan, At the far right of the top blue bar on the blog, there is a magnifying glass. Hover your mouse over that, and you will see a search text box come up. Cory On Wed, Jul 13, 2016 at 1:44 PM, Scott, W Alan wrote: > Can you search the ParaView blog? I am probably being blind, but couldn?t > see where to do it. > > > > Specifically, I am trying to figure out how to put special characters into > sources/ text or whatever other solution allows special characters on the > screen. > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. From david.lonie at kitware.com Wed Jul 13 14:12:44 2016 From: david.lonie at kitware.com (David Lonie) Date: Wed, 13 Jul 2016 14:12:44 -0400 Subject: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) In-Reply-To: References: <2BC7D4E20F304247B667633FFFAF48091BE0AA@NDHAMREXDH01.amer.pfizer.com> Message-ID: It does sound like a driver issue to me as well, since we use the same depth peeling code on both platforms. While Utkarsh is looking at the file opening issue, can you try another test in ParaView 5.1.0? Something simple, like a sphere source with opacity < 1. I'm curious if the new implementation hits the same problem. Thanks, Dave On Wed, Jul 13, 2016 at 9:34 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Could you share the file? Any other info to reproduce this issue? This > was on Windows still? > > On Wed, Jul 13, 2016 at 7:37 AM, Hallock, Kevin > wrote: > > Hi, > > > > I installed 5.1.0 and it crashes when I try to open one of the files > that we built in 5.0.0; here is the crash error: > > > > Problem signature: > > Problem Event Name: APPCRASH > > Application Name: paraview.exe > > Application Version: 0.0.0.0 > > Application Timestamp: 5765d395 > > Fault Module Name: StackHash_b4ee > > Fault Module Version: 0.0.0.0 > > Fault Module Timestamp: 00000000 > > Exception Code: c0000005 > > Exception Offset: 0000000002dbfec2 > > OS Version: 6.1.7601.2.1.0.256.48 > > Locale ID: 1033 > > Additional Information 1: b4ee > > Additional Information 2: b4ee5de6a2322745523997a782b35692 > > Additional Information 3: 277e > > Additional Information 4: 277e19c30fbd5f6bb531ec9e027c37c3 > > > > Are there additional troubleshooting steps you would like for me to try? > > > > Thanks, > > > > Kevin > > > > ________________________________________ > > From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] > > Sent: Tuesday, July 12, 2016 2:39 PM > > To: Hallock, Kevin; David Lonie > > Cc: Paraview-developers > > Subject: Re: [Paraview-developers] Windows 7 transparency appears too > transparent (second posting) > > > > Kevin, > > > > I suspect it's a driver issue. For some reason depth peeling is not > > working (or ParaView is determining cannot work) on your Windows > > machine.Can you try using ParaView 5.1.0? The depth peeling code was > > rewritten in 5.1.0 and I wonder if it fares any better. > > > > cc-ing Dave Lonie who wrote the new depth peeling code. > > > > Utkkarsh > > > > On Tue, Jul 12, 2016 at 8:14 AM, Hallock, Kevin > > wrote: > >> Hi everyone, > >> > >> I built a model in Paraview 5.0.0 (64-bit) on my Mac (El Capitan) and > >> several of the surfaces have 0.5 opacity, which looks fine on my Mac. > When I > >> open the same model in Paraview 5.0.0 (64-bit) on a Windows 7 computer > the > >> transparency no longer behaves well. Transparent surfaces disappear at > >> certain angles, the back face appears less transparent, etc. > >> > >> Any suggestions? > >> > >> Thanks, > >> > >> Kevin > >> > >> PS ? I originally posted this with screen shots of the problem, but the > >> original message was held for several days of review so I cancelled the > >> posting. > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Search the list archives at: > >> http://markmail.org/search/?q=Paraview-developers > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview-developers > >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Hallock at pfizer.com Thu Jul 14 08:17:22 2016 From: Kevin.Hallock at pfizer.com (Hallock, Kevin) Date: Thu, 14 Jul 2016 12:17:22 +0000 Subject: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) In-Reply-To: References: <2BC7D4E20F304247B667633FFFAF48091BE0AA@NDHAMREXDH01.amer.pfizer.com> Message-ID: Spheres seem to render just fine. Is there a way to open a file without having it apply everything immediately? I have been able to open some individual parts of the original model so I would like to load each part of the whole model individually to see if I can identify what is causing the crash. Thanks, Kevin From: David Lonie > Date: Wednesday, July 13, 2016 at 2:12 PM To: Utkarsh Ayachit > Cc: Kevin Hallock >, Paraview-developers > Subject: Re: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) It does sound like a driver issue to me as well, since we use the same depth peeling code on both platforms. While Utkarsh is looking at the file opening issue, can you try another test in ParaView 5.1.0? Something simple, like a sphere source with opacity < 1. I'm curious if the new implementation hits the same problem. Thanks, Dave On Wed, Jul 13, 2016 at 9:34 AM, Utkarsh Ayachit > wrote: Could you share the file? Any other info to reproduce this issue? This was on Windows still? On Wed, Jul 13, 2016 at 7:37 AM, Hallock, Kevin > wrote: > Hi, > > I installed 5.1.0 and it crashes when I try to open one of the files that we built in 5.0.0; here is the crash error: > > Problem signature: > Problem Event Name: APPCRASH > Application Name: paraview.exe > Application Version: 0.0.0.0 > Application Timestamp: 5765d395 > Fault Module Name: StackHash_b4ee > Fault Module Version: 0.0.0.0 > Fault Module Timestamp: 00000000 > Exception Code: c0000005 > Exception Offset: 0000000002dbfec2 > OS Version: 6.1.7601.2.1.0.256.48 > Locale ID: 1033 > Additional Information 1: b4ee > Additional Information 2: b4ee5de6a2322745523997a782b35692 > Additional Information 3: 277e > Additional Information 4: 277e19c30fbd5f6bb531ec9e027c37c3 > > Are there additional troubleshooting steps you would like for me to try? > > Thanks, > > Kevin > > ________________________________________ > From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] > Sent: Tuesday, July 12, 2016 2:39 PM > To: Hallock, Kevin; David Lonie > Cc: Paraview-developers > Subject: Re: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) > > Kevin, > > I suspect it's a driver issue. For some reason depth peeling is not > working (or ParaView is determining cannot work) on your Windows > machine.Can you try using ParaView 5.1.0? The depth peeling code was > rewritten in 5.1.0 and I wonder if it fares any better. > > cc-ing Dave Lonie who wrote the new depth peeling code. > > Utkkarsh > > On Tue, Jul 12, 2016 at 8:14 AM, Hallock, Kevin > > wrote: >> Hi everyone, >> >> I built a model in Paraview 5.0.0 (64-bit) on my Mac (El Capitan) and >> several of the surfaces have 0.5 opacity, which looks fine on my Mac. When I >> open the same model in Paraview 5.0.0 (64-bit) on a Windows 7 computer the >> transparency no longer behaves well. Transparent surfaces disappear at >> certain angles, the back face appears less transparent, etc. >> >> Any suggestions? >> >> Thanks, >> >> Kevin >> >> PS ? I originally posted this with screen shots of the problem, but the >> original message was held for several days of review so I cancelled the >> posting. >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Jul 14 10:07:34 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 14 Jul 2016 10:07:34 -0400 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: Chiranjib, It's not obvious or probably described anywhere, but the client/server code wrapping mechanism wraps member functions that have VTK objects as parameters *only* if those VTK objects have names that start with "vtk". If you prepend vtk to all your sph* classes, it should work. In fact, I tested that locally, and it solves the error you are seeing. HTH, Cory On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur wrote: > Hi, > Thanks for your messages the pointers. I still have some issues. Here is the > attached code snippets which throws me error messages. I am bit clueless > what I am missing here. > > Thanks, > Chiranjib > > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge Orlando > wrote: >> >> Hi, >> >> >> Also , check if "setVariable" is in the public section of your class >> >> Orlando >> >> -----Urspr?ngliche Nachricht----- >> Von: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] >> Im Auftrag von Cory Quammen >> Gesendet: Tuesday, 12. July 2016 15:37 >> An: Chiranjib Sur >> Cc: Paraview Developer Mailing list >> Betreff: Re: [Paraview-developers] paraview PVSessionCore error >> >> Chiranjib, >> >> Usually this error means there is a mismatch between the XML used to >> describe the VTK-side class. Check that your XML name for the member >> function matches the C++, and that the member function setVariable() >> takes only one value. >> >> Cory >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur >> wrote: >> > Hi, >> > I am trying to implement a new filter in ParaView and I get the >> > following >> > error while executing. >> > >> > vtkPVSessionCore (0x162d180): Object type: MyObjectSource, could not >> > find >> > requested method: "setVariable" >> > or the method was called with incorrect arguments. >> > >> > while processing >> > Message 0 = Invoke >> > Argument 0 = vtk_object_pointer {MyObjectSource(0x34b3870)} >> > Argument 1 = string_value {setVariable} >> > Argument 2 = float64_value {0.003} >> > >> > >> > I searched the mailing list and it looks like a very similar bug has >> > been >> > reported >> > http://www.paraview.org/Bug/view.php?id=15593 >> > >> > >> > People have faced similar problem and here are the details >> > http://public.kitware.com/pipermail/paraview/2016-March/036387.html >> > >> > Is there a solution of work-around? >> > >> > Chiranjib >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> -- >> MTU Aero Engines AG >> Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer >> Martens, Michael Schreyoegg >> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus >> Eberhardt >> Sitz der Gesellschaft/Registered Office: Muenchen >> Handelsregister/Commercial Register: Muenchen HRB 157206 >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder >> rechtlich geschuetzte Informationen. >> Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte >> den Absender und loeschen Sie diese >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder >> Weiterleiten ist nicht gestattet. >> >> This e-mail and any attached documents are proprietary to MTU, >> confidential or protected by law. >> If you are not the intended recipient, please advise the sender and delete >> this message and its attachments. >> Any unauthorised storing, copying or distribution is prohibited. > > -- Cory Quammen R&D Engineer Kitware, Inc. From david.lonie at kitware.com Thu Jul 14 13:12:09 2016 From: david.lonie at kitware.com (David Lonie) Date: Thu, 14 Jul 2016 13:12:09 -0400 Subject: [Paraview-developers] Windows 7 transparency appears too transparent (second posting) In-Reply-To: References: <2BC7D4E20F304247B667633FFFAF48091BE0AA@NDHAMREXDH01.amer.pfizer.com> Message-ID: On Thu, Jul 14, 2016 at 8:17 AM, Hallock, Kevin wrote: > Spheres seem to render just fine. Is there a way to open a file without > having it apply everything immediately? I have been able to open some > individual parts of the original model so I would like to load each part of > the whole model individually to see if I can identify what is causing the > crash. Disabling auto-apply should do the trick: http://www.paraview.org/Wiki/Beginning_GUI#Auto_apply It will still read metadata immediately, but the bulk of the data load will be delayed until Apply is clicked. Dave From sur.chiranjib at gmail.com Thu Jul 14 13:55:53 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Thu, 14 Jul 2016 23:25:53 +0530 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: Hi Cory, This is very interesting. I think only the base class sphObject needs to be appended by "vtk". I have observed this when I was playing with the vtkParametricFunction class. But unless you splet it out, i would not have been figure out what was wrong with my code. I wish these kind of information is stored in some wiki form somewhere, or posted in your vtk/paraview blog. This will be immensely helpful to the developer community! Thanks a lot, Chiranjib On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen wrote: > Chiranjib, > > It's not obvious or probably described anywhere, but the client/server > code wrapping mechanism wraps member functions that have VTK objects > as parameters *only* if those VTK objects have names that start with > "vtk". If you prepend vtk to all your sph* classes, it should work. In > fact, I tested that locally, and it solves the error you are seeing. > > HTH, > Cory > > On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur > wrote: > > Hi, > > Thanks for your messages the pointers. I still have some issues. Here is > the > > attached code snippets which throws me error messages. I am bit clueless > > what I am missing here. > > > > Thanks, > > Chiranjib > > > > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge Orlando > > wrote: > >> > >> Hi, > >> > >> > >> Also , check if "setVariable" is in the public section of your > class > >> > >> Orlando > >> > >> -----Urspr?ngliche Nachricht----- > >> Von: Paraview-developers [mailto: > paraview-developers-bounces at paraview.org] > >> Im Auftrag von Cory Quammen > >> Gesendet: Tuesday, 12. July 2016 15:37 > >> An: Chiranjib Sur > >> Cc: Paraview Developer Mailing list > >> Betreff: Re: [Paraview-developers] paraview PVSessionCore error > >> > >> Chiranjib, > >> > >> Usually this error means there is a mismatch between the XML used to > >> describe the VTK-side class. Check that your XML name for the member > >> function matches the C++, and that the member function setVariable() > >> takes only one value. > >> > >> Cory > >> > >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur > > >> wrote: > >> > Hi, > >> > I am trying to implement a new filter in ParaView and I get the > >> > following > >> > error while executing. > >> > > >> > vtkPVSessionCore (0x162d180): Object type: MyObjectSource, could not > >> > find > >> > requested method: "setVariable" > >> > or the method was called with incorrect arguments. > >> > > >> > while processing > >> > Message 0 = Invoke > >> > Argument 0 = vtk_object_pointer {MyObjectSource(0x34b3870)} > >> > Argument 1 = string_value {setVariable} > >> > Argument 2 = float64_value {0.003} > >> > > >> > > >> > I searched the mailing list and it looks like a very similar bug has > >> > been > >> > reported > >> > http://www.paraview.org/Bug/view.php?id=15593 > >> > > >> > > >> > People have faced similar problem and here are the details > >> > http://public.kitware.com/pipermail/paraview/2016-March/036387.html > >> > > >> > Is there a solution of work-around? > >> > > >> > Chiranjib > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Search the list archives at: > >> > http://markmail.org/search/?q=Paraview-developers > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > > >> > >> > >> > >> -- > >> Cory Quammen > >> R&D Engineer > >> Kitware, Inc. > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Search the list archives at: > >> http://markmail.org/search/?q=Paraview-developers > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview-developers > >> -- > >> MTU Aero Engines AG > >> Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. > Rainer > >> Martens, Michael Schreyoegg > >> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus > >> Eberhardt > >> Sitz der Gesellschaft/Registered Office: Muenchen > >> Handelsregister/Commercial Register: Muenchen HRB 157206 > >> > >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder > >> rechtlich geschuetzte Informationen. > >> Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte > >> den Absender und loeschen Sie diese > >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder > >> Weiterleiten ist nicht gestattet. > >> > >> This e-mail and any attached documents are proprietary to MTU, > >> confidential or protected by law. > >> If you are not the intended recipient, please advise the sender and > delete > >> this message and its attachments. > >> Any unauthorised storing, copying or distribution is prohibited. > > > > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Thu Jul 14 14:06:49 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Thu, 14 Jul 2016 23:36:49 +0530 Subject: [Paraview-developers] operation using background thread Message-ID: Hi, While writing a file reader extension for paraview, I am seeing that while PV is loading a large dataset, the GUI windows becomes non responsive. How can I send the "reading" operation on the background so that I can still use the GUI while the file is loading on the background? Thanks in advance, Chiranjib -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Jul 14 14:13:01 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 14 Jul 2016 14:13:01 -0400 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: > I wish these kind of information is stored in some wiki form somewhere, or > posted in your vtk/paraview blog. This will be immensely helpful to the > developer community! Indeed, though a ParaView developer's guide would likely be several hundred pages long, would no doubt miss an important piece of information someone needs, and would be out of date quite quickly. The ParaView code is itself the authoritative source of information, but I know full well - believe me - that it isn't always fast or easy to go that route. The good news is that you are now part of the developer community, so we have one more person to contribute this documentation! It would be great if you could update the ParaView plugins howto page on the wiki for other developers to benefit: http://www.paraview.org/Wiki/Plugin_HowTo Best, Cory > Thanks a lot, > Chiranjib > > > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen > wrote: >> >> Chiranjib, >> >> It's not obvious or probably described anywhere, but the client/server >> code wrapping mechanism wraps member functions that have VTK objects >> as parameters *only* if those VTK objects have names that start with >> "vtk". If you prepend vtk to all your sph* classes, it should work. In >> fact, I tested that locally, and it solves the error you are seeing. >> >> HTH, >> Cory >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur >> wrote: >> > Hi, >> > Thanks for your messages the pointers. I still have some issues. Here is >> > the >> > attached code snippets which throws me error messages. I am bit clueless >> > what I am missing here. >> > >> > Thanks, >> > Chiranjib >> > >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge Orlando >> > wrote: >> >> >> >> Hi, >> >> >> >> >> >> Also , check if "setVariable" is in the public section of your >> >> class >> >> >> >> Orlando >> >> >> >> -----Urspr?ngliche Nachricht----- >> >> Von: Paraview-developers >> >> [mailto:paraview-developers-bounces at paraview.org] >> >> Im Auftrag von Cory Quammen >> >> Gesendet: Tuesday, 12. July 2016 15:37 >> >> An: Chiranjib Sur >> >> Cc: Paraview Developer Mailing list >> >> Betreff: Re: [Paraview-developers] paraview PVSessionCore error >> >> >> >> Chiranjib, >> >> >> >> Usually this error means there is a mismatch between the XML used to >> >> describe the VTK-side class. Check that your XML name for the member >> >> function matches the C++, and that the member function setVariable() >> >> takes only one value. >> >> >> >> Cory >> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur >> >> >> >> wrote: >> >> > Hi, >> >> > I am trying to implement a new filter in ParaView and I get the >> >> > following >> >> > error while executing. >> >> > >> >> > vtkPVSessionCore (0x162d180): Object type: MyObjectSource, could not >> >> > find >> >> > requested method: "setVariable" >> >> > or the method was called with incorrect arguments. >> >> > >> >> > while processing >> >> > Message 0 = Invoke >> >> > Argument 0 = vtk_object_pointer {MyObjectSource(0x34b3870)} >> >> > Argument 1 = string_value {setVariable} >> >> > Argument 2 = float64_value {0.003} >> >> > >> >> > >> >> > I searched the mailing list and it looks like a very similar bug has >> >> > been >> >> > reported >> >> > http://www.paraview.org/Bug/view.php?id=15593 >> >> > >> >> > >> >> > People have faced similar problem and here are the details >> >> > http://public.kitware.com/pipermail/paraview/2016-March/036387.html >> >> > >> >> > Is there a solution of work-around? >> >> > >> >> > Chiranjib >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Search the list archives at: >> >> > http://markmail.org/search/?q=Paraview-developers >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > >> >> >> >> >> >> >> >> -- >> >> Cory Quammen >> >> R&D Engineer >> >> Kitware, Inc. >> >> _______________________________________________ >> >> Powered by www.kitware.com >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Search the list archives at: >> >> http://markmail.org/search/?q=Paraview-developers >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> -- >> >> MTU Aero Engines AG >> >> Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. >> >> Rainer >> >> Martens, Michael Schreyoegg >> >> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus >> >> Eberhardt >> >> Sitz der Gesellschaft/Registered Office: Muenchen >> >> Handelsregister/Commercial Register: Muenchen HRB 157206 >> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder >> >> rechtlich geschuetzte Informationen. >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte >> >> den Absender und loeschen Sie diese >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder >> >> Weiterleiten ist nicht gestattet. >> >> >> >> This e-mail and any attached documents are proprietary to MTU, >> >> confidential or protected by law. >> >> If you are not the intended recipient, please advise the sender and >> >> delete >> >> this message and its attachments. >> >> Any unauthorised storing, copying or distribution is prohibited. >> > >> > >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. > > -- Cory Quammen R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Thu Jul 14 14:15:53 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 14 Jul 2016 14:15:53 -0400 Subject: [Paraview-developers] operation using background thread In-Reply-To: References: Message-ID: On Thu, Jul 14, 2016 at 2:06 PM, Chiranjib Sur wrote: > Hi, > While writing a file reader extension for paraview, I am seeing that while > PV is loading a large dataset, the GUI windows becomes non responsive. > > How can I send the "reading" operation on the background so that I can still > use the GUI while the file is loading on the background? > > Thanks in advance, > Chiranjib > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Thu Jul 14 14:16:51 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 14 Jul 2016 14:16:51 -0400 Subject: [Paraview-developers] operation using background thread In-Reply-To: References: Message-ID: Chiranjib, Sorry for the empty email. Errant mouse click. Performing long-running operations in the background is not currently supported in ParaView. It would be great to have, but we don't have it. Best, Cory On Thu, Jul 14, 2016 at 2:15 PM, Cory Quammen wrote: > On Thu, Jul 14, 2016 at 2:06 PM, Chiranjib Sur wrote: >> Hi, >> While writing a file reader extension for paraview, I am seeing that while >> PV is loading a large dataset, the GUI windows becomes non responsive. >> >> How can I send the "reading" operation on the background so that I can still >> use the GUI while the file is loading on the background? >> >> Thanks in advance, >> Chiranjib >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. -- Cory Quammen R&D Engineer Kitware, Inc. From jorgebanuls at gmail.com Fri Jul 15 06:53:00 2016 From: jorgebanuls at gmail.com (=?UTF-8?Q?Jorge_Ba=C3=B1uls?=) Date: Fri, 15 Jul 2016 11:53:00 +0100 Subject: [Paraview-developers] Selecting blocks from drop down list Message-ID: Hi, I'm developing a filter for Paraview and I need to be able to select blocks from the properties panel (the input is a vtkMultiBlockDataSet). The approach I'm using right now is to write the name of the block(s) and then process that string within the script, but I would like to be able to check the blocks I need from a list. I've seen many examples of how to do this, but only for variables arrays (e.g. the list displays the cell arrays existing in the input). Any ideas on how to apply this to display and select the blocks? Thanks in advance for your help, Jorge Ba?uls -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Fri Jul 15 07:06:52 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 15 Jul 2016 07:06:52 -0400 Subject: [Paraview-developers] Selecting blocks from drop down list In-Reply-To: References: Message-ID: Have you looked at the Extract Blocks filter? That may already be doing what you need and if not, it at least shows how to check the boxes for blocks that you want. On Fri, Jul 15, 2016 at 6:53 AM, Jorge Ba?uls wrote: > Hi, > > I'm developing a filter for Paraview and I need to be able to select > blocks from the properties panel (the input is a vtkMultiBlockDataSet). The > approach I'm using right now is to write the name of the block(s) and then > process that string within the script, but I would like to be able to check > the blocks I need from a list. I've seen many examples of how to do this, > but only for variables arrays (e.g. the list displays the cell arrays > existing in the input). Any ideas on how to apply this to display and > select the blocks? > > Thanks in advance for your help, > > Jorge Ba?uls > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorgebanuls at gmail.com Fri Jul 15 07:18:43 2016 From: jorgebanuls at gmail.com (=?UTF-8?Q?Jorge_Ba=C3=B1uls?=) Date: Fri, 15 Jul 2016 12:18:43 +0100 Subject: [Paraview-developers] Selecting blocks from drop down list In-Reply-To: References: Message-ID: Hi Andy, Indeed, the vtkExtractBlock filter is what I'm using in my script to extract the blocks, which are currently specified by the user in the properties panel as a string with the name of the block(s). Now that you mention it though, it could be useful to see how this filter creates the checklist. Is there a way to access the code behind this filter? Thanks a lot for your help, Jorge Ba?uls On 15 July 2016 at 12:06, Andy Bauer wrote: > Have you looked at the Extract Blocks filter? That may already be doing > what you need and if not, it at least shows how to check the boxes for > blocks that you want. > > On Fri, Jul 15, 2016 at 6:53 AM, Jorge Ba?uls > wrote: > >> Hi, >> >> I'm developing a filter for Paraview and I need to be able to select >> blocks from the properties panel (the input is a vtkMultiBlockDataSet). The >> approach I'm using right now is to write the name of the block(s) and then >> process that string within the script, but I would like to be able to check >> the blocks I need from a list. I've seen many examples of how to do this, >> but only for variables arrays (e.g. the list displays the cell arrays >> existing in the input). Any ideas on how to apply this to display and >> select the blocks? >> >> Thanks in advance for your help, >> >> Jorge Ba?uls >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Fri Jul 15 07:27:17 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Fri, 15 Jul 2016 07:27:17 -0400 Subject: [Paraview-developers] Selecting blocks from drop down list In-Reply-To: References: Message-ID: In ./ParaViewCore/ServerManager/SMApplication/Resources/filters.xml in the source code there's the following section which gives the options and GUI layout: This filter extracts a range of groups from a multiblock dataset This property specifies the input to the Extract Group filter. This property lists the ids of the blocks to extract from the input multiblock dataset. When set, the output mutliblock dataset will be pruned to remove empty nodes. On by default. This is used only when PruneOutput is ON. By default, when pruning the output i.e. remove empty blocks, if node has only 1 non-null child block, then that node is removed. To preserve these parent nodes, set this flag to true. Creating something similar for you may work. If you search the code for things like vtkSMIntVectorProperty.cxx/h you should find information on how the corresponding IntVectorProperty. On Fri, Jul 15, 2016 at 7:18 AM, Jorge Ba?uls wrote: > Hi Andy, > > Indeed, the vtkExtractBlock filter is what I'm using in my script to > extract the blocks, which are currently specified by the user in the > properties panel as a string with the name of the block(s). Now that you > mention it though, it could be useful to see how this filter creates the > checklist. Is there a way to access the code behind this filter? > > Thanks a lot for your help, > > Jorge Ba?uls > > On 15 July 2016 at 12:06, Andy Bauer wrote: > >> Have you looked at the Extract Blocks filter? That may already be doing >> what you need and if not, it at least shows how to check the boxes for >> blocks that you want. >> >> On Fri, Jul 15, 2016 at 6:53 AM, Jorge Ba?uls >> wrote: >> >>> Hi, >>> >>> I'm developing a filter for Paraview and I need to be able to select >>> blocks from the properties panel (the input is a vtkMultiBlockDataSet). The >>> approach I'm using right now is to write the name of the block(s) and then >>> process that string within the script, but I would like to be able to check >>> the blocks I need from a list. I've seen many examples of how to do this, >>> but only for variables arrays (e.g. the list displays the cell arrays >>> existing in the input). Any ideas on how to apply this to display and >>> select the blocks? >>> >>> Thanks in advance for your help, >>> >>> Jorge Ba?uls >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorgebanuls at gmail.com Fri Jul 15 11:31:57 2016 From: jorgebanuls at gmail.com (=?UTF-8?Q?Jorge_Ba=C3=B1uls?=) Date: Fri, 15 Jul 2016 16:31:57 +0100 Subject: [Paraview-developers] Selecting blocks from drop down list In-Reply-To: References: Message-ID: I've tried to implement the property in this way: but I get the following error: ERROR: In M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx, line 390 vtkPVSessionCore (00000000035C2B60): Object type: vtkPythonProgrammableFilter, could not find requested method: "RemoveAllIndices" or the method was called with incorrect arguments. while processing Message 0 = Invoke Argument 0 = vtk_object_pointer {vtkPythonProgrammableFilter (000000000B5222A0)} Argument 1 = string_value {RemoveAllIndices} ERROR: In M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx, line 391 vtkPVSessionCore (00000000035C2B60): Aborting execution for debugging purposes. ERROR: In M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, line 134 vtkSISourceProxy (000000000B4FDA70): Error pushing property state: BlockIndices if I omit clean_command="RemoveAllIndices", then the error appears for command="AddIndex". I've tried to use other commands, such as SetParameter or AddParameter, but no combination seems to work. On 15 July 2016 at 12:27, Andy Bauer wrote: > In ./ParaViewCore/ServerManager/SMApplication/Resources/filters.xml in the > source code there's the following section which gives the options and GUI > layout: > label="Extract Block" > name="ExtractBlock"> > short_help="Extract block.">This filter extracts a > range > of groups from a multiblock dataset > name="Input"> > > > > > > > > This property specifies the input to the Extract > Group > filter. > > command="AddIndex" > name="BlockIndices" > number_of_elements_per_command="1" > panel_visibility="default" > repeat_command="1"> > name="tree"> > > name="Input" /> > > > > > > This property lists the ids of the blocks to extract > from the input multiblock dataset. > > default_values="1" > name="PruneOutput" > number_of_elements="1"> > > When set, the output mutliblock dataset will be > pruned > to remove empty nodes. On by default. > > default_values="0" > name="MaintainStructure" > number_of_elements="1"> > > This is used only when PruneOutput is ON. By > default, > when pruning the output i.e. remove empty blocks, if node has only > 1 > non-null child block, then that node is removed. To preserve these > parent nodes, set this flag to true. > > > > > Creating something similar for you may work. If you search the code for > things like vtkSMIntVectorProperty.cxx/h you should find information on how > the corresponding IntVectorProperty. > > On Fri, Jul 15, 2016 at 7:18 AM, Jorge Ba?uls > wrote: > >> Hi Andy, >> >> Indeed, the vtkExtractBlock filter is what I'm using in my script to >> extract the blocks, which are currently specified by the user in the >> properties panel as a string with the name of the block(s). Now that you >> mention it though, it could be useful to see how this filter creates the >> checklist. Is there a way to access the code behind this filter? >> >> Thanks a lot for your help, >> >> Jorge Ba?uls >> >> On 15 July 2016 at 12:06, Andy Bauer wrote: >> >>> Have you looked at the Extract Blocks filter? That may already be doing >>> what you need and if not, it at least shows how to check the boxes for >>> blocks that you want. >>> >>> On Fri, Jul 15, 2016 at 6:53 AM, Jorge Ba?uls >>> wrote: >>> >>>> Hi, >>>> >>>> I'm developing a filter for Paraview and I need to be able to select >>>> blocks from the properties panel (the input is a vtkMultiBlockDataSet). The >>>> approach I'm using right now is to write the name of the block(s) and then >>>> process that string within the script, but I would like to be able to check >>>> the blocks I need from a list. I've seen many examples of how to do this, >>>> but only for variables arrays (e.g. the list displays the cell arrays >>>> existing in the input). Any ideas on how to apply this to display and >>>> select the blocks? >>>> >>>> Thanks in advance for your help, >>>> >>>> Jorge Ba?uls >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Search the list archives at: >>>> http://markmail.org/search/?q=Paraview-developers >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Sat Jul 16 08:40:52 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Sat, 16 Jul 2016 08:40:52 -0400 Subject: [Paraview-developers] Selecting blocks from drop down list In-Reply-To: References: Message-ID: You need to add in those methods. Look at the vtkExtractBlock.cxx/h class to see how those methods are being used in ParaView. On Fri, Jul 15, 2016 at 11:31 AM, Jorge Ba?uls wrote: > I've tried to implement the property in this way: > > command="AddIndex" > name="BlockIndices" > number_of_elements_per_command="1" > panel_visibility="default" > repeat_command="1"> > name="tree"> > > name="Input" /> > > > > > > but I get the following error: > > ERROR: In > M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx, > line 390 > > vtkPVSessionCore (00000000035C2B60): Object type: > vtkPythonProgrammableFilter, could not find requested method: > "RemoveAllIndices" > > or the method was called with incorrect arguments. > > > while processing > > Message 0 = Invoke > > Argument 0 = vtk_object_pointer {vtkPythonProgrammableFilter > (000000000B5222A0)} > > Argument 1 = string_value {RemoveAllIndices} > > > > > ERROR: In > M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx, > line 391 > > vtkPVSessionCore (00000000035C2B60): Aborting execution for debugging > purposes. > > > > ERROR: In > M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, > line 134 > > vtkSISourceProxy (000000000B4FDA70): Error pushing property state: > BlockIndices > > > if I omit clean_command="RemoveAllIndices", then the error appears for > command="AddIndex". I've tried to use other commands, such as > SetParameter or AddParameter, but no combination seems to work. > > > On 15 July 2016 at 12:27, Andy Bauer wrote: > >> In ./ParaViewCore/ServerManager/SMApplication/Resources/filters.xml in >> the source code there's the following section which gives the options and >> GUI layout: >> > label="Extract Block" >> name="ExtractBlock"> >> > short_help="Extract block.">This filter extracts a >> range >> of groups from a multiblock dataset >> > name="Input"> >> >> >> >> >> >> >> >> This property specifies the input to the Extract >> Group >> filter. >> >> > command="AddIndex" >> name="BlockIndices" >> number_of_elements_per_command="1" >> panel_visibility="default" >> repeat_command="1"> >> > name="tree"> >> >> > name="Input" /> >> >> >> >> >> >> This property lists the ids of the blocks to >> extract >> from the input multiblock dataset. >> >> > default_values="1" >> name="PruneOutput" >> number_of_elements="1"> >> >> When set, the output mutliblock dataset will be >> pruned >> to remove empty nodes. On by default. >> >> > default_values="0" >> name="MaintainStructure" >> number_of_elements="1"> >> >> This is used only when PruneOutput is ON. By >> default, >> when pruning the output i.e. remove empty blocks, if node has >> only 1 >> non-null child block, then that node is removed. To preserve these >> parent nodes, set this flag to true. >> >> >> >> >> Creating something similar for you may work. If you search the code for >> things like vtkSMIntVectorProperty.cxx/h you should find information on how >> the corresponding IntVectorProperty. >> >> On Fri, Jul 15, 2016 at 7:18 AM, Jorge Ba?uls >> wrote: >> >>> Hi Andy, >>> >>> Indeed, the vtkExtractBlock filter is what I'm using in my script to >>> extract the blocks, which are currently specified by the user in the >>> properties panel as a string with the name of the block(s). Now that you >>> mention it though, it could be useful to see how this filter creates the >>> checklist. Is there a way to access the code behind this filter? >>> >>> Thanks a lot for your help, >>> >>> Jorge Ba?uls >>> >>> On 15 July 2016 at 12:06, Andy Bauer wrote: >>> >>>> Have you looked at the Extract Blocks filter? That may already be >>>> doing what you need and if not, it at least shows how to check the boxes >>>> for blocks that you want. >>>> >>>> On Fri, Jul 15, 2016 at 6:53 AM, Jorge Ba?uls >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm developing a filter for Paraview and I need to be able to select >>>>> blocks from the properties panel (the input is a vtkMultiBlockDataSet). The >>>>> approach I'm using right now is to write the name of the block(s) and then >>>>> process that string within the script, but I would like to be able to check >>>>> the blocks I need from a list. I've seen many examples of how to do this, >>>>> but only for variables arrays (e.g. the list displays the cell arrays >>>>> existing in the input). Any ideas on how to apply this to display and >>>>> select the blocks? >>>>> >>>>> Thanks in advance for your help, >>>>> >>>>> Jorge Ba?uls >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Search the list archives at: >>>>> http://markmail.org/search/?q=Paraview-developers >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorgebanuls at gmail.com Sun Jul 17 07:34:22 2016 From: jorgebanuls at gmail.com (=?UTF-8?Q?Jorge_Ba=C3=B1uls?=) Date: Sun, 17 Jul 2016 12:34:22 +0100 Subject: [Paraview-developers] Selecting blocks from drop down list In-Reply-To: References: Message-ID: Hi, for those interested, I've come up with an easy partial solution, being this the implementation: This property allows the user to select only ONE block from the composite tree domain. After digging into the vtkPythonProgrammableFilter class I discovered that the method AddParameter(), which would be ideal for this case, takes only string values as arguments, whereas the vtkCompositeTreeDomain only works within a vtkIntVectorProperty (integer values), hence it's not possible to use it. On the other hand, the method SetParameter() only allows more than one value (up to three) in the arguments if they are of the type double. In the case of integer values, only one value is accepted. Therefore, even if the user checks more than one block, only the last index is stored. In the snippet of code above the user is not allowed to check more than one block by setting repeat_command to 0. I hope that this will be useful for future enquiries, and if someone comes up with a better workaround that actually allows selecting as many blocks as desired please let me know! Jorge On 16 July 2016 at 13:40, Andy Bauer wrote: > You need to add in those methods. Look at the vtkExtractBlock.cxx/h class > to see how those methods are being used in ParaView. > > On Fri, Jul 15, 2016 at 11:31 AM, Jorge Ba?uls > wrote: > >> I've tried to implement the property in this way: >> >> > command="AddIndex" >> name="BlockIndices" >> number_of_elements_per_command="1" >> panel_visibility="default" >> repeat_command="1"> >> > name="tree"> >> >> > name="Input" /> >> >> >> >> >> >> but I get the following error: >> >> ERROR: In >> M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx, >> line 390 >> >> vtkPVSessionCore (00000000035C2B60): Object type: >> vtkPythonProgrammableFilter, could not find requested method: >> "RemoveAllIndices" >> >> or the method was called with incorrect arguments. >> >> >> while processing >> >> Message 0 = Invoke >> >> Argument 0 = vtk_object_pointer {vtkPythonProgrammableFilter >> (000000000B5222A0)} >> >> Argument 1 = string_value {RemoveAllIndices} >> >> >> >> >> ERROR: In >> M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx, >> line 391 >> >> vtkPVSessionCore (00000000035C2B60): Aborting execution for debugging >> purposes. >> >> >> >> ERROR: In >> M:\b\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx, >> line 134 >> >> vtkSISourceProxy (000000000B4FDA70): Error pushing property state: >> BlockIndices >> >> >> if I omit clean_command="RemoveAllIndices", then the error appears for >> command="AddIndex". I've tried to use other commands, such as >> SetParameter or AddParameter, but no combination seems to work. >> >> >> On 15 July 2016 at 12:27, Andy Bauer wrote: >> >>> In ./ParaViewCore/ServerManager/SMApplication/Resources/filters.xml in >>> the source code there's the following section which gives the options and >>> GUI layout: >>> >> label="Extract Block" >>> name="ExtractBlock"> >>> >> short_help="Extract block.">This filter extracts a >>> range >>> of groups from a multiblock dataset >>> >> name="Input"> >>> >>> >>> >>> >>> >>> >>> >>> This property specifies the input to the Extract >>> Group >>> filter. >>> >>> >> command="AddIndex" >>> name="BlockIndices" >>> number_of_elements_per_command="1" >>> panel_visibility="default" >>> repeat_command="1"> >>> >> name="tree"> >>> >>> >> name="Input" /> >>> >>> >>> >>> >>> >>> This property lists the ids of the blocks to >>> extract >>> from the input multiblock dataset. >>> >>> >> default_values="1" >>> name="PruneOutput" >>> number_of_elements="1"> >>> >>> When set, the output mutliblock dataset will be >>> pruned >>> to remove empty nodes. On by default. >>> >>> >> default_values="0" >>> name="MaintainStructure" >>> number_of_elements="1"> >>> >>> This is used only when PruneOutput is ON. By >>> default, >>> when pruning the output i.e. remove empty blocks, if node has >>> only 1 >>> non-null child block, then that node is removed. To preserve >>> these >>> parent nodes, set this flag to true. >>> >>> >>> >>> >>> Creating something similar for you may work. If you search the code for >>> things like vtkSMIntVectorProperty.cxx/h you should find information on how >>> the corresponding IntVectorProperty. >>> >>> On Fri, Jul 15, 2016 at 7:18 AM, Jorge Ba?uls >>> wrote: >>> >>>> Hi Andy, >>>> >>>> Indeed, the vtkExtractBlock filter is what I'm using in my script to >>>> extract the blocks, which are currently specified by the user in the >>>> properties panel as a string with the name of the block(s). Now that you >>>> mention it though, it could be useful to see how this filter creates the >>>> checklist. Is there a way to access the code behind this filter? >>>> >>>> Thanks a lot for your help, >>>> >>>> Jorge Ba?uls >>>> >>>> On 15 July 2016 at 12:06, Andy Bauer wrote: >>>> >>>>> Have you looked at the Extract Blocks filter? That may already be >>>>> doing what you need and if not, it at least shows how to check the boxes >>>>> for blocks that you want. >>>>> >>>>> On Fri, Jul 15, 2016 at 6:53 AM, Jorge Ba?uls >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm developing a filter for Paraview and I need to be able to select >>>>>> blocks from the properties panel (the input is a vtkMultiBlockDataSet). The >>>>>> approach I'm using right now is to write the name of the block(s) and then >>>>>> process that string within the script, but I would like to be able to check >>>>>> the blocks I need from a list. I've seen many examples of how to do this, >>>>>> but only for variables arrays (e.g. the list displays the cell arrays >>>>>> existing in the input). Any ideas on how to apply this to display and >>>>>> select the blocks? >>>>>> >>>>>> Thanks in advance for your help, >>>>>> >>>>>> Jorge Ba?uls >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Search the list archives at: >>>>>> http://markmail.org/search/?q=Paraview-developers >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Jul 18 10:14:47 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Jul 2016 10:14:47 -0400 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: Chiranjib, CC'ing the developer's list so that others may benefit. Please see my modifications to your code attached. I wouldn't stress out about crashes until you more fully implement your plugin. Thanks, Cory On Mon, Jul 18, 2016 at 1:15 AM, Chiranjib Sur wrote: > Hi Cory, > Sorry to bother you again. > > I started with a clear mind this morning. Here is my modified sources > (prepended the class/file names with vtk ) attached. While building I can > build the ".so": and can load this as a plugin. However, when I want to > create the source from the menu, I get a seg fault. I think it's an issue > with some port. Since I have not implemented "RequestData" i don't expect > anyting to be displayed in the PV window, however it landed with a crash. > > You mentioned that by "appending the names with vtk" you could get it > worked. Could yo you please share the modification you have made it to work > or have a look at my attachment? > > Thanks, > Chiranjib > > On Fri, Jul 15, 2016 at 12:37 AM, Chiranjib Sur > wrote: >> >> Yep! I have access now and have the edit privilege. I will start adding >> things shortly. Let me make a list of things that I have learnt mostly via >> discussions using the mailing list. >> >> Chiranjib >> >> >> On Fri, Jul 15, 2016 at 12:28 AM, Cory Quammen >> wrote: >>> >>> Okay, you should have gotten an email with a randomly generated >>> password that should get you access to the wiki. You should be able to >>> edit it - let me know if you can't. >>> >>> Thanks, >>> Cory >>> >>> On Thu, Jul 14, 2016 at 2:53 PM, Cory Quammen >>> wrote: >>> > On Thu, Jul 14, 2016 at 2:46 PM, Chiranjib Sur >>> > wrote: >>> >> Hi Cory, >>> >> Great! I prefer the user name for the account and >>> >> atleast >>> >> for first few posts, I want it to be reviewed by you just to make >>> >> sure, I am >>> >> following the standards. >>> > >>> > Sure, no problem. I'm not really sure there are standards :-) You give >>> > us too much credit. >>> > >>> >> Do you mind for the wiki and edits if I communicate to you directly >>> >> bypassing the PV-developer mailing list? >>> > >>> > Yes, no problem. >>> > >>> > Cory >>> > >>> >> Thanks, >>> >> Chiranjib >>> >> >>> >> On Fri, Jul 15, 2016 at 12:13 AM, Cory Quammen >>> >> >>> >> wrote: >>> >>> >>> >>> Chiranjib, >>> >>> >>> >>> > How do I register to the wiki as an author? And how it works - >>> >>> > anybody >>> >>> > reviews the submission before it is published? >>> >>> >>> >>> The wiki suffered from spam attacks recently, so we had to disable >>> >>> user registration. I'll work to get you an account and then get you >>> >>> the login info. >>> >>> >>> >>> No reviews are needed before publishing, but if you want someone to >>> >>> take a look after you post the changes, I'm happy to review. >>> >>> >>> >>> Thanks, >>> >>> Cory >>> >>> >>> >>> > Thanks, >>> >>> > Chiranjib >>> >>> > >>> >>> > >>> >>> > >>> >>> > On Thu, Jul 14, 2016 at 11:43 PM, Cory Quammen >>> >>> > >>> >>> > wrote: >>> >>> >> >>> >>> >> > I wish these kind of information is stored in some wiki form >>> >>> >> > somewhere, >>> >>> >> > or >>> >>> >> > posted in your vtk/paraview blog. This will be immensely helpful >>> >>> >> > to >>> >>> >> > the >>> >>> >> > developer community! >>> >>> >> >>> >>> >> Indeed, though a ParaView developer's guide would likely be >>> >>> >> several >>> >>> >> hundred pages long, would no doubt miss an important piece of >>> >>> >> information someone needs, and would be out of date quite quickly. >>> >>> >> The >>> >>> >> ParaView code is itself the authoritative source of information, >>> >>> >> but I >>> >>> >> know full well - believe me - that it isn't always fast or easy to >>> >>> >> go >>> >>> >> that route. >>> >>> >> >>> >>> >> The good news is that you are now part of the developer community, >>> >>> >> so >>> >>> >> we have one more person to contribute this documentation! It would >>> >>> >> be >>> >>> >> great if you could update the ParaView plugins howto page on the >>> >>> >> wiki >>> >>> >> for other developers to benefit: >>> >>> >> >>> >>> >> http://www.paraview.org/Wiki/Plugin_HowTo >>> >>> >> >>> >>> >> Best, >>> >>> >> Cory >>> >>> >> >>> >>> >> >>> >>> >> > Thanks a lot, >>> >>> >> > Chiranjib >>> >>> >> > >>> >>> >> > >>> >>> >> > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen >>> >>> >> > >>> >>> >> > wrote: >>> >>> >> >> >>> >>> >> >> Chiranjib, >>> >>> >> >> >>> >>> >> >> It's not obvious or probably described anywhere, but the >>> >>> >> >> client/server >>> >>> >> >> code wrapping mechanism wraps member functions that have VTK >>> >>> >> >> objects >>> >>> >> >> as parameters *only* if those VTK objects have names that start >>> >>> >> >> with >>> >>> >> >> "vtk". If you prepend vtk to all your sph* classes, it should >>> >>> >> >> work. >>> >>> >> >> In >>> >>> >> >> fact, I tested that locally, and it solves the error you are >>> >>> >> >> seeing. >>> >>> >> >> >>> >>> >> >> HTH, >>> >>> >> >> Cory >>> >>> >> >> >>> >>> >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur >>> >>> >> >> >>> >>> >> >> wrote: >>> >>> >> >> > Hi, >>> >>> >> >> > Thanks for your messages the pointers. I still have some >>> >>> >> >> > issues. >>> >>> >> >> > Here >>> >>> >> >> > is >>> >>> >> >> > the >>> >>> >> >> > attached code snippets which throws me error messages. I am >>> >>> >> >> > bit >>> >>> >> >> > clueless >>> >>> >> >> > what I am missing here. >>> >>> >> >> > >>> >>> >> >> > Thanks, >>> >>> >> >> > Chiranjib >>> >>> >> >> > >>> >>> >> >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge Orlando >>> >>> >> >> > wrote: >>> >>> >> >> >> >>> >>> >> >> >> Hi, >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> >> >> Also , check if "setVariable" is in the public section >>> >>> >> >> >> of >>> >>> >> >> >> your >>> >>> >> >> >> class >>> >>> >> >> >> >>> >>> >> >> >> Orlando >>> >>> >> >> >> >>> >>> >> >> >> -----Urspr?ngliche Nachricht----- >>> >>> >> >> >> Von: Paraview-developers >>> >>> >> >> >> [mailto:paraview-developers-bounces at paraview.org] >>> >>> >> >> >> Im Auftrag von Cory Quammen >>> >>> >> >> >> Gesendet: Tuesday, 12. July 2016 15:37 >>> >>> >> >> >> An: Chiranjib Sur >>> >>> >> >> >> Cc: Paraview Developer Mailing list >>> >>> >> >> >> Betreff: Re: [Paraview-developers] paraview PVSessionCore >>> >>> >> >> >> error >>> >>> >> >> >> >>> >>> >> >> >> Chiranjib, >>> >>> >> >> >> >>> >>> >> >> >> Usually this error means there is a mismatch between the XML >>> >>> >> >> >> used >>> >>> >> >> >> to >>> >>> >> >> >> describe the VTK-side class. Check that your XML name for >>> >>> >> >> >> the >>> >>> >> >> >> member >>> >>> >> >> >> function matches the C++, and that the member function >>> >>> >> >> >> setVariable() >>> >>> >> >> >> takes only one value. >>> >>> >> >> >> >>> >>> >> >> >> Cory >>> >>> >> >> >> >>> >>> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur >>> >>> >> >> >> >>> >>> >> >> >> wrote: >>> >>> >> >> >> > Hi, >>> >>> >> >> >> > I am trying to implement a new filter in ParaView and I >>> >>> >> >> >> > get the >>> >>> >> >> >> > following >>> >>> >> >> >> > error while executing. >>> >>> >> >> >> > >>> >>> >> >> >> > vtkPVSessionCore (0x162d180): Object type: MyObjectSource, >>> >>> >> >> >> > could >>> >>> >> >> >> > not >>> >>> >> >> >> > find >>> >>> >> >> >> > requested method: "setVariable" >>> >>> >> >> >> > or the method was called with incorrect arguments. >>> >>> >> >> >> > >>> >>> >> >> >> > while processing >>> >>> >> >> >> > Message 0 = Invoke >>> >>> >> >> >> > Argument 0 = vtk_object_pointer >>> >>> >> >> >> > {MyObjectSource(0x34b3870)} >>> >>> >> >> >> > Argument 1 = string_value {setVariable} >>> >>> >> >> >> > Argument 2 = float64_value {0.003} >>> >>> >> >> >> > >>> >>> >> >> >> > >>> >>> >> >> >> > I searched the mailing list and it looks like a very >>> >>> >> >> >> > similar >>> >>> >> >> >> > bug >>> >>> >> >> >> > has >>> >>> >> >> >> > been >>> >>> >> >> >> > reported >>> >>> >> >> >> > http://www.paraview.org/Bug/view.php?id=15593 >>> >>> >> >> >> > >>> >>> >> >> >> > >>> >>> >> >> >> > People have faced similar problem and here are the details >>> >>> >> >> >> > >>> >>> >> >> >> > >>> >>> >> >> >> > >>> >>> >> >> >> > http://public.kitware.com/pipermail/paraview/2016-March/036387.html >>> >>> >> >> >> > >>> >>> >> >> >> > Is there a solution of work-around? >>> >>> >> >> >> > >>> >>> >> >> >> > Chiranjib >>> >>> >> >> >> > >>> >>> >> >> >> > _______________________________________________ >>> >>> >> >> >> > Powered by www.kitware.com >>> >>> >> >> >> > >>> >>> >> >> >> > Visit other Kitware open-source projects at >>> >>> >> >> >> > http://www.kitware.com/opensource/opensource.html >>> >>> >> >> >> > >>> >>> >> >> >> > Search the list archives at: >>> >>> >> >> >> > http://markmail.org/search/?q=Paraview-developers >>> >>> >> >> >> > >>> >>> >> >> >> > Follow this link to subscribe/unsubscribe: >>> >>> >> >> >> > >>> >>> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> >> >> > >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> >> >> -- >>> >>> >> >> >> Cory Quammen >>> >>> >> >> >> R&D Engineer >>> >>> >> >> >> Kitware, Inc. >>> >>> >> >> >> _______________________________________________ >>> >>> >> >> >> Powered by www.kitware.com >>> >>> >> >> >> >>> >>> >> >> >> Visit other Kitware open-source projects at >>> >>> >> >> >> http://www.kitware.com/opensource/opensource.html >>> >>> >> >> >> >>> >>> >> >> >> Search the list archives at: >>> >>> >> >> >> http://markmail.org/search/?q=Paraview-developers >>> >>> >> >> >> >>> >>> >> >> >> Follow this link to subscribe/unsubscribe: >>> >>> >> >> >> >>> >>> >> >> >> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> >> >> -- >>> >>> >> >> >> MTU Aero Engines AG >>> >>> >> >> >> Vorstand/Board of Management: Reiner Winkler, >>> >>> >> >> >> Vorsitzender/CEO; >>> >>> >> >> >> Dr. >>> >>> >> >> >> Rainer >>> >>> >> >> >> Martens, Michael Schreyoegg >>> >>> >> >> >> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory >>> >>> >> >> >> Board: >>> >>> >> >> >> Klaus >>> >>> >> >> >> Eberhardt >>> >>> >> >> >> Sitz der Gesellschaft/Registered Office: Muenchen >>> >>> >> >> >> Handelsregister/Commercial Register: Muenchen HRB 157206 >>> >>> >> >> >> >>> >>> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene >>> >>> >> >> >> vertrauliche >>> >>> >> >> >> oder >>> >>> >> >> >> rechtlich geschuetzte Informationen. >>> >>> >> >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind, >>> >>> >> >> >> informieren Sie >>> >>> >> >> >> bitte >>> >>> >> >> >> den Absender und loeschen Sie diese >>> >>> >> >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren >>> >>> >> >> >> oder >>> >>> >> >> >> Weiterleiten ist nicht gestattet. >>> >>> >> >> >> >>> >>> >> >> >> This e-mail and any attached documents are proprietary to >>> >>> >> >> >> MTU, >>> >>> >> >> >> confidential or protected by law. >>> >>> >> >> >> If you are not the intended recipient, please advise the >>> >>> >> >> >> sender >>> >>> >> >> >> and >>> >>> >> >> >> delete >>> >>> >> >> >> this message and its attachments. >>> >>> >> >> >> Any unauthorised storing, copying or distribution is >>> >>> >> >> >> prohibited. >>> >>> >> >> > >>> >>> >> >> > >>> >>> >> >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> >> -- >>> >>> >> >> Cory Quammen >>> >>> >> >> R&D Engineer >>> >>> >> >> Kitware, Inc. >>> >>> >> > >>> >>> >> > >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> >> -- >>> >>> >> Cory Quammen >>> >>> >> R&D Engineer >>> >>> >> Kitware, Inc. >>> >>> > >>> >>> > >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Cory Quammen >>> >>> R&D Engineer >>> >>> Kitware, Inc. >>> >> >>> >> >>> > >>> > >>> > >>> > -- >>> > Cory Quammen >>> > R&D Engineer >>> > Kitware, Inc. >>> >>> >>> >>> -- >>> Cory Quammen >>> R&D Engineer >>> Kitware, Inc. >> >> > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- A non-text attachment was scrubbed... Name: sph.zip Type: application/zip Size: 8946 bytes Desc: not available URL: From sur.chiranjib at gmail.com Mon Jul 18 13:05:53 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Mon, 18 Jul 2016 22:35:53 +0530 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: Cory, Thanks much. It means that except appending all classes by "vtk" nothing needs to be changed and is the crash related to "RequestData" implementation? Chiranjib On Mon, Jul 18, 2016 at 7:44 PM, Cory Quammen wrote: > Chiranjib, > > CC'ing the developer's list so that others may benefit. > > Please see my modifications to your code attached. I wouldn't stress > out about crashes until you more fully implement your plugin. > > Thanks, > Cory > > On Mon, Jul 18, 2016 at 1:15 AM, Chiranjib Sur > wrote: > > Hi Cory, > > Sorry to bother you again. > > > > I started with a clear mind this morning. Here is my modified sources > > (prepended the class/file names with vtk ) attached. While building I can > > build the ".so": and can load this as a plugin. However, when I want to > > create the source from the menu, I get a seg fault. I think it's an > issue > > with some port. Since I have not implemented "RequestData" i don't > expect > > anyting to be displayed in the PV window, however it landed with a crash. > > > > You mentioned that by "appending the names with vtk" you could get it > > worked. Could yo you please share the modification you have made it to > work > > or have a look at my attachment? > > > > Thanks, > > Chiranjib > > > > On Fri, Jul 15, 2016 at 12:37 AM, Chiranjib Sur > > > wrote: > >> > >> Yep! I have access now and have the edit privilege. I will start adding > >> things shortly. Let me make a list of things that I have learnt mostly > via > >> discussions using the mailing list. > >> > >> Chiranjib > >> > >> > >> On Fri, Jul 15, 2016 at 12:28 AM, Cory Quammen < > cory.quammen at kitware.com> > >> wrote: > >>> > >>> Okay, you should have gotten an email with a randomly generated > >>> password that should get you access to the wiki. You should be able to > >>> edit it - let me know if you can't. > >>> > >>> Thanks, > >>> Cory > >>> > >>> On Thu, Jul 14, 2016 at 2:53 PM, Cory Quammen < > cory.quammen at kitware.com> > >>> wrote: > >>> > On Thu, Jul 14, 2016 at 2:46 PM, Chiranjib Sur > >>> > wrote: > >>> >> Hi Cory, > >>> >> Great! I prefer the user name for the account and > >>> >> atleast > >>> >> for first few posts, I want it to be reviewed by you just to make > >>> >> sure, I am > >>> >> following the standards. > >>> > > >>> > Sure, no problem. I'm not really sure there are standards :-) You > give > >>> > us too much credit. > >>> > > >>> >> Do you mind for the wiki and edits if I communicate to you directly > >>> >> bypassing the PV-developer mailing list? > >>> > > >>> > Yes, no problem. > >>> > > >>> > Cory > >>> > > >>> >> Thanks, > >>> >> Chiranjib > >>> >> > >>> >> On Fri, Jul 15, 2016 at 12:13 AM, Cory Quammen > >>> >> > >>> >> wrote: > >>> >>> > >>> >>> Chiranjib, > >>> >>> > >>> >>> > How do I register to the wiki as an author? And how it works - > >>> >>> > anybody > >>> >>> > reviews the submission before it is published? > >>> >>> > >>> >>> The wiki suffered from spam attacks recently, so we had to disable > >>> >>> user registration. I'll work to get you an account and then get you > >>> >>> the login info. > >>> >>> > >>> >>> No reviews are needed before publishing, but if you want someone to > >>> >>> take a look after you post the changes, I'm happy to review. > >>> >>> > >>> >>> Thanks, > >>> >>> Cory > >>> >>> > >>> >>> > Thanks, > >>> >>> > Chiranjib > >>> >>> > > >>> >>> > > >>> >>> > > >>> >>> > On Thu, Jul 14, 2016 at 11:43 PM, Cory Quammen > >>> >>> > > >>> >>> > wrote: > >>> >>> >> > >>> >>> >> > I wish these kind of information is stored in some wiki form > >>> >>> >> > somewhere, > >>> >>> >> > or > >>> >>> >> > posted in your vtk/paraview blog. This will be immensely > helpful > >>> >>> >> > to > >>> >>> >> > the > >>> >>> >> > developer community! > >>> >>> >> > >>> >>> >> Indeed, though a ParaView developer's guide would likely be > >>> >>> >> several > >>> >>> >> hundred pages long, would no doubt miss an important piece of > >>> >>> >> information someone needs, and would be out of date quite > quickly. > >>> >>> >> The > >>> >>> >> ParaView code is itself the authoritative source of information, > >>> >>> >> but I > >>> >>> >> know full well - believe me - that it isn't always fast or easy > to > >>> >>> >> go > >>> >>> >> that route. > >>> >>> >> > >>> >>> >> The good news is that you are now part of the developer > community, > >>> >>> >> so > >>> >>> >> we have one more person to contribute this documentation! It > would > >>> >>> >> be > >>> >>> >> great if you could update the ParaView plugins howto page on the > >>> >>> >> wiki > >>> >>> >> for other developers to benefit: > >>> >>> >> > >>> >>> >> http://www.paraview.org/Wiki/Plugin_HowTo > >>> >>> >> > >>> >>> >> Best, > >>> >>> >> Cory > >>> >>> >> > >>> >>> >> > >>> >>> >> > Thanks a lot, > >>> >>> >> > Chiranjib > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen > >>> >>> >> > > >>> >>> >> > wrote: > >>> >>> >> >> > >>> >>> >> >> Chiranjib, > >>> >>> >> >> > >>> >>> >> >> It's not obvious or probably described anywhere, but the > >>> >>> >> >> client/server > >>> >>> >> >> code wrapping mechanism wraps member functions that have VTK > >>> >>> >> >> objects > >>> >>> >> >> as parameters *only* if those VTK objects have names that > start > >>> >>> >> >> with > >>> >>> >> >> "vtk". If you prepend vtk to all your sph* classes, it should > >>> >>> >> >> work. > >>> >>> >> >> In > >>> >>> >> >> fact, I tested that locally, and it solves the error you are > >>> >>> >> >> seeing. > >>> >>> >> >> > >>> >>> >> >> HTH, > >>> >>> >> >> Cory > >>> >>> >> >> > >>> >>> >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur > >>> >>> >> >> > >>> >>> >> >> wrote: > >>> >>> >> >> > Hi, > >>> >>> >> >> > Thanks for your messages the pointers. I still have some > >>> >>> >> >> > issues. > >>> >>> >> >> > Here > >>> >>> >> >> > is > >>> >>> >> >> > the > >>> >>> >> >> > attached code snippets which throws me error messages. I am > >>> >>> >> >> > bit > >>> >>> >> >> > clueless > >>> >>> >> >> > what I am missing here. > >>> >>> >> >> > > >>> >>> >> >> > Thanks, > >>> >>> >> >> > Chiranjib > >>> >>> >> >> > > >>> >>> >> >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge > Orlando > >>> >>> >> >> > wrote: > >>> >>> >> >> >> > >>> >>> >> >> >> Hi, > >>> >>> >> >> >> > >>> >>> >> >> >> > >>> >>> >> >> >> Also , check if "setVariable" is in the public > section > >>> >>> >> >> >> of > >>> >>> >> >> >> your > >>> >>> >> >> >> class > >>> >>> >> >> >> > >>> >>> >> >> >> Orlando > >>> >>> >> >> >> > >>> >>> >> >> >> -----Urspr?ngliche Nachricht----- > >>> >>> >> >> >> Von: Paraview-developers > >>> >>> >> >> >> [mailto:paraview-developers-bounces at paraview.org] > >>> >>> >> >> >> Im Auftrag von Cory Quammen > >>> >>> >> >> >> Gesendet: Tuesday, 12. July 2016 15:37 > >>> >>> >> >> >> An: Chiranjib Sur > >>> >>> >> >> >> Cc: Paraview Developer Mailing list > >>> >>> >> >> >> Betreff: Re: [Paraview-developers] paraview PVSessionCore > >>> >>> >> >> >> error > >>> >>> >> >> >> > >>> >>> >> >> >> Chiranjib, > >>> >>> >> >> >> > >>> >>> >> >> >> Usually this error means there is a mismatch between the > XML > >>> >>> >> >> >> used > >>> >>> >> >> >> to > >>> >>> >> >> >> describe the VTK-side class. Check that your XML name for > >>> >>> >> >> >> the > >>> >>> >> >> >> member > >>> >>> >> >> >> function matches the C++, and that the member function > >>> >>> >> >> >> setVariable() > >>> >>> >> >> >> takes only one value. > >>> >>> >> >> >> > >>> >>> >> >> >> Cory > >>> >>> >> >> >> > >>> >>> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur > >>> >>> >> >> >> > >>> >>> >> >> >> wrote: > >>> >>> >> >> >> > Hi, > >>> >>> >> >> >> > I am trying to implement a new filter in ParaView and I > >>> >>> >> >> >> > get the > >>> >>> >> >> >> > following > >>> >>> >> >> >> > error while executing. > >>> >>> >> >> >> > > >>> >>> >> >> >> > vtkPVSessionCore (0x162d180): Object type: > MyObjectSource, > >>> >>> >> >> >> > could > >>> >>> >> >> >> > not > >>> >>> >> >> >> > find > >>> >>> >> >> >> > requested method: "setVariable" > >>> >>> >> >> >> > or the method was called with incorrect arguments. > >>> >>> >> >> >> > > >>> >>> >> >> >> > while processing > >>> >>> >> >> >> > Message 0 = Invoke > >>> >>> >> >> >> > Argument 0 = vtk_object_pointer > >>> >>> >> >> >> > {MyObjectSource(0x34b3870)} > >>> >>> >> >> >> > Argument 1 = string_value {setVariable} > >>> >>> >> >> >> > Argument 2 = float64_value {0.003} > >>> >>> >> >> >> > > >>> >>> >> >> >> > > >>> >>> >> >> >> > I searched the mailing list and it looks like a very > >>> >>> >> >> >> > similar > >>> >>> >> >> >> > bug > >>> >>> >> >> >> > has > >>> >>> >> >> >> > been > >>> >>> >> >> >> > reported > >>> >>> >> >> >> > http://www.paraview.org/Bug/view.php?id=15593 > >>> >>> >> >> >> > > >>> >>> >> >> >> > > >>> >>> >> >> >> > People have faced similar problem and here are the > details > >>> >>> >> >> >> > > >>> >>> >> >> >> > > >>> >>> >> >> >> > > >>> >>> >> >> >> > > http://public.kitware.com/pipermail/paraview/2016-March/036387.html > >>> >>> >> >> >> > > >>> >>> >> >> >> > Is there a solution of work-around? > >>> >>> >> >> >> > > >>> >>> >> >> >> > Chiranjib > >>> >>> >> >> >> > > >>> >>> >> >> >> > _______________________________________________ > >>> >>> >> >> >> > Powered by www.kitware.com > >>> >>> >> >> >> > > >>> >>> >> >> >> > Visit other Kitware open-source projects at > >>> >>> >> >> >> > http://www.kitware.com/opensource/opensource.html > >>> >>> >> >> >> > > >>> >>> >> >> >> > Search the list archives at: > >>> >>> >> >> >> > http://markmail.org/search/?q=Paraview-developers > >>> >>> >> >> >> > > >>> >>> >> >> >> > Follow this link to subscribe/unsubscribe: > >>> >>> >> >> >> > > >>> >>> >> >> >> > > http://public.kitware.com/mailman/listinfo/paraview-developers > >>> >>> >> >> >> > > >>> >>> >> >> >> > >>> >>> >> >> >> > >>> >>> >> >> >> > >>> >>> >> >> >> -- > >>> >>> >> >> >> Cory Quammen > >>> >>> >> >> >> R&D Engineer > >>> >>> >> >> >> Kitware, Inc. > >>> >>> >> >> >> _______________________________________________ > >>> >>> >> >> >> Powered by www.kitware.com > >>> >>> >> >> >> > >>> >>> >> >> >> Visit other Kitware open-source projects at > >>> >>> >> >> >> http://www.kitware.com/opensource/opensource.html > >>> >>> >> >> >> > >>> >>> >> >> >> Search the list archives at: > >>> >>> >> >> >> http://markmail.org/search/?q=Paraview-developers > >>> >>> >> >> >> > >>> >>> >> >> >> Follow this link to subscribe/unsubscribe: > >>> >>> >> >> >> > >>> >>> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >>> >>> >> >> >> -- > >>> >>> >> >> >> MTU Aero Engines AG > >>> >>> >> >> >> Vorstand/Board of Management: Reiner Winkler, > >>> >>> >> >> >> Vorsitzender/CEO; > >>> >>> >> >> >> Dr. > >>> >>> >> >> >> Rainer > >>> >>> >> >> >> Martens, Michael Schreyoegg > >>> >>> >> >> >> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory > >>> >>> >> >> >> Board: > >>> >>> >> >> >> Klaus > >>> >>> >> >> >> Eberhardt > >>> >>> >> >> >> Sitz der Gesellschaft/Registered Office: Muenchen > >>> >>> >> >> >> Handelsregister/Commercial Register: Muenchen HRB 157206 > >>> >>> >> >> >> > >>> >>> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene > >>> >>> >> >> >> vertrauliche > >>> >>> >> >> >> oder > >>> >>> >> >> >> rechtlich geschuetzte Informationen. > >>> >>> >> >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind, > >>> >>> >> >> >> informieren Sie > >>> >>> >> >> >> bitte > >>> >>> >> >> >> den Absender und loeschen Sie diese > >>> >>> >> >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, > Kopieren > >>> >>> >> >> >> oder > >>> >>> >> >> >> Weiterleiten ist nicht gestattet. > >>> >>> >> >> >> > >>> >>> >> >> >> This e-mail and any attached documents are proprietary to > >>> >>> >> >> >> MTU, > >>> >>> >> >> >> confidential or protected by law. > >>> >>> >> >> >> If you are not the intended recipient, please advise the > >>> >>> >> >> >> sender > >>> >>> >> >> >> and > >>> >>> >> >> >> delete > >>> >>> >> >> >> this message and its attachments. > >>> >>> >> >> >> Any unauthorised storing, copying or distribution is > >>> >>> >> >> >> prohibited. > >>> >>> >> >> > > >>> >>> >> >> > > >>> >>> >> >> > >>> >>> >> >> > >>> >>> >> >> > >>> >>> >> >> -- > >>> >>> >> >> Cory Quammen > >>> >>> >> >> R&D Engineer > >>> >>> >> >> Kitware, Inc. > >>> >>> >> > > >>> >>> >> > > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> -- > >>> >>> >> Cory Quammen > >>> >>> >> R&D Engineer > >>> >>> >> Kitware, Inc. > >>> >>> > > >>> >>> > > >>> >>> > >>> >>> > >>> >>> > >>> >>> -- > >>> >>> Cory Quammen > >>> >>> R&D Engineer > >>> >>> Kitware, Inc. > >>> >> > >>> >> > >>> > > >>> > > >>> > > >>> > -- > >>> > Cory Quammen > >>> > R&D Engineer > >>> > Kitware, Inc. > >>> > >>> > >>> > >>> -- > >>> Cory Quammen > >>> R&D Engineer > >>> Kitware, Inc. > >> > >> > > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Jul 18 13:38:16 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Jul 2016 13:38:16 -0400 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: On Mon, Jul 18, 2016 at 1:05 PM, Chiranjib Sur wrote: > Cory, > Thanks much. It means that except appending all classes by "vtk" nothing > needs to be changed and is the crash related to "RequestData" > implementation? Ah, one problem now that I look at your example again: Use the 'vtkStandardNewMacro()' in your .cpp files to define the New() member functions. I suspect the way you are defining New() causes the garbage collector to prematurely delete the objects because the object reference counts are never incremented. This is likely what leads to the crash. Cory > Chiranjib > > On Mon, Jul 18, 2016 at 7:44 PM, Cory Quammen > wrote: >> >> Chiranjib, >> >> CC'ing the developer's list so that others may benefit. >> >> Please see my modifications to your code attached. I wouldn't stress >> out about crashes until you more fully implement your plugin. >> >> Thanks, >> Cory >> >> On Mon, Jul 18, 2016 at 1:15 AM, Chiranjib Sur >> wrote: >> > Hi Cory, >> > Sorry to bother you again. >> > >> > I started with a clear mind this morning. Here is my modified sources >> > (prepended the class/file names with vtk ) attached. While building I >> > can >> > build the ".so": and can load this as a plugin. However, when I want to >> > create the source from the menu, I get a seg fault. I think it's an >> > issue >> > with some port. Since I have not implemented "RequestData" i don't >> > expect >> > anyting to be displayed in the PV window, however it landed with a >> > crash. >> > >> > You mentioned that by "appending the names with vtk" you could get it >> > worked. Could yo you please share the modification you have made it to >> > work >> > or have a look at my attachment? >> > >> > Thanks, >> > Chiranjib >> > >> > On Fri, Jul 15, 2016 at 12:37 AM, Chiranjib Sur >> > >> > wrote: >> >> >> >> Yep! I have access now and have the edit privilege. I will start adding >> >> things shortly. Let me make a list of things that I have learnt mostly >> >> via >> >> discussions using the mailing list. >> >> >> >> Chiranjib >> >> >> >> >> >> On Fri, Jul 15, 2016 at 12:28 AM, Cory Quammen >> >> >> >> wrote: >> >>> >> >>> Okay, you should have gotten an email with a randomly generated >> >>> password that should get you access to the wiki. You should be able to >> >>> edit it - let me know if you can't. >> >>> >> >>> Thanks, >> >>> Cory >> >>> >> >>> On Thu, Jul 14, 2016 at 2:53 PM, Cory Quammen >> >>> >> >>> wrote: >> >>> > On Thu, Jul 14, 2016 at 2:46 PM, Chiranjib Sur >> >>> > wrote: >> >>> >> Hi Cory, >> >>> >> Great! I prefer the user name for the account and >> >>> >> atleast >> >>> >> for first few posts, I want it to be reviewed by you just to make >> >>> >> sure, I am >> >>> >> following the standards. >> >>> > >> >>> > Sure, no problem. I'm not really sure there are standards :-) You >> >>> > give >> >>> > us too much credit. >> >>> > >> >>> >> Do you mind for the wiki and edits if I communicate to you directly >> >>> >> bypassing the PV-developer mailing list? >> >>> > >> >>> > Yes, no problem. >> >>> > >> >>> > Cory >> >>> > >> >>> >> Thanks, >> >>> >> Chiranjib >> >>> >> >> >>> >> On Fri, Jul 15, 2016 at 12:13 AM, Cory Quammen >> >>> >> >> >>> >> wrote: >> >>> >>> >> >>> >>> Chiranjib, >> >>> >>> >> >>> >>> > How do I register to the wiki as an author? And how it works - >> >>> >>> > anybody >> >>> >>> > reviews the submission before it is published? >> >>> >>> >> >>> >>> The wiki suffered from spam attacks recently, so we had to disable >> >>> >>> user registration. I'll work to get you an account and then get >> >>> >>> you >> >>> >>> the login info. >> >>> >>> >> >>> >>> No reviews are needed before publishing, but if you want someone >> >>> >>> to >> >>> >>> take a look after you post the changes, I'm happy to review. >> >>> >>> >> >>> >>> Thanks, >> >>> >>> Cory >> >>> >>> >> >>> >>> > Thanks, >> >>> >>> > Chiranjib >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> > On Thu, Jul 14, 2016 at 11:43 PM, Cory Quammen >> >>> >>> > >> >>> >>> > wrote: >> >>> >>> >> >> >>> >>> >> > I wish these kind of information is stored in some wiki form >> >>> >>> >> > somewhere, >> >>> >>> >> > or >> >>> >>> >> > posted in your vtk/paraview blog. This will be immensely >> >>> >>> >> > helpful >> >>> >>> >> > to >> >>> >>> >> > the >> >>> >>> >> > developer community! >> >>> >>> >> >> >>> >>> >> Indeed, though a ParaView developer's guide would likely be >> >>> >>> >> several >> >>> >>> >> hundred pages long, would no doubt miss an important piece of >> >>> >>> >> information someone needs, and would be out of date quite >> >>> >>> >> quickly. >> >>> >>> >> The >> >>> >>> >> ParaView code is itself the authoritative source of >> >>> >>> >> information, >> >>> >>> >> but I >> >>> >>> >> know full well - believe me - that it isn't always fast or easy >> >>> >>> >> to >> >>> >>> >> go >> >>> >>> >> that route. >> >>> >>> >> >> >>> >>> >> The good news is that you are now part of the developer >> >>> >>> >> community, >> >>> >>> >> so >> >>> >>> >> we have one more person to contribute this documentation! It >> >>> >>> >> would >> >>> >>> >> be >> >>> >>> >> great if you could update the ParaView plugins howto page on >> >>> >>> >> the >> >>> >>> >> wiki >> >>> >>> >> for other developers to benefit: >> >>> >>> >> >> >>> >>> >> http://www.paraview.org/Wiki/Plugin_HowTo >> >>> >>> >> >> >>> >>> >> Best, >> >>> >>> >> Cory >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> > Thanks a lot, >> >>> >>> >> > Chiranjib >> >>> >>> >> > >> >>> >>> >> > >> >>> >>> >> > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen >> >>> >>> >> > >> >>> >>> >> > wrote: >> >>> >>> >> >> >> >>> >>> >> >> Chiranjib, >> >>> >>> >> >> >> >>> >>> >> >> It's not obvious or probably described anywhere, but the >> >>> >>> >> >> client/server >> >>> >>> >> >> code wrapping mechanism wraps member functions that have VTK >> >>> >>> >> >> objects >> >>> >>> >> >> as parameters *only* if those VTK objects have names that >> >>> >>> >> >> start >> >>> >>> >> >> with >> >>> >>> >> >> "vtk". If you prepend vtk to all your sph* classes, it >> >>> >>> >> >> should >> >>> >>> >> >> work. >> >>> >>> >> >> In >> >>> >>> >> >> fact, I tested that locally, and it solves the error you are >> >>> >>> >> >> seeing. >> >>> >>> >> >> >> >>> >>> >> >> HTH, >> >>> >>> >> >> Cory >> >>> >>> >> >> >> >>> >>> >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur >> >>> >>> >> >> >> >>> >>> >> >> wrote: >> >>> >>> >> >> > Hi, >> >>> >>> >> >> > Thanks for your messages the pointers. I still have some >> >>> >>> >> >> > issues. >> >>> >>> >> >> > Here >> >>> >>> >> >> > is >> >>> >>> >> >> > the >> >>> >>> >> >> > attached code snippets which throws me error messages. I >> >>> >>> >> >> > am >> >>> >>> >> >> > bit >> >>> >>> >> >> > clueless >> >>> >>> >> >> > what I am missing here. >> >>> >>> >> >> > >> >>> >>> >> >> > Thanks, >> >>> >>> >> >> > Chiranjib >> >>> >>> >> >> > >> >>> >>> >> >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge >> >>> >>> >> >> > Orlando >> >>> >>> >> >> > wrote: >> >>> >>> >> >> >> >> >>> >>> >> >> >> Hi, >> >>> >>> >> >> >> >> >>> >>> >> >> >> >> >>> >>> >> >> >> Also , check if "setVariable" is in the public >> >>> >>> >> >> >> section >> >>> >>> >> >> >> of >> >>> >>> >> >> >> your >> >>> >>> >> >> >> class >> >>> >>> >> >> >> >> >>> >>> >> >> >> Orlando >> >>> >>> >> >> >> >> >>> >>> >> >> >> -----Urspr?ngliche Nachricht----- >> >>> >>> >> >> >> Von: Paraview-developers >> >>> >>> >> >> >> [mailto:paraview-developers-bounces at paraview.org] >> >>> >>> >> >> >> Im Auftrag von Cory Quammen >> >>> >>> >> >> >> Gesendet: Tuesday, 12. July 2016 15:37 >> >>> >>> >> >> >> An: Chiranjib Sur >> >>> >>> >> >> >> Cc: Paraview Developer Mailing list >> >>> >>> >> >> >> Betreff: Re: [Paraview-developers] paraview PVSessionCore >> >>> >>> >> >> >> error >> >>> >>> >> >> >> >> >>> >>> >> >> >> Chiranjib, >> >>> >>> >> >> >> >> >>> >>> >> >> >> Usually this error means there is a mismatch between the >> >>> >>> >> >> >> XML >> >>> >>> >> >> >> used >> >>> >>> >> >> >> to >> >>> >>> >> >> >> describe the VTK-side class. Check that your XML name for >> >>> >>> >> >> >> the >> >>> >>> >> >> >> member >> >>> >>> >> >> >> function matches the C++, and that the member function >> >>> >>> >> >> >> setVariable() >> >>> >>> >> >> >> takes only one value. >> >>> >>> >> >> >> >> >>> >>> >> >> >> Cory >> >>> >>> >> >> >> >> >>> >>> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur >> >>> >>> >> >> >> >> >>> >>> >> >> >> wrote: >> >>> >>> >> >> >> > Hi, >> >>> >>> >> >> >> > I am trying to implement a new filter in ParaView and I >> >>> >>> >> >> >> > get the >> >>> >>> >> >> >> > following >> >>> >>> >> >> >> > error while executing. >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > vtkPVSessionCore (0x162d180): Object type: >> >>> >>> >> >> >> > MyObjectSource, >> >>> >>> >> >> >> > could >> >>> >>> >> >> >> > not >> >>> >>> >> >> >> > find >> >>> >>> >> >> >> > requested method: "setVariable" >> >>> >>> >> >> >> > or the method was called with incorrect arguments. >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > while processing >> >>> >>> >> >> >> > Message 0 = Invoke >> >>> >>> >> >> >> > Argument 0 = vtk_object_pointer >> >>> >>> >> >> >> > {MyObjectSource(0x34b3870)} >> >>> >>> >> >> >> > Argument 1 = string_value {setVariable} >> >>> >>> >> >> >> > Argument 2 = float64_value {0.003} >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > I searched the mailing list and it looks like a very >> >>> >>> >> >> >> > similar >> >>> >>> >> >> >> > bug >> >>> >>> >> >> >> > has >> >>> >>> >> >> >> > been >> >>> >>> >> >> >> > reported >> >>> >>> >> >> >> > http://www.paraview.org/Bug/view.php?id=15593 >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > People have faced similar problem and here are the >> >>> >>> >> >> >> > details >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > http://public.kitware.com/pipermail/paraview/2016-March/036387.html >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > Is there a solution of work-around? >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > Chiranjib >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > _______________________________________________ >> >>> >>> >> >> >> > Powered by www.kitware.com >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > Visit other Kitware open-source projects at >> >>> >>> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > Search the list archives at: >> >>> >>> >> >> >> > http://markmail.org/search/?q=Paraview-developers >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > Follow this link to subscribe/unsubscribe: >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >>> >>> >> >> >> > >> >>> >>> >> >> >> >> >>> >>> >> >> >> >> >>> >>> >> >> >> >> >>> >>> >> >> >> -- >> >>> >>> >> >> >> Cory Quammen >> >>> >>> >> >> >> R&D Engineer >> >>> >>> >> >> >> Kitware, Inc. >> >>> >>> >> >> >> _______________________________________________ >> >>> >>> >> >> >> Powered by www.kitware.com >> >>> >>> >> >> >> >> >>> >>> >> >> >> Visit other Kitware open-source projects at >> >>> >>> >> >> >> http://www.kitware.com/opensource/opensource.html >> >>> >>> >> >> >> >> >>> >>> >> >> >> Search the list archives at: >> >>> >>> >> >> >> http://markmail.org/search/?q=Paraview-developers >> >>> >>> >> >> >> >> >>> >>> >> >> >> Follow this link to subscribe/unsubscribe: >> >>> >>> >> >> >> >> >>> >>> >> >> >> >> >>> >>> >> >> >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >>> >>> >> >> >> -- >> >>> >>> >> >> >> MTU Aero Engines AG >> >>> >>> >> >> >> Vorstand/Board of Management: Reiner Winkler, >> >>> >>> >> >> >> Vorsitzender/CEO; >> >>> >>> >> >> >> Dr. >> >>> >>> >> >> >> Rainer >> >>> >>> >> >> >> Martens, Michael Schreyoegg >> >>> >>> >> >> >> Vorsitzender des Aufsichtsrats/Chairman of the >> >>> >>> >> >> >> Supervisory >> >>> >>> >> >> >> Board: >> >>> >>> >> >> >> Klaus >> >>> >>> >> >> >> Eberhardt >> >>> >>> >> >> >> Sitz der Gesellschaft/Registered Office: Muenchen >> >>> >>> >> >> >> Handelsregister/Commercial Register: Muenchen HRB 157206 >> >>> >>> >> >> >> >> >>> >>> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene >> >>> >>> >> >> >> vertrauliche >> >>> >>> >> >> >> oder >> >>> >>> >> >> >> rechtlich geschuetzte Informationen. >> >>> >>> >> >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind, >> >>> >>> >> >> >> informieren Sie >> >>> >>> >> >> >> bitte >> >>> >>> >> >> >> den Absender und loeschen Sie diese >> >>> >>> >> >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, >> >>> >>> >> >> >> Kopieren >> >>> >>> >> >> >> oder >> >>> >>> >> >> >> Weiterleiten ist nicht gestattet. >> >>> >>> >> >> >> >> >>> >>> >> >> >> This e-mail and any attached documents are proprietary to >> >>> >>> >> >> >> MTU, >> >>> >>> >> >> >> confidential or protected by law. >> >>> >>> >> >> >> If you are not the intended recipient, please advise the >> >>> >>> >> >> >> sender >> >>> >>> >> >> >> and >> >>> >>> >> >> >> delete >> >>> >>> >> >> >> this message and its attachments. >> >>> >>> >> >> >> Any unauthorised storing, copying or distribution is >> >>> >>> >> >> >> prohibited. >> >>> >>> >> >> > >> >>> >>> >> >> > >> >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> >> -- >> >>> >>> >> >> Cory Quammen >> >>> >>> >> >> R&D Engineer >> >>> >>> >> >> Kitware, Inc. >> >>> >>> >> > >> >>> >>> >> > >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> -- >> >>> >>> >> Cory Quammen >> >>> >>> >> R&D Engineer >> >>> >>> >> Kitware, Inc. >> >>> >>> > >> >>> >>> > >> >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> -- >> >>> >>> Cory Quammen >> >>> >>> R&D Engineer >> >>> >>> Kitware, Inc. >> >>> >> >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > Cory Quammen >> >>> > R&D Engineer >> >>> > Kitware, Inc. >> >>> >> >>> >> >>> >> >>> -- >> >>> Cory Quammen >> >>> R&D Engineer >> >>> Kitware, Inc. >> >> >> >> >> > >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. > > -- Cory Quammen R&D Engineer Kitware, Inc. From sur.chiranjib at gmail.com Mon Jul 18 13:52:57 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Mon, 18 Jul 2016 23:22:57 +0530 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: So, you recommend that in the .cpp files, instead of using vtkStandardNewMacro(vtksphObjectCube); I should use the following to define the New() member function? vtksphObjectCube* vtksphObjectCube::New() { return new vtksphObjectCube( );} On Mon, Jul 18, 2016 at 11:08 PM, Cory Quammen wrote: > On Mon, Jul 18, 2016 at 1:05 PM, Chiranjib Sur > wrote: > > Cory, > > Thanks much. It means that except appending all classes by "vtk" nothing > > needs to be changed and is the crash related to "RequestData" > > implementation? > > Ah, one problem now that I look at your example again: > > Use the 'vtkStandardNewMacro()' in your .cpp files to > define the New() member functions. I suspect the way you are defining > New() causes the garbage collector to prematurely delete the objects > because the object reference counts are never incremented. This is > likely what leads to the crash. > > Cory > > > Chiranjib > > > > On Mon, Jul 18, 2016 at 7:44 PM, Cory Quammen > > wrote: > >> > >> Chiranjib, > >> > >> CC'ing the developer's list so that others may benefit. > >> > >> Please see my modifications to your code attached. I wouldn't stress > >> out about crashes until you more fully implement your plugin. > >> > >> Thanks, > >> Cory > >> > >> On Mon, Jul 18, 2016 at 1:15 AM, Chiranjib Sur > > >> wrote: > >> > Hi Cory, > >> > Sorry to bother you again. > >> > > >> > I started with a clear mind this morning. Here is my modified sources > >> > (prepended the class/file names with vtk ) attached. While building I > >> > can > >> > build the ".so": and can load this as a plugin. However, when I want > to > >> > create the source from the menu, I get a seg fault. I think it's an > >> > issue > >> > with some port. Since I have not implemented "RequestData" i don't > >> > expect > >> > anyting to be displayed in the PV window, however it landed with a > >> > crash. > >> > > >> > You mentioned that by "appending the names with vtk" you could get it > >> > worked. Could yo you please share the modification you have made it to > >> > work > >> > or have a look at my attachment? > >> > > >> > Thanks, > >> > Chiranjib > >> > > >> > On Fri, Jul 15, 2016 at 12:37 AM, Chiranjib Sur > >> > > >> > wrote: > >> >> > >> >> Yep! I have access now and have the edit privilege. I will start > adding > >> >> things shortly. Let me make a list of things that I have learnt > mostly > >> >> via > >> >> discussions using the mailing list. > >> >> > >> >> Chiranjib > >> >> > >> >> > >> >> On Fri, Jul 15, 2016 at 12:28 AM, Cory Quammen > >> >> > >> >> wrote: > >> >>> > >> >>> Okay, you should have gotten an email with a randomly generated > >> >>> password that should get you access to the wiki. You should be able > to > >> >>> edit it - let me know if you can't. > >> >>> > >> >>> Thanks, > >> >>> Cory > >> >>> > >> >>> On Thu, Jul 14, 2016 at 2:53 PM, Cory Quammen > >> >>> > >> >>> wrote: > >> >>> > On Thu, Jul 14, 2016 at 2:46 PM, Chiranjib Sur > >> >>> > wrote: > >> >>> >> Hi Cory, > >> >>> >> Great! I prefer the user name for the account and > >> >>> >> atleast > >> >>> >> for first few posts, I want it to be reviewed by you just to make > >> >>> >> sure, I am > >> >>> >> following the standards. > >> >>> > > >> >>> > Sure, no problem. I'm not really sure there are standards :-) You > >> >>> > give > >> >>> > us too much credit. > >> >>> > > >> >>> >> Do you mind for the wiki and edits if I communicate to you > directly > >> >>> >> bypassing the PV-developer mailing list? > >> >>> > > >> >>> > Yes, no problem. > >> >>> > > >> >>> > Cory > >> >>> > > >> >>> >> Thanks, > >> >>> >> Chiranjib > >> >>> >> > >> >>> >> On Fri, Jul 15, 2016 at 12:13 AM, Cory Quammen > >> >>> >> > >> >>> >> wrote: > >> >>> >>> > >> >>> >>> Chiranjib, > >> >>> >>> > >> >>> >>> > How do I register to the wiki as an author? And how it works - > >> >>> >>> > anybody > >> >>> >>> > reviews the submission before it is published? > >> >>> >>> > >> >>> >>> The wiki suffered from spam attacks recently, so we had to > disable > >> >>> >>> user registration. I'll work to get you an account and then get > >> >>> >>> you > >> >>> >>> the login info. > >> >>> >>> > >> >>> >>> No reviews are needed before publishing, but if you want someone > >> >>> >>> to > >> >>> >>> take a look after you post the changes, I'm happy to review. > >> >>> >>> > >> >>> >>> Thanks, > >> >>> >>> Cory > >> >>> >>> > >> >>> >>> > Thanks, > >> >>> >>> > Chiranjib > >> >>> >>> > > >> >>> >>> > > >> >>> >>> > > >> >>> >>> > On Thu, Jul 14, 2016 at 11:43 PM, Cory Quammen > >> >>> >>> > > >> >>> >>> > wrote: > >> >>> >>> >> > >> >>> >>> >> > I wish these kind of information is stored in some wiki > form > >> >>> >>> >> > somewhere, > >> >>> >>> >> > or > >> >>> >>> >> > posted in your vtk/paraview blog. This will be immensely > >> >>> >>> >> > helpful > >> >>> >>> >> > to > >> >>> >>> >> > the > >> >>> >>> >> > developer community! > >> >>> >>> >> > >> >>> >>> >> Indeed, though a ParaView developer's guide would likely be > >> >>> >>> >> several > >> >>> >>> >> hundred pages long, would no doubt miss an important piece of > >> >>> >>> >> information someone needs, and would be out of date quite > >> >>> >>> >> quickly. > >> >>> >>> >> The > >> >>> >>> >> ParaView code is itself the authoritative source of > >> >>> >>> >> information, > >> >>> >>> >> but I > >> >>> >>> >> know full well - believe me - that it isn't always fast or > easy > >> >>> >>> >> to > >> >>> >>> >> go > >> >>> >>> >> that route. > >> >>> >>> >> > >> >>> >>> >> The good news is that you are now part of the developer > >> >>> >>> >> community, > >> >>> >>> >> so > >> >>> >>> >> we have one more person to contribute this documentation! It > >> >>> >>> >> would > >> >>> >>> >> be > >> >>> >>> >> great if you could update the ParaView plugins howto page on > >> >>> >>> >> the > >> >>> >>> >> wiki > >> >>> >>> >> for other developers to benefit: > >> >>> >>> >> > >> >>> >>> >> http://www.paraview.org/Wiki/Plugin_HowTo > >> >>> >>> >> > >> >>> >>> >> Best, > >> >>> >>> >> Cory > >> >>> >>> >> > >> >>> >>> >> > >> >>> >>> >> > Thanks a lot, > >> >>> >>> >> > Chiranjib > >> >>> >>> >> > > >> >>> >>> >> > > >> >>> >>> >> > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen > >> >>> >>> >> > > >> >>> >>> >> > wrote: > >> >>> >>> >> >> > >> >>> >>> >> >> Chiranjib, > >> >>> >>> >> >> > >> >>> >>> >> >> It's not obvious or probably described anywhere, but the > >> >>> >>> >> >> client/server > >> >>> >>> >> >> code wrapping mechanism wraps member functions that have > VTK > >> >>> >>> >> >> objects > >> >>> >>> >> >> as parameters *only* if those VTK objects have names that > >> >>> >>> >> >> start > >> >>> >>> >> >> with > >> >>> >>> >> >> "vtk". If you prepend vtk to all your sph* classes, it > >> >>> >>> >> >> should > >> >>> >>> >> >> work. > >> >>> >>> >> >> In > >> >>> >>> >> >> fact, I tested that locally, and it solves the error you > are > >> >>> >>> >> >> seeing. > >> >>> >>> >> >> > >> >>> >>> >> >> HTH, > >> >>> >>> >> >> Cory > >> >>> >>> >> >> > >> >>> >>> >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur > >> >>> >>> >> >> > >> >>> >>> >> >> wrote: > >> >>> >>> >> >> > Hi, > >> >>> >>> >> >> > Thanks for your messages the pointers. I still have some > >> >>> >>> >> >> > issues. > >> >>> >>> >> >> > Here > >> >>> >>> >> >> > is > >> >>> >>> >> >> > the > >> >>> >>> >> >> > attached code snippets which throws me error messages. I > >> >>> >>> >> >> > am > >> >>> >>> >> >> > bit > >> >>> >>> >> >> > clueless > >> >>> >>> >> >> > what I am missing here. > >> >>> >>> >> >> > > >> >>> >>> >> >> > Thanks, > >> >>> >>> >> >> > Chiranjib > >> >>> >>> >> >> > > >> >>> >>> >> >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge > >> >>> >>> >> >> > Orlando > >> >>> >>> >> >> > wrote: > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Hi, > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Also , check if "setVariable" is in the public > >> >>> >>> >> >> >> section > >> >>> >>> >> >> >> of > >> >>> >>> >> >> >> your > >> >>> >>> >> >> >> class > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Orlando > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> -----Urspr?ngliche Nachricht----- > >> >>> >>> >> >> >> Von: Paraview-developers > >> >>> >>> >> >> >> [mailto:paraview-developers-bounces at paraview.org] > >> >>> >>> >> >> >> Im Auftrag von Cory Quammen > >> >>> >>> >> >> >> Gesendet: Tuesday, 12. July 2016 15:37 > >> >>> >>> >> >> >> An: Chiranjib Sur > >> >>> >>> >> >> >> Cc: Paraview Developer Mailing list > >> >>> >>> >> >> >> Betreff: Re: [Paraview-developers] paraview > PVSessionCore > >> >>> >>> >> >> >> error > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Chiranjib, > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Usually this error means there is a mismatch between > the > >> >>> >>> >> >> >> XML > >> >>> >>> >> >> >> used > >> >>> >>> >> >> >> to > >> >>> >>> >> >> >> describe the VTK-side class. Check that your XML name > for > >> >>> >>> >> >> >> the > >> >>> >>> >> >> >> member > >> >>> >>> >> >> >> function matches the C++, and that the member function > >> >>> >>> >> >> >> setVariable() > >> >>> >>> >> >> >> takes only one value. > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Cory > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> wrote: > >> >>> >>> >> >> >> > Hi, > >> >>> >>> >> >> >> > I am trying to implement a new filter in ParaView > and I > >> >>> >>> >> >> >> > get the > >> >>> >>> >> >> >> > following > >> >>> >>> >> >> >> > error while executing. > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > vtkPVSessionCore (0x162d180): Object type: > >> >>> >>> >> >> >> > MyObjectSource, > >> >>> >>> >> >> >> > could > >> >>> >>> >> >> >> > not > >> >>> >>> >> >> >> > find > >> >>> >>> >> >> >> > requested method: "setVariable" > >> >>> >>> >> >> >> > or the method was called with incorrect arguments. > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > while processing > >> >>> >>> >> >> >> > Message 0 = Invoke > >> >>> >>> >> >> >> > Argument 0 = vtk_object_pointer > >> >>> >>> >> >> >> > {MyObjectSource(0x34b3870)} > >> >>> >>> >> >> >> > Argument 1 = string_value {setVariable} > >> >>> >>> >> >> >> > Argument 2 = float64_value {0.003} > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > I searched the mailing list and it looks like a very > >> >>> >>> >> >> >> > similar > >> >>> >>> >> >> >> > bug > >> >>> >>> >> >> >> > has > >> >>> >>> >> >> >> > been > >> >>> >>> >> >> >> > reported > >> >>> >>> >> >> >> > http://www.paraview.org/Bug/view.php?id=15593 > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > People have faced similar problem and here are the > >> >>> >>> >> >> >> > details > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > http://public.kitware.com/pipermail/paraview/2016-March/036387.html > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > Is there a solution of work-around? > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > Chiranjib > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > _______________________________________________ > >> >>> >>> >> >> >> > Powered by www.kitware.com > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > Visit other Kitware open-source projects at > >> >>> >>> >> >> >> > http://www.kitware.com/opensource/opensource.html > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > Search the list archives at: > >> >>> >>> >> >> >> > http://markmail.org/search/?q=Paraview-developers > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > Follow this link to subscribe/unsubscribe: > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > > http://public.kitware.com/mailman/listinfo/paraview-developers > >> >>> >>> >> >> >> > > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> -- > >> >>> >>> >> >> >> Cory Quammen > >> >>> >>> >> >> >> R&D Engineer > >> >>> >>> >> >> >> Kitware, Inc. > >> >>> >>> >> >> >> _______________________________________________ > >> >>> >>> >> >> >> Powered by www.kitware.com > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Visit other Kitware open-source projects at > >> >>> >>> >> >> >> http://www.kitware.com/opensource/opensource.html > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Search the list archives at: > >> >>> >>> >> >> >> http://markmail.org/search/?q=Paraview-developers > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Follow this link to subscribe/unsubscribe: > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> >>> >>> >> >> >> -- > >> >>> >>> >> >> >> MTU Aero Engines AG > >> >>> >>> >> >> >> Vorstand/Board of Management: Reiner Winkler, > >> >>> >>> >> >> >> Vorsitzender/CEO; > >> >>> >>> >> >> >> Dr. > >> >>> >>> >> >> >> Rainer > >> >>> >>> >> >> >> Martens, Michael Schreyoegg > >> >>> >>> >> >> >> Vorsitzender des Aufsichtsrats/Chairman of the > >> >>> >>> >> >> >> Supervisory > >> >>> >>> >> >> >> Board: > >> >>> >>> >> >> >> Klaus > >> >>> >>> >> >> >> Eberhardt > >> >>> >>> >> >> >> Sitz der Gesellschaft/Registered Office: Muenchen > >> >>> >>> >> >> >> Handelsregister/Commercial Register: Muenchen HRB > 157206 > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene > >> >>> >>> >> >> >> vertrauliche > >> >>> >>> >> >> >> oder > >> >>> >>> >> >> >> rechtlich geschuetzte Informationen. > >> >>> >>> >> >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind, > >> >>> >>> >> >> >> informieren Sie > >> >>> >>> >> >> >> bitte > >> >>> >>> >> >> >> den Absender und loeschen Sie diese > >> >>> >>> >> >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, > >> >>> >>> >> >> >> Kopieren > >> >>> >>> >> >> >> oder > >> >>> >>> >> >> >> Weiterleiten ist nicht gestattet. > >> >>> >>> >> >> >> > >> >>> >>> >> >> >> This e-mail and any attached documents are proprietary > to > >> >>> >>> >> >> >> MTU, > >> >>> >>> >> >> >> confidential or protected by law. > >> >>> >>> >> >> >> If you are not the intended recipient, please advise > the > >> >>> >>> >> >> >> sender > >> >>> >>> >> >> >> and > >> >>> >>> >> >> >> delete > >> >>> >>> >> >> >> this message and its attachments. > >> >>> >>> >> >> >> Any unauthorised storing, copying or distribution is > >> >>> >>> >> >> >> prohibited. > >> >>> >>> >> >> > > >> >>> >>> >> >> > > >> >>> >>> >> >> > >> >>> >>> >> >> > >> >>> >>> >> >> > >> >>> >>> >> >> -- > >> >>> >>> >> >> Cory Quammen > >> >>> >>> >> >> R&D Engineer > >> >>> >>> >> >> Kitware, Inc. > >> >>> >>> >> > > >> >>> >>> >> > > >> >>> >>> >> > >> >>> >>> >> > >> >>> >>> >> > >> >>> >>> >> -- > >> >>> >>> >> Cory Quammen > >> >>> >>> >> R&D Engineer > >> >>> >>> >> Kitware, Inc. > >> >>> >>> > > >> >>> >>> > > >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> -- > >> >>> >>> Cory Quammen > >> >>> >>> R&D Engineer > >> >>> >>> Kitware, Inc. > >> >>> >> > >> >>> >> > >> >>> > > >> >>> > > >> >>> > > >> >>> > -- > >> >>> > Cory Quammen > >> >>> > R&D Engineer > >> >>> > Kitware, Inc. > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> Cory Quammen > >> >>> R&D Engineer > >> >>> Kitware, Inc. > >> >> > >> >> > >> > > >> > >> > >> > >> -- > >> Cory Quammen > >> R&D Engineer > >> Kitware, Inc. > > > > > > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Jul 18 14:08:39 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 18 Jul 2016 14:08:39 -0400 Subject: [Paraview-developers] paraview PVSessionCore error In-Reply-To: References: Message-ID: No, exactly the opposite. Use vtkStandardNewMacro(). On Mon, Jul 18, 2016 at 1:52 PM, Chiranjib Sur wrote: > So, you recommend that in the .cpp files, instead of using > vtkStandardNewMacro(vtksphObjectCube); > > I should use the following to define the New() member function? > > vtksphObjectCube* vtksphObjectCube::New() > > { return new vtksphObjectCube( );} > > > On Mon, Jul 18, 2016 at 11:08 PM, Cory Quammen > wrote: >> >> On Mon, Jul 18, 2016 at 1:05 PM, Chiranjib Sur >> wrote: >> > Cory, >> > Thanks much. It means that except appending all classes by "vtk" nothing >> > needs to be changed and is the crash related to "RequestData" >> > implementation? >> >> Ah, one problem now that I look at your example again: >> >> Use the 'vtkStandardNewMacro()' in your .cpp files to >> define the New() member functions. I suspect the way you are defining >> New() causes the garbage collector to prematurely delete the objects >> because the object reference counts are never incremented. This is >> likely what leads to the crash. >> >> Cory >> >> > Chiranjib >> > >> > On Mon, Jul 18, 2016 at 7:44 PM, Cory Quammen >> > wrote: >> >> >> >> Chiranjib, >> >> >> >> CC'ing the developer's list so that others may benefit. >> >> >> >> Please see my modifications to your code attached. I wouldn't stress >> >> out about crashes until you more fully implement your plugin. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Mon, Jul 18, 2016 at 1:15 AM, Chiranjib Sur >> >> >> >> wrote: >> >> > Hi Cory, >> >> > Sorry to bother you again. >> >> > >> >> > I started with a clear mind this morning. Here is my modified sources >> >> > (prepended the class/file names with vtk ) attached. While building I >> >> > can >> >> > build the ".so": and can load this as a plugin. However, when I want >> >> > to >> >> > create the source from the menu, I get a seg fault. I think it's an >> >> > issue >> >> > with some port. Since I have not implemented "RequestData" i don't >> >> > expect >> >> > anyting to be displayed in the PV window, however it landed with a >> >> > crash. >> >> > >> >> > You mentioned that by "appending the names with vtk" you could get it >> >> > worked. Could yo you please share the modification you have made it >> >> > to >> >> > work >> >> > or have a look at my attachment? >> >> > >> >> > Thanks, >> >> > Chiranjib >> >> > >> >> > On Fri, Jul 15, 2016 at 12:37 AM, Chiranjib Sur >> >> > >> >> > wrote: >> >> >> >> >> >> Yep! I have access now and have the edit privilege. I will start >> >> >> adding >> >> >> things shortly. Let me make a list of things that I have learnt >> >> >> mostly >> >> >> via >> >> >> discussions using the mailing list. >> >> >> >> >> >> Chiranjib >> >> >> >> >> >> >> >> >> On Fri, Jul 15, 2016 at 12:28 AM, Cory Quammen >> >> >> >> >> >> wrote: >> >> >>> >> >> >>> Okay, you should have gotten an email with a randomly generated >> >> >>> password that should get you access to the wiki. You should be able >> >> >>> to >> >> >>> edit it - let me know if you can't. >> >> >>> >> >> >>> Thanks, >> >> >>> Cory >> >> >>> >> >> >>> On Thu, Jul 14, 2016 at 2:53 PM, Cory Quammen >> >> >>> >> >> >>> wrote: >> >> >>> > On Thu, Jul 14, 2016 at 2:46 PM, Chiranjib Sur >> >> >>> > wrote: >> >> >>> >> Hi Cory, >> >> >>> >> Great! I prefer the user name for the account >> >> >>> >> and >> >> >>> >> atleast >> >> >>> >> for first few posts, I want it to be reviewed by you just to >> >> >>> >> make >> >> >>> >> sure, I am >> >> >>> >> following the standards. >> >> >>> > >> >> >>> > Sure, no problem. I'm not really sure there are standards :-) You >> >> >>> > give >> >> >>> > us too much credit. >> >> >>> > >> >> >>> >> Do you mind for the wiki and edits if I communicate to you >> >> >>> >> directly >> >> >>> >> bypassing the PV-developer mailing list? >> >> >>> > >> >> >>> > Yes, no problem. >> >> >>> > >> >> >>> > Cory >> >> >>> > >> >> >>> >> Thanks, >> >> >>> >> Chiranjib >> >> >>> >> >> >> >>> >> On Fri, Jul 15, 2016 at 12:13 AM, Cory Quammen >> >> >>> >> >> >> >>> >> wrote: >> >> >>> >>> >> >> >>> >>> Chiranjib, >> >> >>> >>> >> >> >>> >>> > How do I register to the wiki as an author? And how it works >> >> >>> >>> > - >> >> >>> >>> > anybody >> >> >>> >>> > reviews the submission before it is published? >> >> >>> >>> >> >> >>> >>> The wiki suffered from spam attacks recently, so we had to >> >> >>> >>> disable >> >> >>> >>> user registration. I'll work to get you an account and then get >> >> >>> >>> you >> >> >>> >>> the login info. >> >> >>> >>> >> >> >>> >>> No reviews are needed before publishing, but if you want >> >> >>> >>> someone >> >> >>> >>> to >> >> >>> >>> take a look after you post the changes, I'm happy to review. >> >> >>> >>> >> >> >>> >>> Thanks, >> >> >>> >>> Cory >> >> >>> >>> >> >> >>> >>> > Thanks, >> >> >>> >>> > Chiranjib >> >> >>> >>> > >> >> >>> >>> > >> >> >>> >>> > >> >> >>> >>> > On Thu, Jul 14, 2016 at 11:43 PM, Cory Quammen >> >> >>> >>> > >> >> >>> >>> > wrote: >> >> >>> >>> >> >> >> >>> >>> >> > I wish these kind of information is stored in some wiki >> >> >>> >>> >> > form >> >> >>> >>> >> > somewhere, >> >> >>> >>> >> > or >> >> >>> >>> >> > posted in your vtk/paraview blog. This will be immensely >> >> >>> >>> >> > helpful >> >> >>> >>> >> > to >> >> >>> >>> >> > the >> >> >>> >>> >> > developer community! >> >> >>> >>> >> >> >> >>> >>> >> Indeed, though a ParaView developer's guide would likely be >> >> >>> >>> >> several >> >> >>> >>> >> hundred pages long, would no doubt miss an important piece >> >> >>> >>> >> of >> >> >>> >>> >> information someone needs, and would be out of date quite >> >> >>> >>> >> quickly. >> >> >>> >>> >> The >> >> >>> >>> >> ParaView code is itself the authoritative source of >> >> >>> >>> >> information, >> >> >>> >>> >> but I >> >> >>> >>> >> know full well - believe me - that it isn't always fast or >> >> >>> >>> >> easy >> >> >>> >>> >> to >> >> >>> >>> >> go >> >> >>> >>> >> that route. >> >> >>> >>> >> >> >> >>> >>> >> The good news is that you are now part of the developer >> >> >>> >>> >> community, >> >> >>> >>> >> so >> >> >>> >>> >> we have one more person to contribute this documentation! It >> >> >>> >>> >> would >> >> >>> >>> >> be >> >> >>> >>> >> great if you could update the ParaView plugins howto page on >> >> >>> >>> >> the >> >> >>> >>> >> wiki >> >> >>> >>> >> for other developers to benefit: >> >> >>> >>> >> >> >> >>> >>> >> http://www.paraview.org/Wiki/Plugin_HowTo >> >> >>> >>> >> >> >> >>> >>> >> Best, >> >> >>> >>> >> Cory >> >> >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> > Thanks a lot, >> >> >>> >>> >> > Chiranjib >> >> >>> >>> >> > >> >> >>> >>> >> > >> >> >>> >>> >> > On Thu, Jul 14, 2016 at 7:37 PM, Cory Quammen >> >> >>> >>> >> > >> >> >>> >>> >> > wrote: >> >> >>> >>> >> >> >> >> >>> >>> >> >> Chiranjib, >> >> >>> >>> >> >> >> >> >>> >>> >> >> It's not obvious or probably described anywhere, but the >> >> >>> >>> >> >> client/server >> >> >>> >>> >> >> code wrapping mechanism wraps member functions that have >> >> >>> >>> >> >> VTK >> >> >>> >>> >> >> objects >> >> >>> >>> >> >> as parameters *only* if those VTK objects have names that >> >> >>> >>> >> >> start >> >> >>> >>> >> >> with >> >> >>> >>> >> >> "vtk". If you prepend vtk to all your sph* classes, it >> >> >>> >>> >> >> should >> >> >>> >>> >> >> work. >> >> >>> >>> >> >> In >> >> >>> >>> >> >> fact, I tested that locally, and it solves the error you >> >> >>> >>> >> >> are >> >> >>> >>> >> >> seeing. >> >> >>> >>> >> >> >> >> >>> >>> >> >> HTH, >> >> >>> >>> >> >> Cory >> >> >>> >>> >> >> >> >> >>> >>> >> >> On Wed, Jul 13, 2016 at 1:57 AM, Chiranjib Sur >> >> >>> >>> >> >> >> >> >>> >>> >> >> wrote: >> >> >>> >>> >> >> > Hi, >> >> >>> >>> >> >> > Thanks for your messages the pointers. I still have >> >> >>> >>> >> >> > some >> >> >>> >>> >> >> > issues. >> >> >>> >>> >> >> > Here >> >> >>> >>> >> >> > is >> >> >>> >>> >> >> > the >> >> >>> >>> >> >> > attached code snippets which throws me error messages. >> >> >>> >>> >> >> > I >> >> >>> >>> >> >> > am >> >> >>> >>> >> >> > bit >> >> >>> >>> >> >> > clueless >> >> >>> >>> >> >> > what I am missing here. >> >> >>> >>> >> >> > >> >> >>> >>> >> >> > Thanks, >> >> >>> >>> >> >> > Chiranjib >> >> >>> >>> >> >> > >> >> >>> >>> >> >> > On Tue, Jul 12, 2016 at 8:09 PM, RIVERA ROLDAN, Jorge >> >> >>> >>> >> >> > Orlando >> >> >>> >>> >> >> > wrote: >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Hi, >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Also , check if "setVariable" is in the public >> >> >>> >>> >> >> >> section >> >> >>> >>> >> >> >> of >> >> >>> >>> >> >> >> your >> >> >>> >>> >> >> >> class >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Orlando >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> -----Urspr?ngliche Nachricht----- >> >> >>> >>> >> >> >> Von: Paraview-developers >> >> >>> >>> >> >> >> [mailto:paraview-developers-bounces at paraview.org] >> >> >>> >>> >> >> >> Im Auftrag von Cory Quammen >> >> >>> >>> >> >> >> Gesendet: Tuesday, 12. July 2016 15:37 >> >> >>> >>> >> >> >> An: Chiranjib Sur >> >> >>> >>> >> >> >> Cc: Paraview Developer Mailing list >> >> >>> >>> >> >> >> Betreff: Re: [Paraview-developers] paraview >> >> >>> >>> >> >> >> PVSessionCore >> >> >>> >>> >> >> >> error >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Chiranjib, >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Usually this error means there is a mismatch between >> >> >>> >>> >> >> >> the >> >> >>> >>> >> >> >> XML >> >> >>> >>> >> >> >> used >> >> >>> >>> >> >> >> to >> >> >>> >>> >> >> >> describe the VTK-side class. Check that your XML name >> >> >>> >>> >> >> >> for >> >> >>> >>> >> >> >> the >> >> >>> >>> >> >> >> member >> >> >>> >>> >> >> >> function matches the C++, and that the member function >> >> >>> >>> >> >> >> setVariable() >> >> >>> >>> >> >> >> takes only one value. >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Cory >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> On Tue, Jul 12, 2016 at 1:22 AM, Chiranjib Sur >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> wrote: >> >> >>> >>> >> >> >> > Hi, >> >> >>> >>> >> >> >> > I am trying to implement a new filter in ParaView >> >> >>> >>> >> >> >> > and I >> >> >>> >>> >> >> >> > get the >> >> >>> >>> >> >> >> > following >> >> >>> >>> >> >> >> > error while executing. >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > vtkPVSessionCore (0x162d180): Object type: >> >> >>> >>> >> >> >> > MyObjectSource, >> >> >>> >>> >> >> >> > could >> >> >>> >>> >> >> >> > not >> >> >>> >>> >> >> >> > find >> >> >>> >>> >> >> >> > requested method: "setVariable" >> >> >>> >>> >> >> >> > or the method was called with incorrect arguments. >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > while processing >> >> >>> >>> >> >> >> > Message 0 = Invoke >> >> >>> >>> >> >> >> > Argument 0 = vtk_object_pointer >> >> >>> >>> >> >> >> > {MyObjectSource(0x34b3870)} >> >> >>> >>> >> >> >> > Argument 1 = string_value {setVariable} >> >> >>> >>> >> >> >> > Argument 2 = float64_value {0.003} >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > I searched the mailing list and it looks like a very >> >> >>> >>> >> >> >> > similar >> >> >>> >>> >> >> >> > bug >> >> >>> >>> >> >> >> > has >> >> >>> >>> >> >> >> > been >> >> >>> >>> >> >> >> > reported >> >> >>> >>> >> >> >> > http://www.paraview.org/Bug/view.php?id=15593 >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > People have faced similar problem and here are the >> >> >>> >>> >> >> >> > details >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > http://public.kitware.com/pipermail/paraview/2016-March/036387.html >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > Is there a solution of work-around? >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > Chiranjib >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > _______________________________________________ >> >> >>> >>> >> >> >> > Powered by www.kitware.com >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > Visit other Kitware open-source projects at >> >> >>> >>> >> >> >> > http://www.kitware.com/opensource/opensource.html >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > Search the list archives at: >> >> >>> >>> >> >> >> > http://markmail.org/search/?q=Paraview-developers >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > Follow this link to subscribe/unsubscribe: >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >>> >>> >> >> >> > >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> -- >> >> >>> >>> >> >> >> Cory Quammen >> >> >>> >>> >> >> >> R&D Engineer >> >> >>> >>> >> >> >> Kitware, Inc. >> >> >>> >>> >> >> >> _______________________________________________ >> >> >>> >>> >> >> >> Powered by www.kitware.com >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Visit other Kitware open-source projects at >> >> >>> >>> >> >> >> http://www.kitware.com/opensource/opensource.html >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Search the list archives at: >> >> >>> >>> >> >> >> http://markmail.org/search/?q=Paraview-developers >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Follow this link to subscribe/unsubscribe: >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> >>> >>> >> >> >> -- >> >> >>> >>> >> >> >> MTU Aero Engines AG >> >> >>> >>> >> >> >> Vorstand/Board of Management: Reiner Winkler, >> >> >>> >>> >> >> >> Vorsitzender/CEO; >> >> >>> >>> >> >> >> Dr. >> >> >>> >>> >> >> >> Rainer >> >> >>> >>> >> >> >> Martens, Michael Schreyoegg >> >> >>> >>> >> >> >> Vorsitzender des Aufsichtsrats/Chairman of the >> >> >>> >>> >> >> >> Supervisory >> >> >>> >>> >> >> >> Board: >> >> >>> >>> >> >> >> Klaus >> >> >>> >>> >> >> >> Eberhardt >> >> >>> >>> >> >> >> Sitz der Gesellschaft/Registered Office: Muenchen >> >> >>> >>> >> >> >> Handelsregister/Commercial Register: Muenchen HRB >> >> >>> >>> >> >> >> 157206 >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene >> >> >>> >>> >> >> >> vertrauliche >> >> >>> >>> >> >> >> oder >> >> >>> >>> >> >> >> rechtlich geschuetzte Informationen. >> >> >>> >>> >> >> >> Wenn Sie nicht der beabsichtigte Empfaenger sind, >> >> >>> >>> >> >> >> informieren Sie >> >> >>> >>> >> >> >> bitte >> >> >>> >>> >> >> >> den Absender und loeschen Sie diese >> >> >>> >>> >> >> >> E-Mail sowie die Anhaenge. Das unbefugte Speichern, >> >> >>> >>> >> >> >> Kopieren >> >> >>> >>> >> >> >> oder >> >> >>> >>> >> >> >> Weiterleiten ist nicht gestattet. >> >> >>> >>> >> >> >> >> >> >>> >>> >> >> >> This e-mail and any attached documents are proprietary >> >> >>> >>> >> >> >> to >> >> >>> >>> >> >> >> MTU, >> >> >>> >>> >> >> >> confidential or protected by law. >> >> >>> >>> >> >> >> If you are not the intended recipient, please advise >> >> >>> >>> >> >> >> the >> >> >>> >>> >> >> >> sender >> >> >>> >>> >> >> >> and >> >> >>> >>> >> >> >> delete >> >> >>> >>> >> >> >> this message and its attachments. >> >> >>> >>> >> >> >> Any unauthorised storing, copying or distribution is >> >> >>> >>> >> >> >> prohibited. >> >> >>> >>> >> >> > >> >> >>> >>> >> >> > >> >> >>> >>> >> >> >> >> >>> >>> >> >> >> >> >>> >>> >> >> >> >> >>> >>> >> >> -- >> >> >>> >>> >> >> Cory Quammen >> >> >>> >>> >> >> R&D Engineer >> >> >>> >>> >> >> Kitware, Inc. >> >> >>> >>> >> > >> >> >>> >>> >> > >> >> >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> >> >> >>> >>> >> -- >> >> >>> >>> >> Cory Quammen >> >> >>> >>> >> R&D Engineer >> >> >>> >>> >> Kitware, Inc. >> >> >>> >>> > >> >> >>> >>> > >> >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> >> >>> >>> -- >> >> >>> >>> Cory Quammen >> >> >>> >>> R&D Engineer >> >> >>> >>> Kitware, Inc. >> >> >>> >> >> >> >>> >> >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > -- >> >> >>> > Cory Quammen >> >> >>> > R&D Engineer >> >> >>> > Kitware, Inc. >> >> >>> >> >> >>> >> >> >>> >> >> >>> -- >> >> >>> Cory Quammen >> >> >>> R&D Engineer >> >> >>> Kitware, Inc. >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> -- >> >> Cory Quammen >> >> R&D Engineer >> >> Kitware, Inc. >> > >> > >> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. > > -- Cory Quammen R&D Engineer Kitware, Inc. From chuck.atkins at kitware.com Tue Jul 19 13:40:27 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Tue, 19 Jul 2016 13:40:27 -0400 Subject: [Paraview-developers] Segfault opening ParaView on Ubuntu 14.04 In-Reply-To: References: Message-ID: Hi Sean, I ran in to this a few months ago. The best we could determine was that it was a bug in the AMD binary driver. The problem seems to be explicitly limited to the AMD binary + OpenGL2 backend. Can you try running the build you have against llvmpipe to confirm? ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Tue, Jul 12, 2016 at 10:24 AM, Shawn Waldon wrote: > Hi all, > > My laptop is running Ubuntu 14.04 with an ATI graphics card. I built > paraview master (with Qt5.6 if it matters) and it got as far as the splash > screen before segfaulting when I tried to run it. Here is a stack trace > from GDB [1]. I'm travelling right now, but I'll be back in time for the > hackathon tomorrow. Maybe we can look at it then. > > Shawn > > [1]: > Program received signal SIGSEGV, Segmentation fault. > 0x0000001500000001 in ?? () > (gdb) where > #0 0x0000001500000001 in ?? () > #1 0x00007fffe7d7f8cb in XQueryExtension () from > /usr/lib/x86_64-linux-gnu/libX11.so.6 > #2 0x00007fffe7d73be2 in XInitExtension () from > /usr/lib/x86_64-linux-gnu/libX11.so.6 > #3 0x00007fffdbb1789f in XextAddDisplay () from > /usr/lib/x86_64-linux-gnu/libXext.so.6 > #4 0x00007fffea35797a in ?? () from /usr/lib/fglrx/libGL.so.1 > #5 0x00007fffcf7d32cf in ?? () from /usr/lib/dri/fglrx_dri.so > #6 0x00007fffcf7c86d8 in driCreateContextAttribs () from > /usr/lib/dri/fglrx_dri.so > #7 0x00007fffea32b698 in ?? () from /usr/lib/fglrx/libGL.so.1 > #8 0x00007fffea32bf29 in glXCreateContextAttribsARB () from > /usr/lib/fglrx/libGL.so.1 > #9 0x00007fffe82f7908 in vtkXOpenGLRenderWindow::CreateAWindow > (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:599 > #10 0x00007fffe82f8bd3 in vtkXOpenGLRenderWindow::WindowInitialize > (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:976 > #11 0x00007fffe82f8ca7 in vtkXOpenGLRenderWindow::Initialize > (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:998 > #12 0x00007fffe82f90ed in vtkXOpenGLRenderWindow::Start (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:1125 > #13 0x00007ffff29f8df7 in vtkRenderWindow::DoStereoRender (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:748 > #14 0x00007ffff29f8dd0 in vtkRenderWindow::DoFDRender (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:737 > #15 0x00007ffff29f877c in vtkRenderWindow::DoAARender (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:616 > #16 0x00007ffff29f7d4b in vtkRenderWindow::Render (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:432 > #17 0x00007fffe8241180 in vtkOpenGLRenderWindow::Render (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:661 > #18 0x00007fffe82fbab5 in vtkXOpenGLRenderWindow::Render (this=0x2f54da0) > at > /home/shawn/dev/paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:1786 > #19 0x00007ffff38a16da in vtkPVRenderView::Render (this=0x2f01600, > interactive=false, > skip_rendering=false) > at > /home/shawn/dev/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:1506 > #20 0x00007ffff38a0d7f in vtkPVRenderView::StillRender (this=0x2f01600) > at > /home/shawn/dev/paraview/src/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:1345 > #21 0x00007fffee210ee8 in vtkPVRenderViewCommand (arlu=0x725860, > ob=0x2f01600, > method=0x2fbce59 "StillRender", msg=..., resultStream=...) > at Wrapping/ClientServer/vtkPVRenderViewClientServer.cxx:234 > #22 0x00007fffec9d3922 in vtkClientServerInterpreter::CallCommandFunction > (this=0x725860, > cname=0x7ffff3901752 "vtkPVRenderView", ptr=0x2f01600, > method=0x2fbce59 "StillRender", msg=..., > result=...) > at > /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:848 > #23 0x00007fffec9d210b in vtkClientServerInterpreter::ProcessCommandInvoke > (this=0x725860, css=..., > midx=0) > at > /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:437 > #24 0x00007fffec9d1663 in vtkClientServerInterpreter::ProcessOneMessage > (this=0x725860, css=..., > message=0) > at > /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:269 > #25 0x00007fffec9d14ed in vtkClientServerInterpreter::ProcessStream > (this=0x725860, css=...) > at > /home/shawn/dev/paraview/src/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:238 > #26 0x00007ffff2fa3f57 in vtkPVSessionCore::ExecuteStreamInternal > (this=0x741bb0, stream=..., > ignore_errors=false) > at > /home/shawn/dev/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:669 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jul 21 21:07:28 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 22 Jul 2016 01:07:28 +0000 Subject: [Paraview-developers] SuperBuild Message-ID: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> Well, I tried SuperBuild on the clusters, and failed. So, let's go back to the start. The default compilers on redsky and chama are intel. I do have gcc available. Which should I use? When I run the gcc compiler, the build fails trying to find libatomic. Here is the first failure: [ 82%] Built target visitbridge CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:296 (include) CMakeLists.txt:407 (include) -- Configuring incomplete, errors occurred! See also "/projects/viz/paraview/ParaView/5.1.1-sb-Mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeOutput.log". See also "/projects/viz/paraview/ParaView/5.1.1-sb-Mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeError.log". make[2]: *** [llvm/src/llvm-stamp/llvm-configure] Error 1 make[1]: *** [CMakeFiles/llvm.dir/all] Error 2 make: *** [all] Error 2 When I try building with the intel compiler, I fail much further along, with MPI. I get something about it not being able to figure out if it has MPI, then points to the MPI compiler here: redsky-login2:ParaView$ ls /opt/openmpi-1.8-intel/bin/mpicxx /opt/openmpi-1.8-intel/bin/mpicxx@ So, let's start with - what compiler should I be using? And, who is the right person to be bothering? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jul 21 21:37:10 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 22 Jul 2016 01:37:10 +0000 Subject: [Paraview-developers] [EXTERNAL] SuperBuild In-Reply-To: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> References: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> Message-ID: <14b7a9fe677848bcbcf71391b4033f81@ES01AMSNLNT.srn.sandia.gov> Woops. I inverted the compilers. First is with Intel (i.e., the libatomic), Second is gcc (i.e., trying to find mpicxx). Yes, with gcc I actually was looking for /opt/openmpi-1.8-gcc/bin/mpicxx, which does exist. Alan From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, July 21, 2016 7:07 PM To: Utkarsh Ayachit (utkarsh.ayachit at kitware.com) ; paraview-developers at paraview.org Subject: [EXTERNAL] [Paraview-developers] SuperBuild Well, I tried SuperBuild on the clusters, and failed. So, let's go back to the start. The default compilers on redsky and chama are intel. I do have gcc available. Which should I use? When I run the gcc compiler, the build fails trying to find libatomic. Here is the first failure: [ 82%] Built target visitbridge CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:296 (include) CMakeLists.txt:407 (include) -- Configuring incomplete, errors occurred! See also "/projects/viz/paraview/ParaView/5.1.1-sb-Mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeOutput.log". See also "/projects/viz/paraview/ParaView/5.1.1-sb-Mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeError.log". make[2]: *** [llvm/src/llvm-stamp/llvm-configure] Error 1 make[1]: *** [CMakeFiles/llvm.dir/all] Error 2 make: *** [all] Error 2 When I try building with the intel compiler, I fail much further along, with MPI. I get something about it not being able to figure out if it has MPI, then points to the MPI compiler here: redsky-login2:ParaView$ ls /opt/openmpi-1.8-intel/bin/mpicxx /opt/openmpi-1.8-intel/bin/mpicxx@ So, let's start with - what compiler should I be using? And, who is the right person to be bothering? Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Jul 22 10:01:52 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 22 Jul 2016 10:01:52 -0400 Subject: [Paraview-developers] SuperBuild In-Reply-To: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> References: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> Message-ID: > what compiler should I be using? gcc > And, who is the right person to be bothering? Let's stick with the mailing list. There are several folks here who routinely work on the the superbuild so collectively, we can work on the diagnosing the issue. Utkarsh From utkarsh.ayachit at kitware.com Fri Jul 22 10:02:36 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 22 Jul 2016 10:02:36 -0400 Subject: [Paraview-developers] [EXTERNAL] SuperBuild In-Reply-To: <14b7a9fe677848bcbcf71391b4033f81@ES01AMSNLNT.srn.sandia.gov> References: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> <14b7a9fe677848bcbcf71391b4033f81@ES01AMSNLNT.srn.sandia.gov> Message-ID: > libatomic), Second is gcc (i.e., trying to find mpicxx). Yes, with gcc I > actually was looking for /opt/openmpi-1.8-gcc/bin/mpicxx, which does exist. Can post the exact error message? Thanks. From sur.chiranjib at gmail.com Fri Jul 22 14:09:30 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Fri, 22 Jul 2016 23:39:30 +0530 Subject: [Paraview-developers] [EXTERNAL] SuperBuild In-Reply-To: References: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> <14b7a9fe677848bcbcf71391b4033f81@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi, One relevant question regarding the PV superbuild. I was trying to build OSPRay module in linux (MPI+qt4+python+zlib). In superbuild I chose the packages and tried NOT TO use any system installed package for the above. However, the build eneded up in errors. When I try to build normal paraview (same other software dependencies), everything works fine. Are there any special instructions for the OSPRay module (any other mandatory package that need to be installed etc.)? Thanks, Chiranjib On Fri, Jul 22, 2016 at 7:32 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > > libatomic), Second is gcc (i.e., trying to find mpicxx). Yes, with gcc I > > actually was looking for /opt/openmpi-1.8-gcc/bin/mpicxx, which does > exist. > > Can post the exact error message? Thanks. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Fri Jul 22 14:12:24 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 22 Jul 2016 14:12:24 -0400 Subject: [Paraview-developers] [EXTERNAL] SuperBuild In-Reply-To: References: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> <14b7a9fe677848bcbcf71391b4033f81@ES01AMSNLNT.srn.sandia.gov> Message-ID: Dave, can you respond to the OSPray queries please. You may want to start a new thread since it's a little unrelated to Alan's original question. I don't want the the thread to get more confusing. Thanks. Utkarsh On Fri, Jul 22, 2016 at 2:09 PM, Chiranjib Sur wrote: > Hi, > One relevant question regarding the PV superbuild. I was trying to build > OSPRay module in linux (MPI+qt4+python+zlib). In superbuild I chose the > packages and tried NOT TO use any system installed package for the above. > However, the build eneded up in errors. > > When I try to build normal paraview (same other software dependencies), > everything works fine. > > Are there any special instructions for the OSPRay module (any other > mandatory package that need to be installed etc.)? > > Thanks, > Chiranjib > > On Fri, Jul 22, 2016 at 7:32 PM, Utkarsh Ayachit > wrote: >> >> > libatomic), Second is gcc (i.e., trying to find mpicxx). Yes, with gcc >> > I >> > actually was looking for /opt/openmpi-1.8-gcc/bin/mpicxx, which does >> > exist. >> >> Can post the exact error message? Thanks. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > From wascott at sandia.gov Fri Jul 22 14:52:13 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 22 Jul 2016 18:52:13 +0000 Subject: [Paraview-developers] [EXTERNAL] SuperBuild In-Reply-To: References: <4d00283e58ad45a28602cebbb518312d@ES01AMSNLNT.srn.sandia.gov> <14b7a9fe677848bcbcf71391b4033f81@ES01AMSNLNT.srn.sandia.gov> Message-ID: Developer Error (i.e., my error). :-) I am now using the gcc compiler, and after getting my scripts worked out, I have good Superbuilds on client and cluster sides. Thanks all. Alan -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, July 22, 2016 12:12 PM To: Chiranjib Sur ; David E DeMarle Cc: Scott, W Alan ; paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] SuperBuild Dave, can you respond to the OSPray queries please. You may want to start a new thread since it's a little unrelated to Alan's original question. I don't want the the thread to get more confusing. Thanks. Utkarsh On Fri, Jul 22, 2016 at 2:09 PM, Chiranjib Sur wrote: > Hi, > One relevant question regarding the PV superbuild. I was trying to > build OSPRay module in linux (MPI+qt4+python+zlib). In superbuild I > chose the packages and tried NOT TO use any system installed package for the above. > However, the build eneded up in errors. > > When I try to build normal paraview (same other software > dependencies), everything works fine. > > Are there any special instructions for the OSPRay module (any other > mandatory package that need to be installed etc.)? > > Thanks, > Chiranjib > > On Fri, Jul 22, 2016 at 7:32 PM, Utkarsh Ayachit > wrote: >> >> > libatomic), Second is gcc (i.e., trying to find mpicxx). Yes, with >> > gcc I actually was looking for /opt/openmpi-1.8-gcc/bin/mpicxx, >> > which does exist. >> >> Can post the exact error message? Thanks. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > From sumeet.kumar507 at gmail.com Sun Jul 24 19:59:37 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Sun, 24 Jul 2016 16:59:37 -0700 Subject: [Paraview-developers] Segmentation Fault (core dumped) while reading HDF5 file in Reader Plugin in Paraview 5.1 Message-ID: I have compiled Paraview 5.1 in linux. I am currently developing a plugin for reading a hdf5 file. There is no error produced while compilation. I am linking hdf5 hdf5_c++. The plugin also loads successfully in Paraview. But when I open an hdf file it aborts with "Segmentation fault (core dump)" message. Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jul 25 08:41:07 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 25 Jul 2016 08:41:07 -0400 Subject: [Paraview-developers] Segmentation Fault (core dumped) while reading HDF5 file in Reader Plugin in Paraview 5.1 In-Reply-To: References: Message-ID: Sorry, there's not much information here to know what's going on. I'd suggest rebuilding both the plugin and ParaView in "debug" mode and then running the same through a debugger and seeing why and where it segfaults. On Sun, Jul 24, 2016 at 7:59 PM, sumeet kumar wrote: > I have compiled Paraview 5.1 in linux. I am currently developing a plugin > for reading a hdf5 file. > There is no error produced while compilation. I am linking hdf5 hdf5_c++. > > The plugin also loads successfully in Paraview. But when I open an hdf > file it aborts with "Segmentation fault (core dump)" message. > > > Sumeet > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Mon Jul 25 12:19:10 2016 From: dave.demarle at kitware.com (David E DeMarle) Date: Mon, 25 Jul 2016 12:19:10 -0400 Subject: [Paraview-developers] ParaView with OSPRay via super build : was Re: [EXTERNAL] SuperBuild Message-ID: Chiranjib, To build ParaView with OSPRay you need two things: 1) c++11 compiler flags 2) OSPRay version 0.10.0 or newer, which you can build or install. To build OSPRay you need to build or preferably install intel's ISPC compiler. The ParaView super build was updated before 5.1 to do all of the above automatically when you enable the OSPRay project. If you post the compilation errors, we can help more effectively. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Fri, Jul 22, 2016 at 2:09 PM, Chiranjib Sur wrote: > Hi, > One relevant question regarding the PV superbuild. I was trying to build > OSPRay module in linux (MPI+qt4+python+zlib). In superbuild I chose the > packages and tried NOT TO use any system installed package for the above. > However, the build eneded up in errors. > > When I try to build normal paraview (same other software dependencies), > everything works fine. > > Are there any special instructions for the OSPRay module (any other > mandatory package that need to be installed etc.)? > > Thanks, > Chiranjib > > On Fri, Jul 22, 2016 at 7:32 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> > libatomic), Second is gcc (i.e., trying to find mpicxx). Yes, with gcc >> I >> > actually was looking for /opt/openmpi-1.8-gcc/bin/mpicxx, which does >> exist. >> >> Can post the exact error message? Thanks. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Jul 25 14:58:37 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 25 Jul 2016 18:58:37 +0000 Subject: [Paraview-developers] Bad superbuild Message-ID: I am trying to build clusters (again) with the superbuild. This is Linux, master. I am using the gnu compiler and openmpi for gnu. I am having issues with MPI. I am trying to use a system installed MPI. Here is what I am sending to cmake: cMakeVars = -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sb-mesa/Linux-chama-x86_64 -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Debug -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5 -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON -DPARAVIEW_USE_MPI:BOOL=ON -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-gnu//include/ If anyone needs my CMakeCache.txt, please ask and I can send it off list. Here is my failure: [ 4%] Building C object VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtktiff.dir/tif_thunder.c.o CMakeFiles/IceTMPI.dir/mpi.c.o: In function `getMPIRequest': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:110: undefined reference to `ompi_request_null' /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:116: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `create_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:160: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `destroy_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:168: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `icetCreateMPICommunicator': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:200: undefined reference to `ompi_mpi_comm_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `MPISubset': Thanks all! Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Mon Jul 25 18:22:25 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Mon, 25 Jul 2016 15:22:25 -0700 Subject: [Paraview-developers] Segmentation Fault (core dumped) while reading HDF5 file in Reader Plugin in Paraview 5.1 In-Reply-To: References: Message-ID: Now, my problem got fixed. I was using C++ API for HDF5 file earlier. But when I changed my HDF5 API to C, there was no segmentation fault error. May be, Paraview supports C API for HDF5. Thanks Sumeet On Mon, Jul 25, 2016 at 5:41 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Sorry, there's not much information here to know what's going on. I'd > suggest rebuilding both the plugin and ParaView in "debug" mode and then > running the same through a debugger and seeing why and where it segfaults. > > On Sun, Jul 24, 2016 at 7:59 PM, sumeet kumar > wrote: > >> I have compiled Paraview 5.1 in linux. I am currently developing a plugin >> for reading a hdf5 file. >> There is no error produced while compilation. I am linking hdf5 hdf5_c++. >> >> The plugin also loads successfully in Paraview. But when I open an hdf >> file it aborts with "Segmentation fault (core dump)" message. >> >> >> Sumeet >> >> -- >> >> Sumeet Kumar Sinha >> Graduate Student >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> Website : http://www.sumeetsinha.in/ >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Jul 25 19:54:04 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 25 Jul 2016 23:54:04 +0000 Subject: [Paraview-developers] superbuild again on intel compilers on Linux cluster Message-ID: I am also trying to do Intel superbuilds on a Linux, Intel compiler, as we will have to do for Trinity. We are failing trying to find libatomic - a gnu library! That shouldn't happen, I would figure. Anyway, here is where I ended up: cMakeVars = -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64 -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Release -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sbi/ParaView5 -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-intel//bin/mpicxx -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON -DPARAVIEW_USE_MPI:BOOL=ON -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-intel//include/ -- Using git-describe to determine ParaView version -- Could not use git to determine source version, using version -- Using ParaView Version: 5.1.0 (5|1|0|) -- Using system EGL. Pick correct python based on your deployment target -- Enabling zlib since needed by: boost;cgns;ffmpeg;hdf5;png;python;silo -- Enabling szip since needed by: hdf5 -- Enabling hdf5 since needed by: cgns;silo -- Enabling cgns as requested. -- Enabling ffmpeg as requested. -- Enabling mpi as requested. -- Enabling bzip2 since needed by: python -- Enabling png as requested. -- Enabling python as requested. -- Enabling numpy as requested. -- Enabling llvm since needed by: osmesa -- Enabling osmesa as requested. -- Enabling boost since needed by: visitbridge -- Enabling silo as requested. -- Enabling visitbridge as requested. -- Enabling paraview as requested. -- PROJECTS_ENABLED zlib;szip;hdf5;cgns;ffmpeg;mpi;bzip2;png;python;numpy;llvm;osmesa;boost;silo;visitbridge;paraview -- Configuring done -- Generating done -- Build files have been written to: /projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build [ 7%] Built target zlib [ 14%] Built target szip [ 20%] Built target hdf5 [ 27%] Built target cgns [ 33%] Built target boost [ 39%] Built target ffmpeg [ 45%] Built target silo [ 51%] Built target visitbridge [ 57%] Built target png [ 63%] Built target bzip2 [ 70%] Built target python [ 76%] Built target mpi [ 82%] Built target numpy [ 83%] Performing configure step for 'llvm' CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:296 (include) CMakeLists.txt:407 (include) -- Configuring incomplete, errors occurred! See also "/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeOutput.log". See also "/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeError.log". make[2]: *** [llvm/src/llvm-stamp/llvm-configure] Error 1 make[1]: *** [CMakeFiles/llvm.dir/all] Error 2 Thanks for any help, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Mon Jul 25 21:15:44 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 25 Jul 2016 21:15:44 -0400 Subject: [Paraview-developers] superbuild again on intel compilers on Linux cluster In-Reply-To: References: Message-ID: Hi Alan, This is a known problem with C++11 compatibility and the Intel compiler. Intel's C++ compiler provides the necessary language features for C++ 11 but does not provide any of the standard C++ library headers for it. Instead it pulls headers from an available g++. If a new enough g++ is not used for the headers then you end up with a very strange situation of half broken C++11 support with language support but no library support. To make matters worse, different versions of icpc are (in)compatible with different versions of g++ headers. You can fix it by changing which g++ icpc is using to get the correct C++11 support using the GCCROOT, GXX_INCLUDE, and GXX_ROOT environment variables. If none of the variables are specified then it will be pulling C++ headers from your available system compiler, which on EL6 is gcc 4.4 which definitely does not have the necessary C++11 support. Intel <= 16.0.2 should work correctly with g++ 4.8.x and 4.9.x headers while >= 16.0.3 should work with g++ 4.8.x all the way through 5.x. This will also be an issue for anybody else trying to use C++11 and icpc to get complete support. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 7:54 PM, Scott, W Alan wrote: > I am also trying to do Intel superbuilds on a Linux, Intel compiler, as we > will have to do for Trinity. We are failing trying to find libatomic ? a > gnu library! That shouldn?t happen, I would figure. Anyway, here is where > I ended up: > > > > cMakeVars = > -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64 > -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Release > -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON > -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sbi/ParaView5 > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON > -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON > -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON > -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON > -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-intel//bin/mpicxx > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON > -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-intel//include/ > > > > -- Using git-describe to determine ParaView version > > -- Could not use git to determine source version, using version > > -- Using ParaView Version: 5.1.0 (5|1|0|) > > -- Using system EGL. Pick correct python based on your deployment target > > -- Enabling zlib since needed by: boost;cgns;ffmpeg;hdf5;png;python;silo > > -- Enabling szip since needed by: hdf5 > > -- Enabling hdf5 since needed by: cgns;silo > > -- Enabling cgns as requested. > > -- Enabling ffmpeg as requested. > > -- Enabling mpi as requested. > > -- Enabling bzip2 since needed by: python > > -- Enabling png as requested. > > -- Enabling python as requested. > > -- Enabling numpy as requested. > > -- Enabling llvm since needed by: osmesa > > -- Enabling osmesa as requested. > > -- Enabling boost since needed by: visitbridge > > -- Enabling silo as requested. > > -- Enabling visitbridge as requested. > > -- Enabling paraview as requested. > > -- PROJECTS_ENABLED > zlib;szip;hdf5;cgns;ffmpeg;mpi;bzip2;png;python;numpy;llvm;osmesa;boost;silo;visitbridge;paraview > > -- Configuring done > > -- Generating done > > -- Build files have been written to: > /projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build > > [ 7%] Built target zlib > > [ 14%] Built target szip > > [ 20%] Built target hdf5 > > [ 27%] Built target cgns > > [ 33%] Built target boost > > [ 39%] Built target ffmpeg > > [ 45%] Built target silo > > [ 51%] Built target visitbridge > > [ 57%] Built target png > > [ 63%] Built target bzip2 > > [ 70%] Built target python > > [ 76%] Built target mpi > > [ 82%] Built target numpy > > [ 83%] Performing configure step for 'llvm' > > CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): > > Host compiler appears to require libatomic, but cannot find it. > > Call Stack (most recent call first): > > cmake/config-ix.cmake:296 (include) > > CMakeLists.txt:407 (include) > > > > > > -- Configuring incomplete, errors occurred! > > See also > "/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeOutput.log". > > See also > "/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeError.log". > > make[2]: *** [llvm/src/llvm-stamp/llvm-configure] Error 1 > > make[1]: *** [CMakeFiles/llvm.dir/all] Error 2 > > > > > > Thanks for any help, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Jul 25 21:19:00 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 26 Jul 2016 01:19:00 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: superbuild again on intel compilers on Linux cluster In-Reply-To: References: Message-ID: <7ecef633863b4e448a29c7cf816e8814@ES01AMSNLNT.srn.sandia.gov> Excellent, thanks! I?ll let you know if it works. From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Monday, July 25, 2016 7:16 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] superbuild again on intel compilers on Linux cluster Hi Alan, This is a known problem with C++11 compatibility and the Intel compiler. Intel's C++ compiler provides the necessary language features for C++ 11 but does not provide any of the standard C++ library headers for it. Instead it pulls headers from an available g++. If a new enough g++ is not used for the headers then you end up with a very strange situation of half broken C++11 support with language support but no library support. To make matters worse, different versions of icpc are (in)compatible with different versions of g++ headers. You can fix it by changing which g++ icpc is using to get the correct C++11 support using the GCCROOT, GXX_INCLUDE, and GXX_ROOT environment variables. If none of the variables are specified then it will be pulling C++ headers from your available system compiler, which on EL6 is gcc 4.4 which definitely does not have the necessary C++11 support. Intel <= 16.0.2 should work correctly with g++ 4.8.x and 4.9.x headers while >= 16.0.3 should work with g++ 4.8.x all the way through 5.x. This will also be an issue for anybody else trying to use C++11 and icpc to get complete support. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 7:54 PM, Scott, W Alan > wrote: I am also trying to do Intel superbuilds on a Linux, Intel compiler, as we will have to do for Trinity. We are failing trying to find libatomic ? a gnu library! That shouldn?t happen, I would figure. Anyway, here is where I ended up: cMakeVars = -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64 -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Release -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sbi/ParaView5 -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-intel//bin/mpicxx -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON -DPARAVIEW_USE_MPI:BOOL=ON -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-intel//include/ -- Using git-describe to determine ParaView version -- Could not use git to determine source version, using version -- Using ParaView Version: 5.1.0 (5|1|0|) -- Using system EGL. Pick correct python based on your deployment target -- Enabling zlib since needed by: boost;cgns;ffmpeg;hdf5;png;python;silo -- Enabling szip since needed by: hdf5 -- Enabling hdf5 since needed by: cgns;silo -- Enabling cgns as requested. -- Enabling ffmpeg as requested. -- Enabling mpi as requested. -- Enabling bzip2 since needed by: python -- Enabling png as requested. -- Enabling python as requested. -- Enabling numpy as requested. -- Enabling llvm since needed by: osmesa -- Enabling osmesa as requested. -- Enabling boost since needed by: visitbridge -- Enabling silo as requested. -- Enabling visitbridge as requested. -- Enabling paraview as requested. -- PROJECTS_ENABLED zlib;szip;hdf5;cgns;ffmpeg;mpi;bzip2;png;python;numpy;llvm;osmesa;boost;silo;visitbridge;paraview -- Configuring done -- Generating done -- Build files have been written to: /projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build [ 7%] Built target zlib [ 14%] Built target szip [ 20%] Built target hdf5 [ 27%] Built target cgns [ 33%] Built target boost [ 39%] Built target ffmpeg [ 45%] Built target silo [ 51%] Built target visitbridge [ 57%] Built target png [ 63%] Built target bzip2 [ 70%] Built target python [ 76%] Built target mpi [ 82%] Built target numpy [ 83%] Performing configure step for 'llvm' CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:296 (include) CMakeLists.txt:407 (include) -- Configuring incomplete, errors occurred! See also "/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeOutput.log". See also "/projects/viz/paraview/ParaView/5.1.1-sbi-mesa/Linux-chama-x86_64/Build/llvm/src/llvm-build/CMakeFiles/CMakeError.log". make[2]: *** [llvm/src/llvm-stamp/llvm-configure] Error 1 make[1]: *** [CMakeFiles/llvm.dir/all] Error 2 Thanks for any help, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Mon Jul 25 21:20:00 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 25 Jul 2016 21:20:00 -0400 Subject: [Paraview-developers] Bad superbuild In-Reply-To: References: Message-ID: Hi Alan, The FindMPI module can be sensitive to an enormous number of settings. Do you have openmpi loaded as an environment module? If so, I would get rid of any -DMPI_FOO variables from the CMake configure line and just let the FindMPI.cmake module do it's thing. If the MPI compiler wrappers are in your PATH then it should be able to interrogate them correctly. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 2:58 PM, Scott, W Alan wrote: > I am trying to build clusters (again) with the superbuild. This is Linux, > master. I am using the gnu compiler and openmpi for gnu. I am having > issues with MPI. I am trying to use a system installed MPI. > > > > Here is what I am sending to cmake: > > cMakeVars = > -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sb-mesa/Linux-chama-x86_64 > -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Debug > -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON > -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5 > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON > -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON > -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON > -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON > -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON > -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-gnu//include/ > > > > > > > > > > If anyone needs my CMakeCache.txt, please ask and I can send it off list. > > > > Here is my failure: > > > > [ 4%] Building C object > VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtktiff.dir/tif_thunder.c.o > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `getMPIRequest': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:110: > undefined reference to `ompi_request_null' > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:116: > undefined reference to `ompi_request_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `create_request': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:160: > undefined reference to `ompi_request_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `destroy_request': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:168: > undefined reference to `ompi_request_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `icetCreateMPICommunicator': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:200: > undefined reference to `ompi_mpi_comm_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `MPISubset': > > > > Thanks all! > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Mon Jul 25 21:24:16 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 26 Jul 2016 01:24:16 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Bad superbuild In-Reply-To: References: Message-ID: So, let me ask this. Should I not point at MPI at all through CMake vars, but just point the PATH including the MPI compiler? Alan From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Monday, July 25, 2016 7:20 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Bad superbuild Hi Alan, The FindMPI module can be sensitive to an enormous number of settings. Do you have openmpi loaded as an environment module? If so, I would get rid of any -DMPI_FOO variables from the CMake configure line and just let the FindMPI.cmake module do it's thing. If the MPI compiler wrappers are in your PATH then it should be able to interrogate them correctly. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 2:58 PM, Scott, W Alan > wrote: I am trying to build clusters (again) with the superbuild. This is Linux, master. I am using the gnu compiler and openmpi for gnu. I am having issues with MPI. I am trying to use a system installed MPI. Here is what I am sending to cmake: cMakeVars = -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sb-mesa/Linux-chama-x86_64 -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Debug -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5 -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON -DPARAVIEW_USE_MPI:BOOL=ON -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-gnu//include/ If anyone needs my CMakeCache.txt, please ask and I can send it off list. Here is my failure: [ 4%] Building C object VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtktiff.dir/tif_thunder.c.o CMakeFiles/IceTMPI.dir/mpi.c.o: In function `getMPIRequest': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:110: undefined reference to `ompi_request_null' /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:116: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `create_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:160: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `destroy_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:168: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `icetCreateMPICommunicator': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:200: undefined reference to `ompi_mpi_comm_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `MPISubset': Thanks all! Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Mon Jul 25 21:35:18 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Mon, 25 Jul 2016 21:35:18 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Bad superbuild In-Reply-To: References: Message-ID: Yes, that's generally the most reliable way to get the correct and complete MPI support. I suspect the FindMPI module was getting half-baked information from the wrappers and augmenting with the specified MPI_INCLUDE_PATH. If you don't want it in the environment then I would try explicitly setting the compiler wrappers and nothing else with: -DMPI_C_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicc -DMPI_CXX_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx and drop any other MPI_FOO vars, leaving the FindMPI module interrogate the wrappers to populate the rest. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 9:24 PM, Scott, W Alan wrote: > So, let me ask this. Should I not point at MPI at all through CMake vars, > but just point the PATH including the MPI compiler? > > > > Alan > > > > > > > > *From:* Chuck Atkins [mailto:chuck.atkins at kitware.com] > *Sent:* Monday, July 25, 2016 7:20 PM > *To:* Scott, W Alan > *Cc:* paraview-developers at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview-developers] Bad superbuild > > > > Hi Alan, > The FindMPI module can be sensitive to an enormous number of settings. Do > you have openmpi loaded as an environment module? If so, I would get rid > of any -DMPI_FOO variables from the CMake configure line and just let the > FindMPI.cmake module do it's thing. If the MPI compiler wrappers are in > your PATH then it should be able to interrogate them correctly. > > > ---------- > Chuck Atkins > Staff R&D Engineer, Scientific Computing > Kitware, Inc. > (518) 881-1183 > > > > On Mon, Jul 25, 2016 at 2:58 PM, Scott, W Alan wrote: > > I am trying to build clusters (again) with the superbuild. This is Linux, > master. I am using the gnu compiler and openmpi for gnu. I am having > issues with MPI. I am trying to use a system installed MPI. > > > > Here is what I am sending to cmake: > > cMakeVars = > -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sb-mesa/Linux-chama-x86_64 > -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Debug > -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON > -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5 > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON > -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON > -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON > -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON > -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON > -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-gnu//include/ > > > > > > > > > > If anyone needs my CMakeCache.txt, please ask and I can send it off list. > > > > Here is my failure: > > > > [ 4%] Building C object > VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtktiff.dir/tif_thunder.c.o > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `getMPIRequest': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:110: > undefined reference to `ompi_request_null' > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:116: > undefined reference to `ompi_request_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `create_request': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:160: > undefined reference to `ompi_request_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `destroy_request': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:168: > undefined reference to `ompi_request_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `icetCreateMPICommunicator': > > /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:200: > undefined reference to `ompi_mpi_comm_null' > > CMakeFiles/IceTMPI.dir/mpi.c.o: In function `MPISubset': > > > > Thanks all! > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jul 25 21:36:02 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 25 Jul 2016 21:36:02 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Bad superbuild In-Reply-To: References: Message-ID: > So, let me ask this. Should I not point at MPI at all through CMake vars, but just point the PATH including the MPI compiler? The problem is that you're not using the right/new variables and hence FindMPI is not working. To avoid running into that pitfalls, Chuck's suggestion works. In general, nothing wrong with setting the MPI_* flags. If FindMPI has issues finding MPI compilers using the environment, then often just setting following variables should suffice: * MPI_C_COMPILER : path to mpicc * MPI_CXX_COMPILER : path to mpicxx FindMPI can then query these compilers to determine the other variables, like include dirs etc. Note, don't mix up the MPI_C_COMPILER and MPI_CXX_COMPILER, one is for C code, while the other is for C++ code. Utkarsh From wascott at sandia.gov Mon Jul 25 21:43:34 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 26 Jul 2016 01:43:34 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Bad superbuild In-Reply-To: References: Message-ID: Mind taking a look at the Wiki, under Build and Install? The section on ParaView Settings is confusing. Further, the flags for the MPI_*_COMPILER are a actually different thatn you have here. http://www.paraview.org/Wiki/ParaView:Build_And_Install#ParaView_Settings Thanks, alan From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Monday, July 25, 2016 7:35 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview-developers] Bad superbuild Yes, that's generally the most reliable way to get the correct and complete MPI support. I suspect the FindMPI module was getting half-baked information from the wrappers and augmenting with the specified MPI_INCLUDE_PATH. If you don't want it in the environment then I would try explicitly setting the compiler wrappers and nothing else with: -DMPI_C_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicc -DMPI_CXX_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx and drop any other MPI_FOO vars, leaving the FindMPI module interrogate the wrappers to populate the rest. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 9:24 PM, Scott, W Alan > wrote: So, let me ask this. Should I not point at MPI at all through CMake vars, but just point the PATH including the MPI compiler? Alan From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Monday, July 25, 2016 7:20 PM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Bad superbuild Hi Alan, The FindMPI module can be sensitive to an enormous number of settings. Do you have openmpi loaded as an environment module? If so, I would get rid of any -DMPI_FOO variables from the CMake configure line and just let the FindMPI.cmake module do it's thing. If the MPI compiler wrappers are in your PATH then it should be able to interrogate them correctly. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 2:58 PM, Scott, W Alan > wrote: I am trying to build clusters (again) with the superbuild. This is Linux, master. I am using the gnu compiler and openmpi for gnu. I am having issues with MPI. I am trying to use a system installed MPI. Here is what I am sending to cmake: cMakeVars = -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sb-mesa/Linux-chama-x86_64 -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Debug -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5 -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON -DPARAVIEW_USE_MPI:BOOL=ON -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-gnu//include/ If anyone needs my CMakeCache.txt, please ask and I can send it off list. Here is my failure: [ 4%] Building C object VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtktiff.dir/tif_thunder.c.o CMakeFiles/IceTMPI.dir/mpi.c.o: In function `getMPIRequest': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:110: undefined reference to `ompi_request_null' /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:116: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `create_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:160: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `destroy_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:168: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `icetCreateMPICommunicator': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:200: undefined reference to `ompi_mpi_comm_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `MPISubset': Thanks all! Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Jul 26 12:37:21 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 26 Jul 2016 12:37:21 -0400 Subject: [Paraview-developers] Bad superbuild In-Reply-To: References: Message-ID: <20160726163721.GA8159@rotor.kitware.com> On Mon, Jul 25, 2016 at 18:58:37 +0000, Scott, W Alan wrote: > I am trying to build clusters (again) with the superbuild. This is > Linux, master. I am using the gnu compiler and openmpi for gnu. I am > having issues with MPI. I am trying to use a system installed MPI. > > Here is what I am sending to cmake: > cMakeVars = > -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sb-mesa/Linux-chama-x86_64 > -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Debug > -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON > -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5 > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON > -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON > -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON > -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON > -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx > -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON > -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-gnu//include/ It looks like you forgot to pass USE_SYSTEM_mpi=ON, so it is building its own MPI rather than the one you told it about. Do you see MPI bits in the install/ directory? If so, it's not using the MPI you want. --Ben From utkarsh.ayachit at kitware.com Tue Jul 26 16:04:04 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 26 Jul 2016 16:04:04 -0400 Subject: [Paraview-developers] ANN: ParaView 5.1.2 tagged Message-ID: Folks, ParaView 5.1.2 has been tagged. Git tag name: v5.1.2 Source tar/zip files are available for download: http://www.paraview.org/download/ Binaries will be available for testing within the next few days. This release includes the following fixes: - Fixed depth peeling issues when running in client-server mode with remote rendering - Fixed depth peeling issues with multiple contexts. - Fix Exodus reader issues when dealing with datasets with no timesteps. - Reduce required CMake version to 3.3 - Fixes BUG #0016766. The "?" button was not working. - Expose option to select number of ghost levels in "Ghost Cells Generator" filter - Cinema specB revolved around origin, not the data centroid. Fixed that. - Adding in a Catalyst example for the new zero-copy array class. - Fixing Examples/Catalyst/PythonFullExample when running with pvpython - Update QtTesting to get fixes for context menu in tree view - Update VTK for GDAL Reader fixes (vtk/vtk!1575) - The ParaView Team From sumeet.kumar507 at gmail.com Tue Jul 26 19:49:15 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 26 Jul 2016 16:49:15 -0700 Subject: [Paraview-developers] Visualizing field data on 3D Delaunchy generated mesh from points Message-ID: I have a collection of points with their coordinates. Each point have certain field ( let say scalar, vector or tensor associated with it). I am currently using delaunchy 3D filter to create a 3D mesh and it works fine. But next what I want is to visualize the data I had on the nodes. How can I achieve this in Paraview. No field data appears on the delaunchy #D generated mesh. Also, when I change my time step, the filter again creates a Delaunchy 3D mesh. Is there any way to tell the algorithm generate the mesh only once and utilize it for other steps. Please note that, the number of nodes and their coordinates are not changing with time. Thanks Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From furutaka.kazuyoshi at jaea.go.jp Tue Jul 26 21:17:32 2016 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Wed, 27 Jul 2016 10:17:32 +0900 (JST) Subject: [Paraview-developers] [Paraview] ANN: ParaView 5.1.2 tagged In-Reply-To: References: Message-ID: <20160727.101732.9146558100445296.furutaka.kazuyoshi@jaea.go.jp> From: Utkarsh Ayachit Subject: [Paraview] ANN: ParaView 5.1.2 tagged Date: Tue, 26 Jul 2016 16:04:04 -0400 > ParaView 5.1.2 has been tagged. > > Git tag name: v5.1.2 > > Source tar/zip files are available for download: > http://www.paraview.org/download/ CMake failed the configuration on fedora 24 linux x86_64... Kazuyoshi CMake Error at VTK/CMake/vtkCompilerExtras.cmake:47 (if): if given arguments: "cc: error: ARGS: No such file or directory cc (GCC) 6.1.1 20160621 (Red Hat 6.1.1-3) Copyright (C) 2016 Free Software Foundation, Inc. This is free software" " see the source for copying conditions. There is NO warranty" " not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. " "VERSION_GREATER" "4.2.0" "AND" "BUILD_SHARED_LIBS" "AND" "HAVE_GCC_VISIBILITY" "AND" "VTK_USE_GCC_VISIBILITY" "AND" "NOT" "MINGW" "AND" "NOT" "CYGWIN" Unknown arguments specified Call Stack (most recent call first): VTK/CMakeLists.txt:282 (include) -- Configuring incomplete, errors occurred! See also "/home/furutaka/work/ParaView/ParaView-bld-v5.1.2/CMakeFiles/CMakeOutput.log". See also "/home/furutaka/work/ParaView/ParaView-bld-v5.1.2/CMakeFiles/CMakeError.log". -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From furutaka.kazuyoshi at jaea.go.jp Tue Jul 26 22:13:00 2016 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Wed, 27 Jul 2016 11:13:00 +0900 (JST) Subject: [Paraview-developers] [Paraview] ANN: ParaView 5.1.2 tagged In-Reply-To: <20160727.101732.9146558100445296.furutaka.kazuyoshi@jaea.go.jp> References: <20160727.101732.9146558100445296.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20160727.111300.2279717469396705203.furutaka.kazuyoshi@jaea.go.jp> From: Kazuyoshi Furutaka Subject: Re: [Paraview] ANN: ParaView 5.1.2 tagged Date: Wed, 27 Jul 2016 10:17:32 +0900 (JST) > CMake failed the configuration on fedora 24 linux x86_64... Sorry for the noise... After fetching (instead of pulling) from the repo, the configuration was successful... Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From cory.quammen at kitware.com Tue Jul 26 23:25:47 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 26 Jul 2016 23:25:47 -0400 Subject: [Paraview-developers] Visualizing field data on 3D Delaunchy generated mesh from points In-Reply-To: References: Message-ID: Sumeet, Hmm, Delaunay 3D should pass the point data arrays on to the output. Here is an example pipeline where this works: Point source: Number of Points, 100; Radius, 1 Calculator: Expression, "coordsX", Result Array Name, "X" Delaunay 3D The output of Delaunay 3D contains the X array. As for creating the Delaunay 3D output just once, I would create the mesh from one of your time steps one time and save it out as a .vtu file. Next, when you are creating your animation, just load your point files as before along with the .vtu file. To associate the data from each time step on the mesh, use the Resample with Dataset filter. Set the Delaunay 3D mesh as the Source and the time-varying data as the Input. The Input point data will now be "attached" to the Delaunay 3D output mesh, and you should be able to visualize it. HTH, Cory On Tue, Jul 26, 2016 at 7:49 PM, sumeet kumar wrote: > I have a collection of points with their coordinates. Each point have > certain field ( let say scalar, vector or tensor associated with it). I am > currently using delaunchy 3D filter to create a 3D mesh and it works fine. > > But next what I want is to visualize the data I had on the nodes. How can > I achieve this in Paraview. No field data appears on the delaunchy #D > generated mesh. > > Also, when I change my time step, the filter again creates a Delaunchy 3D > mesh. Is there any way to tell the algorithm generate the mesh only once > and utilize it for other steps. Please note that, the number of nodes and > their coordinates are not changing with time. > > Thanks > Sumeet > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Wed Jul 27 01:09:58 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Tue, 26 Jul 2016 22:09:58 -0700 Subject: [Paraview-developers] Visualizing field data on 3D Delaunchy generated mesh from points In-Reply-To: References: Message-ID: Hey Cory, Thank you, for giving an excellent well explained answer. Your demonstration with the little example was very useful and it did all what I wanted. I have some more questions for you. It would really nice if you could help with me these questions also, *Background : *I basically am currently developing visualization tool (reader plugin) for a structural FEM software my research team is developing. Usually the mesh are big and sometimes complicated. I am using Delauncy3D to generate a mesh for my given gauss points. For simple examples, it works great. But for bigger meshes with smaller mesh size (smaller elements) it shows a warning message as bellow [image: Inline image 1] I think this warning messages comes if two point are very close. This warning results in some wrong mesh generation in areas where mesh sizes are small (or points are closer). My question is that 1. Can I somehow avoid and fix this situation. 2. Another question is not related to Delaunchy3D, but to the data visualization. When I visualize my data for different time steps, the field data bounds (upper and lower bounds) remains fixed. I want that the bounds to automatically change for each time_step by automatically finding out the maximum and minimum value of the field data, so that I can see the field_data variation over my model. Best Sumeet On Tue, Jul 26, 2016 at 8:25 PM, Cory Quammen wrote: > Sumeet, > > Hmm, Delaunay 3D should pass the point data arrays on to the output. Here > is an example pipeline where this works: > > Point source: Number of Points, 100; Radius, 1 > Calculator: Expression, "coordsX", Result Array Name, "X" > Delaunay 3D > > The output of Delaunay 3D contains the X array. > > As for creating the Delaunay 3D output just once, I would create the mesh > from one of your time steps one time and save it out as a .vtu file. Next, > when you are creating your animation, just load your point files as before > along with the .vtu file. To associate the data from each time step on the > mesh, use the Resample with Dataset filter. Set the Delaunay 3D mesh as the > Source and the time-varying data as the Input. The Input point data will > now be "attached" to the Delaunay 3D output mesh, and you should be able to > visualize it. > > HTH, > Cory > > On Tue, Jul 26, 2016 at 7:49 PM, sumeet kumar > wrote: > >> I have a collection of points with their coordinates. Each point have >> certain field ( let say scalar, vector or tensor associated with it). I am >> currently using delaunchy 3D filter to create a 3D mesh and it works fine. >> >> But next what I want is to visualize the data I had on the nodes. How can >> I achieve this in Paraview. No field data appears on the delaunchy #D >> generated mesh. >> >> Also, when I change my time step, the filter again creates a Delaunchy 3D >> mesh. Is there any way to tell the algorithm generate the mesh only once >> and utilize it for other steps. Please note that, the number of nodes and >> their coordinates are not changing with time. >> >> Thanks >> Sumeet >> >> -- >> >> Sumeet Kumar Sinha >> Graduate Student >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> Website : http://www.sumeetsinha.in/ >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > > > -- > Cory Quammen > R&D Engineer > Kitware, Inc. > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 30527 bytes Desc: not available URL: From jfavre at cscs.ch Wed Jul 27 05:41:16 2016 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 27 Jul 2016 09:41:16 +0000 Subject: [Paraview-developers] time-dependent output in programmable source Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68436698D2@MBX211.d.ethz.ch> hi there I have a time-dependent python programmable source. Once run, the Information view tab shows the two-column output with indices and values. The first problem I see, is that I give exact values, and the GUI gives me floating point values that are not exact: for example: timesteps = (0.,0.05, 0.1, 0.15, 0.2, 0.25, 0.3, 0.35) outInfo.Remove(executive.TIME_STEPS()) for timestep in timesteps: outInfo.Append(executive.TIME_STEPS(), timestep) outInfo.Remove(executive.TIME_RANGE()) outInfo.Append(executive.TIME_RANGE(), timesteps[0]) outInfo.Append(executive.TIME_RANGE(), timesteps[-1]) and the GUI shows the following Values: 0 0.05000 0.010000...1 0.149999999 0.200000...1 0.25 0.29999999 0.34999999 the next problem is the VCR Controls; if I mouse-over the Last Frame button, it correctly shows "0.35", but the Time display shows "0.349999". That's annoying. the real problem is that using the Play button, the executive does not iterate through the timesteps values I have advertized, but rather, it iterates through the following values: ts = 0.0388888888889 ts = 0.0777777777778 ts = 0.116666666667 ts = 0.155555555556 ts = 0.194444444444 ts = 0.233333333333 ts = 0.272222222222 ts = 0.311111111111 ts = 0.35 My understanding is that the VCR controls uses a fixed number of timesteps, and does an interpolation from the minimum time value to the maximum time values. Indeed, if I now augment the number of timestes my programmable source is capable of producing, for example: timesteps = (0.,0.05, 0.1, 0.15, 0.2, 0.25, 0.3, 0.35, 0.4, 0.45, 0.5, 0.55) for timestep in timesteps: outInfo.Append(executive.TIME_STEPS(), timestep) When using the Play button of the VCR controls, it requests the following times: ts = 0.0611111111111 ts = 0.122222222222 ts = 0.183333333333 ts = 0.244444444444 ts = 0.305555555556 ts = 0.366666666667 ts = 0.427777777778 ts = 0.488888888889 ts = 0.55 so, it seems like it always produces 9 timestep requests, instead of what the reader advertizes. Playing with a different set of timesteps values, it seems like the VCR always calculates (maxTime - minTime)/(10-1) for the time increment. I don't feel like this should be the accepted behaviour for the VCR controls. Am I missing some python code? I have followed Chapter 13 of the User Guide. I have attached the full python code. This is version 5.1.2. Jean/CSCS -------------- next part -------------- A non-text attachment was scrubbed... Name: TS.0.py Type: application/x-download Size: 2126 bytes Desc: TS.0.py URL: From cory.quammen at kitware.com Wed Jul 27 10:15:03 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 27 Jul 2016 10:15:03 -0400 Subject: [Paraview-developers] Visualizing field data on 3D Delaunchy generated mesh from points In-Reply-To: References: Message-ID: On Wed, Jul 27, 2016 at 1:09 AM, sumeet kumar wrote: > Hey Cory, > > Thank you, for giving an excellent well explained answer. Your > demonstration with the little example was very useful and it did all what I > wanted. > > > I have some more questions for you. It would really nice if you could > help with me these questions also, > > *Background : *I basically am currently developing visualization tool > (reader plugin) for a structural FEM software my research team is > developing. Usually the mesh are big and sometimes complicated. > > I am using Delauncy3D to generate a mesh for my given gauss points. For > simple examples, it works great. But for bigger meshes with smaller mesh > size (smaller elements) it shows a warning message as bellow > > [image: Inline image 1] > > I think this warning messages comes if two point are very close. This > warning results in some wrong mesh generation in areas where mesh sizes are > small (or points are closer). My question is that > > 1. Can I somehow avoid and fix this situation. > > I suspect you are right about the problem coming from two points being very close. Geometry algorithms are always tricky to make work in all cases and Delaunay 3D is no exception. Maybe you could try the Clean filter to merge nearby points? Bump up the tolerance if you keep having issues. It's not a perfect solution, but better than nothing. > > 1. Another question is not related to Delaunchy3D, but to the data > visualization. When I visualize my data for different time steps, the field > data bounds (upper and lower bounds) remains fixed. I want that the bounds > to automatically change for each time_step by automatically finding out the > maximum and minimum value of the field data, so that I can see the > field_data variation over my model. > > I assume you are talking about the range of the color legend? If so, go to Edit -> Settings (ParaView -> Preferences on Mac), make sure the General tab is selected. Under the Transfer Function Reset Mode, choose "Grow and update every time step". This should do what you want. HTH, Cory > > 1. > > Best > > Sumeet > > On Tue, Jul 26, 2016 at 8:25 PM, Cory Quammen > wrote: > >> Sumeet, >> >> Hmm, Delaunay 3D should pass the point data arrays on to the output. Here >> is an example pipeline where this works: >> >> Point source: Number of Points, 100; Radius, 1 >> Calculator: Expression, "coordsX", Result Array Name, "X" >> Delaunay 3D >> >> The output of Delaunay 3D contains the X array. >> >> As for creating the Delaunay 3D output just once, I would create the mesh >> from one of your time steps one time and save it out as a .vtu file. Next, >> when you are creating your animation, just load your point files as before >> along with the .vtu file. To associate the data from each time step on the >> mesh, use the Resample with Dataset filter. Set the Delaunay 3D mesh as the >> Source and the time-varying data as the Input. The Input point data will >> now be "attached" to the Delaunay 3D output mesh, and you should be able to >> visualize it. >> >> HTH, >> Cory >> >> On Tue, Jul 26, 2016 at 7:49 PM, sumeet kumar >> wrote: >> >>> I have a collection of points with their coordinates. Each point have >>> certain field ( let say scalar, vector or tensor associated with it). I am >>> currently using delaunchy 3D filter to create a 3D mesh and it works fine. >>> >>> But next what I want is to visualize the data I had on the nodes. How >>> can I achieve this in Paraview. No field data appears on the delaunchy #D >>> generated mesh. >>> >>> Also, when I change my time step, the filter again creates a Delaunchy >>> 3D mesh. Is there any way to tell the algorithm generate the mesh only once >>> and utilize it for other steps. Please note that, the number of nodes and >>> their coordinates are not changing with time. >>> >>> Thanks >>> Sumeet >>> >>> -- >>> >>> Sumeet Kumar Sinha >>> Graduate Student >>> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >>> Website : http://www.sumeetsinha.in/ >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> >> >> -- >> Cory Quammen >> R&D Engineer >> Kitware, Inc. >> > > > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 30527 bytes Desc: not available URL: From cory.quammen at kitware.com Wed Jul 27 10:54:44 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 27 Jul 2016 10:54:44 -0400 Subject: [Paraview-developers] time-dependent output in programmable source In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F68436698D2@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F68436698D2@MBX211.d.ethz.ch> Message-ID: Hi Jean, Responses inlined below: On Wed, Jul 27, 2016 at 5:41 AM, Favre Jean wrote: > hi there > > I have a time-dependent python programmable source. Once run, the Information view tab shows the two-column output with indices and values. The first problem I see, is that I give exact values, and the GUI gives me floating point values that are not exact: for example: > > timesteps = (0.,0.05, 0.1, 0.15, 0.2, 0.25, 0.3, 0.35) > outInfo.Remove(executive.TIME_STEPS()) > > for timestep in timesteps: > outInfo.Append(executive.TIME_STEPS(), timestep) > > outInfo.Remove(executive.TIME_RANGE()) > outInfo.Append(executive.TIME_RANGE(), timesteps[0]) > outInfo.Append(executive.TIME_RANGE(), timesteps[-1]) > > and the GUI shows the following Values: > > 0 > 0.05000 > 0.010000...1 > 0.149999999 > 0.200000...1 > 0.25 > 0.29999999 > 0.34999999 > > the next problem is the VCR Controls; if I mouse-over the Last Frame button, it correctly shows "0.35", but the Time display shows "0.349999". That's annoying. Yep, that's annoying. You can change the displayed precision following TJ's blog post: https://blog.kitware.com/change-the-animation-clock-precision-in-paraview/ This is in the version of ParaView that Utkarsh just tagged. > the real problem is that using the Play button, the executive does not iterate through the timesteps values I have advertized, but rather, it iterates through the following values: > > ts = 0.0388888888889 > ts = 0.0777777777778 > ts = 0.116666666667 > ts = 0.155555555556 > ts = 0.194444444444 > ts = 0.233333333333 > ts = 0.272222222222 > ts = 0.311111111111 > ts = 0.35 > > My understanding is that the VCR controls uses a fixed number of timesteps, and does an interpolation from the minimum time value to the maximum time values. > > Indeed, if I now augment the number of timestes my programmable source is capable of producing, for example: > > timesteps = (0.,0.05, 0.1, 0.15, 0.2, 0.25, 0.3, 0.35, 0.4, 0.45, 0.5, 0.55) > for timestep in timesteps: > outInfo.Append(executive.TIME_STEPS(), timestep) > > When using the Play button of the VCR controls, it requests the following times: > ts = 0.0611111111111 > ts = 0.122222222222 > ts = 0.183333333333 > ts = 0.244444444444 > ts = 0.305555555556 > ts = 0.366666666667 > ts = 0.427777777778 > ts = 0.488888888889 > ts = 0.55 > > so, it seems like it always produces 9 timestep requests, instead of what the reader advertizes. Playing with a different set of timesteps values, it seems like the VCR always calculates (maxTime - minTime)/(10-1) for the time increment. > > I don't feel like this should be the accepted behaviour for the VCR controls. Am I missing some python code? I have followed Chapter 13 of the User Guide. > > I have attached the full python code. This is version 5.1.2. When I use your Programmable Source python code in the UI, everything seems to work as expected. I can even change the list of timesteps in the RequestInformation script and things update as expected. So I think your Programmable Source code is fine. When I run your full servermanager python through the python console, I don't see any time step information in the UI. If I make a small, inconsequential change to the RequestInformation script and click Apply, all the timestep info appears. So something is not being defined correctly. I'm not sure what's happening. I suspect a problem in updating StringVectorProperties, but can't be sure. Cory > > Jean/CSCS > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen R&D Engineer Kitware, Inc. From jfavre at cscs.ch Wed Jul 27 11:12:20 2016 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 27 Jul 2016 15:12:20 +0000 Subject: [Paraview-developers] time-dependent output in programmable source In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F68436698D2@MBX211.d.ethz.ch>, Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684366AEA2@MBX211.d.ethz.ch> Thanks Cory the first tip was useful. and the second tip too. Indeed, if I cut-&-paste my RequestInformation code and my RequestData code directly into an empty ProgrammableSource object, my production code (similar to the small demonstrator I provided) works fine. There is something wrong in loading a full session through the python console as you have clearly confirmed. Sometimes though (actually often), a simple tweak is not enough. Yes, all the timestep info appears. But then it crashes on 'Play". Can you open a bug using the demonstrator I provided? ----------------- Jean From utkarsh.ayachit at kitware.com Wed Jul 27 11:24:42 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Jul 2016 11:24:42 -0400 Subject: [Paraview-developers] time-dependent output in programmable source In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F68436698D2@MBX211.d.ethz.ch> Message-ID: > You can change the displayed precision following TJ's blog post: > https://blog.kitware.com/change-the-animation-clock-precision-in-paraview/ > This is in the version of ParaView that Utkarsh just tagged. No, it's not :). 5.1.2 only includes fixes for the specific issues listed in the tag announcement. From cory.quammen at kitware.com Wed Jul 27 11:28:44 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 27 Jul 2016 11:28:44 -0400 Subject: [Paraview-developers] time-dependent output in programmable source In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F68436698D2@MBX211.d.ethz.ch> Message-ID: On Wed, Jul 27, 2016 at 11:24 AM, Utkarsh Ayachit wrote: >> You can change the displayed precision following TJ's blog post: >> https://blog.kitware.com/change-the-animation-clock-precision-in-paraview/ >> This is in the version of ParaView that Utkarsh just tagged. > > No, it's not :). 5.1.2 only includes fixes for the specific issues > listed in the tag announcement. Oops, nevermind. It's in master and will be in 5.2. -- Cory Quammen R&D Engineer Kitware, Inc. From sumeet.kumar507 at gmail.com Wed Jul 27 11:51:54 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Wed, 27 Jul 2016 08:51:54 -0700 Subject: [Paraview-developers] Visualization field data on Gauss Points Message-ID: I have a unstructured mesh with different types of elements like (quads, hexahedrons, tets etc). I have also gauss points associated with these elements and there are field data ( like stress, strain ) associated with gauss points only while displacements, velocity are associated with nodes. The nodal data can be easily be visualized and interpolated in para-view. Is there any way in paraview, to visualize data located at gauss points and interpolate it accordingly within the element and over nearby connected elements? I have the with me the location of all gauss points, the entire unstructured mesh (comprising of nodes and element). I also have the information about collection of gauss points belonging to the element. Best Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Wed Jul 27 11:54:12 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Wed, 27 Jul 2016 08:54:12 -0700 Subject: [Paraview-developers] Visualization field data on Gauss Points In-Reply-To: References: Message-ID: Adding to the above, Since I do not had a solution for this. What am I currently doing is generating a Delaunchy3D mesh from the gauss points and then visualizing the field data in paraview. Thanks Sumeet On Wed, Jul 27, 2016 at 8:51 AM, sumeet kumar wrote: > I have a unstructured mesh with different types of elements like (quads, > hexahedrons, tets etc). I have also gauss points associated with these > elements and there are field data ( like stress, strain ) associated with > gauss points only while displacements, velocity are associated with nodes. > The nodal data can be easily be visualized and interpolated in para-view. > > Is there any way in paraview, to visualize data located at gauss points > and interpolate it accordingly within the element and over nearby connected > elements? > > I have the with me the location of all gauss points, the entire > unstructured mesh (comprising of nodes and element). I also have the > information about collection of gauss points belonging to the element. > > Best > Sumeet > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Jul 27 12:55:24 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 27 Jul 2016 16:55:24 +0000 Subject: [Paraview-developers] Adding menu items without compile Message-ID: Is it possible to add menu items to ParaView, without having to recompile? An example would be if I want to add a Sandia custom .pdf to the Help menu? If not, would this be a useful feature to add, and how hard would it be? Thanks team, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Jul 27 13:36:48 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 27 Jul 2016 13:36:48 -0400 Subject: [Paraview-developers] Adding menu items without compile In-Reply-To: References: Message-ID: It's not currently possible, we can certainly add support for it. On Wed, Jul 27, 2016 at 12:55 PM, Scott, W Alan wrote: > Is it possible to add menu items to ParaView, without having to recompile? > An example would be if I want to add a Sandia custom .pdf to the Help menu? > If not, would this be a useful feature to add, and how hard would it be? > > > > Thanks team, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From wascott at sandia.gov Wed Jul 27 16:09:45 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 27 Jul 2016 20:09:45 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Bad superbuild In-Reply-To: References: Message-ID: <44d03dc0c3a948f581160243bbc6a0aa@ES01AMSNLNT.srn.sandia.gov> 5.1.2 and Superbuilds Worked like a charm after following Chuck and Utkarsh?s advice. Thanks team! From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Monday, July 25, 2016 7:44 PM To: Chuck Atkins Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] [EXTERNAL] Re: Bad superbuild Mind taking a look at the Wiki, under Build and Install? The section on ParaView Settings is confusing. Further, the flags for the MPI_*_COMPILER are a actually different thatn you have here. http://www.paraview.org/Wiki/ParaView:Build_And_Install#ParaView_Settings Thanks, alan From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Monday, July 25, 2016 7:35 PM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview-developers] Bad superbuild Yes, that's generally the most reliable way to get the correct and complete MPI support. I suspect the FindMPI module was getting half-baked information from the wrappers and augmenting with the specified MPI_INCLUDE_PATH. If you don't want it in the environment then I would try explicitly setting the compiler wrappers and nothing else with: -DMPI_C_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicc -DMPI_CXX_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx and drop any other MPI_FOO vars, leaving the FindMPI module interrogate the wrappers to populate the rest. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 9:24 PM, Scott, W Alan > wrote: So, let me ask this. Should I not point at MPI at all through CMake vars, but just point the PATH including the MPI compiler? Alan From: Chuck Atkins [mailto:chuck.atkins at kitware.com] Sent: Monday, July 25, 2016 7:20 PM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Bad superbuild Hi Alan, The FindMPI module can be sensitive to an enormous number of settings. Do you have openmpi loaded as an environment module? If so, I would get rid of any -DMPI_FOO variables from the CMake configure line and just let the FindMPI.cmake module do it's thing. If the MPI compiler wrappers are in your PATH then it should be able to interrogate them correctly. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. (518) 881-1183 On Mon, Jul 25, 2016 at 2:58 PM, Scott, W Alan > wrote: I am trying to build clusters (again) with the superbuild. This is Linux, master. I am using the gnu compiler and openmpi for gnu. I am having issues with MPI. I am trying to use a system installed MPI. Here is what I am sending to cmake: cMakeVars = -DCMAKE_INSTALL_PREFIX:PATH=/projects/viz/paraview/ParaView/5.1.1-sb-mesa/Linux-chama-x86_64 -DBUILD_TESTING:BOOL=OFF -DCMAKE_BUILD_TYPE:STRING=Debug -DParaView_FROM_GIT:BOOL=OFF -DParaView_FROM_SOURCE_DIR:BOOL=ON -DPARAVIEW_SOURCE_DIR:PATH=/projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5 -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_paraview:BOOL=ON -DENABLE_ffmpeg:BOOL=ON -DENABLE_python:BOOL=ON -DENABLE_numpy:BOOL=ON -DENABLE_png:BOOL=ON -DENABLE_osmesa:BOOL=ON -DENABLE_cgns:BOOL=ON -DENABLE_silo:BOOL=ON -DENABLE_visitbridge:BOOL=ON -DMPI_COMPILER:FILEPATH=/opt/openmpi-1.8-gnu//bin/mpicxx -DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON -DENABLE_mpi:BOOL=ON -DPARAVIEW_USE_MPI:BOOL=ON -DMPI_INCLUDE_PATH:PATH=/opt/openmpi-1.8-gnu//include/ If anyone needs my CMakeCache.txt, please ask and I can send it off list. Here is my failure: [ 4%] Building C object VTK/ThirdParty/tiff/vtktiff/CMakeFiles/vtktiff.dir/tif_thunder.c.o CMakeFiles/IceTMPI.dir/mpi.c.o: In function `getMPIRequest': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:110: undefined reference to `ompi_request_null' /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:116: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `create_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:160: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `destroy_request': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:168: undefined reference to `ompi_request_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `icetCreateMPICommunicator': /projects/viz/paraview/src/ParaView/5.1.1-sb/ParaView5/ThirdParty/IceT/vtkicet/src/communication/mpi.c:200: undefined reference to `ompi_mpi_comm_null' CMakeFiles/IceTMPI.dir/mpi.c.o: In function `MPISubset': Thanks all! Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Jul 28 10:55:40 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Jul 2016 10:55:40 -0400 Subject: [Paraview-developers] ANN: ParaView 5.1.2 available for download Message-ID: Folks, ParaView 5.1.2 is now available for download [1]. Please refer to the release notes on the Kitware blog [2]. As always, we look forward to your feedback [3]. Also stay tuned to the Kitware Blog [4] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more! - ParaView Team [1] http://www.paraview.org/download/ [2] https://blog.kitware.com/paraview-5-1-2-release-notes/ [3] http://paraview.uservoice.com [4] https://blog.kitware.com/tag/ParaView/ From utkarsh.ayachit at kitware.com Thu Jul 28 13:09:15 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Jul 2016 13:09:15 -0400 Subject: [Paraview-developers] [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for download In-Reply-To: References: Message-ID: Can you confirm that your ParaView superbuild has this commit (https://gitlab.kitware.com/paraview/paraview-superbuild/commit/bf831e2e2b4c3a6a764c63f65759884eb287b3f6)? On Thu, Jul 28, 2016 at 12:51 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > There still seems to be something misconfigured deep down in the > Superbuild configuration files. We saw this in the 5.1.0 build as well. > The install directory has install/lib/paraview-5.0 rather than > install/lib/paraview-5.1. I downloaded clean Superbuild source directory > before this build ?.. > > > -- Installing: /home/angel/PV/5.1.2/Build/install/bin/paraview > -- Installing: > /home/angel/PV/5.1.2/Build/install/share/applications/paraview.desktop > -- Installing: > /home/angel/PV/5.1.2/Build/install/share/icons/hicolor/22x22/apps/paraview. > png > -- Installing: > /home/angel/PV/5.1.2/Build/install/share/icons/hicolor/32x32/apps/paraview. > png > -- Installing: > /home/angel/PV/5.1.2/Build/install/share/icons/hicolor/96x96/apps/paraview. > png > -- Installing: > /home/angel/PV/5.1.2/Build/install/share/appdata/paraview.appdata.xml > [100%] Completed 'paraview' > [100%] Built target paraview > Install the project... > -- Install configuration: "Release" > CMake Error at cmake_install.cmake:36 (file): > file INSTALL cannot find > "/home/angel/PV/5.1.2/Build/install/lib/paraview-5.1". > > > make: *** [install] Error 1 > > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: ParaView on behalf of Utkarsh > Ayachit > Date: Thursday, July 28, 2016 at 10:55 AM > To: ParaView , ParaView Developers > > Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for > download > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm the authenticity of all links > contained within the message prior to copying and pasting the address to a > Web browser. > > > > > ---- > > Folks, > > ParaView 5.1.2 is now available for download [1]. Please refer to the > release notes on the Kitware blog [2]. As always, we look forward to > your feedback [3]. > > Also stay tuned to the Kitware Blog [4] for upcoming features and > enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much > more! > > - ParaView Team > > [1] Caution-http://www.paraview.org/download/ > [2] Caution-https://blog.kitware.com/paraview-5-1-2-release-notes/ > [3] Caution-http://paraview.uservoice.com > [4] Caution-https://blog.kitware.com/tag/ParaView/ > _______________________________________________ > Powered by Caution-www.kitware.com > > Visit other Kitware open-source projects at > Caution-http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > Caution-http://paraview.org/Wiki/ParaView > > Search the list archives at: Caution-http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > Caution-http://public.kitware.com/mailman/listinfo/paraview From wascott at sandia.gov Thu Jul 28 13:09:33 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 28 Jul 2016 17:09:33 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for download In-Reply-To: References: Message-ID: Strange. I built with Superbuild yesterday, and used install, and here is what I get for the libraries: /.../lib/paraview-5.1 Note that my build is behind a firewall, thus I have to hand copy everything manually. Could this be the difference? Alan -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) Sent: Thursday, July 28, 2016 10:51 AM To: Utkarsh Ayachit ; ParaView ; ParaView Developers Subject: [EXTERNAL] Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for download There still seems to be something misconfigured deep down in the Superbuild configuration files. We saw this in the 5.1.0 build as well. The install directory has install/lib/paraview-5.0 rather than install/lib/paraview-5.1. I downloaded clean Superbuild source directory before this build ?.. -- Installing: /home/angel/PV/5.1.2/Build/install/bin/paraview -- Installing: /home/angel/PV/5.1.2/Build/install/share/applications/paraview.desktop -- Installing: /home/angel/PV/5.1.2/Build/install/share/icons/hicolor/22x22/apps/paraview. png -- Installing: /home/angel/PV/5.1.2/Build/install/share/icons/hicolor/32x32/apps/paraview. png -- Installing: /home/angel/PV/5.1.2/Build/install/share/icons/hicolor/96x96/apps/paraview. png -- Installing: /home/angel/PV/5.1.2/Build/install/share/appdata/paraview.appdata.xml [100%] Completed 'paraview' [100%] Built target paraview Install the project... -- Install configuration: "Release" CMake Error at cmake_install.cmake:36 (file): file INSTALL cannot find "/home/angel/PV/5.1.2/Build/install/lib/paraview-5.1". make: *** [install] Error 1 ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: ParaView on behalf of Utkarsh Ayachit Date: Thursday, July 28, 2016 at 10:55 AM To: ParaView , ParaView Developers Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for download All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- Folks, ParaView 5.1.2 is now available for download [1]. Please refer to the release notes on the Kitware blog [2]. As always, we look forward to your feedback [3]. Also stay tuned to the Kitware Blog [4] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more! - ParaView Team [1] Caution-http://www.paraview.org/download/ [2] Caution-https://blog.kitware.com/paraview-5-1-2-release-notes/ [3] Caution-http://paraview.uservoice.com [4] Caution-https://blog.kitware.com/tag/ParaView/ _______________________________________________ Powered by Caution-www.kitware.com Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView Search the list archives at: Caution-http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: Caution-http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Jul 28 13:57:39 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Jul 2016 13:57:39 -0400 Subject: [Paraview-developers] [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for download In-Reply-To: References: Message-ID: Not sure, but I cannot reproduce the issue. Can you do this: > mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1 ensure that the directory is created and then try again. I wonder if that directory is not being created for some reason. On Thu, Jul 28, 2016 at 1:18 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Yes, the changes to both of those files are in place. > > Here?s what I ran prior to the build: > > git clone http://paraview.org/ParaViewSuperbuild.git > cd ParaViewSuperbuild > git checkout v5.1.2 > > > > I then ran cmake using cmake-3.5.2 > > I can see that the build is using the 5.1.2 tar ball > > [ 97%] Performing download step (download, verify and extract) for > 'paraview' > -- verifying file... > file='/home/angel/PV/5.1.2/Downloads/ParaView-v5.1.2.tar.gz' > -- verifying file... done > -- extracting... > src='/home/angel/PV/5.1.2/Downloads/ParaView-v5.1.2.tar.gz' > dst='/home/angel/PV/5.1.2/Build/paraview/src/paraview' > -- extracting... [tar xfz] > -- extracting... [analysis] > -- extracting... [rename] > -- extracting... [clean up] > -- extracting... done > > > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Utkarsh Ayachit > Date: Thursday, July 28, 2016 at 1:09 PM > To: Rick Angelini > Cc: ParaView , ParaView Developers > > Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for > download > > Can you confirm that your ParaView superbuild has this commit > (https://gitlab.kitware.com/paraview/paraview-superbuild/commit/bf831e2e2b4 > c3a6a764c63f65759884eb287b3f6)? > > On Thu, Jul 28, 2016 at 12:51 PM, Angelini, Richard C (Rick) CIV > USARMY RDECOM ARL (US) wrote: >> There still seems to be something misconfigured deep down in the >> Superbuild configuration files. We saw this in the 5.1.0 build as >>well. >> The install directory has install/lib/paraview-5.0 rather than >> install/lib/paraview-5.1. I downloaded clean Superbuild source >>directory >> before this build ?.. >> >> >> -- Installing: /home/angel/PV/5.1.2/Build/install/bin/paraview >> -- Installing: >> /home/angel/PV/5.1.2/Build/install/share/applications/paraview.desktop >> -- Installing: >> >>/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/22x22/apps/paraview >>. >> png >> -- Installing: >> >>/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/32x32/apps/paraview >>. >> png >> -- Installing: >> >>/home/angel/PV/5.1.2/Build/install/share/icons/hicolor/96x96/apps/paraview >>. >> png >> -- Installing: >> /home/angel/PV/5.1.2/Build/install/share/appdata/paraview.appdata.xml >> [100%] Completed 'paraview' >> [100%] Built target paraview >> Install the project... >> -- Install configuration: "Release" >> CMake Error at cmake_install.cmake:36 (file): >> file INSTALL cannot find >> "/home/angel/PV/5.1.2/Build/install/lib/paraview-5.1". >> >> >> make: *** [install] Error 1 >> >> >> ________________________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> >> -----Original Message----- >> From: ParaView on behalf of Utkarsh >> Ayachit >> Date: Thursday, July 28, 2016 at 10:55 AM >> To: ParaView , ParaView Developers >> >> Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for >> download >> >> All active links contained in this email were disabled. Please verify >>the >> identity of the sender, and confirm the authenticity of all links >> contained within the message prior to copying and pasting the address to >>a >> Web browser. >> >> >> >> >> ---- >> >> Folks, >> >> ParaView 5.1.2 is now available for download [1]. Please refer to the >> release notes on the Kitware blog [2]. As always, we look forward to >> your feedback [3]. >> >> Also stay tuned to the Kitware Blog [4] for upcoming features and >> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much >> more! >> >> - ParaView Team >> >> [1] Caution-http://www.paraview.org/download/ >> [2] Caution-https://blog.kitware.com/paraview-5-1-2-release-notes/ >> [3] Caution-http://paraview.uservoice.com >> [4] Caution-https://blog.kitware.com/tag/ParaView/ >> _______________________________________________ >> Powered by Caution-www.kitware.com >> >> Visit other Kitware open-source projects at >> Caution-http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> Caution-http://paraview.org/Wiki/ParaView >> >> Search the list archives at: >>Caution-http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> Caution-http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Jul 28 14:09:27 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Jul 2016 14:09:27 -0400 Subject: [Paraview-developers] [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for download In-Reply-To: References: Message-ID: You are doing a clean build, right? In an empty directory and not just "make clean". Utkarsh On Thu, Jul 28, 2016 at 2:06 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > OK - but it is creating lib/paraview-5.0 which I believe is a mistake of > some sort ?.. > > I can?t believe that it?s anything in my CMAKE command: > > cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \ > -Ddownload_location=`pwd`/../Downloads \ > -DParaView_FROM_GIT=OFF \ > -DParaView_URL=`pwd`/../Downloads/ParaView-v${version}.tar.gz \ > -DCMAKE_BUILD_TYPE=Release \ > -DENABLE_visitbridge:BOOL=ON \ > -DENABLE_cgns=ON \ > -DENABLE_boost=ON \ > -DENABLE_ffmpeg=ON \ > -DENABLE_hdf5=ON \ > -DENABLE_matplotlib=ON \ > -DENABLE_mesa=OFF \ > -DENABLE_mpi=ON \ > -DENABLE_numpy=ON \ > -DENABLE_paraview=ON \ > -DENABLE_python=ON \ > -DENABLE_qt4=ON \ > -DENABLE_silo=ON \ > -DENABLE_szip=ON \ > -Dqt_DISABLE_WEBKIT=OFF \ > -DUSE_NONFREE_COMPONENTS=OFF \ > -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \ > -DUSE_SYSTEM_mpi=OFF ../ParaViewSuperbuild > > make -j 8 install > > > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Utkarsh Ayachit > Date: Thursday, July 28, 2016 at 1:57 PM > To: Rick Angelini > Cc: ParaView , ParaView Developers > > Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for > download > > mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1 From wascott at sandia.gov Thu Jul 28 14:59:17 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 28 Jul 2016 18:59:17 +0000 Subject: [Paraview-developers] Bad Linux 5.1.2 download Message-ID: <3af7fadfd3c844369a7db9b4b010d518@ES01AMSNLNT.srn.sandia.gov> Utkarsh, I believe we have a bad 5.1.2 Linux download. ceerws2213:bin$ ./paraview /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVClientServerCoreCore-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkParallelCore-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOCore-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingCore-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkCommonDataModel-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVServerManagerRendering-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVVTKExtensionsDefault-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersParallelFlowPaths-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersFlowPaths-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOImport-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOParallel-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOExodus-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libembree.so.2) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.17' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libospray.so.0) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkInteractionWidgets-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingAnnotation-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingVolume-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVClientServerCoreDefault-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersParallelDIY2-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOLSDyna-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOVisItBridge-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingParallelLIC-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingContextOpenGL2-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libQtCLucene.so.4) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkmetaio-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkavtdatabase_par-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtklightweight_visit_vtk-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkavtdbatts-pv5.1.so.1) /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libXdmfCore.so) ceerws2213:bin$ ls /usr/lib64/libstdc++.so. libstdc++.so.5@ libstdc++.so.5.0.7* libstdc++.so.6@ libstdc++.so.6.0.13* Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Jul 28 16:17:57 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 28 Jul 2016 20:17:57 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for download In-Reply-To: References: Message-ID: <5c091ea4d7a24ecc87feaebd6540be0a@ES01AMSNLNT.srn.sandia.gov> Rick/All, Here is what I do, which worked. Not sure if it will help, but here it is. I am behind a firewall, and cannot pull from git with SuperBuild. This is on clusters. cMakeVars = cMakeVars +\ '-DCMAKE_INSTALL_PREFIX:PATH='+pvInstallDir+' '+\ '-DBUILD_TESTING:BOOL=OFF '+\ '-DParaView_FROM_GIT:BOOL=OFF '+\ '-DParaView_FROM_SOURCE_DIR:BOOL=ON '+\ '-DPARAVIEW_SOURCE_DIR:PATH='+pvSrcDir+' cMakeVars = cMakeVars +\ '-DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON '+\ '-DENABLE_mpi:BOOL=ON '+\ '-DPARAVIEW_USE_MPI:BOOL=ON '+\ '-DUSE_SYSTEM_mpi:BOOL=ON ' cMakeVars = cMakeVars +\ '-DENABLE_paraview:BOOL=ON '+\ '-DENABLE_ffmpeg:BOOL=ON '+\ '-DENABLE_python:BOOL=ON '+\ '-DENABLE_numpy:BOOL=ON '+\ '-DENABLE_png:BOOL=ON '+\ '-DENABLE_osmesa:BOOL=ON '+\ '-DENABLE_cgns:BOOL=ON '+\ '-DENABLE_silo:BOOL=ON '+\ '-DENABLE_visitbridge:BOOL=ON ' -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) Sent: Thursday, July 28, 2016 2:09 PM To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) ; Utkarsh Ayachit Cc: ParaView Developers ; ParaView Subject: [EXTERNAL] Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for download I made slight change to my build script - turned GIT=OFF to GIT=ON, and I seem to have a clean build???? Changed this: cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/5.1.2 \ -Ddownload_location=`pwd`/../Downloads \ DParaView_FROM_GIT=OFF \ -DParaView_URL=`pwd`/../Downloads/ParaView-v5.1.2.tar.gz \ ? to this: cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \ -Ddownload_location=`pwd`/../Downloads \ DParaView_FROM_GIT=ON \ -DParaView_URL=git://www.paraview.org/files/v5.1/ParaView-v5.1.2.tar.gz \ ?. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: ParaView on behalf of Rick Angelini Date: Thursday, July 28, 2016 at 2:23 PM To: Utkarsh Ayachit Cc: ParaView Developers , ParaView Subject: Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.2 available for download Utkarsh - yes I was building 5.1.2 in a totally clean directory - as I said, I also downloaded clean SuperBuild sources prior to doing the build. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -----Original Message----- From: Utkarsh Ayachit Date: Thursday, July 28, 2016 at 2:09 PM To: Rick Angelini Cc: ParaView , ParaView Developers Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available for download You are doing a clean build, right? In an empty directory and not just "make clean". Utkarsh On Thu, Jul 28, 2016 at 2:06 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > OK - but it is creating lib/paraview-5.0 which I believe is a mistake > of some sort ?.. > > I can?t believe that it?s anything in my CMAKE command: > > cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/angel/pv-test/${version} \ > -Ddownload_location=`pwd`/../Downloads \ -DParaView_FROM_GIT=OFF \ > -DParaView_URL=`pwd`/../Downloads/ParaView-v${version}.tar.gz \ > -DCMAKE_BUILD_TYPE=Release \ -DENABLE_visitbridge:BOOL=ON \ > -DENABLE_cgns=ON \ -DENABLE_boost=ON \ -DENABLE_ffmpeg=ON \ > -DENABLE_hdf5=ON \ -DENABLE_matplotlib=ON \ -DENABLE_mesa=OFF \ > -DENABLE_mpi=ON \ -DENABLE_numpy=ON \ -DENABLE_paraview=ON \ > -DENABLE_python=ON \ -DENABLE_qt4=ON \ -DENABLE_silo=ON \ > -DENABLE_szip=ON \ -Dqt_DISABLE_WEBKIT=OFF \ > -DUSE_NONFREE_COMPONENTS=OFF \ > -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \ -DUSE_SYSTEM_mpi=OFF > ../ParaViewSuperbuild > > make -j 8 install > > > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > -----Original Message----- > From: Utkarsh Ayachit > Date: Thursday, July 28, 2016 at 1:57 PM > To: Rick Angelini > Cc: ParaView , ParaView Developers > > Subject: Re: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.2 available >for download > > mkdir -p /home/angel/PV/5.1.2/Build/install/lib/paraview-5.1 From utkarsh.ayachit at kitware.com Thu Jul 28 20:56:14 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Jul 2016 20:56:14 -0400 Subject: [Paraview-developers] Bad Linux 5.1.2 download In-Reply-To: <3af7fadfd3c844369a7db9b4b010d518@ES01AMSNLNT.srn.sandia.gov> References: <3af7fadfd3c844369a7db9b4b010d518@ES01AMSNLNT.srn.sandia.gov> Message-ID: Looks like we'll need to package the libstdc++ as well. What linux distro/version are you running on? On Thu, Jul 28, 2016 at 2:59 PM, Scott, W Alan wrote: > Utkarsh, > > I believe we have a bad 5.1.2 Linux download. > > > > ceerws2213:bin$ ./paraview > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVClientServerCoreCore-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkParallelCore-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOCore-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingCore-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkCommonDataModel-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVServerManagerRendering-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVVTKExtensionsDefault-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersParallelFlowPaths-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersFlowPaths-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOImport-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOParallel-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOExodus-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libembree.so.2) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.17' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libospray.so.0) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkInteractionWidgets-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingAnnotation-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingVolume-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVClientServerCoreDefault-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersParallelDIY2-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOLSDyna-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOVisItBridge-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingParallelLIC-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingContextOpenGL2-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libQtCLucene.so.4) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkmetaio-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkavtdatabase_par-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtklightweight_visit_vtk-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkavtdbatts-pv5.1.so.1) > > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: > /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by > /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libXdmfCore.so) > > > > > > ceerws2213:bin$ ls /usr/lib64/libstdc++.so. > > libstdc++.so.5@ libstdc++.so.5.0.7* libstdc++.so.6@ > libstdc++.so.6.0.13* > > > > > > Alan > > > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > From utkarsh.ayachit at kitware.com Thu Jul 28 21:17:25 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 28 Jul 2016 21:17:25 -0400 Subject: [Paraview-developers] Bad Linux 5.1.2 download In-Reply-To: References: <3af7fadfd3c844369a7db9b4b010d518@ES01AMSNLNT.srn.sandia.gov> Message-ID: I've uploaded a new version of the binaries that includes libstdc++ as well. Can you give it a try please? On Thu, Jul 28, 2016 at 8:56 PM, Utkarsh Ayachit wrote: > Looks like we'll need to package the libstdc++ as well. What linux > distro/version are you running on? > > On Thu, Jul 28, 2016 at 2:59 PM, Scott, W Alan wrote: >> Utkarsh, >> >> I believe we have a bad 5.1.2 Linux download. >> >> >> >> ceerws2213:bin$ ./paraview >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVClientServerCoreCore-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkParallelCore-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOCore-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingCore-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkCommonDataModel-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVServerManagerRendering-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVVTKExtensionsDefault-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersParallelFlowPaths-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersFlowPaths-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOImport-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOParallel-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOExodus-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libembree.so.2) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.17' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libospray.so.0) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkInteractionWidgets-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingAnnotation-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingVolume-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkPVClientServerCoreDefault-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkFiltersParallelDIY2-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOLSDyna-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkIOVisItBridge-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingParallelLIC-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkRenderingContextOpenGL2-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libQtCLucene.so.4) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkmetaio-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkavtdatabase_par-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtklightweight_visit_vtk-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libvtkavtdbatts-pv5.1.so.1) >> >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by >> /projects/viz/paraview/ParaView/5.1.2-kw/Linux-cee-rhel6-x86_64/lib/paraview-5.1/libXdmfCore.so) >> >> >> >> >> >> ceerws2213:bin$ ls /usr/lib64/libstdc++.so. >> >> libstdc++.so.5@ libstdc++.so.5.0.7* libstdc++.so.6@ >> libstdc++.so.6.0.13* >> >> >> >> >> >> Alan >> >> >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0822 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> --------------------------------------------------------- >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> From wascott at sandia.gov Fri Jul 29 15:39:45 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 29 Jul 2016 19:39:45 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Bad Linux 5.1.2 download In-Reply-To: References: <3af7fadfd3c844369a7db9b4b010d518@ES01AMSNLNT.srn.sandia.gov> Message-ID: <6314f6e55f2e46f6933979735154c0b1@ES01AMSNLNT.srn.sandia.gov> Moving to paraview.org. Utkarsh, Kitware Linux binary download now appears to be good. I am finding libstdc++ correctly. Alan I've uploaded a new version of the binaries that includes libstdc++ as well. Can you give it a try please? On Thu, Jul 28, 2016 at 8:56 PM, Utkarsh Ayachit wrote: > Looks like we'll need to package the libstdc++ as well. What linux > distro/version are you running on? > > On Thu, Jul 28, 2016 at 2:59 PM, Scott, W Alan wrote: >> Utkarsh, >> >> I believe we have a bad 5.1.2 Linux download. >> >> >> >> ceerws2213:bin$ ./paraview >> >> ParaView/lib/paraview-5.1/paraview: >> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found >> (required by >> ParaView/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1) >> From sumeet.kumar507 at gmail.com Sat Jul 30 03:13:23 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Sat, 30 Jul 2016 00:13:23 -0700 Subject: [Paraview-developers] Accessing Delaunay3D filter inside my reader plugin. Message-ID: I am writing a reader plug-in which reads a hdf5 file and creates a unstructured mesh of nodes & elements and also unstructured mesh of only gauss points. The next what I want to do is to take this unstructured mesh of points and generate a Delaunay3D mesh. I can achieve the same in Paraview during rendering (in the GUI phase). But I want to achieve this inside the c++ code automatically. Basically I want to use the unstructured mesh of points to generate the Delaunay3D mesh (vtkUnstructuredGrid) and save it for further exploitation . Best Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Sun Jul 31 13:17:48 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Sun, 31 Jul 2016 22:47:48 +0530 Subject: [Paraview-developers] Accessing Delaunay3D filter inside my reader plugin. In-Reply-To: References: Message-ID: Hi Sumit, Have you explored the examples for Delaunay3D in vtk. The example given here (http://www.vtk.org/Wiki/VTK/Examples/Cxx/Modelling/Delaunay3D) has all the details about how to use this filer inside your C++ code. If you have already seen it then post some more details about your problem. Best wishes, Chiranjib On Sat, Jul 30, 2016 at 12:43 PM, sumeet kumar wrote: > > I am writing a reader plug-in which reads a hdf5 file and creates a > unstructured mesh of nodes & elements and also unstructured mesh of only > gauss points. > The next what I want to do is to take this unstructured mesh of points and > generate a Delaunay3D mesh. > I can achieve the same in Paraview during rendering (in the GUI phase). > But I want to achieve this inside the c++ code automatically. Basically I > want to use the unstructured mesh of points to > generate the Delaunay3D mesh (vtkUnstructuredGrid) and save it for further > exploitation . > > > Best > Sumeet > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Sun Jul 31 13:25:19 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Sun, 31 Jul 2016 10:25:19 -0700 Subject: [Paraview-developers] Accessing Delaunay3D filter inside my reader plugin. In-Reply-To: References: Message-ID: Hi Chiranjib, I already saw this example. This example assumes that I have a* .vtp file . * But actually I have a hdf5 file where I have all the relevant data in my format. With that I create a unstructured mesh of points and now want to use that point data to generate the Delaunay3D mesh. Which means I already have a cloud of points with me in < object. Now I want to use this object to create a Delaunay3D mesh. Basically what I do not understand is how to deal with input connection, output ports etc.. or is there any simple way to deal with this. Sumeet On Sun, Jul 31, 2016 at 10:17 AM, Chiranjib Sur wrote: > Hi Sumit, > Have you explored the examples for Delaunay3D in vtk. The example given > here (http://www.vtk.org/Wiki/VTK/Examples/Cxx/Modelling/Delaunay3D) has > all the details about how to use this filer inside your C++ code. > If you have already seen it then post some more details about your > problem. > > Best wishes, > Chiranjib > > On Sat, Jul 30, 2016 at 12:43 PM, sumeet kumar > wrote: > >> >> I am writing a reader plug-in which reads a hdf5 file and creates a >> unstructured mesh of nodes & elements and also unstructured mesh of only >> gauss points. >> The next what I want to do is to take this unstructured mesh of points >> and generate a Delaunay3D mesh. >> I can achieve the same in Paraview during rendering (in the GUI phase). >> But I want to achieve this inside the c++ code automatically. Basically I >> want to use the unstructured mesh of points to >> generate the Delaunay3D mesh (vtkUnstructuredGrid) and save it for further >> exploitation . >> >> >> Best >> Sumeet >> >> -- >> >> Sumeet Kumar Sinha >> Graduate Student >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> Website : http://www.sumeetsinha.in/ >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Sun Jul 31 13:30:25 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Sun, 31 Jul 2016 23:00:25 +0530 Subject: [Paraview-developers] Accessing Delaunay3D filter inside my reader plugin. In-Reply-To: References: Message-ID: This part of the example describes about the input connection, ports etc // Generate a mesh from the input points. If Alpha is non-zero, then // tetrahedra, triangles, edges and vertices that lie within the // alpha radius are output. vtkSmartPointer delaunay3DAlpha = vtkSmartPointer::New(); delaunay3DAlpha->SetInputConnection (cleaner->GetOutputPort()); delaunay3DAlpha->SetAlpha(0.1); VTK pipeline is the place you need to explore ( http://www.vtk.org/Wiki/VTK/Tutorials/New_Pipeline). Chiranjib On Sun, Jul 31, 2016 at 10:55 PM, sumeet kumar wrote: > Hi Chiranjib, > > I already saw this example. This example assumes that I have a* .vtp file > . * > > But actually I have a hdf5 file where I have all the relevant data in my > format. With that I create a unstructured mesh of > points and now want to use that point data to generate the Delaunay3D mesh. > Which means I already have a cloud of points with me in < > object. Now I want to use this object to create a > Delaunay3D mesh. Basically what I do not understand is how to deal with > input connection, output ports etc.. or is there any simple way to deal > with this. > > > Sumeet > > On Sun, Jul 31, 2016 at 10:17 AM, Chiranjib Sur > wrote: > >> Hi Sumit, >> Have you explored the examples for Delaunay3D in vtk. The example given >> here (http://www.vtk.org/Wiki/VTK/Examples/Cxx/Modelling/Delaunay3D) has >> all the details about how to use this filer inside your C++ code. >> If you have already seen it then post some more details about your >> problem. >> >> Best wishes, >> Chiranjib >> >> On Sat, Jul 30, 2016 at 12:43 PM, sumeet kumar > > wrote: >> >>> >>> I am writing a reader plug-in which reads a hdf5 file and creates a >>> unstructured mesh of nodes & elements and also unstructured mesh of only >>> gauss points. >>> The next what I want to do is to take this unstructured mesh of points >>> and generate a Delaunay3D mesh. >>> I can achieve the same in Paraview during rendering (in the GUI phase). >>> But I want to achieve this inside the c++ code automatically. Basically I >>> want to use the unstructured mesh of points to >>> generate the Delaunay3D mesh (vtkUnstructuredGrid) and save it for further >>> exploitation . >>> >>> >>> Best >>> Sumeet >>> >>> -- >>> >>> Sumeet Kumar Sinha >>> Graduate Student >>> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >>> Website : http://www.sumeetsinha.in/ >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> > > > -- > > Sumeet Kumar Sinha > Graduate Student > Phone: (+1) <%28%2B91%29%209910516219>5306018271 > Website : http://www.sumeetsinha.in/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Sun Jul 31 13:34:35 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Sun, 31 Jul 2016 23:04:35 +0530 Subject: [Paraview-developers] Accessing Delaunay3D filter inside my reader plugin. In-Reply-To: References: Message-ID: This might also be useful for you http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Replacement_of_SetInput Chiranjib On Sun, Jul 31, 2016 at 11:00 PM, Chiranjib Sur wrote: > This part of the example describes about the input connection, ports etc > > // Generate a mesh from the input points. If Alpha is non-zero, then > // tetrahedra, triangles, edges and vertices that lie within the > // alpha radius are output. > vtkSmartPointer delaunay3DAlpha = > vtkSmartPointer::New(); > delaunay3DAlpha->SetInputConnection (cleaner->GetOutputPort()); > delaunay3DAlpha->SetAlpha(0.1); > > > VTK pipeline is the place you need to explore ( > http://www.vtk.org/Wiki/VTK/Tutorials/New_Pipeline). > > Chiranjib > > On Sun, Jul 31, 2016 at 10:55 PM, sumeet kumar > wrote: > >> Hi Chiranjib, >> >> I already saw this example. This example assumes that I have a* .vtp >> file . * >> >> But actually I have a hdf5 file where I have all the relevant data in my >> format. With that I create a unstructured mesh of >> points and now want to use that point data to generate the Delaunay3D mesh. >> Which means I already have a cloud of points with me in < >> object. Now I want to use this object to create a >> Delaunay3D mesh. Basically what I do not understand is how to deal with >> input connection, output ports etc.. or is there any simple way to deal >> with this. >> >> >> Sumeet >> >> On Sun, Jul 31, 2016 at 10:17 AM, Chiranjib Sur >> wrote: >> >>> Hi Sumit, >>> Have you explored the examples for Delaunay3D in vtk. The example given >>> here (http://www.vtk.org/Wiki/VTK/Examples/Cxx/Modelling/Delaunay3D) >>> has all the details about how to use this filer inside your C++ code. >>> If you have already seen it then post some more details about your >>> problem. >>> >>> Best wishes, >>> Chiranjib >>> >>> On Sat, Jul 30, 2016 at 12:43 PM, sumeet kumar < >>> sumeet.kumar507 at gmail.com> wrote: >>> >>>> >>>> I am writing a reader plug-in which reads a hdf5 file and creates a >>>> unstructured mesh of nodes & elements and also unstructured mesh of only >>>> gauss points. >>>> The next what I want to do is to take this unstructured mesh of points >>>> and generate a Delaunay3D mesh. >>>> I can achieve the same in Paraview during rendering (in the GUI phase). >>>> But I want to achieve this inside the c++ code automatically. Basically I >>>> want to use the unstructured mesh of points to >>>> generate the Delaunay3D mesh (vtkUnstructuredGrid) and save it for further >>>> exploitation . >>>> >>>> >>>> Best >>>> Sumeet >>>> >>>> -- >>>> >>>> Sumeet Kumar Sinha >>>> Graduate Student >>>> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >>>> Website : http://www.sumeetsinha.in/ >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Search the list archives at: >>>> http://markmail.org/search/?q=Paraview-developers >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>> >>>> >>> >> >> >> -- >> >> Sumeet Kumar Sinha >> Graduate Student >> Phone: (+1) <%28%2B91%29%209910516219>5306018271 >> Website : http://www.sumeetsinha.in/ >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sumeet.kumar507 at gmail.com Sun Jul 31 17:38:55 2016 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Sun, 31 Jul 2016 14:38:55 -0700 Subject: [Paraview-developers] Visualization field data at Gauss Points Message-ID: I have a unstructured mesh with different types of elements like (quads, hexahedrons, tets etc). I have also gauss points associated with these elements and there are field data ( like stress, strain ) associated with gauss points only while displacements, velocity are associated with nodes. The nodal data can be easily be visualized and interpolated in para-view. Is there any way in paraview, to visualize data located at gauss points and interpolate it accordingly within the element and over nearby connected elements? I have the with me the location of all gauss points, the entire unstructured mesh (comprising of nodes and element). I also have the information about collection of gauss points belonging to the element. Since I do not had a solution for this. What am I currently doing is generating a Delaunchy3D mesh from the gauss points and then visualizing the field data in paraview. Best Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetsinha.in/ -------------- next part -------------- An HTML attachment was scrubbed... URL: