From utkarsh.ayachit at kitware.com Wed Jan 6 13:27:14 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 6 Jan 2016 13:27:14 -0500 Subject: [Paraview-developers] ANN: ParaView 5.0.0-RC4 Tagged! Message-ID: Folks, ParaView 5.0.0-RC4 has been tagged! Git tag name: v5.0.0-RC4 Source tar/zip files are available for download: http://www.paraview.org/download/ Binaries will be available for testing within the next few days. - The ParaView Team From utkarsh.ayachit at kitware.com Fri Jan 8 15:28:57 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 8 Jan 2016 15:28:57 -0500 Subject: [Paraview-developers] ANN: ParaView 5.0.0 Tagged! Message-ID: Folks, ParaView 5.0.0 has been tagged! Git tag name: v5.0.0 Source tar/zip files are available for download: http://www.paraview.org/download/ Binaries will be available for testing within the next few days. - The ParaView Team From aashish.chaudhary at kitware.com Sat Jan 9 11:58:46 2016 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Sat, 9 Jan 2016 11:58:46 -0500 Subject: [Paraview-developers] ANN: ParaView 5.0.0 Tagged! In-Reply-To: References: Message-ID: This is great news Utkarsh and congratulations to the entire ParaView team!! - Aashish On Fri, Jan 8, 2016 at 3:28 PM, Utkarsh Ayachit wrote: > Folks, > > ParaView 5.0.0 has been tagged! > > Git tag name: v5.0.0 > > Source tar/zip files are available for download: > http://www.paraview.org/download/ > > Binaries will be available for testing within the next few days. > > - The ParaView Team > _______________________________________________ > 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 > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Jan 11 09:47:38 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 11 Jan 2016 09:47:38 -0500 Subject: [Paraview-developers] ANN: ParaView 5.0.0 Tagged! In-Reply-To: <5693BEE9.3010403@surfsara.nl> References: <5693BEE9.3010403@surfsara.nl> Message-ID: Paul, The glyph panel not showing updated arrays when input is changed is indeed a bug. I've reported it here [1]. However, the RTData (?) part is expected behavior. When you changed the pipeline, RTData (point data) is no longer available in the output of the GLyph filter but since the color array selection was previous set to it, the menu will still show it with the "(?)" suffix. Once you changed to solid color, it cleaned up all non-existing entries and hence it disappeared. Utkarsh [1] http://www.paraview.org/Bug/view.php?id=15924 On Mon, Jan 11, 2016 at 9:40 AM, Paul Melis wrote: > Hi Utkarsh, > > Congrats, nice new features! > > I'm trying out the "Glyph at cell centers" feature as described in the blog, > using the same pipeline (wavelet -> point to cell data -> glyph). It seems > the Glyph filter does not update its list of Active Attribute Scalars when > its input is changed. More concretely: > > 1. Create a wavelet source, apply > 2. Add a Glyph filter, the Glyph filter's Scalars list shows RTData as point > data (correct). Apply glyph filter > 3. Add a Point Data To Cell Data source to the wavelet, apply > 4. Pick Glyph1, Change input, set to PDtoCD > 5. The Glyph filter stills show RTData as point data, but RTData as cell > data is not available > 6. Select PDtoCD filter and create a new Glyph filter. Its Scalars list will > now show correctly the cell data RTData. > > In addition, after these steps Glyph1 shows "RTData (?)" in the Coloring > list ... which disappears after changing the coloring to Solid Color :) > > Regards, > Paul > > > On 08-01-16 21:28, Utkarsh Ayachit wrote: >> >> Folks, >> >> ParaView 5.0.0 has been tagged! >> >> Git tag name: v5.0.0 >> >> Source tar/zip files are available for download: >> http://www.paraview.org/download/ >> >> Binaries will be available for testing within the next few days. >> >> - The ParaView Team >> _______________________________________________ >> 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 >> > > > -- > > Paul Melis > | Visualization group leader & developer | SURFsara | > | Science Park 140 | 1098 XG Amsterdam | > | T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl | From paul.melis at surfsara.nl Mon Jan 11 09:40:41 2016 From: paul.melis at surfsara.nl (Paul Melis) Date: Mon, 11 Jan 2016 15:40:41 +0100 Subject: [Paraview-developers] ANN: ParaView 5.0.0 Tagged! In-Reply-To: References: Message-ID: <5693BEE9.3010403@surfsara.nl> Hi Utkarsh, Congrats, nice new features! I'm trying out the "Glyph at cell centers" feature as described in the blog, using the same pipeline (wavelet -> point to cell data -> glyph). It seems the Glyph filter does not update its list of Active Attribute Scalars when its input is changed. More concretely: 1. Create a wavelet source, apply 2. Add a Glyph filter, the Glyph filter's Scalars list shows RTData as point data (correct). Apply glyph filter 3. Add a Point Data To Cell Data source to the wavelet, apply 4. Pick Glyph1, Change input, set to PDtoCD 5. The Glyph filter stills show RTData as point data, but RTData as cell data is not available 6. Select PDtoCD filter and create a new Glyph filter. Its Scalars list will now show correctly the cell data RTData. In addition, after these steps Glyph1 shows "RTData (?)" in the Coloring list ... which disappears after changing the coloring to Solid Color :) Regards, Paul On 08-01-16 21:28, Utkarsh Ayachit wrote: > Folks, > > ParaView 5.0.0 has been tagged! > > Git tag name: v5.0.0 > > Source tar/zip files are available for download: > http://www.paraview.org/download/ > > Binaries will be available for testing within the next few days. > > - The ParaView Team > _______________________________________________ > 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 > -- Paul Melis | Visualization group leader & developer | SURFsara | | Science Park 140 | 1098 XG Amsterdam | | T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl | From utkarsh.ayachit at kitware.com Tue Jan 12 11:24:31 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 12 Jan 2016 11:24:31 -0500 Subject: [Paraview-developers] ANN: ParaView 5.0.0 is available for download Message-ID: Folks, ParaView 5.0.0 is now available for download[1]. Checkout 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! And thanks to everyone who voted to make ParaView the "Best HPC Visualization Product or Technology (Readers Choice)" awarded by HPCWire [5]. - The ParaView team [1] http://www.paraview.org/download/ [2] http://www.kitware.com/blog/home/post/1032 [3] http://paraview.uservoice.com [4] http://www.kitware.com/blog/ [5] http://www.hpcwire.com/2015-hpcwire-readers-choice-awards/#ffs-tabbed-113 From paul.melis at surfsara.nl Tue Jan 12 11:57:23 2016 From: paul.melis at surfsara.nl (Paul Melis) Date: Tue, 12 Jan 2016 17:57:23 +0100 Subject: [Paraview-developers] ANN: ParaView 5.0.0 is available for download In-Reply-To: References: Message-ID: <56953073.8020500@surfsara.nl> On 12-01-16 17:24, Utkarsh Ayachit wrote: > Folks, > > ParaView 5.0.0 is now available for download[1]. Checkout the release > notes on the Kitware blog [2]. As always, we look forward to your > feedback [3]. Looks like there is a run-away memory leak when using the pvOSPRay plugin. Simply loading the plugin, closing the default RenderView and adding a pvOSPray view triggers unbound memory consumption without even loading data. This is with the official 5.0.0 Linux 64-bit binaries just downloaded from paraview.org. Paul -- Paul Melis | Visualization group leader & developer | SURFsara | | Science Park 140 | 1098 XG Amsterdam | | T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl | From wascott at sandia.gov Tue Jan 12 22:00:30 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 13 Jan 2016 03:00:30 +0000 Subject: [Paraview-developers] Candy for the ears Message-ID: <43574135eb824a37b384319198889e8a@ES01AMSNLNT.srn.sandia.gov> I had a user come into my office yesterday, and he was extremely complementary with regards to ParaView. He is using PV 4.4.0, and he said that it has been a great, clean workhorse for him. He commented that it is extremely stable, well featured, powerful and getting easier to use. Thought everyone could use the pat on the back. Good work team. Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-H (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Jan 13 10:18:58 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 13 Jan 2016 10:18:58 -0500 Subject: [Paraview-developers] Candy for the ears In-Reply-To: <43574135eb824a37b384319198889e8a@ES01AMSNLNT.srn.sandia.gov> References: <43574135eb824a37b384319198889e8a@ES01AMSNLNT.srn.sandia.gov> Message-ID: Very cool! Thanks for sharing, Alan :). On Tue, Jan 12, 2016 at 10:00 PM, Scott, W Alan wrote: > I had a user come into my office yesterday, and he was extremely > complementary with regards to ParaView. He is using PV 4.4.0, and he said > that it has been a great, clean workhorse for him. He commented that it is > extremely stable, well featured, powerful and getting easier to use. > Thought everyone could use the pat on the back. > > > > Good work team. > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-H > > (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 berk.geveci at kitware.com Wed Jan 13 10:26:25 2016 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 13 Jan 2016 10:26:25 -0500 Subject: [Paraview-developers] Candy for the ears In-Reply-To: <43574135eb824a37b384319198889e8a@ES01AMSNLNT.srn.sandia.gov> References: <43574135eb824a37b384319198889e8a@ES01AMSNLNT.srn.sandia.gov> Message-ID: Thanks for passing this along Alan :-) On Tue, Jan 12, 2016 at 10:00 PM, Scott, W Alan wrote: > I had a user come into my office yesterday, and he was extremely > complementary with regards to ParaView. He is using PV 4.4.0, and he said > that it has been a great, clean workhorse for him. He commented that it is > extremely stable, well featured, powerful and getting easier to use. > Thought everyone could use the pat on the back. > > > > Good work team. > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-H > > (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 michael.hillier at canada.ca Tue Jan 19 16:20:26 2016 From: michael.hillier at canada.ca (Hillier, Michael (NRCan/RNCan)) Date: Tue, 19 Jan 2016 21:20:26 +0000 Subject: [Paraview-developers] How to obtain pqPipelineSource from vtkObject? Message-ID: I am having trouble figuring out how to get a pqPipelineSource from a vtkObject (specifically a vtkPolyData) so that I can view those objects in paraview from my plugin. Here is my code vtkSmartPointer reader = vtkSmartPointer::New(); std::string binary_string; // I get this from a database which stores contents of a binary .vtp file reader->SetInputString(binary_string); reader->ReadFromInputStringOn(); reader->Update(); pqApplicationCore *core = pqApplicationCore::instance(); pqDisplayPolicy *displayPolicy = core->getDisplayPolicy(); pqView *view = pqActiveObjects::instance().activeView(); pqPipelineSource* source = ??? // want to obtain from vtkObject/vtkPolyData somehow (vtkPolyData * pdata = reader->GetOutput()); vtkSMProxy *sourceProxy = source->getProxy(); sourceProxy->UpdateVTKObjects(); displayPolicy->setRepresentationVisibility(source->getOutputPort(0),view,true); Any help much appreciated. Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Jan 21 15:22:58 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 21 Jan 2016 15:22:58 -0500 Subject: [Paraview-developers] Changes to 3D Widget panels in ParaView 5.1 Message-ID: Folks, It's known to many that since ParaView 4.* we've been in the process of deprecating the old panel customization code (pqProxyPanel class hierarchy [1]) and replacing that with customizible property widgets (pqPropertyWidget class hierarchy [2]). While most filters had already moved over to the new framework, the few things that remained the old style were the panels for 3D widgets (pq3DWidget and subclasses [3]). A recent merge [4] finally upgrades the 3D widget panels to be subclasses of pqPropertyWidget, introducing a new class hierarchy: pqInteractivePropertyWidget. The changes needed for ServerManagerConfiguration XML to use the property widgets are documented here [6] and are consistent with mechanisms to customize property widget for others types of properties. If you had a custom 3D widget panel, then that will need to be refactored to be a pqPropertyWidget subclass. Comparing the pq3DWidget subclass with it's pqInteractivePropertyWidget counter part will be a way to get started. If you need any assistance, please don't hesitate to use the mailing list or contact me. After this change, pqProxyPanel hierarchy (or what we often call the old property panels) is ripe to be finally removed entirely. Since folks have been warned about their imminent demise since 4.3.1 (January 2015)[7], unless there's a strong objection, we will continue to work towards removing them entirely for the next release i.e. 5.1. Utkarsh [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqProxyPanel.html [2] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqPropertyWidget.html [3] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpq3DWidget.html [4] https://gitlab.kitware.com/paraview/paraview/merge_requests/547 [5] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqInteractivePropertyWidget.html [6] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/MajorAPIChanges.html [7] http://www.paraview.org/Wiki/ParaView_Release_Notes#Note_to_plugin.2Fcustom_application_developers From utkarsh.ayachit at kitware.com Fri Jan 22 15:39:06 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 22 Jan 2016 15:39:06 -0500 Subject: [Paraview-developers] How to obtain pqPipelineSource from vtkObject? In-Reply-To: <20160119213010.5FD98E3443@public.kitware.com> References: <20160119213010.5FD98E3443@public.kitware.com> Message-ID: Michael, This isn't how things are expected to work in ParaView. I'd suggest instead of creating a vtkXMLPolyDataReader directly in your plugin and setting the binary string on it, create a new vtkPolyDataAlgorithm subclass that in its RequestData() method obtains the vtp file from the database and then sets it on an internal vtkXMLPolyDataReader and then executes it and passes the data out. Now you can create a plugin for this new vtkPolyDataAlgorithm and then available for the application to use/create like other data source proxies like readers or sphere source etc. Utkarsh On Tue, Jan 19, 2016 at 4:20 PM, Hillier, Michael (NRCan/RNCan) wrote: > I am having trouble figuring out how to get a pqPipelineSource from a > vtkObject (specifically a vtkPolyData) so that I can view those objects in > paraview from my plugin. Here is my code > > > > > > vtkSmartPointer reader = > vtkSmartPointer::New(); > > std::string binary_string; // I get this from a database which stores > contents of a binary .vtp file > > reader->SetInputString(binary_string); > > reader->ReadFromInputStringOn(); > > reader->Update(); > > > > pqApplicationCore *core = pqApplicationCore::instance(); > > pqDisplayPolicy *displayPolicy = core->getDisplayPolicy(); > > pqView *view = pqActiveObjects::instance().activeView(); > > > > pqPipelineSource* source = ??? // want to obtain from vtkObject/vtkPolyData > somehow (vtkPolyData * pdata = reader->GetOutput()); > > vtkSMProxy *sourceProxy = source->getProxy(); > > sourceProxy->UpdateVTKObjects(); > > displayPolicy->setRepresentationVisibility(source->getOutputPort(0),view,true); > > > > > > Any help much appreciated. > > > > Michael > > > _______________________________________________ > 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 michael.hillier at canada.ca Fri Jan 22 18:07:54 2016 From: michael.hillier at canada.ca (Hillier, Michael (NRCan/RNCan)) Date: Fri, 22 Jan 2016 23:07:54 +0000 Subject: [Paraview-developers] How to obtain pqPipelineSource from vtkObject? In-Reply-To: References: <20160119213010.5FD98E3443@public.kitware.com> Message-ID: Hi Utkarsh, Thanks for your reply. I am not too surprised that how I was implementing was not how things are expected. I did manage to get what I had to work via another mechanism: vtkSMProxyManager *proxyManager = vtkSMProxyManager::GetProxyManager(); vtkSMSessionProxyManager *sessionProxyManager = proxyManager->GetActiveSessionProxyManager(); // Create a vtkTrivalProducer and set its output to be the poly data vtkSmartPointer producer; producer.TakeReference(vtkSMSourceProxy::SafeDownCast(sessionProxyManager->NewProxy("sources","PVTrivialProducer"))); vtkNew Controller; Controller->PreInitializeProxy(producer); vtkObjectBase *clientSideObject = producer->GetClientSideObject(); vtkPVTrivialProducer *realProducer = vtkPVTrivialProducer::SafeDownCast(clientSideObject); realProducer->SetOutput(pdata); Controller->PostInitializeProxy(producer); Controller->RegisterPipelineProxy(producer,"test_pipe"); producer->UpdateVTKObjects(); Would creating a subclass of vtkPolyDataAlgorithm simply this? Would it make it more efficient? I try to re implement this way so that I do things the right way. Thanks Michael -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Friday, January 22, 2016 3:39 PM To: Hillier, Michael (NRCan/RNCan) Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] How to obtain pqPipelineSource from vtkObject? Michael, This isn't how things are expected to work in ParaView. I'd suggest instead of creating a vtkXMLPolyDataReader directly in your plugin and setting the binary string on it, create a new vtkPolyDataAlgorithm subclass that in its RequestData() method obtains the vtp file from the database and then sets it on an internal vtkXMLPolyDataReader and then executes it and passes the data out. Now you can create a plugin for this new vtkPolyDataAlgorithm and then available for the application to use/create like other data source proxies like readers or sphere source etc. Utkarsh On Tue, Jan 19, 2016 at 4:20 PM, Hillier, Michael (NRCan/RNCan) wrote: > I am having trouble figuring out how to get a pqPipelineSource from a > vtkObject (specifically a vtkPolyData) so that I can view those > objects in paraview from my plugin. Here is my code > > > > > > vtkSmartPointer reader = > vtkSmartPointer::New(); > > std::string binary_string; // I get this from a database which stores > contents of a binary .vtp file > > reader->SetInputString(binary_string); > > reader->ReadFromInputStringOn(); > > reader->Update(); > > > > pqApplicationCore *core = pqApplicationCore::instance(); > > pqDisplayPolicy *displayPolicy = core->getDisplayPolicy(); > > pqView *view = pqActiveObjects::instance().activeView(); > > > > pqPipelineSource* source = ??? // want to obtain from > vtkObject/vtkPolyData somehow (vtkPolyData * pdata = > reader->GetOutput()); > > vtkSMProxy *sourceProxy = source->getProxy(); > > sourceProxy->UpdateVTKObjects(); > > displayPolicy->setRepresentationVisibility(source->getOutputPort(0),vi > displayPolicy->ew,true); > > > > > > Any help much appreciated. > > > > Michael > > > _______________________________________________ > 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 carson at tacc.utexas.edu Wed Jan 27 14:59:45 2016 From: carson at tacc.utexas.edu (Carson Brownlee) Date: Wed, 27 Jan 2016 19:59:45 +0000 Subject: [Paraview-developers] ANN: ParaView 5.0.0 is available for download Message-ID: <65403225-B719-432B-BB78-F708B8B4027A@tacc.utexas.edu> hi Paul, Dave DeMarle requested that I help with any pvOSPRay related questions. My name is Carson Brownlee, one of the authors of pvOSPRay. Thank you for the feedback on this. I can verify the memory leak in the binaries. This is not present (or at least fairly minor) in the github repo. If you have the time, building from the official github source here, http://tacc.github.io/pvOSPRay/getting_pvospray.html should reduce memory significantly. We will be working with Kitware to make sure that this gets updated in future releases. Carson On 12-01-16 17:24, Utkarsh Ayachit wrote: > Folks, > > ParaView 5.0.0 is now available for download[1]. Checkout the release > notes on the Kitware blog [2]. As always, we look forward to your > feedback [3]. Looks like there is a run-away memory leak when using the pvOSPRay plugin. Simply loading the plugin, closing the default RenderView and adding a pvOSPray view triggers unbound memory consumption without even loading data. This is with the official 5.0.0 Linux 64-bit binaries just downloaded from paraview.org. Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.melis at surfsara.nl Fri Jan 29 03:19:50 2016 From: paul.melis at surfsara.nl (Paul Melis) Date: Fri, 29 Jan 2016 09:19:50 +0100 Subject: [Paraview-developers] ANN: ParaView 5.0.0 is available for download In-Reply-To: <65403225-B719-432B-BB78-F708B8B4027A@tacc.utexas.edu> References: <65403225-B719-432B-BB78-F708B8B4027A@tacc.utexas.edu> Message-ID: <56AB20A6.70004@surfsara.nl> Hi Carson, Thanks for the update! I'll check back on pvOspray then when new binaries are done (don't have the time available to build from source right now). Regards, Paul On 27-01-16 20:59, Carson Brownlee wrote: > hi Paul, > > Dave DeMarle requested that I help with any pvOSPRay related questions. My name is Carson Brownlee, one of the authors of pvOSPRay. Thank you for the feedback on this. > > I can verify the memory leak in the binaries. This is not present (or at least fairly minor) in the github repo. If you have the time, building from the official github source here,http://tacc.github.io/pvOSPRay/getting_pvospray.html should reduce memory significantly. We will be working with Kitware to make sure that this gets updated in future releases. > > Carson > > > On 12-01-16 17:24, Utkarsh Ayachit wrote: >>/Folks, />//>/ParaView 5.0.0 is now available for download[1]. Checkout the release />/notes on the Kitware blog [2]. As always, we look forward to your />/feedback [3]. / > Looks like there is a run-away memory leak when using the pvOSPRay > plugin. Simply loading the plugin, closing the default RenderView and > adding a pvOSPray view triggers unbound memory consumption without even > loading data. > > This is with the official 5.0.0 Linux 64-bit binaries just downloaded > fromparaview.org . > > Paul > > -- Paul Melis | Visualization group leader & developer | SURFsara | | Science Park 140 | 1098 XG Amsterdam | | T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl | From cory.quammen at kitware.com Fri Jan 29 14:37:54 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 29 Jan 2016 14:37:54 -0500 Subject: [Paraview-developers] http support disabled on midas3.kitware.com Message-ID: Hi folks, The server that hosts ParaView data -- midas3.kitware.com now only supports https, and does not support downloading via the http protocol. This may result in build errors when the test data is being downloaded. To address this error, the CMake client you used to configure ParaView needs OpenSSL support. Newer binaries from cmake.org have this support. When building from source, this is not enabled by default -- enable the configuration option CMAKE_USE_OPENSSL. Cory -- Cory Quammen R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: